nm vs wireless on my lappy

Wed Jan 10 21:48:24 UTC 2007

Greetings all;

Things are too quiet on the NM list, so I'm going to ask here since its an 
FC5 install, 32 bit on a 64 bit lappy, an HP dv5210us with a broadcom 
bcm4318 radio in it.

I know the SSID, and that's set, and the key for that SSID is also set.

But when I pull the eth0 cable, NM then logs this:

Jan 10 16:04:21 diablo kernel: ieee80211: 802.11 data/management/control 
stack, git-1.1.13
Jan 10 16:04:21 diablo kernel: ieee80211: Copyright (C) 2004-2005 Intel 
Corporation <jketreno at linux.intel.com>
Jan 10 16:04:21 diablo kernel: bcm43xx driver
Jan 10 16:04:21 diablo kernel: ACPI: PCI Interrupt 0000:03:02.0[A] -> Link 
[LNKF] -> GSI 10 (level, low) -> IRQ 10
Jan 10 16:04:21 diablo kernel: bcm43xx: Chip ID 0x4318, rev 0x2
Jan 10 16:04:21 diablo kernel: bcm43xx: Number of cores: 4
Jan 10 16:04:21 diablo kernel: bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 
0x4243, enabled
Jan 10 16:04:21 diablo kernel: bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 
0x4243, disabled
Jan 10 16:04:21 diablo kernel: bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 
0x4243, enabled
Jan 10 16:04:21 diablo kernel: bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 
0x4243, enabled
Jan 10 16:04:21 diablo kernel: bcm43xx: PHY connected
Jan 10 16:04:21 diablo kernel: bcm43xx: Detected PHY: Version: 3, Type 2, 
Revision 7
Jan 10 16:04:21 diablo kernel: bcm43xx: Detected Radio: ID: 8205017f 
(Manuf: 17f Ver: 2050 Rev: 8)
Jan 10 16:04:21 diablo kernel: bcm43xx: Radio turned off
Jan 10 16:04:21 diablo kernel: bcm43xx: Radio turned off
Jan 10 16:04:21 diablo kernel: SoftMAC: ASSERTION FAILED (0) at: 
net/ieee80211/softmac/ieee80211softmac_wx.c:306:ieee80211softmac_wx_get_rate()
Jan 10 16:04:21 diablo kernel: SoftMAC: empty ratesinfo?
Jan 10 16:04:21 diablo kernel: SoftMAC: empty ratesinfo?
Jan 10 16:04:21 diablo kernel: bcm43xx: set security called, .level = 
0, .enabled = 0, .encrypt = 0
Jan 10 16:04:21 diablo kernel: SoftMAC: Associate: Scanning for networks 
first.
Jan 10 16:04:21 diablo kernel: SoftMAC: Associate: failed to initiate 
scan. Is device up?
Jan 10 16:04:21 diablo kernel: bcm43xx: PHY connected
Jan 10 16:04:21 diablo kernel: bcm43xx: Microcode rev 0x13f, pl 0x66 
(2005-10-15  22:46:19)
Jan 10 16:04:21 diablo kernel: bcm43xx: Firmware: no support for microcode 
rev > 0x128
Jan 10 16:04:21 diablo kernel: bcm43xx: core_up for active 802.11 core 
failed (-1)
Jan 10 16:04:38 diablo kernel: SoftMAC: empty ratesinfo?
Jan 10 16:04:38 diablo kernel: SoftMAC: empty ratesinfo?
Jan 10 16:04:38 diablo kernel: bcm43xx: set security called, .level = 
0, .enabled = 0, .encrypt = 0
Jan 10 16:04:38 diablo kernel: SoftMAC: Canceling existing associate 
request!
Jan 10 16:04:38 diablo kernel: SoftMAC: Associate: Scanning for networks 
first.
Jan 10 16:04:38 diablo kernel: SoftMAC: Associate: failed to initiate 
scan. Is device up?
Jan 10 16:04:38 diablo kernel: bcm43xx: Microcode rev 0x13f, pl 0x66 
(2005-10-15  22:46:19)
Jan 10 16:04:38 diablo kernel: bcm43xx: Firmware: no support for microcode 
rev > 0x128
Jan 10 16:04:38 diablo kernel: bcm43xx: core_up for active 802.11 core 
failed (-1)

This is with the kernels own bcm43xx driver loaded.

Now if I rmmod it, and modprobe ndiswrapper which is setup around the 
winderz driver (which I did have working about 9 months ago, so I know it 
works), and repeat this exercise, I get this:
an 10 16:23:48 diablo kernel: ndiswrapper version 1.25 loaded 
(preempt=no,smp=no)
Jan 10 16:23:48 diablo kernel: ndiswrapper: driver bcmwl5a 
(Broadcom,02/11/2005, 3.100.64.0) loaded
Jan 10 16:23:48 diablo kernel: ACPI: PCI Interrupt 0000:03:02.0[A] -> Link 
[LNKF] -> GSI 10 (level, low) -> IRQ 10
Jan 10 16:23:48 diablo kernel: ndiswrapper: using IRQ 10
Jan 10 16:23:49 diablo kernel: wlan0: vendor: ''
Jan 10 16:23:49 diablo kernel: wlan0: ethernet device 00:14:a5:75:32:c9 
using NDIS driver bcmwl5a, 14E4:4318:103C:1355.5.conf
Jan 10 16:23:49 diablo kernel: wlan0: encryption modes supported: WEP; 
TKIP with WPA, WPA2, WPA2PSK; AES/CCMP with WPA, WPA2, WPA2PSK
Jan 10 16:23:49 diablo kernel: usbcore: registered new driver ndiswrapper
Jan 10 16:23:49 diablo kernel: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
Jan 10 16:23:55 diablo kernel: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready
Jan 10 16:23:55 diablo NetworkManager: <information>    wlan0: Device is 
fully-supported using driver 'ndiswrapper'.
Jan 10 16:23:55 diablo NetworkManager: <information>    nm_device_init(): 
waiting for device's worker thread to start
Jan 10 16:23:55 diablo NetworkManager: <information>    nm_device_init(): 
device's worker thread started, continuing.
Jan 10 16:23:55 diablo NetworkManager: <information>    Now managing 
wireless (802.11) device 'wlan0'.
Jan 10 16:23:55 diablo NetworkManager: <information>    Deactivating 
device wlan0.

Then I also tried to activate it with the network-configuration gui, and 
got this:

Jan 10 16:25:03 diablo NetworkManager: nm_device_is_802_3_ethernet: 
assertion `dev != NULL' failed
Jan 10 16:25:03 diablo NetworkManager: nm_device_is_802_11_wireless: 
assertion `dev != NULL' failed
Jan 10 16:26:13 diablo kernel: ADDRCONF(NETDEV_UP): wlan0: link is not 
ready

But the indicator led is on, and kwifimanager detects it and displays the 
SSID, but says the quality is 0, and wifi radar also fails but floods the 
log with meaningless commercial drivel from isc.

Obviously from the log, my year old radio is still too new for the kernel 
driver.  The latest non-smp kernel is installed and running, 
2.6.18-1.2257-fc5.  But then again, 2.6.18 is pretty darned old too.

Can anyone see what the next thing I need to address is to restore this to 
working?

Thanks folks.

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2007 by Maurice Eugene Heskett, all rights reserved.