tgos@xxxxxxxx writes:
> Hello everyone,
>
> I only subscribed to that mailing list, because I'm a very curious person and
> I
> always have to know everything. ^_-
>
> Once I read about DEVFS, I simply had to try it.
> I installed DEVFSD, recompiled the Kernel (v 2.4.2) and everything worked
> fine.
>
> Except one problem:
> My HDs are /dev/hgd and /dev/hdf (connected to my second IDE controller).
> Both had been there (thanks to DEVFSD), as well as under their new name.
>
> But my CDROM wasn't there anymore. It usually should be /dev/hda, but neither
> that, nor the new device names for the first IDE controller existed.
>
> I recompiled the kernel and found out that the CDROM support was set to
> "module". After I compiled it into the Kernel, the device was there (/dev/hda)
> and I could use it.
>
> But since I don't use the CDROM pretty often, I usually compile CDROM support
> and the ISO9660 support as modules.
>
>
> Here's my question:
> I thought if I compile the CDROM support as module and later on load
> that module, the DEVFS will add a new device and thanks to DEVFSD it
> will also exist as /dev/hda
> But it wasn't there.
>
> Is there any way to get it there or is the only chance compiling
> CDROM support into the Kernel?
I have all my IDE drivers as modules, and my IDE CD-ROM shows up just
fine under /dev/ide. The modules I have loaded are:
isofs 19600 0 (unused)
ide-cd 27264 0
cdrom 28416 0 [ide-cd]
ide-probe-mod 9344 0
ide-mod 64480 0 [ide-cd ide-probe-mod]
with the bottom one loaded first.
As a sanity check, look at your kernel logs and see if you get a
message like:
hdb: ATAPI 48X CD-ROM drive, 128kB Cache, DMA
This is supposed to come from the ide-cd module, when it detects your
CD-ROM.
Regards,
Richard....
Permanent: rgooch@xxxxxxxxxxxxx
Current: rgooch@xxxxxxxxxxxxxxx
|