On Wed, 2004-11-03 at 12:06, James D. Parra wrote:

make sure your modules.dep file is up to date before you run mkinitrd. I think the command is "modprobe -n".

~~~ This is interesting. The output of mf_initrd cannot determine the dependencies of module 3w-9xxx;

# mk_initrd Root device: /dev/hdc3 (mounted on / as ext3) Module list: sata_sil jbd ext3 scsi_mod 3w-9xxx

Kernel image: /boot/vmlinuz-2.6.5-7.111-smp Initrd image: /boot/initrd-2.6.5-7.111-smp Shared libs: lib64/ld-2.3.3.so lib64/libc.so.6 lib64/libselinux.so.1 Cannot determine dependencies of module 3w-9xxx. Is modules.dep up to date? Cannot determine dependencies of module 3w-9xxx. Is modules.dep up to date? Modules: kernel/drivers/scsi/scsi_mod.ko kernel/drivers/scsi/sd_mod.ko kernel/drivers/scsi/libata.ko kernel/drivers/scsi/sata_sil.ko kernel/fs/jbd/jbd.ko kernel/fs/ext3/ext3.ko Bootsplash: SuSE (1024x768)

Run lilo now to update the boot loader configuration.

~~~

... while the command, # modprobe -n 3w-9xxx.smp FATAL: Module 3w_9xxx.smp not found.

...and # modprobe -n 3w-9xxx FATAL: Module 3w_9xxx not found.

... had errors.

What I have found is that I am using the 3w-9xxx.smp module, which is shown under /lib/modules/kernel/drivers/scsi/3w-9xxx.smp, however it appeares that mk_initrd is expecting the .ko file extention. The module 3x-9xxx.ko will not load into the x86_64 kernel.

Any clues?

Thank you,

~James

Are you using the kernel module or the one from 3ware? Did you rename the module to a .ko extension and try it? I am using the 9500-12 card under SuSe 9.1 64bit with no problems. Brad Dameron SeaTab Software www.seatab.com