Re: CentOS 5.3 nvidia nForce network bugs, kernel panics (forcedeth, MCP67)
Posted by AlanBartlett on 2009/6/19 15:43:30
Quote:
Very resourceful.
After installing it (rpm -ivh kmod-forcedeth-*.rpm), check that the driver module is present under your /lib/modules/`uname -r`/extra/ directory and that a /etc/depmod.d/forcedeth.conf file now exists.
In general, you should stop the network service (service network stop), unload the older version of the driver from the kernel (modprobe -r forcedeth) and then restart the network (service network start). Often, people prefer to take the simpler option of rebooting the system.
You will need to manually update -- i.e. do all of the above -- for each and every new kernel that is installed. That is unless those openvz kernels do retain their own ABI consistency. (You could check for that by executing a find /lib/modules -name forcedeth.ko command after a new kernel has been installed. If there is a symbolic link from the new kernel's weak-updates/ directory to the extra/ directory of this, your current kernel, it would appear that the openvz kernels do retain some degree of ABI consistency.)
I have downloaded the src.rpm of kmod-forcedeth and rebuilded it by mock for my kernel version.
Very resourceful.
I'm interesting what should I do to activate this module ?
Does it activate automatically after installation ?
And what a procedure for updating ?
I.e. after installing a new openvz kernel, I should also rebuild the forcedeth-kmod and only after this reboot the server ?
After installing it (rpm -ivh kmod-forcedeth-*.rpm), check that the driver module is present under your /lib/modules/`uname -r`/extra/ directory and that a /etc/depmod.d/forcedeth.conf file now exists.
In general, you should stop the network service (service network stop), unload the older version of the driver from the kernel (modprobe -r forcedeth) and then restart the network (service network start). Often, people prefer to take the simpler option of rebooting the system.
You will need to manually update -- i.e. do all of the above -- for each and every new kernel that is installed. That is unless those openvz kernels do retain their own ABI consistency. (You could check for that by executing a find /lib/modules -name forcedeth.ko command after a new kernel has been installed. If there is a symbolic link from the new kernel's weak-updates/ directory to the extra/ directory of this, your current kernel, it would appear that the openvz kernels do retain some degree of ABI consistency.)
This Post was from: https://www.centos.org/newbb/viewtopic.php?forum=40&topic_id=20835&post_id=79283