Messages in this thread | ![/](/images/icornerl.gif) | | Date | Thu, 21 Mar 1996 00:05:14 -0600 | From | vergil <> | Subject | MCD as module problems - longish |
| |
For those of you who wonder, yes there are still idiots out there using a single speed Mitsumi LU005S.
I went modular on 1.3.76 and got kerneld (from modutiles 1.3.57) working with it. For the most part it works great except with my mitsumi. After a few mounts/unmounts or audio CD inits, the driver will fail to initialize.
the EIP from the "panic" EIP: 0010:[<00128cc0>] points to something in this (from /System.map) 00128ac0 T sys_mount
After rebooting I tried loading the module by hand and it failed to init. The first time it just failed. The second time it said it couldn't get block-major-23, so I am assuming the first instance/failure doesn't release the resource.
Only a cold-boot WITH a tray open/close (while the system is in memory test usually) will work to get the drive working again.
When I have the MCD "hard linked" into the kernel there is about a 1 in 50 chance that the init will fail, but it is much better behaved, and simply says "/dev/mcd is not a block device". Coincidentally, I had a similar problem when I ran OS/2 2.x, so this is quite possibly a hardware bug. If it makes any difference (and I wouldn't know :)) I am using the interface card that came with the drive.
At any rate, the mitsumi is going back into the kernel, and I'll play with the source and see if there's anything I might be able to find, but I'm no expert. Email me if you have a similar problem, a solution, a patch or a flame :) Thanks!
Christopher Wall <vergil@idir.net>
| ![\](/images/icornerr.gif) |