cdrecord problem

[janneo]

Well, my Linux-box works like it should now. Almost. I have been struggling to get by CD-writer to work. I have read the howto and I have installed the required software. IDE-SCSI is enabled in LiLO, Kernel has SCSI and SCSI emulation enabled. But when I run "cdrecord -scanbus" I get this:

cdrecord: No such file or directory. Cannot open SCSI driver.
cdrecord: For possible targets try 'cdrecord -scanbus'. Make sure you are root.

I am running it as root. cdrecord is installed using apt-get, version in 1.10.

[jaygee432]

Try manually loading the module, i.e., insmod ide-scsi.

[janneo]

Actually SCSI is compiled directly in the kernel. For some reason, I always seem to have problems with kernel-modules.

Off-topic: why is it that when I compile a new kernel, none of the modules seem to work? Yes modules-support is enabled, and I do everything by the book. But it always complains that it can't load or find the modules.

[ 16 November 2001: Message edited by: janneo ]

[bdg1983]

It could be that scsi emulation be compiled as modules and not within the kernel.

Could you please list the exact steps you are using to compile the kernel? Plus the copying the new kernel and System.map to /boot and anything else you do.

[janneo]

How I compile the kernel:

1. make menuconfig
(1.1 Configure the kernel)
2. make dep
3. make clean
4. make bzImage
5. make modules
6. cp /usr/src/linux/arch/i386/boot/bzImage /boot/vmlinuz-2.4.14
7. cp /usr/src/linux/System.map /boot/System.map-2.4.14
8. make modules_install
9. edit lilo.conf
10. lilo
11. reboot

All done.

[bdg1983]

Have you verified that the new modules exist in /lib/modules/<kernel version>? The make modules and make modules_install steps were successful?

I have this in my /etc/modules.conf that points it to the correct module directory under /lib/modules for whatever kernel I boot.

keep
path[toplevel]=/lib/modules/`uname -r`

`uname -r` plugs in the kernel version and ensures the correct /lib/modules/<kernel version> directory is used.

I also have separate directories under /etc/modules for my kernel versions.

/etc/modules/2.4.2
/etc/modules/2.4.13
/etc/modules/2.4.14

And in those directories instead of having the standard .default and .rootfs, I add the kernel compile date/time etc. (uname -v), so for example I have

/etc/modules/2.4.14/#1 Wed Nov 7 19:31:50 EST 2001.default
/etc/modules/2.4.14/#1 Wed Nov 7 19:31:50 EST 2001.rootfs

So whatever kernel I boot, only the modules I have compiled and also setup in /etc/modules.conf and /etc/modules/<kernel version> are loaded.

If you upgrade your kernel from the 2.2 series to the 2.4, then you will need to upgrade modutils and possibly a few other packages. Check the docs at www.kernel.org (http://www.kernel.org) to see what is recommended.

[janneo]

I'm not in Linux right now, so I can't check... But compiling & installing the modules work OK, no error-messages. And there is an entry in /lib/modules. Haven't checked the /etc/modules.conf.