hardy udev b43 wlan0_rename fix

Bug #202575 reported by el es
2
Affects Status Importance Assigned to Milestone
udev (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: udev

Current Hardy 8.04 latest beta (done yesterday a dist upgrade from Gutsy)

When I managed to get the b43 kernel driver to work, as in this solution:
https://bugs.launchpad.net/ubuntu/+source/b43-fwcutter/+bug/202567

I noticed that udev creates the wlan0_rename interface;

The fix, according to Larry Finger on bcm43xx-dev mailing list is :

----
It is a mac80211-introduced "problem". With bcm43xx-softmac, there is only a single device
presented, and one does not care what type it is when it is renamed. With mac80211 (used by b43), at
least two devices are available, wmaster0 with type==0x801, and wlan0 with type==1. Without the
ATTRS{type==1} clause, wmaster=>eth1 and wlan0=>wlan0_rename. With the clause, only wlan0 is subject
to renaming and all works OK.
----

So far the situation is that Network Manager Applet displays 2 different interfaces for the wi-fi card : one is eth1 (and both are shown as WIRED apparently...).

The temporary solution is (again, published on bcm43xx mailing list):
1. go to /etc/udev/rules.d
2. sudo mcedit 70-persistent-net.rules
3. comment out the line
# PCI device 0x14e4:0x4318 (bcm43xx)
# SUBSYSTEM=="net", DRIVERS=="?*", ATTRS{address}=="00:0e:9b:bf:af:f4", NAME="eth1" <this line

4. save, exit back to terminal
5. sudo rmmod b43
6. sudo modprobe b43
7. udev will add a line like this to the aforementioned file:

# PCI device 0x14e4:0x4318 (b43-pci-bridge)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0e:9b:bf:af:f4", ATTR{type}=="1", NAME="wlan0"

Now the Network Manager shows the wlan0 interface correctly as wireless adaptor.

Did this, works for me.

el es (el-es-poczta)
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.