[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: kernel versus broadcom wlan



Florian Kulzer wrote:
[...]
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.

[...]
Yes, I have tried several firmware versions. The "bcm43xx" driver had reacted to one or the other - but with errors. The latest firmware-versions mentioned in these instructions are actually installed in /lib/firmware.
# 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.
[...]
Try to load the module manually (as root) with verbose messages:

modprobe -v b43

Hopefully that will give us a clue.

There is NO OUTPUT from the "-v" option. But the module gets loaded.
# lsmod |grep 43 :
b43                   119976  0
ssb                    39428  1 b43
rfkill                 12816  1 b43
pcmcia                 45720  2 b43,ssb
firmware_class         15232  2 43,pcmcia
led_class              10120  1 b43
input_polldev           9872  1 b43
pcmcia_core            46500  2 b43,pcmcia
mac80211              132236  1 b43
------------------------------------------------------------------
this looks quite correct, but it doesn't do any visible thing.

OH, an other thing: About every second boot hangs after the message:
"Synchronizing the System Clock" (or something like this)

Could this probably be cause by some fault while trying to install and activate the firmware?

Hugo


Reply to: