Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Wireless--can't scan/associate (Broadcom card)[sorta-solved]
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
eliddell
n00b
n00b


Joined: 16 Nov 2004
Posts: 36

PostPosted: Fri Aug 29, 2008 6:54 pm    Post subject: Wireless--can't scan/associate (Broadcom card)[sorta-solved] Reply with quote

Update: After a bunch of messing around, downgrading the kernel to 2.6.25 because I needed vmware-server to work, etc etc ad nauseum, the wireless card has suddenly decided to successfully iwlist scan a network other than mine. I still don't know why, what changed, or why it won't work on my home network, but it looks like it probably isn't a driver problem after all.


I tried to get the wireless card on my laptop up and running back in May, got nowhere, and dropped it for a while. Now I'm trying again.

The card is a Broadcom 4311 (rev 02), and the laptop is a HP Pavilion dv6607. The b43 driver from the kernel appears to initialize the card correctly (the little blue LED even comes on, and the contents of dmesg indicate no show-stopping errors that I can identify) but I cannot scan or connect to my network using the card, even though the wireless router/access point is located not three feet away. I know the SSID for the network, the router's admin utility indicates it is being broadcast, and there is no security running on the network (and won't be until I get this working). I have tried both wireless-tools and wpa_supplicant. I have tried setting the SSID specifically as well as scanning. I have also tried ndiswrapper, and didn't get even as far with it as I did with b43 (I suppose there's a possibility I was using the wrong driver--I'm running a 64-bit system and 64-bit XP drivers seem to be hard to come by--but . . .) I haven't tried sacrificing a rubber chicken to the network gods while standing on my head in the shower at midnight, but that's mainly because I don't have a rubber chicken. ;P

Miscellaneous system information follows.

Relevant section of lspci -vnn:
Code:
03:00.0 Network controller [0280]: Broadcom Corporation BCM94311MCG wlan mini-PCI [14e4:4311] (rev 02)
        Subsystem: Hewlett-Packard Company Device [103c:1374]
        Flags: bus master, fast devsel, latency 0, IRQ 19
        Memory at f6000000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: [40] Power Management version 3
        Capabilities: [58] Vendor Specific Information <?>
        Capabilities: [e8] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable-
        Capabilities: [d0] Express Endpoint, MSI 00
        Kernel driver in use: b43-pci-bridge


dmesg | grep b43 (after some messing around eariler today):
Code:
b43-phy0: Broadcom 4311 WLAN found
b43-phy0 debug: Found PHY: Analog 4, Type 2, Revision 9
b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2
firmware: requesting b43/ucode13.fw
firmware: requesting b43/lp0initvals13.fw
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 64-bit DMA initialized
b43-phy0 ERROR: PHY transmission error
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-64 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 16/128, Failed frames 0/1507 = 0.0%, Average tries 0.89
b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 64-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-64 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 6/128, Failed frames 0/44 = 0.0%, Average tries 0.97
b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 64-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2
b43-phy0: Radio turned off by software
b43-phy0: Radio turned on by software
b43-phy0 debug: Removing Interface type 2
b43-phy0 debug: Wireless interface stopped
b43-phy0 debug: DMA-64 rx_ring: Used slots 0/64, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_BK: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_BE: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_VI: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0 debug: DMA-64 tx_ring_AC_VO: Used slots 10/128, Failed frames 0/1287 = 0.0%, Average tries 0.98
b43-phy0 debug: DMA-64 tx_ring_mcast: Used slots 0/128, Failed frames 0/0 = 0.0%, Average tries 0.00
b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10)
b43-phy0 debug: Chip initialized
b43-phy0 debug: 64-bit DMA initialized
b43-phy0 debug: Wireless interface started
b43-phy0 debug: Adding Interface type 2


Relevant section of ifconfig -a after ifconfig wlan0 up:
Code:
wlan0     Link encap:Ethernet  HWaddr 00:1A:73:BD:05:86 
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

wmaster0  Link encap:UNSPEC  HWaddr 00-1A-73-BD-05-86-60-00-00-00-00-00-00-00-00-00 
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


