Hello,I apologize in advance for vagueness in this question - been a while since I've delved into linux and things have changed a lot in the last few years (well, I've been actively using it for many years, it's just been long enough since I've had driver level issues that I clearly no longer am up to date).
I'm trying to get 5.2 EL up and running on a new system. It's based on an Asus P5Q-EM motherboard which has the new intel P45 chipset and a RealTek RTL8168B PCI express ethernet controller.
I downloaded an eval copy of the 5.2 DVD and installed it. Ethernet wasn't working, some poking around revealed that it had matched the r8169 kernel module against my ethernet controller. I downloaded the correct driver from the realtek site, built and installed it on the system. One reboot later and I had working ethernet.
I then applied all of the latest updates from the redhat network and one reboot later ethernet was no longer working. I can re-install the r8168 module but after a reboot it appears that the system has ignored that and reloaded the r8169 module for me.
The original install was based on the 2.6.18-92.el5xen kernel/modules. If I reboot into that (rather than the newer 2.6.18-91.1.10.el5xen) ethernet works.
I edited /etc/modprobe.conf to change the line: alias eth0 r8169 to: alias eth0 r8168But things still don't work. Some further pinging/debugging from another machine and right after eth0 is configured at boot I actually do have a working ethernet controller. But then later in the boot (it looks to be around where xend is loaded) my working r8168 module is replaced with the ever-resilient r8169 module...
Some poking around on google suggests that kudzu really loves the r8169 module although others have been able to fix it with the modprobe.conf change that doesn't work for me.
Checking /etc/sysconfig/hwconf I see that kudzu has matched r8169 to the ethernet controller.
I found a note in the RH knowledge base that said I can disable kudzu at boot (it was a chkconfig command or something), but that didn't work either.
I've greped all of /etc for r8169 - the only references were modprobe.conf and hwconf. But, from what I understand hwconf doesn't actually effect system state, it's just a record of what kudzu found - is this correct?
Any suggestions as to what I might do to fix this or further debug it would be greatly appreciated.
Thank you! Shannon
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
