I've discovered sme additional info on this problem. It seems to be related
to probing; if I specify "hdc=noprobe hdc=cdrom" in my append statement in
LILO, the CD-ROM mounts fine.
I tried to pin down the problem (I think it's in ide-probe.c), but I can't
find the exact thing that breaks it. In probe_for_drive(), do_probe() is
called twice for CDROMs, the first time as a hard drive, and the second as a
ATAPI device. I confirmed with some debugging code that the (failed)
do_probe(WIN_IDENTIFY) does not break the drive, but the
do_probe(WIN_PIDENTIFY) does kill it.
Does anyone with more experience in this area have any ideas? Thanks in
advance..
Brad
Brad Nelson wrote:
> I'm installing Linux on a dual PIII Asus based system. My initial
> install was kernel 2.2.12-20smp, the out-of-the-box kernel in RedHat
> 6.1; my Plextor PX-W8432T IDE CD-R mounts fine in that version.
>
> However, after building and installing kernel 2.2.14, I can't get the
> CD-R(OM) to mount. I've got several symptoms:
>
> 1. mount -t iso9660 /dev/cdrom /mnt/cdrom returns very quickly under
> 2.2.14, and instead of mounting, it changes the mountpoint to a file
> with 0 bytes (?!), e.g.
> before: drwxrwxr-x 2 root root 4096 Feb 6 1996 cdrom
> after: -r-xr-xr-x 1 root root 0 Dec 31 1969 cdrom
>
> 2. Of course, the device is not really mounted, even though a simple
> "mount" (no args) shows it to be so.
>
> 3. When I try to subsequently umount the CD-ROM, I get the following
> errors:
> VFS: Disk change detected on device ide1(22,0)
> hdc: status error: status=0x58 { DriveReady SeekComplete DataRequest }
> hdc: DMA disabled
> hdc: drive not ready for command
> hdc: ATAPI reset complete
> hdc: irq timeout: status=0x80 { Busy }
> hdc: ATAPI reset complete
> hdc: irq timeout: status=0x80 { Busy }
> end_request: I/O error, dev 16:00 (hdc), sector 64
<snip>
> Again, this works perfectly under 2.2.12-20; I haven't tried anything
> other than 2.2.12-20 and 2.2.14. I have both kernels bootable via lilo;
> I boot 2.2.12-20, mount the CDROM and all is well, umount and reboot to
> 2.2.14, try to mount, it fails (either mount or umount), I reboot back
> to 2.2.12-20, and it succeeds again. I don't have any patches applied to
> either kernel.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Mar 23 2000 - 21:00:19 EST