My apologies if this is a repeat... I originally sent it yesterday
evening, and haven't seen any sign of it on the list.
---
I'm starting to test out the 2.6.0-test1 kernel, and for the most part
everything is going smoothly. There is one problem that has me
stumped, however... I can't seem to get module auto-loading to work for
the cdrom. None of the other modules seem to have any trouble.
I'm currently running Debian sid, with module-init-tools 0.9.13-pre.
I've defined the alias "block-major-22 ide-cd", and verified that both
"modprobe -nv block-major-22" and "modprobe -nv ide-cd" give the
expected results. When I try to mount a CD, however, I get the message
"/dev/hdc not a valid block device". Browsing the system logfiles, I
don't see any indication that a module load was even attempted.
Everything works fine if I load the ide-cd module manually first.
I browsed the list archives and did some googling, but didn't find
anything which sounded similar. Any idea what's wrong?
Thanx!
In article <[email protected]>,
Greg Norris <[email protected]> wrote:
| I'm currently running Debian sid, with module-init-tools 0.9.13-pre.
| I've defined the alias "block-major-22 ide-cd", and verified that both
| "modprobe -nv block-major-22" and "modprobe -nv ide-cd" give the
| expected results. When I try to mount a CD, however, I get the message
| "/dev/hdc not a valid block device". Browsing the system logfiles, I
| don't see any indication that a module load was even attempted.
| Everything works fine if I load the ide-cd module manually first.
Is hdd set to anything special? And is hdc set to cdrom? If not, try an
explicit "hdc=cdrom" on the boot line. I have had to do this on several
systems, in spite of dmesg telling me the kernel knows that it's a CD.
--
bill davidsen <[email protected]>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
On Wed, Jul 23, 2003 at 08:58:45PM +0000, bill davidsen wrote:
> Is hdd set to anything special? And is hdc set to cdrom? If not, try
> an explicit "hdc=cdrom" on the boot line. I have had to do this on
> several systems, in spite of dmesg telling me the kernel knows that
> it's a CD.
Thanx for the suggestion, but it unfortunately doesn't appear to have
made any difference. :-( The full kernel command-line was
"acpismp=force hdc=cdrom hdd=cdrom" (hdc is a DVD-ROM, and hdd is a
CD-RW).
# mount /cdrom
mount: /dev/hdc is not a valid block device
# grep ide /proc/modules
# mount -t iso9660 /dev/hdc /cdrom
mount: /dev/hdc is not a valid block device
# modprobe ide-cd
end_request: I/O error, dev hdc, sector 0
hdc: ATAPI 48X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
end_request: I/O error, dev hdd, sector 0
hdd: ATAPI 48X CD-ROM CD-R/RW drive, 2048kB Cache, UDMA(33)
# mount -t iso9660 /dev/hdc /cdrom
mount: block device /dev/hdc is write-protected, mounting read-only
ISO 9660 Extensions: Microsoft Joliet Level 3
ISO 9660 Extensions: RRIP_1991A
I can't find any messages under /var/log or dmesg to indicate that a
module load was attempted for block-major-22 (or anything else, for
that matter).
I appreciate the suggestion, tho!