Hi, It seems I am more awake today. A bit of testing using /etc/init.d/boot.localfs " lsmod > /root/lsmod.list " showed that the megaraid module is loaded with a 2.6.5-7.111-default kernel, but not with 2.6.5-7.145-default So: lsmod > /root/lsmod.list # Load the megaraid module as kernels more recent than 2.6.5-7.111-default # do not seem to want to modprobe -a megaraid #lsmod > /root/lsmod_after.list showed the megaraid module being loaded and the file system being mounted during boot with 2.6.5-7.145-default, from fstab: /dev/sda1 /raid5 ext3 defaults,usrquota,grpquota 0 2 I did try loading both megaraid and megaraid_mm, but that caused raidmon to screw up: lsmod > /root/lsmod.list # Load the megaraid module as kernels more recent than 2.6.5-7.111-default # do not seem to want to modprobe -a megaraid modprobe -a megaraid_mm lsmod > /root/lsmod_after.list as this bit in raidmon did not work: " megadevice="megadev0" rm -f /dev/$megadevice 2>/dev/null megamajor=`cat /proc/devices|gawk '/megadev/{print$1}' ` mknod /dev/$megadevice c $megamajor 0 2>/dev/null " and this test: " # New check: 10-31-01: Does node exist if [ ! -c /dev/$megadevice ] then echo " Character Device Node /dev/$megadevice does not exist. Raid Monitor could not be started " exit 1 fi " failed due to a lack of /dev/megadev0 there seemed to be two entries in /proc/devices matching '/megadev/{print$1}' so fair enough. I guess that network card problem could be something similar with kernel modules. Maybe a simple bit of testing using /etc/init.d/network will find something?? On Tue, 8 Feb 2005, Mike Rose wrote:
We have seen something that might be similar with kernel versions beyond 2.6.5-7.111-default and an intel computer running with an LSI 320-1 hardware RAID controller. The megaraid and megaraid_mm modules are loaded after boot, but during boot something is missing as /dev/sda1 (RAID array) will not mount during boot, but will mount after boot....
Mike Rose
On Tue, 8 Feb 2005, Vladimir Potapov wrote:
After upgrade to kernel-2.6.5-7.145-default on boot my network card - 3Com 59X(Boomerang) not running and in log I see following error:
eth0: Dropping NETIF_F_SG since no checksum feature.
With lsmod I see that the kernel module for network card loading correctly(load module 3C59X). When I logging to console and restart network (rcnetwork restart) the interface up and network work fine. In RedHat mailing lists I see that the problem can be with kudzu, but in my configuration no services running before network.
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here