Sorry about the top-post, but I believe the problem here is that the arrays are not "booted" yet when the kernel sysconfig file is read (I've had the same problem with high-point's as well as 3ware's in dual opteron systems. One solution may be to add a mount for the dependent filesystems in the /etc/init.d/boot.local (what I did for the highpoint's), or (in the same file) add modprobe 3w-9xxx. I haven't looked at the details of the 3ware device to know if you can reduce the "boot" time -- which may also help. Thanks, Patrick W. Freeman Systems Specialist Datallegro, Inc. -----Original Message----- From: James D. Parra [mailto:Jamesp@MusicReports.com] Sent: Tuesday, November 02, 2004 11:49 AM To: SuSE AMD64 (E-mail) Subject: [suse-amd64] adding a module for new harder- 2.6 kernel Hello, Have a Dual Opteron with SuSE 9.1 installed with the x86_64 kernel. I added a 3Ware 9000 controller and I can insert the module (3x-9xxx) and access the file system, but after a reboot the module is not reloaded. I have an entry in /etc/sysconfig/kernel as shown below; # This variable contains the list of modules to be added to the initial # ramdisk by calling the script "mk_initrd" # (like drivers for scsi-controllers, for lvm or reiserfs) # INITRD_MODULES="sata_sil jbd ext3 3w-9xxx" ...however the module still doesn't load after a reboot. Does anyone know how to have new modules load in the 2.6 kernel? Many thanks in advance. James -- Check the List-Unsubscribe header to unsubscribe For additional commands, email: suse-amd64-help@suse.com