[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ide-scsi emulation fails due to missing module sr_mod in kernel 2.4.18-bf2.4



Michael Rauch wrote:
hi,

i recently replaced the SuSE installation on my desktop with debian/woody. now i have some troubles getting my IDE cd-burner (alias hdd) working. after reading the CD-WRITING-HOWTO and googling around for some time i figured that the module sr_mod (afaik SCSI CD-ROM support) is not present in my system, i'm using the prebuilt 2.4.18-bf2.4 kernel and sr_mod.o is missing from /lib/modules/2.4.18-bf2.4/kernel/drivers/scsi where i would expect it to be.

now i'm wondering if there is some other way to get this module on my system beside of getting the kernel and module sources and baking a new kernel.

#!michael




I just had to go through this here, so I had better reply while it is "fresh" in my rather ancient mind! <grin>.

The 2.4.18-bf2.4 kernel is a "special" kernel that has been stripped of a lot of stuff so it will fit on a boot-floppy for install purposes. Several of the more basic drivers are compiled into the kernel, it isn't set up to use initrd, and modules not needed for installation have been removed. In lots of circumstances it will NOT be suitable for long-term use beyond the initial install, as you have found out.

Fortunately, the pre-compiled "kernel-image" debs have all the stuff there, and have been set up to be fully modular. This brings up some "gotchas" if you decide to use it, though. Your other option is to d/l the source and compile your own kernel. I believe using the pre-compiled kernel-image debs will be a bit faster for you. I used the "kernel-image-2.4.19-686 package out of "testing", but I believe you will only get a 2.4.18 package if you stick to "Woody" or "Stable".

Gotchas:
1. The new kernel image used initrd, so you WILL have to edit your /etc/lilo.conf file and add the "initrd-/initrd.img" to your new vmlinuz stanza. This is well documented, and you are warned. You will still be able to use the "old" kernel to boot up if you make a mistake.

2. If you are using a NIC that had its driver pre-compiled into the bf2.4 kernel (like the RealTek 8139 chipset), you will have to insert it into the new kernel via modconf or add the proper module to the /etc/modules file. If you don't, then you will NOT have networking until you do.

3. You will have to add the "ide-scsi" and "sr_mod" modules to get your burner recognized. When you do this, the old links to hdd (and/or hdc depending on your config) will not work. If you have two CDROM devices on hdc and hdd like I do, then hdc --> sr0, and hdd--> sr1. This means you will probably have to change the soft-link for /dev/cdrom in your /dev directory. I also created another "soft link" there for my burner (/dev/cdr --> /dev/sr1). You might also have to add the second device (cdr) to your /etc/fstab file to be able to mount it.

Thats all I can think of at the moment. That was about all I had to do to get everything running normally after the install of the new kernel-image package.

Cheers,
-Don Spoon-



Reply to: