Holger Schurig wrote:
>>> When I power-up my device, I only see that ssb has been
>>> loaded. Not "b43.ko" as well. Is this expected?
>> Where were you looking?
> 
> If "b43.ko" has been loaded?  With lsmod:
> 
> # lsmod
> Module                  Size  Used by
> mousedev                5800  0
> ssb                    19204  0
> usbtouchscreen          3332  0
> 
>> In dmesg, you should see something 
>> like:
>>
>> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x11, vendor 0x4243)
>> ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x0A, vendor 0x4243)
>> ssb: Core 2 found: USB 1.1 Host (cc 0x817, rev 0x03, vendor 0x4243)
>> ssb: Core 3 found: PCI-E (cc 0x820, rev 0x01, vendor 0x4243)
>> ssb: Sonics Silicon Backplane found on PCI device 0000:01:00.0
>> b43-phy0: Broadcom 4311 WLAN found 
> 
> My output here is:
> 
> ssb: Core 0 found: ChipCommon (cc 0x800, rev 0x04, vendor 0x4243)
> ssb: Core 1 found: IEEE 802.11 (cc 0x812, rev 0x05, vendor 0x4243)
> ssb: Core 2 found: PCMCIA (cc 0x80D, rev 0x02, vendor 0x4243)
> ssb: Core 3 found: V90 (cc 0x807, rev 0x02, vendor 0x4243)
> ssb: Core 4 found: PCI (cc 0x804, rev 0x09, vendor 0x4243)
> ssb: Sonics Silicon Backplane found on PCI device 0000:03:00.0
> 
> And, because b43.ko doesn't get auto-loaded, I don't have a
> "b43-phy0"-line.
> 
> 
> 
> 
> I'm not sure if the following is relevant, but here is the
> output of "lspci -n":
> 
> 03:00.0 0280: 14e4:4320 (rev 03)
> 
> And if I manually "modprobe b43", I get this:
> 
> b43-phy0: Broadcom 4306 WLAN found
> b43-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2
> b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
> b43-phy0 debug: Radio turned off
> wmaster0: Selected rate control algorithm 'simple'
> 
> After "iwconfig eth1 essid XXXXX", "iwconfig eth1 key s:XXXXX"
> and "ifconfig eth1 up", I get this:
> 
> b43-phy0 debug: Adding Interface type 2
> b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02)
> b43-phy0 debug: Radio turned on
> b43-phy0 debug: Radio enabled by hardware
> b43-phy0 ERROR: bbatt(11) >= size of LO array
> b43-phy0 debug: Chip initialized
> b43-phy0 debug: 30-bit DMA initialized
> b43-phy0 debug: Wireless interface started
> HW CONFIG: channel=1 freq=2412 phymode=3
> b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: 
> ff:ff:ff:ff:ff:ff
> 
> But I'm pretty sure this is unrelated to auto-loading b43 :-)
> 
> 
> 
>> I assume that you meant b43 when you typed b32
> 
> Yes. That's why I did "dmesg >a" and "scp" for the texts above :-)
> 
> 
> 
>> you may also see errors like
>> b43-phy0 debug: Invalid LO control pair (I: 111, Q: 111)
>> and
>> b43-phy0 ERROR: Adjusting Local Oscillator to an uncalibrated control pair: 
>> rfatt=3,no-padmix bbatt=2
> 
> Fortunately not in my case.

Are you using openSUSE 10.2? If so, you need to add the following rule to 
/etc/udev/rules.d/80-sysconfig.rules:

SUBSYSTEM=="ssb", ACTION=="add", ENV{MODALIAS}=="?*", RUN+="/sbin/modprobe 
$env{MODALIAS}"

If you are running a different distribution, the change will probably be 
different, but it will be 
caused by udev not processing ssb events.

Larry
_______________________________________________
Bcm43xx-dev mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev

Reply via email to