invalid block device still continues

Mike Gorse mgorse at WPI.EDU
Wed Apr 12 09:49:16 EDT 2000

You can also figure out what drive your kernel is assigning things by
using dmesg (which retrieves a copy of the kernel messages shown at boot
time).  Ie, dmesg |grep hdc gives me the following:

    ide1: BM-DMA at 0xf008-0xf00f, BIOS settings: hdc:pio, hdd:pio
hdc: CD-ROM 32X/AKU, ATAPI CDROM drive
hdc: ATAPI 20X CD-ROM drive, 128kB Cache

--Michael Gorse, WPI Cs '01 / ICQ:22583968 / --
     If you're an oister, then don't let your perl get away from you.

On Wed, 12 Apr 2000 cpt.kirk at wrote:

> One thing I noticed is that you have the file type incorrect. CDROMs use
> iso9660. I would try this first:
> mount -t auto /dev/cdrom /mnt/cdrom
> if it returns an error that the file system must be specified:
> mount -t iso9660 /dev/cdrom /mnt/cdrom
> Both of the above make two assumptions which are valid on the Linux
> systems I have played with. The one thing is that not all systems have the
> cdrom subdirectory. If the /dev/cdrom doesn't work then you will have to
> use the hd specification for its location. Keep in mind that they aren't
> always sequential. If the drive is set to the master on secondary then it
> will be hdc even if there is no hdb present.
> Kirk Wood
> Cpt.Kirk at
> ------------------
> Why can't you be a non-conformist, like everybody else?
> _______________________________________________
> Speakup mailing list
> Speakup at

More information about the Speakup mailing list