Hi all, I'm sure some know the problem: Since SuSE recocnizes the NICs by MAC, they keep shifting around their ID's on slight config changes. I tried to check this problem by editing /etc/modprobe.conf like so: <snip> # Aliases - specify your hardware ######################################################################## install eth0 /sbin/modprobe via-rhine install eth1 /sbin/modprobe dmfe install eth2 /sbin/modprobe ne2k-pci </snip> However that does not order anything, I have dmfe on eth0, ne2k on eth1 and the onboard via-rhine on eth2. Hmmmm.... Anyone have an idea ? Regards Daniel
Dan Am wrote:
Hi all,
I'm sure some know the problem: Since SuSE recocnizes the NICs by MAC, they keep shifting around their ID's on slight config changes. I tried to check this problem by editing /etc/modprobe.conf like so:
<snip> # Aliases - specify your hardware ########################################################################
install eth0 /sbin/modprobe via-rhine install eth1 /sbin/modprobe dmfe install eth2 /sbin/modprobe ne2k-pci </snip>
However that does not order anything, I have dmfe on eth0, ne2k on eth1 and the onboard via-rhine on eth2. Hmmmm.... Anyone have an idea ?
Regards
Daniel
Check out the thread at http://lists.suse.com/archive/suse-linux-e/2004-Dec/3110.html. Apparently the best you can hope for is persistent names that don't start with eth. Jason Joines =================================
Jason Joines wrote:
Dan Am wrote:
Hi all,
I'm sure some know the problem: Since SuSE recocnizes the NICs by MAC, they keep shifting around their ID's on slight config changes. I tried to check this problem by editing /etc/modprobe.conf like so: <snip> # Aliases - specify your hardware ########################################################################
install eth0 /sbin/modprobe via-rhine install eth1 /sbin/modprobe dmfe install eth2 /sbin/modprobe ne2k-pci </snip>
However that does not order anything, I have dmfe on eth0, ne2k on eth1 and the onboard via-rhine on eth2. Hmmmm.... Anyone have an idea ? Regards
Daniel
Check out the thread at http://lists.suse.com/archive/suse-linux-e/2004-Dec/3110.html. Apparently the best you can hope for is persistent names that don't start with eth.
Jason Joines =================================
I never got any of the things in that thread to work reliably. It looks like the nameif utility will work if you don't use eth* names. Luckily, my two NIC's use different modules so I put the module for the one I wanted to be eth0 into the initial ram disk. This seems to be working. You could probably do the same thing as I believe they are loaded in a particular order. Putting via-rhine in first followed by dmfe and leave ne2k-pci out to be initialized normally after the other two are already up. Jason ===========
Dan Am wrote:
Hi all,
I'm sure some know the problem: Since SuSE recocnizes the NICs by MAC, they keep shifting around their ID's on slight config changes. I tried to check this problem by editing /etc/modprobe.conf like so:
<snip> # Aliases - specify your hardware ########################################################################
install eth0 /sbin/modprobe via-rhine install eth1 /sbin/modprobe dmfe install eth2 /sbin/modprobe ne2k-pci </snip>
However that does not order anything, I have dmfe on eth0, ne2k on eth1 and the onboard via-rhine on eth2. Hmmmm.... Anyone have an idea ?
Yes, it takes two to tango, not three. ;-)
participants (3)
-
Dan Am
-
James Knott
-
Jason Joines