On Tue, 29 Jan 2008 11:11:19 -0700 "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> I have got the Broadcom WLAN Chip BCM943111MCG in my PC. > "b43-fwcutter" installed some firmware. > But it works in Debian SID with ndiswrapper only so far. > But, you know, ndiswrapper imports parts of WINDOWS into Debian. I don't > want that. > > Searching the web have I found, that there are two new Linux drivers: > > * b43 > * b43legacy > > I didn't find these in a Debian kernel source. > So I have built my new kernel from 2.6.24 > <http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.24.tar.bz2> from > kernel.org > > Now it seems, that the b43 kernel module does not serve the hardware, > but ssb does: b43 depends on ssb > ###$ lshw -C net description: Network controller > product: BCM94311MCG wlan mini-PCI > vendor: Broadcom Corporation > physical id: 0 > bus info: [EMAIL PROTECTED]:03:00.0 > version: 02 > width: 64 bits > clock: 33MHz > capabilities: bus_master cap_list > configuration: driver=b43-pci-bridge latency=0 module=ssb > > > ^^^^^^^^ > If I understand things correctly, then should the module be: module=b43 > rather. > > > ^^^^^^^^ > Googling tells me, that this problem is caused by "udev" and could be > corrected by an entry in the file > > * z75_persistent-net.rules, which I suppose, is in Debian > /etc/udev/rules.d/z25_persistent-net-rules, which looks in my > system after trials of modifications like this: > > ------------------------------------------------------- > SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:24:aa:41:9d", > NAME="eth0" > > SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:00:00:1a:73:a8", > ATTRS{type}=="1", NAME="wlan0" > > SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1a:73:a8:0f:1f", > ATTRS{type}=="1", NAME="eth1" > --------------------------------------------------------- > > When googling deeper, I run into discrepancies: > Is the adding of ATTRS{type}=="1", correct > or should it be ATTR{type}=="1" without "S"? I use ATTRS; it works. > And the names of the device seem to vary from distribution to distribution: > from "wlan0" ... "eth2". > What is correct in the Debian environment? I believe it's your choice; you can tell udev to name an interface anything you want. > Something is still wrong with my system. > Does anybody have some clue, how to get this Wireless LAN up and running > in Debian? See my other mail in this thread about the ML; and also take a look at this page: http://linuxwireless.org/en/users/Drivers/b43 > Hugo Celejar -- mailmin.sourceforge.net - remote access via secure (OpenPGP) email ssuds.sourceforge.net - A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
