Author: Jan Henkins Date: To: lug, Hampshire LUG Discussion List Subject: Re: [Hampshire] Some strange brokenness...
Hello Nic,
On Tue, January 25, 2011 20:00, Vic wrote: >
> Hi All.
>
> In a rather ill-executed manoeuvre yesterday, I finally upgraded my
> RHEL3-type box. And I've borked it :-(
What did you upgrade it to?
> I have two ethernet interfaces in this box - an nVidia interface on the
> motherboard, and a Realtek chip on the PCI bus.
>
> The nVidia interface - using forcedeth - works fine. No problems at all.
>
> The Realtek interface is proving difficult: on initial boot, the interface
> name is screwed up. It comes up as "dev377" or similar (the number
> changes).
>
> If I modprobe -r the driver, then modprobe it back in again, the interface
> comes up with the correct name, and things then get back to normal.
Sounds a bit fishy...
> I'm a bit lost on this one. I've just added some debug to the module
> options, but I'm waiting for my kernel build to finish before I reboot it.
>
> Has anyone seen anything like this before?
Nope, although you have already stumbled across at least one workaround,
which you can of course script. Have a peek at the contents of your
/etc/modprobe.conf (or /etc/modules, cannot exactly remember the correct
one for RHEL), and look for the "alias ethX modulename" line (X being the
proper eth device number) for some strange module parameters. If there
isn't anything obviously wrong, I would comment that one out and do the
following:
* Edit /etc/sysconfig/network-scripts/ifcfg-ethX and change "Onboot" to "No"
* Add something like this at the bottom of the /etc/rc.local file:
/sbin/modprobe modulename
sleep 5
ifconfig ethX up
