b43leacy connection speed
Hello I'm using b43legacy with a BCM4309 - 14e4:4324 (rev 02) card. Also the following might be useful for you to know: $ cat /sys/bus/ssb/devices/*/uevent PHYSDEVBUS=ssb MODALIAS=ssb:v4243id0812rev04 PHYSDEVBUS=ssb MODALIAS=ssb:v4243id0807rev01 PHYSDEVBUS=ssb MODALIAS=ssb:v4243id0812rev04 and I'm using firmware 3.130.20.0 the driver seems to be stable, but I only get 1Mbps bit rate wlan0 IEEE 802.11g ESSID:"my_essid" Mode:Managed Frequency:2.432 GHz Access Point: my_access_point_mac Bit Rate=1 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2346 B Link Quality=83/100 Signal level=-47 dBm Noise level=-68 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 my question is, is this a known limitation for the current state of the driver or I do I need to do something to set higher bit-rates? thanks Ioannis PS: a belated thank you to Larry for his fine work on this project and the excellent support he provides. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Updated Status on b43 driver and Fedora 7
Larry Finger wrote: Andrig T. Miller wrote: I booted a new Fedora kernel this morning, and it loaded the new b43 driver, and I still had the v4 firmware in /lib/firmware. The first time I connected it connected at 2 Mb/s, versus the 1 Mb/s that it used to connect at. I had needed to reboot a second time for an unrelated reason, and when it connected the next time I connected at 5 Mb/s, and I have been happily using my internal Broadcom 4318 wireless networking all day, without issue. Thanks for all the hard work, it is really paying off! It is connecting at 1 Mbs every time, the increases are the natural ramp-up of the rates. Why it differed from boot to boot is probably a matter of when you happened to check and how many transmissions happened before you looked. If your V4 firmware is still in /lib/firmware, then the Fedora kernel is a little behind the wireless-dev tree. Once the code that uses the new naming scheme hits their kernel, your wireless will probably stop working. Be prepared. Yes, the new driver is very solid. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev It's not that 'solid' on my chipset, at least not the one present in the Fedora kernel. I have a BCM4309 14e4:4324 (rev 02) chipset and it drops connection from time to time with this driver. It connects fine at 1Mbps, really quick link establishment, but maybe half an hour later it drops and reconnects again. There are lots of messages in the kernel log, I'm including here what I think is useful: this is what I get when it first initialises: b43-phy1: Broadcom 4306 WLAN found b43-phy1 debug: Found PHY: Analog 1, Type 2, Revision 1 b43-phy1 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 b43-phy1 debug: Radio turned off wmaster0: Selected rate control algorithm 'simple' b43-phy1 debug: Ignoring unconnected 802.11 core b43-phy1 debug: Adding Interface type 2 b43-phy1 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) b43-phy1 debug: Radio turned on b43-phy1 debug: Radio enabled by hardware b43-phy1 ERROR: bbatt(11) = size of LO array b43-phy1 debug: Chip initialized b43-phy1 debug: 30-bit DMA initialized b43-wlan: TODO: Incomplete code in keymac_write() at drivers/net/wireless/b43/main .c:753 * repeated several times* b43-phy1 debug: Wireless interface started ADDRCONF(NETDEV_UP): wlan0: link is not ready wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:30:bd:fe:23:83 wlan0: RX authentication from 00:30:bd:fe:23:83 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:30:bd:fe:23:83 wlan0: RX AssocResp from 00:30:bd:fe:23:83 (capab=0x411 status=0 aid=10) wlan0: associated wlan0: switched to short barker preamble (BSSID=00:30:bd:fe:23:83) ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready when it drops connection I get the following messages in dmesg: wlan0: No ProbeResp from current AP 00:30:bd:fe:23:83 - assume out of range b43-phy1 debug: Using software based encryption for keyidx: 0, mac: 00:30:bd:fe:23 :83 wlan0: No STA entry for own AP 00:30:bd:fe:23:83 wlan0: No STA entry for own AP 00:30:bd:fe:23:83 wlan0: No STA entry for own AP 00:30:bd:fe:23:83 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready b43-phy1 debug: Removing Interface type 2 b43-phy1 ERROR: MAC suspend failed b43-phy1 debug: Wireless interface stopped b43-phy1 debug: DMA-32 0x0260 (RX) max used slots: 1/64 b43-phy1 debug: DMA-32 0x0200 (RX) max used slots: 2/64 b43-phy1 debug: DMA-32 0x02A0 (TX) max used slots: 0/128 b43-phy1 debug: DMA-32 0x0280 (TX) max used slots: 0/128 b43-phy1 debug: DMA-32 0x0260 (TX) max used slots: 0/128 b43-phy1 debug: DMA-32 0x0240 (TX) max used slots: 0/128 b43-phy1 debug: DMA-32 0x0220 (TX) max used slots: 92/128 b43-phy1 debug: DMA-32 0x0200 (TX) max used slots: 0/128 b43-phy1 debug: Radio turned off b43-phy1 debug: Radio turned off b43-phy1 debug: Adding Interface type 2 this is the link quality info: Bit Rate=1 Mb/s Retry min limit:7 RTS thr:off Fragment thr=2346 B Link Quality=73/100 Signal level=-56 dBm Noise level=-41 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 is the SNR low? Is that why it drops the connection ? The router sits 3 meters away from my laptop, direct sight. thanks -Ioannis ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Larry Finger wrote: Ioannis Nousias wrote: iwconfig: eth1 IEEE 802.11b/g ESSID:My ESSID here Nickname:Broadcom 4306 Mode:Managed Frequency=2.432 GHz Access Point: my router's MAC here Bit Rate=24 Mb/s Tx-Power=14 dBm RTS thr:off Fragment thr:off Your interface has not authenticated. If it had, there would be an encryption key here. Link Quality=66/100 Signal level=-61 dBm Noise level=-66 dBm This is a low signal/noise. Attached is a patch that will cut the rate from 24M to 11M to see if that helps get you connected. Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 I'm not sure. Is there a log? nm-tool reports this: In the panel kicker applet used with NM on KDE, I get a progression bar. I guess it isn't universal. But, I think it reloads itself. In fact I can see it in dmesg. Is it possible that NM causes it to reload the module ? I don't think NM is doing it by itself. At least it doesn't do that on my system. When I unload the module, I have to manually reload it, and then reconnect. Larry Thanks, but no luck. I even tried with 1Mbps and still can't connect. with 11Mbps: Link Quality=58/100 Signal level=-64 dBm Noise level=-67 dBm with 1Mbps: Link Quality=68/100 Signal level=-59 dBm Noise level=-65 dBm -Ioannis PS: I can see wpa_supplicants being invoked by NM, so that part should be ok. root 5202 0.0 0.1 4948 1388 ?S08:46 0:00 /usr/sbin/wpa_supplicant -g /var/run/wpa_supplicant-global ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Larry Finger wrote: bcm43xx: TODO: Incomplete code in keymac_write() at /home/s0238762/Desktop/bcm43xx-softmac-sa/bcm43xx/bcm43xx_m ain.c:1146 ... bcm43xx: Keys cleared bcm43xx: Selected 802.11 core (phytype 2) ADDRCONF(NETDEV_UP): eth1: link is not ready I'm sitting 5meters apart from the router. The signal indication in NetworkManager is nearly full strength. at least we are getting there. Thanks The fact that you are seeing signal in NetworkManager means that scanning is working. Please send the output of the ifconfig and iwconfig commands once NM has tried to connect. during the time NM tries to connect ifconfig: eth1 Link encap:Ethernet HWaddr my MAC here inet6 addr: fe80::290:4bff:fe71:e8f5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8 errors:0 dropped:1 overruns:0 frame:0 TX packets:559 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:676 (676.0 b) TX bytes:28690 (28.0 KiB) Interrupt:11 Base address:0x8000 iwconfig: eth1 IEEE 802.11b/g ESSID:My ESSID here Nickname:Broadcom 4306 Mode:Managed Frequency=2.432 GHz Access Point: my router's MAC here Bit Rate=24 Mb/s Tx-Power=14 dBm RTS thr:off Fragment thr:off Link Quality=66/100 Signal level=-61 dBm Noise level=-66 dBm Rx invalid nwid:0 Rx invalid crypt:1 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 What percentage does NM reach before it stops trying? I'm not sure. Is there a log? nm-tool reports this: NetworkManager Tool State: connecting - Device: eth1 NM Path: /org/freedesktop/NetworkManager/Devices/eth1 Type: 802.11 Wireless Driver:bcm43xx Active:yes HW Address:my MAC Capabilities: Supported: yes Speed: 24 Mb/s Wireless Settings Scanning:yes WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Networks (* = Current Network) some neighbour's ESSID:Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, Strength 77%, Encrypted (WEP) *My ESSID: Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, Strength 89%, Encrypted (WPA) some other neighbour ESSID: Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, Strength 74% IP Settings: IP Address: 0.0.0.0 Subnet Mask: 0.0.0.0 Broadcast: 0.0.0.0 Gateway: 0.0.0.0 Primary DNS: 0.0.0.0 Secondary DNS: 0.0.0.0 Are you using any encryption? WPA-PSK with TKIP PS2: once loaded the module can not be removed. rmmod (or modprobe -r) do nothing on it. I have not seen this problem before. Are there any messages in the logs or on the console? $ sudo /sbin/modprobe -rv bcm43xx rmmod /lib/modules/2.6.21-1.3228.fc7/extra/bcm43xx/bcm43xx.ko rmmod /lib/modules/2.6.21-1.3228.fc7/extra/ieee80211/softmac/ieee80211softmac.ko rmmod /lib/modules/2.6.21-1.3228.fc7/extra/ieee80211/ieee80211.ko $ /sbin/lsmod | grep bcm43 bcm43xx 437384 0 ieee80211softmac 39168 1 bcm43xx ieee80211 38344 2 bcm43xx,ieee80211softmac But, I think it reloads itself. In fact I can see it in dmesg. Is it possible that NM causes it to reload the module ? thanks for you help -Ioannis ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
BCM4309 with bcm43xx-mac80211 and WPA
hi, does bcm43xx-mac80211 support WPA for the BCM4309 chipset ? It seems that the driver detects and initialised the card, but I can't connect to my router. I'm using NetworkManager and it does see my router, but doesn't connect to it. Not to mention that after a while the driver causes a system freeze. I'm using WPA PSK-TKIP I've also tried with the bcm43xx (and a V3 firmware), but that doesn't seem to recognise the card at all. 'dmesg' reports only this: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] bcm43xx driver and I don't get an interface associated to the card. thanks -Ioannis ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Larry Finger wrote: Ioannis Nousias wrote: hi, does bcm43xx-mac80211 support WPA for the BCM4309 chipset ? It seems that the driver detects and initialised the card, but I can't connect to my router. I'm using NetworkManager and it does see my router, but doesn't connect to it. Not to mention that after a while the driver causes a system freeze. I'm using WPA PSK-TKIP Yes, bcm43xx-mac80211 supports WPA. I don't know about the system freeze, but most problems in associating and authenticating with mac80211 are due to low signal strengths. The driver is improving, but still has problems. ok I see. I do get transmission errors (PHY). I've also tried with the bcm43xx (and a V3 firmware), but that doesn't seem to recognise the card at all. 'dmesg' reports only this: ieee80211_crypt: unregistered algorithm 'NULL' ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] I do not think that you selected IEEE802.11i TKIP encryption under the Generic IEEE802.11 stack when you configured your system. The message here is ieee80211_crypt: registered algorithm 'TKIP'. I am assuming that wpa_supplicant is available and started by NetworkManager. That is what happens on my system. Larry in the bcm43xx case, NetworkManager doesn't detect a wireless card at all. Its menu shows only 'Wired Network'. As I said, the card doesn't seem to be recognised. I was thinking to compile the latest version, but if I'm not mistaken, this: 'git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git' is the entire kernel source. Can I compile somehow the bcm43xx or bcm43xx-mac80211 only for my current kernel ? thanks ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4309 with bcm43xx-mac80211 and WPA
Larry Finger wrote: Ioannis Nousias wrote: in the bcm43xx case, NetworkManager doesn't detect a wireless card at all. Its menu shows only 'Wired Network'. As I said, the card doesn't seem to be recognised. What is the result of the command 'dmesg | grep bcm43xx'? bcm43xx driver nothing else I was thinking to compile the latest version, but if I'm not mistaken, this: 'git://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-dev.git' is the entire kernel source. Can I compile somehow the bcm43xx or bcm43xx-mac80211 only for my current kernel ? Yes, that is the complete source. What is your current kernel? Do you have kernel sources on your machine? Larry I'm using 2.6.21-1.3228.fc7 (that's Fedora 7) and I only heave the development package for my kernel, which is not a complete kernel source, but is enough to compile some kernel modules against it (I've tried with uvc-linux for instance) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
debug option
hello, does the driver have a 'run-time' option/parameter to enable printing of debug information or at least be more verbose ? basically I can't get it to work and it doesn't report any warning/error messages. The only information I have is the following: I'm using Fedora's 7 2.6.21 kernel on a Dell D800 laptop. I extracted the firmware from this file (using bcm43xx-fwcutter): http://boredklink.googlepages.com/wl_apsta.o modprobe reports this: $ sudo /sbin/modprobe -v bcm43xx insmod /lib/modules/2.6.21-1.3194.fc7/kernel/net/ieee80211/ieee80211_crypt.ko insmod /lib/modules/2.6.21-1.3194.fc7/kernel/net/ieee80211/ieee80211.ko insmod /lib/modules/2.6.21-1.3194.fc7/kernel/net/ieee80211/softmac/ieee80211softmac.ko insmod /lib/modules/2.6.21-1.3194.fc7/kernel/drivers/net/wireless/bcm43xx/bcm43xx.ko dmesg reports this: $ dmesg | tail ieee80211_crypt: registered algorithm 'NULL' ieee80211: 802.11 data/management/control stack, git-1.1.13 ieee80211: Copyright (C) 2004-2005 Intel Corporation [EMAIL PROTECTED] bcm43xx driver disabling and enabling the device again reports this (that's using the Fn-F2 key): usb 1-2: USB disconnect, address 4 atkbd.c: Unknown key pressed (translated set 2, code 0x88 on isa0060/serio0). atkbd.c: Use 'setkeycodes e008 keycode' to make it known. usb 1-2: new full speed USB device using uhci_hcd and address 5 usb 1-2: configuration #1 chosen from 1 choice i.e. I make sure the device is enabled (I can see it in hal device manager properly identified), but iwconfig says: $ /sbin/iwconfig lono wireless extensions. eth0 no wireless extensions. I also have a modprobe configuration file named 'modprobe.bcm43xx' with the following contents: $ cat /etc/modprobe.d/modprobe.bcm43xx alias pci:v14E4d0x4301sv*sd*bc*sc*i* bcm43xx alias pci:v14E4d0x4307sv*sd*bc*sc*i* bcm43xx alias pci:v14E4d0x4318sv*sd*bc*sc*i* bcm43xx alias pci:v14E4d0x4320sv*sd*bc*sc*i* bcm43xx alias pci:v14E4d0x4324sv*sd*bc*sc*i* bcm43xx alias pci:v14E4d0x4325sv*sd*bc*sc*i* bcm43xx mine has the 4324 id: $ /sbin/lspci -nn | grep -i bcm43 02:03.0 Network controller [0280]: Broadcom Corporation BCM4309 802.11a/b/g [14e4:4324] (rev 02) thank you -Ioannis PS: I used to have it working with ndiswrapper when I had Fedora Core 6, but I'd like to use the native driver now. I made sure the bcm43xx driver is not in modprobe's blacklist any more. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
