On Tue, Jan 29, 2008 at 18:00:42 -0700, wauhugo AT yahoo DOT com wrote: > Florian Kulzer wrote: >> The two b43* modules depend on the mac80211 stack instead of the >> ieee80211 one; with a self-compiled kernel and an older "inherited" >> configuration file you might first have to activate the new stack in >> "Networking > Wireless" to be able to select the b43* modules in "Device >> driver > Network device support > Wireless LAN". >> >> > Before posting on this list had I read through some posts, which > describe the same effect, which I see. And finally the "ssb" versus > "b43" issue had there been blamed on "udev" rules: > http://bugzilla.kernel.org/show_bug.cgi?id=9402#c14 > http://bugzilla.kernel.org/show_bug.cgi?id=9402#c12 > > But the posts, which I had read were not for original Debian. > > I want a solution for Debian but I don't understand "udev", nor many > other things in depth.
Udev is responsible for managing the device nodes in /dev and the names of the network devices. More information is here: /usr/share/doc/udev/writing_udev_rules/index.html The two bugzilla links above suggest that this chip will show up as two network interfaces when using the new driver, one is the interface that you will use normally and the other one is some sort of "master" (maybe related to this sbb bus?). Udev tries to ensure correct and persistent naming of network devices: Whenever a network device with an unknown hardware address (and a working associated driver) is detected during boot, udev will add a rule for this new HW address to the /etc/udev/rules.d/z25_persistent-net.rules file. Udev makes an "educated guess" about the best name for the new device, and this name will stick with the device from then on. The problem with the broadcom chip appears to be that the firmware is not present at the first boot of a Debian system, so only the master device is detected and added to z25_persistent-net.rules. This seems somehow to block correct name assignment for the "real" (usable) device (later, when the firmware has been installed). The bugzilla links suggest that you can simply delete or rename the persistent-net.rules file and reboot. With the firmware present udev obviously creates the rules for the two interfaces at once and correctly. If this does not work then we need to see the content of the rules file (after its re-creation with the firmware present during boot) and the full output of "/sbin/ifconfig" and "dmesg|grep b43". -- Regards, | http://users.icfo.es/Florian.Kulzer Florian | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
