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 "11ab 4364" part? Also, how do I get this to load across reboots? I have the alias and module in my modprobe.conf but that is not enough.
Thanks, jlc
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 but what specifically is the "11ab 4364" part? Also, how do I get this to load across reboots? I have the alias and module in my modprobe.conf but that is not enough.
11AB 4364 are likely the PCI Vendor/Device IDs.
indeed...
http://pci-ids.ucw.cz/iii/?i=11ab
shows thats Marvell, and that DeviceID 4364 is the 88E8056 PCI-E Gigabit Ethernet Controller
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 assume it would start working once rebooted so long as the module loaded? Which I am still trying to figure out how :)
Thanks! jlc
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 after loading the module? I assume it would start working once rebooted so long as the module loaded? Which I am still trying to figure out how :)
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]
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 not seem to be present, delaying initialization. [FAILED]
So just to clarify #modprobe "module name" *is* enough to load a module across reboots, but you must be correct in that that nic needs a nudge...
Thanks, jlc
on 8-26-2008 12:57 PM Joseph L. Casale spake the following:
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 "11ab 4364" part? Also, how do I get this to load across reboots? I have the alias and module in my modprobe.conf but that is not enough.
Thanks, jlc
I guess you could add the "echo "11ab 4364" > /sys/bus/pci/drivers/sky2/new_id" line to the end of rc.local as a kludge until the driver is fixed.
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 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 "11ab 4364" part? Also, how do I get this to load across reboots? I have the alias and module in my modprobe.conf but that is not enough.
Thanks, jlc _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Aug 28, 2008 at 8:03 AM, Gopinath Achari gopinath@signal-networks.com 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 of module load.
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.
Adding things to /etc/rc.sysinit is very much incorrect, as well as reckless, dangerous, and other such negative words.
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 an "install" line but I am unable to get this to work. I was trying to load blkbk for example and tried everything under the sun but it wouldn't load. I ended up rolling an initrd with it which worked but I am not satisfied that's a good idea, next yum update and its broken!
It looks like install needs "install blkbk /sbin/modprobe blkbk" but this didn't work?
Any idea?
Thanks! jlc
On Thu, Aug 28, 2008 at 12:05 PM, Joseph L. Casale JCasale@activenetwerx.com 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.conf was the correct place and tried a line which didn't work. man modprobe.conf shows an "install" line but I am unable to get this to work. I was trying to load blkbk for example and tried everything under the sun but it wouldn't load. I ended up rolling an initrd with it which worked but I am not satisfied that's a good idea, next yum update and its broken!
It looks like install needs "install blkbk /sbin/modprobe blkbk" but this didn't work?
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 module is blkbk?
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 module is blkbk?
They are used in Xen. I need netbk, xenblk, blktap, blkbk, and netloop. If I modprobe them from the console, then start a vm everything is groovy so I am sure when they load isn't an issue especially if they can handle early loading with my custom initrd.
Was my modprobe.conf syntax right?
Thanks for all your help! jlc
-
Gopinath Achari -
Jim Perrin -
John R Pierce -
Joseph L. Casale -
Scott Silva