-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Dec 28, 2005 at 08:24:08AM -0500, Alfred von Campe wrote: > >You might want to first check your BIOS settings for the CDROM drive, > >and then the data cable. I really don't think there is such a thing > >as an incompatible CDROM, but I have seen some BIOS settings making > >CDROM drives behave weirdly. > > What type of BIOS settings are you talking about? The system is > currently up and running, so I can't easily check it (but I'll > probably reboot it later today). DMA, Access mode, IRQs, IDE controle related settings. It will depend on your exact BIOS version and brand. > >I would recommend checking the master/slave jumper settings. Is the > >cdrom drive the only drive on the cable? On what positions does the > >bios > >report the drive (primary/secondary channel, master/slave?). changing > >DMA settings for the drive may help too. How does Linux recognize the > >drive (dmesg + /proc on which, as which drive hda, hdb, hdc, hdd?) > > The master/slave setting is set to exactly the same setting (slave) > as the CD-ROM drive it replaced (there is another drive on that same > cable). And how do I change the DMA settings? I think this is what > may be causing the problem. Linux currently doesn't recognize the > drive, as it is disconnected. But I believe it's /dev/hdb (although > it might be /dev/hdd). There are two hard disks at /dev/hda and /dev/ > hdc that are mirrored together and mounted as /home. Having a Slave drive in a interface where a Master drive is nor present violates the ATA standard, and can cause problems with some chipsets. Unfortunately, that is a very common practice. []s - -- Rodrigo Barbosa <rodrigob at suespammers.org> "Quid quid Latine dictum sit, altum viditur" "Be excellent to each other ..." - Bill & Ted (Wyld Stallyns) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDspSepdyWzQ5b5ckRAtS5AJ9KKPlD9+rgb4ZasYq2euliIWx1jACgtrpG rTYZylKN4Bg6IlIFvGPGCq8= =pInx -----END PGP SIGNATURE-----