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: Updated Status on b43 driver and Fedora 7
On Fri, Aug 24, 2007 at 05:50:12PM -0500, Larry Finger wrote: 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. FWIW, this isn't quite true -- at least not in F7. It is true in rawhide, and I'm a bit surprised that no one has complained yet... :-) In F7 I am carrying a patch to reverse the change to the new firmware format. I want to keep F7 near wireless-dev's head, but I didn't want to break a bunch of existing configurations. I haven't quite figured-out how long I'm going to carry this in F7. It will not be in F8. Just curious, what was the motivation for the new firmware format? Can the new format be quickly described in high level terms? I'm wondering if a tool could easily convert the old firmware format to the new, so that we might add it as an upgrade tool for F8. Thanks, John -- John W. Linville [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Which module
Ok, I have been trying to make heads or tails of it, which driver do I need to use for the broadcom 4311 dell wlan 1390. Is it b43 or bcm43xx? I have just upgraded a fedora 7 installation to 2.6.22.4-65 and want to give the native driver a try again. Thanks in advance for any assistance. -- John Registered Linux User 263680, get counted at http://counter.li.org ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Which module
John Pierce wrote: Ok, I have been trying to make heads or tails of it, which driver do I need to use for the broadcom 4311 dell wlan 1390. Is it b43 or bcm43xx? I have just upgraded a fedora 7 installation to 2.6.22.4-65 and want to give the native driver a try again. You may use either one. The driver supported by mainstream kernels is bcm43xx, which uses SoftMAC as its MAC layer. The driver named b43, which uses mac80211 as its MAC layer, will be replacing bcm43xx in mainstream in the coming months. If that F7 kernel offers b43 as an option, use it. The performance of the two drivers is essentially the same; however, the stability and flexibility of mac80211 is a great improvement over SoftMAC. For completeness, there is yet another driver for the BCM43xx chips that is named b43legacy. It is used for any 802.11b cards/chips and for one older variant of the BCM4306 802.11g chip. If you happen to see a reference to bcm43xx-mac80211, that is the old name for b43. Larry ___ 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
Ioannis Nousias wrote: 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. I'm a little surprised that that device works with b43. From the revisions that are in your mail, I would have expected it to use b43legacy. Please send the extract from the dmesg output that looks 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
Re: Updated Status on b43 driver and Fedora 7
On Monday 27 August 2007 17:00:18 Johannes Berg wrote: It is certainly not impossible, you can easily map the old to the new names and write a script that renames them, adds the header and In theory. In practice not. How do you reliably map the random initvalsXX naming to the new one? I don't even know what initvals05 (for random example) is. Do you? Why not simply start from a safe and clean point. Auto-download the new firmware from your pre-install scripts and be done with it. Network connectivity was always required for installing the broadcom driver. Why should this change now? -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Which module
On Mon, 2007-08-27 at 10:56 -0500, Larry Finger wrote: You may use either one. The driver supported by mainstream kernels is bcm43xx, which uses SoftMAC as its MAC layer. The driver named b43, which uses mac80211 as its MAC layer, will be replacing bcm43xx in mainstream in the coming months. If that F7 kernel offers b43 as an option, use it. The performance of the two drivers is essentially the same; however, the stability and flexibility of mac80211 is a great improvement over SoftMAC. The F7 kernel should currently use bcm43xx-mac80211 by default. If you fetch http://david.woodhou.se/bcm43xx-override and put it in /etc/modprobe.d then you'll use the softmac bcm43xx driver instead. That might be worth a try if you have problems with the mac80211 version. Note that each of those require firmware extracted from different versions of the 'official' drivers. -- dwmw2 ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card rev 02
Dru Devore wrote: I wrote this group about this card, Broadcom Corporation Dell Wireless 1390 WLAN Mini-PCI Card rev 02, a couple of weeks ago and got some information from Larry, Thank you Larry. I have been seeing a lot of messages lately about the b43 and was wondering if it would possibly work with this chip. If not what can I do to help the support for this card. Also, if anyone knows how to get this card to work in any way without locking up the OS I would appreciate that information also. I am currently using ndisswrapper and it is freezing the whole OS. I need this to work so I can get back off windows, vista, on this computer. That chip is what I use with b43. It does not freeze the computer. You need to get a mainstream kernel from kernel.org that is 2.6.21, or later. Those kernels use the bcm43xx driver. Alternatively, you can get the kernel from John Linville's wireless-dev git tree and build b43 for it. You will also need to install the supported firmware for your driver by downloading the appropriate version of wl_apstaXXX.o, installing fwcutter, and extracting the embedded codes. For bcm43xx, you will need V3 and use bcm43xx-fwcutter. For b43, you will need V4 and b43-fwcutter. Don't blame us for the complications here. It is Broadcom's fault. The archives of the mailing list and the bcm43xx site have a lot of explanation on how to do this. Alternatively, go to the forums of your distro. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
