interface names get swapped, but udev rules don't work

futuremonkey · 2010-12-23 15:14:39

I'm using the (apparently nightmarish) broadcom_wl module.

This:
https://wiki.archlinux.org/index.php/Br … every_time

and this:
https://wiki.archlinux.org/index.php/Co … es_varying

don't work. the 10-network.rules file I create is just completely ignored.

Any ideas?

Arch is my distro of choice for my desktop, but it is turning out to be an enormous PITA on my laptop.

Mr Green · 2010-12-23 15:30:04

Can you post your pci device id please

Last edited by Mr Green (2010-12-23 15:30:38)

SiD · 2010-12-23 15:31:48

arch wiki wrote:

It is possible to specify the module loading order in /etc/rc.conf
# Always load 8139too before e100
MODULES=(8139too e100)

have you tried this already?

futuremonkey · 2010-12-23 15:46:43

wired: was eth0 at install, after boot is mysteriously eth1
MAC address is: 88:ae:1d:db:94:f6

wireless: now eth0, was eth1 upon initial configuration
MAC address is: 00:26:82:e7:3f:a2

/etc/udev/rules.d/10-network.rules looks like this:

SUBSYSTEM=="net", ATTR{address}=="88:ae:1d:db:94:f6", NAME="eth0"
SUBSYSTEM=="net", ATTR{address}=="00:26:82:e7:3f:a2", NAME="eth1"

yet ifconfig -a shows that it's being ignored for some reason.

futuremonkey · 2010-12-23 15:57:23

Mr Green wrote:

Can you post your pci device id please

I'm assuming you mean this:

# lspci -nn | grep 14e4
05:00.0 Network controller [0280]: Broadcom Corporation Device [14e4:4727] (rev 01)

SiD · 2010-12-23 15:59:25

what about putting the modules in MODULES=() in rc.conf, does that work?

futuremonkey · 2010-12-23 16:00:34

SiD wrote:

what about putting the modules in MODULES=() in rc.conf, does that work?

MODULES=(lib80211_crypt_tkip wl !b43 !ssb)

per the wiki. Doesn't work.

SiD · 2010-12-23 16:06:49

also if you put both modules (for wired and wireless device) in rc.conf and don't use a udev-rule at all?

futuremonkey · 2010-12-23 16:15:26

SiD wrote:

also if you put both modules (for wired and wireless device) in rc.conf and don't use a udev-rule at all?

Wired ethernet controller is RTL8101E/8102E [10ec:8136]

which apparently uses the r8169 module.

so,

MODULES=(r8169 lib80211_crypt_tkip wl ..... )

and it still doesn't work.

eldragon · 2010-12-23 17:00:20

hmmm,

NAME
The name, a network interface should be renamed to. Or as a
temporary workaraound, the name a device node should be named.
Usually the kernel provides the defined node name, or even creates
and removes the node before udev even receives any event. Changing
the node name from the kernel's default creates inconsistencies and
is not supported. If the kernel and NAME specify different names,
an error will be logged. Udev is only expected to handle device
node permissions and to create additional symlinks, not to change
kernel-provided device node names. Instead of renaming a device
node, SYMLINK should be used. Symlink names must never conflict
with device node names, it will result in unpredictable behavior.

try creating symlinks instead.

futuremonkey · 2010-12-23 23:17:31

I've given up, but I thank everyone for the help. I just can't understand why it all worked fine until I dared to reboot, at which point it became completely FUBAR. Oh well, so it goes.

Mr Green · 2010-12-24 06:59:12

Broadcom have recently updated there driver

http://www.broadcom.com/docs/linux_sta/README.txt

So guess AUR package is out of date

Do not give up

MrG

zenlord · 2010-12-24 08:39:07

SiD wrote:

also if you put both modules (for wired and wireless device) in rc.conf and don't use a udev-rule at all?

And another suggestion: completely disable udev autoload and specify all your modules inside the rc.conf? That way you can be sure it is udev-related. (it should be, but since I'm a broadcom-wl user myself and I have seen noone with the same problem as yours, it might be something not related to udev altogether?

Zl.

Arch Linux

#1 2010-12-23 15:14:39

interface names get swapped, but udev rules don't work

#2 2010-12-23 15:30:04

Re: interface names get swapped, but udev rules don't work

#3 2010-12-23 15:31:48

Re: interface names get swapped, but udev rules don't work

#4 2010-12-23 15:46:43

Re: interface names get swapped, but udev rules don't work

#5 2010-12-23 15:57:23

Re: interface names get swapped, but udev rules don't work

#6 2010-12-23 15:59:25

Re: interface names get swapped, but udev rules don't work

#7 2010-12-23 16:00:34

Re: interface names get swapped, but udev rules don't work

#8 2010-12-23 16:06:49

Re: interface names get swapped, but udev rules don't work

#9 2010-12-23 16:15:26

Re: interface names get swapped, but udev rules don't work

#10 2010-12-23 17:00:20

Re: interface names get swapped, but udev rules don't work

#11 2010-12-23 23:17:31

Re: interface names get swapped, but udev rules don't work

#12 2010-12-24 06:59:12

Re: interface names get swapped, but udev rules don't work

#13 2010-12-24 08:39:07

Re: interface names get swapped, but udev rules don't work

Board footer