Re: How to statically assign eth devices?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I use alias eth0 3c59x in /etc/modules.conf to force my laptop builtin nic to be
eth0 even when not connected to the LAN

That way any pcmcia nic cards (including my wifi) come up starting at eth1



Tom Ball (Tom.Ball@xxxxxxx) wrote:
>
>Is there a way to assign a specific module to eth devices in the ip link
>table?  On my laptop, something is calling "ip link" or its equivalent
>when the busses are scanned for my wireless card (pcmcia) and docking
>station ethernet (PCI).  The problem is that when I boot docked the PCI
>buss is scanned first so the ethernet driver gets assigned eth0, while
>when booted standalone the wireless gets eth0 because there's no PCI
>buss.  RedHat's network package requires device aliases in
>/etc/modules.conf, so half the time networking fails due to mismatched
>cards and devices.
>
>I've hacked this by rmmod'ing both drivers after buss scanning and
>before pcmcia is loaded, so that ifup reloads them in the right order.
>Is there a better way to enforce which card/driver gets assigned to
>eth0?  Perhaps a way to suppress a module from being loaded when its bus
>is being scanned?  Or a way for network drivers to not be installed in
>the ip link table when loaded?
>
>Tom
>
>
>
>

--
Brian Johnson
* This is where my witty signature line would be if I bothered to edit this line :) *



-- 
Shrike-list mailing list
Shrike-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/shrike-list

[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux