--You are correct, those two features will be hardwired into the kernel rather than loaded as modules. Now all you have to do with experiment with the modules-disk cheatcode. If you can't get anywhere with it, you could try emailing Klaus, but I'd use that only as a last resort.

Quote Originally Posted by SUOrangeman
For a little more background: http://www.knoppix.net/forum/viewtopic.php?p=25463

I'm trying to install KNOPPIX to my nift WD Raptor hard drive. I am currently using a Promise SATA150 TX4 controller card, which is not directly supported. Promise has released the source code of a Linux driver and I have managed to get it compiled.

With the modules-disk cheatcode in KNOPPIX 3.3, I am hoping that I can just put this driver on a floppy and have KNOPPIX pick it up during boot, so that it detects my hard drive. According the the driver's README, I need to load scsi.o and sd.o before I attempt to load the module for this controller.

Looking at the kernel config file, I see (:/boot/config-2.4.22-xfs)

# SCSI support
CONFIG_SCSI=y

# SCSI support type (disk, tape, CD-ROM)
CONFIG_BLK_DEV_SD=y

I haven't compiled a kernel is quite some time. Is it safe to assume that these two settings control the "destiny" of scsi.o and sd.o? That is, can I assume these drivers are built into the kernel (=y)and not built as modules(=m)? What is my best option for getting the scsi.o and sd.o files I need to load my controller driver?/boot/config-2.4.22-xfs

Thanks in advance!

-SUO