On 6/29/07, Richard Chapman <rchapman@xxxxxxxxxxxxxxx> wrote:
Hmmm... Thanks Peter Actually - this is quite a big problem. It seems like new kernels come along reasonably often - and my intention was to leave this machine in a corner somewhere without any screen and manage it through nx and webmin. I have seen the problem already because as soon as it was on the Internet it got a new kernel - and after rebooting it couldn't find the eth0 again. I did just the insmod part of the procedure - and the network came up again - but as soon as I reboot it disappears again. I realise now that i really need to repeat the whole procedure with the appropriate version of kernel-devel. I have since done this, and it now boots OK. I guess there is nothing I can do but wait and hope for redhat to fix the driver - is there? Richard.
If the driver needs to be recompiled for each kernel version, one possible solution is to create a dkms ( dynamic kernel module support ) module for the driver. This is not trivial, but once it is done, the driver will be automatically compiled whenever kernel gets updated and the system rebooted. See the second section of this wiki: http://wiki.centos.org/HowTos/BuildingKernelModules The page is still work in progress but might help you build your own dkms driver. Akemi _______________________________________________ CentOS mailing list CentOS@xxxxxxxxxx http://lists.centos.org/mailman/listinfo/centos
