Very Computer

Quote:>    I've just upgraded from 1.3.20 to 1.3.24, and the new kernel hangs
> during bootup when it tries to initialize (?) the CDROM drive.  It generates
> the following messages repeatedly, until I hit the reset button:
>    hdc: media changed
>    hdc: irq timeout: status = 0x58
>    hdc: ATAPI reset complete

I see this too, though it eventually succeeds:
hdc: media changed
hdc: irq timeout: status=0x58
hdc: irq timeout: status=0x58
hdc: ATAPI reset complete
hdc: status error: status=0x58
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x58
end_request: I/O error, dev 1600, sector 0
hdc: drive not ready for command
hdc: unexpected_intr: status=0xd8
hdc: unexpected_intr: status=0xd8
hdc: media changed
hdc: irq timeout: status=0x58
hdc: irq timeout: status=0x58
hdc: ATAPI reset complete
hdc: status error: status=0x58
hdc: drive not ready for command
hdc: ATAPI reset complete
hdc: status error: status=0x58
end_request: I/O error, dev 1600, sector 0
hdc: drive not ready for command
hdc: unexpected_intr: status=0xd8
hdc: unexpected_intr: status=0x58
hdc: unexpected_intr: status=0xd8
VFS: Disk change detected on device 22/0
  hdc: unknown partition table
Max size:214430   Log zone size:2048
First datazone:22   Root inode number 45056

this happens when the disk is mounted, either from /etc/fstab or rc.cdrom.

regards, mark hahn.
--

                                        http://neurocog.lrdc.pitt.edu/~hahn

How about emailing that info to Scott Snyder so he can fix it!
--

For Linux IDE (big/many) help, see:  /usr/src/linux/drivers/block/README.ide
For latest Linux kernels: ftp.cs.helsinki.fi:/pub/Software/Linux/Kernel/v1.[23]

I assume you are using a FX001DE or some Mitsumi drive.
Mine did the same thing. I tracked it down to bad atapi
reset behavior. A temporary fix is to disable the media
change sensing in the driver. This isn't a great fix but
it lets you access your cdrom drive with 1.3.24.

Dave

I assume you are using a FX001DE or some Mitsumi drive.
Mine did the same thing. I tracked it down to bad atapi
reset behavior. A temporary fix is to disable the media
change sensing in the driver. This isn't a great fix but
it lets you access your cdrom drive with 1.3.24.

Dave