iwconfig wlan0:
Code:
wlan0     IEEE 802.11  ESSID:"" 
          Mode:Managed  Frequency:2.412 GHz  Access Point: Not-Associated   
          Tx-Power=27 dBm   
          Retry min limit:7   RTS thr:off   Fragment thr=2352 B   
          Encryption key:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0


one variant of wpa_supplicant.conf that I've experimented with:
Code:
# This is a network block that connects to any unsecured access point.
# We give it a low priority so any defined blocks are preferred.
network={
   key_mgmt=NONE
   priority=-9999999
}

#ap_scan = 1

network={
   ssid="SSRQ"
   scan_ssid=1
   key_mgmt=NONE
   priority=0
}


. . . and the results of wpa_supplicant -c/etc/wpa_supplicant/wpa_supplicant.conf -Dwext -iwlan0 -d (one iteration):
Code:
Initializing interface 'wlan0' conf '/etc/wpa_supplicant/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/etc/wpa_supplicant/wpa_supplicant.conf' -> '/etc/wpa_supplicant/wpa_supplicant.conf'
Reading configuration file '/etc/wpa_supplicant/wpa_supplicant.conf'
Priority group 0
   id=1 ssid='SSRQ'
Priority group -9999999
   id=0 ssid=''
Initializing interface (2) 'wlan0'
EAPOL: SUPP_PAE entering state DISCONNECTED
EAPOL: KEY_RX entering state NO_KEY_RECEIVE
EAPOL: SUPP_BE entering state INITIALIZE
EAP: EAP entering state DISABLED
EAPOL: External notification - portEnabled=0
EAPOL: External notification - portValid=0
SIOCGIWRANGE: WE(compiled)=22 WE(source)=21 enc_capa=0xf
  capabilities: key_mgmt 0xf enc 0xf
WEXT: Operstate: linkmode=1, operstate=5
Own MAC address: 00:1a:73:bd:05:86
wpa_driver_wext_set_wpa
wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0
wpa_driver_wext_set_countermeasures
ioctl[SIOCSIWAUTH]: Operation not supported
WEXT auth param 4 value 0x0 - wpa_driver_wext_set_drop_unencrypted
Setting scan request: 0 sec 100000 usec
Added interface wlan0
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b06 len=12
State: DISCONNECTED -> SCANNING
Starting AP scan (specific SSID)
Scan SSID - hexdump_ascii(len=4):
     53 53 52 51                                       SSRQ
Trying to get current scan results first without requesting a new scan to speed up initial association
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Selecting BSS from priority group -9999999
No suitable AP found.
Setting scan request: 0 sec 0 usec
Starting AP scan (broadcast SSID)
RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP])
Wireless event: cmd=0x8b19 len=16
Received 0 bytes of scan results (0 BSSes)
Scan results: 0
Selecting BSS from priority group 0
Selecting BSS from priority group -9999999
No suitable AP found.


I understand the "ioctl[SIOCSIWAUTH]: Operation not supported" to be harmless, and I can't see anything else wrong except the fact that this Is Not Working.

Help?


Last edited by eliddell on Fri Nov 14, 2008 11:47 pm; edited 1 time in total
Back to top
View user's profile Send private message
Xanadu
Guru
Guru


Joined: 10 Oct 2002
Posts: 335
Location: Hour West of Philly (USA)

PostPosted: Fri Aug 29, 2008 8:18 pm    Post subject: Reply with quote

I have one of these in my main machine (which I'm not on at the moment). I've been trying the b43* module for a while now. I even bumped the kernel up to 2.4.26 to see if it was any better. Well... I still went back to ndiswrapper. I haven't had a single issue using ndiswrapper with that card. I'm sorry that I can't sit here right now and give you the exact version of the firmware you'll need since I'm on a Windows box at work...

I can get to typing it out here later tonight from my machine so I can give exact versions of things.


eliddell wrote:
I haven't tried sacrificing a rubber chicken to the network gods while standing on my head in the shower at midnight, but that's mainly because I don't have a rubber chicken.


You forgot to be singing Louie Armstrong's "It's A Wonderful World" while doing so. That may also produce the issue you're seeing.
_________________
I'm not a prophet or a stone-age man
I'm just a mortal with potential of a super man

-David Bowie
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum