RE: [CentOS] loading modules across reboots

2008-08-28 Thread Joseph L. Casale
>Really, it depends on when this module is needed. If it's for a scsi >controller, or other critical system disk, it needs to be in the >initrd. If it can be loaded after the system is mostly running >(network devices, usb bits, etc) then it can be slapped in other >module locations. What sort of m

Re: [CentOS] loading modules across reboots

2008-08-28 Thread Jim Perrin
On Thu, Aug 28, 2008 at 12:05 PM, Joseph L. Casale <[EMAIL PROTECTED]> wrote: >>You can do this in /etc/modprobe.conf (or /etc/modprobe.d) OR you can >>create an /etc/rc.modules (for legacy support) OR you can add your >>bits to /etc/sysconfig/modules/foo.modules. > > Jim, > I did assume modprobe.c

RE: [CentOS] loading modules across reboots

2008-08-28 Thread Joseph L. Casale
>You can do this in /etc/modprobe.conf (or /etc/modprobe.d) OR you can >create an /etc/rc.modules (for legacy support) OR you can add your >bits to /etc/sysconfig/modules/foo.modules. Jim, I did assume modprobe.conf was the correct place and tried a line which didn't work. man modprobe.conf shows

Re: [CentOS] loading modules across reboots

2008-08-28 Thread Jim Perrin
On Thu, Aug 28, 2008 at 8:03 AM, Gopinath Achari <[EMAIL PROTECTED]> wrote: > add an entry of that module in /etc/rc.sysinit > > insmod /lib/modules/2.6.x.x/drivers/kernel/net/modulename.o > > and it automatically loads the module during the reboot This is very much the WRONG place for this type

Re: [CentOS] loading modules across reboots

2008-08-28 Thread Gopinath Achari
add an entry of that module in /etc/rc.sysinit insmod /lib/modules/2.6.x.x/drivers/kernel/net/modulename.o and it automatically loads the module during the reboot On Tue, 2008-08-26 at 13:57 -0600, Joseph L. Casale wrote: > I have a CentOS 5.2 install on a machine with the Marvell nic is

RE: [CentOS] loading modules across reboots

2008-08-26 Thread Joseph L. Casale
>possibly the driver as delivered doesn't recognize that specific version >of the device, so needs a nudge to handle this specific device ID ? > >[this is purely a wild a** guess] Ok, so I see this on boot: Bringing up interface eth0: [ OK ] Bringing up interface eth1: sky2 device eth1 does no

Re: [CentOS] loading modules across reboots

2008-08-26 Thread John R Pierce
Joseph L. Casale wrote: 11AB 4364 are likely the PCI Vendor/Device IDs. # lspci 00:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) # lspci -n 00:00.0 0200: 11ab:4364 (rev 12) Yup, so what was the significance of this requirement

RE: [CentOS] loading modules across reboots

2008-08-26 Thread Joseph L. Casale
>11AB 4364 are likely the PCI Vendor/Device IDs. # lspci 00:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) # lspci -n 00:00.0 0200: 11ab:4364 (rev 12) Yup, so what was the significance of this requirement after loading the module? I as

Re: [CentOS] loading modules across reboots

2008-08-26 Thread John R Pierce
Joseph L. Casale wrote: I have a CentOS 5.2 install on a machine with the Marvell nic issue outlined in http://bugs.centos.org/view.php?id=2612. I have a few questions regarding this, what does the # echo "11ab 4364" > /sys/bus/pci/drivers/sky2/new_id line do? Obviously it starts right after bu

[CentOS] loading modules across reboots

2008-08-26 Thread Joseph L. Casale
I have a CentOS 5.2 install on a machine with the Marvell nic issue outlined in http://bugs.centos.org/view.php?id=2612. I have a few questions regarding this, what does the # echo "11ab 4364" > /sys/bus/pci/drivers/sky2/new_id line do? Obviously it starts right after but what specifically is the