Re: kernel versus broadcom wlan

On Wed, Jan 30, 2008 at 12:25:46 -0700, wauhugo AT yahoo DOT com wrote:
Florian Kulzer wrote:

[...]

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?).

So in my system is only the MASTER, the SSB part being recognized and
activated?

[...]

How can I see, whether the FIRMWARE has been loaded or not?
"ndiswrapper" uses a different firmware
<http://h10025.www1.hp.com/ewfrf/wc/genericSoftwareDownloadIndex?softwareitem=ob-46095-1&cc=us&lc=en&dlc=en&dlc=en&lang=en>,


than the "b43-fwcutter" or "bcm43xx-fwcutter" thingy, which install a
different versions by default. The versions, used by "ndiswrapper" are
having wrong checksums.

Did you try to follow these instructions?

http://linuxwireless.org/en/users/Drivers/b43#devicefirmware

Celejar posted this link earlier; it looks like a good source of
information to me.

[...]

# cat z25_persistent-net.rules:
# This file was automatically generated by the /lib/udev/write_net_rules
# program run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single line.

# PCI device 0x10de:0x0269 (forcedeth)
SUBSYSTEM=="net", DRIVERS=="?*", ATTR{address}=="00:1b:24:aa:41:9d", NAME="eth0"
-------------------------------------------------
That is all.

That is an nvidia MCP51 Ethernet Controller, your wired ethernet. Udev
is not aware of the broadcom interface at all. I think this indicates a
problem with loading the b43 module.

and the
full output of "/sbin/ifconfig"
# /sbin/ifconfig:
eth0 Link encap:Ethernet HWaddr 00:1b:24:aa:41:9d inet
addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21b:24ff:feaa:419d/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

[...]

------------------------------------------------------
just the cable, no Wireless LAN interface up.
and "dmesg|grep b43".

-----------------------------------------------------
nothing, no output. Even searching through /var/log for a string "b43"
delivers only results connected with "aptitude".

Try to load the module manually (as root) with verbose messages:

modprobe -v b43

Hopefully that will give us a clue.

--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |


--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx
with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages