Re: BCM94311MCG Rev 2 connects then drops on HP DV6605/ AMD64 X2
glenn greenfield wrote: eth0: no link during initialization. NET: Registered protocol family 10 lo: Disabled Privacy Extensions ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_UP): wlan0: link is not ready lp: driver loaded but no devices found ppdev: user-space parallel port driver wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:12:17:2f:bb:b6 wlan0: RX authentication from 00:12:17:2f:bb:b6 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:12:17:2f:bb:b6 wlan0: RX AssocResp from 00:12:17:2f:bb:b6 (capab=0x411 status=0 aid=2) wlan0: associated wlan0: CTS protection enabled (BSSID=00:12:17:2f:bb:b6) wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready Clocksource tsc unstable (delta = -158243821 ns) wlan0: no IPv6 routers present b43-phy0 debug: Removing Interface type 2 b43-phy0 debug: Wireless interface stopped b43-phy0 debug: DMA-64 0x0200 (RX) max used slots: 1/64 b43-phy0 debug: DMA-64 0x0340 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x0300 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x02C0 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x0280 (TX) max used slots: 0/128 b43-phy0 debug: DMA-64 0x0240 (TX) max used slots: 4/128 b43-phy0 debug: DMA-64 0x0200 (TX) max used slots: 0/128 input: b43-phy0 as /devices/virtual/input/input10 b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) b43-phy0 debug: Chip initialized b43-phy0 debug: 64-bit DMA initialized Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:radio b43-phy0 debug: Wireless interface started b43-phy0 debug: Adding Interface type 2 ADDRCONF(NETDEV_UP): wlan0: link is not ready eth0: no link during initialization. ADDRCONF(NETDEV_UP): eth0: link is not ready wlan0: CTS protection enabled (BSSID=00:12:17:2f:bb:b6) wlan0: RX deauthentication from 00:12:17:2f:bb:b6 (reason=16) wlan0: deauthenticated wlan0: privacy configuration mismatch and mixed-cell disabled - disassociate wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:12:17:2f:bb:b6 wlan0: RX deauthentication from 00:12:17:2f:bb:b6 (reason=6) wlan0: RX authentication from 00:12:17:2f:bb:b6 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:12:17:2f:bb:b6 wlan0: RX AssocResp from 00:12:17:2f:bb:b6 (capab=0x411 status=0 aid=2) wlan0: associated wlan0: CTS protection enabled (BSSID=00:12:17:2f:bb:b6) wlan0: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 wlan0: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 wlan0: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: no IPv6 routers present nvidia: module license 'NVIDIA' taints kernel. ACPI: PCI Interrupt Link [LGPU] enabled at IRQ 16 ACPI: PCI Interrupt :00:12.0[A] - Link [LGPU] - GSI 16 (level, low) - IRQ 16 PCI: Setting latency timer of device :00:12.0 to 64 NVRM: loading NVIDIA UNIX x86_64 Kernel Module 169.09 Fri Jan 11 14:04:37 PST 2008 b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error printk: 9 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 9 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 3 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 5 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 3 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 1 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 5 messages suppressed. b43-phy0 ERROR: PHY transmission error printk: 2 messages suppressed. b43-phy0 ERROR: PHY transmission error Perhaps I have the wrong firmware? I used what was in Debian on my first attempts but it seems that version is outdated or just incorrect for my wireless card. So I tried this: wget http://mirror2.openwrt.org/sources/broadcom-wl-4.150.10.5.tar.bz2 tar xjvf broadcom-wl-4.150.10.5.tar.bz2 cd broadcom-wl-4.150.10.5 b43-fwcutter -w /lib/firmware driver/wl_apsta_mimo.o Sorry, the
Re: BCM4311 issues on 2.6.24 kernel
Bryan Short wrote: Kind folks: I have an HP dv6408nr laptop. Here are the relevant things: [EMAIL PROTECTED] ~ $ sudo lsmod Password: Module Size Used by b43 149424 0 ndiswrapper 207264 0 rfkill_input6528 0 snd_seq_dummy 5508 0 snd_seq_oss33664 0 snd_seq_midi_event 9472 1 snd_seq_oss snd_seq55840 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 9876 3 snd_seq_dummy,snd_seq_oss,snd_seq genrtc 10892 0 vboxdrv 1633248 0 rfkill 9744 3 b43,rfkill_input mac80211 129164 1 b43 led_class 7048 1 b43 ohci_hcd 28164 0 input_polldev 6800 1 b43 nvidia 7007860 36 ssb39300 2 b43,ohci_hcd forcedeth 51212 0 snd_hda_intel 354212 1 sdhci 20100 0 i2c_nforce2 8064 0 pcmcia 42776 2 b43,ssb i2c_core 26752 2 nvidia,i2c_nforce2 mmc_core 55432 1 sdhci k8temp 7424 0 joydev 14464 0 e1000 122816 0 scsi_wait_scan 2816 0 sl811_hcd 14848 0 uhci_hcd 27168 0 ehci_hcd 36620 0 [EMAIL PROTECTED] ~ $ sudo ifconfig eth0 Link encap:Ethernet HWaddr 00:1B:24:54:04:DA inet addr:192.168.1.3 http://192.168.1.3 Bcast:192.168.1.255 http://192.168.1.255 Mask:255.255.255.0 http://255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:4528 errors:0 dropped:0 overruns:0 frame:0 TX packets:3797 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:5702598 (5.4 Mb) TX bytes:525825 (513.5 Kb) Interrupt:20 Base address:0xc000 loLink encap:Local Loopback inet addr:127.0.0.1 http://127.0.0.1 Mask:255.0.0.0 http://255.0.0.0 UP LOOPBACK RUNNING MTU:16436 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:0 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) wlan0 Link encap:Ethernet HWaddr 00:1A:73:6B:51:09 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-6B-51-09-60-5F-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) [EMAIL PROTECTED] ~ $ sudo iwlist wlan0 scan wlan0 Scan completed : Cell 01 - Address: 00:0F:B5:6C:B6:84 ESSID:Nosso Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Quality=95/100 Signal level=-63 dBm Noise level=-49 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:tsf=0124b60aef13 Cell 02 - Address: 00:17:3F:64:D8:92 ESSID:vjrk Mode:Master Channel:11 Frequency:2.462 GHz (Channel 11) Quality=81/100 Signal level=-88 dBm Noise level=-49 dBm Encryption key:on IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s; 36 Mb/s 48 Mb/s; 54 Mb/s Extra:tsf=037ffee2bff4 [136110.201872] b43-phy5: Broadcom 4311 WLAN found [136110.219394] b43-phy5 debug: Found PHY: Analog 4, Type 2, Revision 9 [136110.219419] b43-phy5 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 2 [136110.228889] phy5: Selected rate control algorithm 'simple' [136110.314214] input: b43-phy5 as /class/input/input12 [136110.617686] b43-phy5 debug: Loading
Last 4 patches from Michael
I have just tested the last four patches from Michael. Compilation is fine and no regressions that I have seen as of yet. My 4306 and 4318 are working just fine with the changes. -Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Does auto-loading of b43 work for you?
Larry Finger wrote: Has anyone used the new driver variation known as b43 from that branch of wireless-dev and gotten auto-loading at bootup of the b43 module on i386 or x86_64 platforms. It still doesn't work here even after upgrading to the latest version of udev. Before I post to LKML regarding this problem, I would like to get an idea if is restricted to my system, or if it is a general problem with x86 architectures. We know it works on PPC platforms. If your system is also failing, I would like to know your distro. Thanks, Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev Works fine here on my x86_64 gentoo install :) -Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 2.6.23-rc1-wireless-dev bcm43xx_mac80211 associates, but Ethernet appears broken
Larry Finger wrote: Jory A. Pratt wrote: Yes I am able to reproduce it. I have done upgraded and downgraded my enitre toolchain. exact same problem is present on my system when I try my 4306 and 4318. What encryption method are you using? Larry I use wep encryption on a WRT54G V3 with dd-wrt. I will work on it later tonight and see what I can come up with. -Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: firmware versions?
Johannes Berg wrote: Hi, We were just discussing the negative effects of having too many different firmwares (like the problem Andy ran into); if you're using the version 4 driver and have a different firmware than * 343.126 (this is the currently recommended one) * 351.1092 (I'm using that) could you reply with the version you're using? The driver prints something like: bcm43xx-phy0 debug: Loading firmware version 351.1092 (2006-05-13 03:13:11) when it loads. johannes ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev I am now able to use wireless-dev branch so I can post some info :) bcm43xx-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) bcm43xx-phy0 debug: Found PHY: Analog 2, Type 2, Revision 2 This is a 4306 mini-pci I picked up for the lappy I will test the 4318 later today as well :) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 2.6.23-rc1-wireless-dev bcm43xx_mac80211 associates, but Ethernet appears broken
Michael Buesch wrote:
On Friday 10 August 2007 04:27:33 Ehud Gavron wrote:
I have spent eight hours on this today and I can't find a way to do a
subset of the patches. I haven't quite given up, but I'm reaching a
point where I could use some insight. I didn't copy the list... but
feel free to if you think it of public value.
The only things that don't make obvious sense (TO ME) are
1. all the changes to bcm43xx_interrupt_handler I don't
understand what it NEEDS to be or why it WAS one way and IS another
2. @@ -2314,7 +2310,6 @@ static void bcm43xx_periodic_tasks_setup
{
struct delayed_work *work = dev-periodic_work;
-assert(bcm43xx_status(dev) ==
BCM43xx_STAT_INITIALIZED); this is a
removal with no insertion to replace it
It's an assertion. That doesn't generate code.
3. -if (likely(bcm43xx_status(dev) == BCM43xx_STAT_INITIALIZED)) {
+if (likely(bcm43xx_status(dev) = BCM43xx_STAT_STARTED))
{ -- shouldn't this be
BCM43xx_STAT_STARTED ???
(That's in bcm43xx_get_tx_stats() right?)
No, we are checking for Are we at least started here?.
So we need =STARTED. ==STARTED would do it, too, but that's
the same with the current code. STARTED would clearly be wrong.
I have other questions, but the code is blurring in front of my eyes.
Yeah, well. I think it does for everybody. ;)
I'm pretty sure that it's a bug in the toolchain (gcc or binutils
or maybe something else) that's triggered by this patch.
So the toolchain generating bad code and corrupting the data.
The weird thing, however, is that you said you were able to associate,
but not able to send that packet (it was a ping, or something like that?).
From the driver point of view it doesn't matter if we TX/RX an
association packet or some other packet. The codepaths are _exactly_
the same.
That is all _very_ strange. I never had such a weird bug
in my whole life.
Michael, I know you are busy. Could you please re-look at your patch,
and note the cases where you change
bcm43xx_status(dev) == BCM43xx_STAT_INITIALIZED
I think in the other cases you change them to
bcm43xx_status(dev) BCM43xx_STAT_STARTED
which makes sense to me... so I can't understand #3 above.
The patch looks absolutely correct to me, except the tiny tiny
part in the core-starting, where I already sent a patch to
you (you said it wouldn't help).
Any input would be appreciated.
PS No, I don't know this code. No I've never written a Linux driver.
I'm a newbie. I just happen to have a laptop that doesn't like the new
code and likes the old code for bcm43xx-mac80211. I'm not the only
one.
Huh? Someone else able to reproduce it??
Yes I am able to reproduce it. I have done upgraded and downgraded my
enitre toolchain. exact same problem is present on my system when I try
my 4306 and 4318.
-Jory
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 4311 works with fedora 7 but only at 1mb/s
Larry Finger wrote: John H. wrote: Did I misunderstand something? I thought some script was available or some easy way to use either bcm43xx or the new one. brennan says he has a script to just let you use the newer driver with higher mbps, but I have never heard back from him. I have no idea what he is/was talking about. Until late yesterday, the best performance was with the unaltered bcm43xx, or the port of that driver to mac80211. Today, the changes now propagating through the system make bcm43xx-mac80211 into the preferred driver. You should ask Fedora how soon those will make it into their development kernels (called Rawhide?). If you want to use this new code now, you will need to use git to get the contents of Linville's wireless-dev tree and get the patches from the mailing list, or I can post them on my FTP site. If you can wait a day or so, Linville should incorporate those patches. In either case, the new version auto-scales the rate to 54M for most cards. Even the BCM4318, which has been the most trouble, gets up to 19 Mbs receiving, and 12 transmitting. The BCM4311 gets 20 Mbs in both directions. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev The initial 5 patches have been applied already by John. There are only two patches left to apply. These patches are in the following thread. [PATCH] bcm43xx-mac80211: Make hwpctl optional (disabled by default) [PATCH] bcm43xx-mac80211: Remove the stackdump in rfatt/bbattassertion -Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
current mac80211 mb tree broken
drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c: In function 'bcm43xx_write_probe_resp_plcp': drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c:1152: error: too few arguments to function 'ieee80211_generic_frame_duration' drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c: In function 'bcm43xx_generate_probe_resp': drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.c:1213: error: too few arguments to function 'ieee80211_generic_frame_duration' make[5]: *** [drivers/net/wireless/mac80211/bcm43xx/bcm43xx_main.o] Error 1 -Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: 2.6.22-rc6, dhcp, promiscuous mode, and other things
Pavel Roskin wrote: Hello! On Tue, 2007-06-26 at 18:58 -0700, Ehud Gavron wrote: I've been alternately switching between 2.6.22-rc3 (Linville git tree) and 2.5.22-rc6 (Linville git tree as of today), henceforth rc3 and rc6 respectively. There have been significant changes in bcm43xx_mac80211 in its own git repository (http://bu3sch.de/git/wireless-dev.git), which improved things a lot. As far as I know, the changes are not in 2.6.22-rc6 yet, or you would have seen a backtrace. These changes do nothing for the 4311 nor the 4318 in current state. You are stuck waiting like the rest of the community. You can always use softmac which is what mainline is still using by default. The bcm4306 only throws a backtrace with certain revisions, not every user will see a backtrace, be glad if your one of them users. -Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Please pull latest and greatest bcm43xx
Michael Buesch wrote: John, Please pull for-linville branch of my tree. It contains a lot of bugfixes and makes a _big_ step towards mergability for mainline. It's not 100% ready for a merge, yet, but we are making good progress. The transmission power problems on the 4306, that were one of the big merge blockers, seem almost all fixed. I get good performance now. I also added lots of txpower debugging stuff so one can actually see what's going on and how it's scaling. Together with Michael Wu's sta-locking rewrite patch for mac80211 we have the most critical merge blockers resolved now. I'd like people to test this code. It will spew a big assertion failure and a stacktrace on loading. Ignore that for now. It's known and considered nonfatal for now. The following changes since commit 9181e959da76d85d688d8ec763702ed2f3b4edf9: John W. Linville: rt2x00firmware.c: include delay.h to avoid build error on ppc64 are found in the git repository at: http://bu3sch.de/git/wireless-dev.git/ for-linville Michael Buesch: bcm43xx-mac80211: Don't stop the mac80211 software queues in pwork. Merge branch 'master' of git://git.kernel.org/.../linville/wireless-dev bcm43xx-mac80211: Use the mac80211 provided workqueue bcm43xx-mac80211: Fix mutex leakage in pwork. bcm43xx-mac80211: Flush the workqueue to make sure periodic work has finished. bcm43xx-mac80211: Implement runtime debugging mechanism. bcm43xx-mac80211: Code to inject TX ring overflows. bcm43xx-mac80211: Rewrite the attenuation adjustment. Merge branch 'master' of git://git.kernel.org/.../linville/wireless-dev ssb: Fix maxpwr and itssi read. bcm43xx-mac80211: Add more txpower debugging. bcm43xx-mac80211: add debugfs file to manually control txpower bcm43xx-mac80211: Some LO cleanups Merge branch 'master' of git://git.kernel.org/.../linville/wireless-dev bcm43xx-mac80211: Use the dynamic min/max values for adjusting the attenuation. drivers/net/wireless/mac80211/bcm43xx/bcm43xx.h| 29 + .../wireless/mac80211/bcm43xx/bcm43xx_debugfs.c| 210 + .../wireless/mac80211/bcm43xx/bcm43xx_debugfs.h| 21 + .../net/wireless/mac80211/bcm43xx/bcm43xx_dma.c| 63 +++ .../net/wireless/mac80211/bcm43xx/bcm43xx_dma.h| 10 drivers/net/wireless/mac80211/bcm43xx/bcm43xx_lo.c | 107 ++-- drivers/net/wireless/mac80211/bcm43xx/bcm43xx_lo.h |6 .../net/wireless/mac80211/bcm43xx/bcm43xx_main.c | 64 +-- .../net/wireless/mac80211/bcm43xx/bcm43xx_phy.c| 515 --- .../net/wireless/mac80211/bcm43xx/bcm43xx_phy.h| 23 + .../net/wireless/mac80211/bcm43xx/bcm43xx_xmit.c | 18 + .../net/wireless/mac80211/bcm43xx/bcm43xx_xmit.h |2 drivers/ssb/pci.c | 12 include/linux/ssb/ssb_regs.h | 12 14 files changed, 693 insertions(+), 399 deletions(-) I am pleased with the performance on my pcmcia 4306 by all means now :) great work in that department. I test my bcm4318 as well it worked, but very unusable bit rate fluxuates so bad that you can not do anything consistent. Just want to make sure you know the code has been tested on both cards and were it stands ... Once again great work Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: bcm-43xx HORRIBLY slow with 4311 card and 2.6.20
Johannes Berg wrote: On Sun, 2007-04-08 at 03:42 -0500, John H. wrote: What do I do? Apply Larry's patches. I don't remember the URL and can't find it easily right now, you'll find it with some searching on this mailing list. johannes ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev ftp://lwfinger.dynalias.org/patches this is where you can find all the patches that you should be using at any given time that are not included in mainline kernel or will not be included into mainline before final is released for 2.6.21. Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
2050 radio init fix!!
Just so everyone is aware of how well development is coming along here is some proof. Larry you have done an awsome job bring the softmac up to a very usuable standard in todays modern home network!! Wireless interface testing using Iperf == Testing 802.11b/g bit rates Original Bit Rate of 36 Mbs will be restored Rate set to 5.5 Mbs with iwconfig Transmit rate: 3.38 3.32 3.49 3.38 3.36 Mbits/sec, Max: 3.49, Min: 3.32, Average: 3.39, Sigma: 0.06 Receive rate: 9.98 9.88 9.95 9.85 9.94 Mbits/sec, Max: 9.98, Min: 9.85, Average: 9.92, Sigma: 0.05 Rate set to 6 Mbs with iwconfig Transmit rate: 3.86 3.90 3.93 3.95 3.87 Mbits/sec, Max: 3.95, Min: 3.86, Average: 3.90, Sigma: 0.03 Receive rate: 11.5 11.8 11.7 11.8 11.8 Mbits/sec, Max: 11.8, Min: 11.5, Average: 11.7, Sigma: 0.1 Rate set to 9 Mbs with iwconfig Transmit rate: 5.15 5.05 5.12 5.14 5.11 Mbits/sec, Max: 5.15, Min: 5.05, Average: 5.11, Sigma: 0.03 Receive rate: 11.8 12.1 12.1 11.9 12.1 Mbits/sec, Max: 12.1, Min: 11.8, Average: 12.0, Sigma: 0.1 Rate set to 11 Mbs with iwconfig Transmit rate: 5.20 5.26 5.18 5.19 5.16 Mbits/sec, Max: 5.26, Min: 5.16, Average: 5.20, Sigma: 0.03 Receive rate: 9.96 10.3 10.3 10.2 10.3 Mbits/sec, Max: 10.30, Min: 9.96, Average: 10.21, Sigma: 0.13 Rate set to 18 Mbs with iwconfig Transmit rate: 7.51 7.62 7.59 7.40 7.60 Mbits/sec, Max: 7.62, Min: 7.40, Average: 7.54, Sigma: 0.08 Receive rate: 12.6 12.5 11.0 12.5 12.6 Mbits/sec, Max: 12.6, Min: 11.0, Average: 12.2, Sigma: 0.6 Rate set to 24 Mbs with iwconfig Transmit rate: 8.49 8.62 8.70 8.23 8.32 Mbits/sec, Max: 8.70, Min: 8.23, Average: 8.47, Sigma: 0.18 Receive rate: 12.4 12.6 12.6 11.6 8.98 Mbits/sec, Max: 12.6, Min: 9.0, Average: 11.6, Sigma: 1.4 Rate set to 36 Mbs with iwconfig Transmit rate: 8.97 9.83 10.3 10.4 10.3 Mbits/sec, Max: 10.40, Min: 8.97, Average: 9.96, Sigma: 0.53 Receive rate: 12.5 11.6 10.9 10.5 9.59 Mbits/sec, Max: 12.5, Min: 9.6, Average: 11.0, Sigma: 1.0 Rate set to 48 Mbs with iwconfig Transmit rate: 10.9 10.5 10.5 9.75 10.9 Mbits/sec, Max: 10.9, Min: 9.8, Average: 10.5, Sigma: 0.4 Receive rate: 11.3 11.3 11.7 7.97 8.02 Mbits/sec, Max: 11.7, Min: 8.0, Average: 10.1, Sigma: 1.7 Rate set to 54 Mbs with iwconfig Transmit rate: 8.43 10.0 9.03 11.6 11.5 Mbits/sec, Max: 11.60, Min: 8.43, Average: 10.11, Sigma: 1.28 Receive rate: 9.56 9.14 12.7 12.4 11.6 Mbits/sec, Max: 12.70, Min: 9.14, Average: 11.08, Sigma: 1.46 Bit Rate reset to original value Enojy the results and keep moving forward. 03:02.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02) Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problem with the lid closing event
Hendrik Sattler wrote: Am Dienstag 30 Januar 2007 16:22 schrieb Larry Finger: This is the software I installed: http://www.srcf.ucam.org/~mjg59/vbetool/ It won't even compile here. Perhaps it is because I have an x86_64 system. I don't have time to debug that program. You can use the debian package or its source: http://packages.debian.org/testing/utils/vbetool They have an amd64 package thus it should compile just fine. VBETOOLS is useless on x86_64, the package is only for i386 to i686 32bit machines, so your suggestion is useless in this case. Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: RFC: bcm43xx-d80211: Add radio hardware switch code to mb tree
Michael Buesch wrote:
On Wednesday 24 January 2007 20:08, Larry Finger wrote:
Michael Buesch wrote:
On Wednesday 24 January 2007 19:39, Larry Finger wrote:
switch (led_index) {
case 0:
led-behaviour = BCM43xx_LED_ACTIVITY;
+ led-activelow = 1;
Why activelow?
It makes the light be on when there is no activity and blink off when there
is. With that behavior,
it is a lot easier to see that the switch is on.
Ah, ok.
It's debatable if that behaviour is desireable.
I don't like it, but if people want to have it, we can implement it.
I do not think this is what people want. If the radio is off the light
should just be off, when radio is on turn the light on, is a much more
desirable.
Thanks,
-Jory
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
bcm4318
Well after doing a serious upgrade on my line I discovered just how bad off the bcm4318 truely is. I have a 3Mbp/s line and with bcm4318 I am lucky if I can utilize a 1/3rd of that. ( i.e =1.0Mbps ) Those who have this card might want to concider throwing it in the trash, it does not work with dscape and softmac development is dead if you read Micheal's post to the mail list. ALL development should only be done on wireless-dev tree :/ . So for now I will stick with my wired ethernet just so I get to use what I pay for. Just figured I would let you all know how bad off the bcm4318 truely is right now :/ If your interested in testing your line results see www.2wire.com and run their speed meter. Jory ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [PATCH] bcm43xx: use softmac-suggested TX rate
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Buesch wrote: Hi John, Sorry, took a little bit longer than expected, but here it is. :) Please queue for 2.6.18. -- From: Daniel Drake [EMAIL PROTECTED] Use Softmac-suggested TX ratecode: ieee80211softmac_suggest_txrate() Signed-off-by: Daniel Drake [EMAIL PROTECTED] Signed-off-by: Michael Buesch [EMAIL PROTECTED] Index: wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_xmit.c === --- wireless-2.6.orig/drivers/net/wireless/bcm43xx/bcm43xx_xmit.c 2006-06-14 16:53:50.0 +0200 +++ wireless-2.6/drivers/net/wireless/bcm43xx/bcm43xx_xmit.c 2006-06-14 17:44:23.0 +0200 @@ -296,11 +296,14 @@ u16 control = 0; u16 wsec_rate = 0; u16 encrypt_frame; + const u16 ftype = WLAN_FC_GET_TYPE(le16_to_cpu(wireless_header-frame_ctl)); + const int is_mgt = (ftype == IEEE80211_FTYPE_MGMT); /* Now construct the TX header. */ memset(txhdr, 0, sizeof(*txhdr)); - bitrate = bcm-softmac-txrates.default_rate; + bitrate = ieee80211softmac_suggest_txrate(bcm-softmac, + is_multicast_ether_addr(wireless_header-addr1), is_mgt); ofdm_modulation = !(ieee80211_is_cck_rate(bitrate)); fallback_bitrate = bcm43xx_calc_fallback_rate(bitrate); fallback_ofdm_modulation = !(ieee80211_is_cck_rate(fallback_bitrate)); Well I decided to take the plunge and test this for you all. Only problem is it fails to compile CC net/ieee80211/softmac/ieee80211softmac_io.o net/ieee80211/softmac/ieee80211softmac_io.c: In function 'ieee80211softmac_send_mgt_frame': net/ieee80211/softmac/ieee80211softmac_io.c:463: error: too many arguments to function 'ieee80211_tx_frame' make[3]: *** [net/ieee80211/softmac/ieee80211softmac_io.o] Error 1 make[2]: *** [net/ieee80211/softmac] Error 2 make[1]: *** [net/ieee80211] Error 2 make: *** [net] Error 2 I will look into it tomorrow night unless once of you get around to it before then. Jory -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEki3iGDfjNg8unQIRAhMzAJ4rvfbtJS2FiXyOMkf9lVI41QYDwQCgrmus K9z8D/x5HFCi1dGBMaF+fb0= =u26i -END PGP SIGNATURE- ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [PATCH, RTF/RFC] bcm43xx: Enable local IRQs while executing periodic work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Buesch wrote: On Sunday 28 May 2006 18:37, you wrote: On Sun, May 28, 2006 at 06:29:01PM +0200, Michael Buesch wrote: Well, I would like to know it for sure. ;) Could you load the kernel which crashed and look there. It is quite important to know if it is caused by a shared IRQ or not. OK, i'm running the kernel that crashed now. it's the same: Ok Jason, could you please test the following patch and try to reproduce with it? Jory, could you also test this patch on your machine with the shared bcm43xx IRQ? While testing, put some load on one of the devices sharing the IRQ with bcm43xx (I think it was eth0 for example). I have tested the hell out of the patch works great so far, no crash nothing of bad news to report here. I have done some intesive testing with eth0 and also done major testing with acpi as I disabled noapic on the boot options. So finall words would be to push it to 2.6.17-rc* as I am sure it will be a few more release canadites before it rolls out as final. Jory -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEelE1GDfjNg8unQIRAjAtAJ4k1CBAX1sX8li4hHzQkjdnwvovwQCdGAWm Gj7la0sFPldjftUP+PuSaPI= =yVFf -END PGP SIGNATURE- ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Great Work
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Well I have just gotten around to testing latest patch for 2.6.16-rc2, exceptional work. All XMIT ERROR's are just about resolved except when device attempts to suspend. I am gonna test proc entry patch a bit later today, time to see if it will work properly yet! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFD72BcGDfjNg8unQIRAnU/AJjWczTl3ysW1Xg+MESfI5chu14YAJ0W7Tnm 9tJ+3Kov/FZ+eWtn/ZRmsw== =QxuO -END PGP SIGNATURE- ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[Bcm43xx-dev] /proc/net/wireless?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Is there a reason we are not registering device completely yet? Main reason behind me finding this is I can not use my normal network configuration without an entry being in /proc/net/wireless. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFD0Bm3GDfjNg8unQIRAsU9AJ99aK5lny0mFCQmoadU8tsjqX+PrwCgiUew mUBcY5P1neX+jwb4XF2oTc4= =2vJV -END PGP SIGNATURE- ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bcm43xx-dev] errors using ck-sources-2.6.15
Michael Buesch wrote: On Thursday 05 January 2006 03:05, Jory A. Pratt wrote: bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x36802368, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x67802678, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x94002940, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0xa3802a38, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0xb4002b40, 0x2000, 0x2000 Seems to be an issue with schedular if this is correct any have a possible solution of how we can resolve the problem? This cannot be a scheduler issue. Please provide the whole dmesg output of the driver. bcm43xx driver 0.0.1 bcm43xx: Chip ID 0x4318, rev 0x2 bcm43xx: Number of cores: 4 bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled bcm43xx: PHY connected bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7 bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8) bcm43xx: Radio turned off bcm43xx: Radio turned off XFS mounting filesystem hda5 Ending clean XFS mount for filesystem: hda5 XFS mounting filesystem hda6 Ending clean XFS mount for filesystem: hda6 bcm43xx: PHY connected bcm43xx: InitVals written bcm43xx: Radio turned on bcm43xx: Chip initialized bcm43xx: DMA initialized bcm43xx: 80211 cores initialized bcm43xx: Keys cleared SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_assoc.c:149:ieee80211softmac_assoc_work() SoftMAC: Associate: Network not known, trying to initiate scan: SoftMAC: Start scanning with channel: 1 SoftMAC: Scanning 13 channels ok. SoftMAC: Flags for channel 1: SoftMAC: FIXME: Probing Channel 1 bcm43xx: set security called bcm43xx:.active_key = 0 bcm43xx:.level = 1 bcm43xx:.enabled = 1 bcm43xx:.encrypt = 1 SoftMAC: Flags for channel 2: SoftMAC: FIXME: Probing Channel 2 SoftMAC: Flags for channel 3: SoftMAC: FIXME: Probing Channel 3 SoftMAC: Flags for channel 4: SoftMAC: FIXME: Probing Channel 4 SoftMAC: Flags for channel 5: SoftMAC: FIXME: Probing Channel 5 SoftMAC: Flags for channel 6: SoftMAC: FIXME: Probing Channel 6 SoftMAC: Flags for channel 7: SoftMAC: FIXME: Probing Channel 7 SoftMAC: Flags for channel 8: SoftMAC: FIXME: Probing Channel 8 SoftMAC: Flags for channel 9: SoftMAC: FIXME: Probing Channel 9 SoftMAC: Flags for channel 10: SoftMAC: FIXME: Probing Channel 10 SoftMAC: Flags for channel 11: SoftMAC: FIXME: Probing Channel 11 SoftMAC: Flags for channel 12: SoftMAC: FIXME: Probing Channel 12 eth1: no IPv6 routers present SoftMAC: Flags for channel 13: SoftMAC: FIXME: Probing Channel 13 SoftMAC: Scanning finished SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_assoc.c:149:ieee80211softmac_assoc_work() SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_auth.c:13:ieee80211softmac_auth_req() SoftMAC: Queueing Authentication Request to 00:0d:72:bf:98:f1 SoftMAC: cannot associate without being authenticated, requested authentication SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue() SoftMAC: Sent Authentication Request to 00:0d:72:bf:98:f1. SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_auth.c:105:ieee80211softmac_auth_resp() SoftMAC: Open Authentication completed with 00:0d:72:bf:98:f1 SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_assoc.c:149:ieee80211softmac_assoc_work() SoftMAC: /home/anarchy/ieee80211softmac-20060102/ieee80211softmac_assoc.c:15:ieee80211softmac_assoc() SoftMAC: sent association request! SoftMAC: associated! bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x11002110, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x25802258, 0x2000, 0x2000 I have tried with the last 4 snapshots 01-04 all are giving same results also have tested with snapshots
[Bcm43xx-dev] latest svn with call trace
bcm43xx driver 0.0.1
bcm43xx: Chip ID 0x4318, rev 0x2
bcm43xx: Number of cores: 4
bcm43xx: Core 0: ID 0x800, rev 0xd, vendor 0x4243, enabled
bcm43xx: Core 1: ID 0x812, rev 0x9, vendor 0x4243, disabled
bcm43xx: Core 2: ID 0x804, rev 0xc, vendor 0x4243, enabled
bcm43xx: Core 3: ID 0x80d, rev 0x7, vendor 0x4243, enabled
bcm43xx: PHY connected
bcm43xx: Detected PHY: Version: 3, Type 2, Revision 7
bcm43xx: Detected Radio: ID: 8205017f (Manuf: 17f Ver: 2050 Rev: 8)
bcm43xx: Radio turned off
bcm43xx: Radio turned off
bcm43xx: PHY connected
bcm43xx: InitVals written
bcm43xx: Radio turned on
bcm43xx: ASSERTION FAILED (radio_attenuation 10) at:
/home/anarchy/broadcom/driver/bcm43xx_phy.c:1257:bcm43xx_find_lopair()
bcm43xx: WARNING: Writing invalid LOpair (low: 99, high: 104, index: 143)
Call Trace:8801cf97{:bcm43xx:bcm43xx_phy_lo_adjust+343}
8801ba5b{:bcm43xx:bcm43xx_phy_init_pctl+427}
8801e569{:bcm43xx:bcm43xx_phy_init+1625}
8800f4e8{:bcm43xx:bcm43xx_chip_init+1528}
88010210{:bcm43xx:bcm43xx_init_board+1072}
803beccd{dev_open+61}
803bdeaf{dev_change_flags+111}
803f8ead{devinet_ioctl+765}
803bfaa6{dev_ioctl+806}
803b4721{sock_ioctl+577} 80185b4b{do_ioctl+27}
80185e0b{vfs_ioctl+635} 80185e69{sys_ioctl+73}
8010f2d9{error_exit+0} 8010e9ae{system_call+126}
bcm43xx: Chip initialized
bcm43xx: DMA initialized
bcm43xx: 80211 cores initialized
bcm43xx: Keys cleared
SoftMAC:
/home/anarchy/source/ieee80211softmac_assoc.c:157:ieee80211softmac_assoc_work()
SoftMAC: Associate: Network not known, trying to initiate scan: SoftMAC:
Start scanning with channel: 1
SoftMAC: Scanning 13 channels
ok.
bcm43xx: set security called
bcm43xx:.active_key = 0
bcm43xx:.level = 1
bcm43xx:.enabled = 1
bcm43xx:.encrypt = 1
eth1: no IPv6 routers present
SoftMAC: Scanning finished
SoftMAC:
/home/anarchy/source/ieee80211softmac_assoc.c:157:ieee80211softmac_assoc_work()
SoftMAC:
/home/anarchy/source/ieee80211softmac_auth.c:13:ieee80211softmac_auth_req()
SoftMAC: Queueing Authentication Request to 00:0d:72:bf:98:f1
SoftMAC: cannot associate without being authenticated, requested
authentication
SoftMAC:
/home/anarchy/source/ieee80211softmac_auth.c:55:ieee80211softmac_auth_queue()
SoftMAC: Sent Authentication Request to 00:0d:72:bf:98:f1.
SoftMAC:
/home/anarchy/source/ieee80211softmac_auth.c:105:ieee80211softmac_auth_resp()
SoftMAC: Open Authentication completed with 00:0d:72:bf:98:f1
SoftMAC:
/home/anarchy/source/ieee80211softmac_assoc.c:157:ieee80211softmac_assoc_work()
SoftMAC:
/home/anarchy/source/ieee80211softmac_assoc.c:15:ieee80211softmac_assoc()
SoftMAC: sent association request!
SoftMAC:
/home/anarchy/source/ieee80211softmac_auth.c:105:ieee80211softmac_auth_resp()
SoftMAC: Authentication response received from 00:0d:72:bf:98:f1 but no
queue item exists.
SoftMAC: associated!
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
[Bcm43xx-dev] errors using ck-sources-2.6.15
bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x36802368, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x67802678, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0x94002940, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0xa3802a38, 0x2000, 0x2000 bcm43xx: XMIT ERROR bcm43xx: Generic Reason: 0x4d80 bcm43xx: DMA reasons:0x, 0x, 0x, 0x bcm43xx: DMA TX status: 0x2000, 0xb4002b40, 0x2000, 0x2000 Seems to be an issue with schedular if this is correct any have a possible solution of how we can resolve the problem? ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bcm43xx-dev] crypto code
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johannes Berg wrote: Since this is purely linux specific I figured I can submit... johannes Well after a bit of fooling around I got the bcm4318 AirForce One up and working. I had to drop to 11M for now to keep association, but other then that all is well. Thanks for the great job that has come so far. Keep up the great work. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDtcQZGDfjNg8unQIRAtSQAKCs0rwgmtKgvDNSd7CgNpn5k8ANDwCgi4Eh X1dYoltQQFUBwa15xqFA6ho= =PcOq -END PGP SIGNATURE- ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de http://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [Bcm43xx-dev] dscape: RX deauthentication (reason=15)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hisham Muhammad wrote: Hello, I'm trying to get bcm43xx-dscape to work. I'm using: * ieee80211-devicescape-051222 (applied fine on linux-2.6.15-rc6) * wpa_supplicant-0.4.7_dscape-02.patch * bcm43xx-dscape-20051226 I see packets being received and transmitted in sta0 in ifconfig, but no internet connection yet (yes, I did set route properly). dmesg shows this repeated over and over: HW CONFIG: channel=1 freq=2412 mode=2 phymode=3 HW CONFIG: channel=2 freq=2417 mode=2 phymode=3 HW CONFIG: channel=3 freq=2422 mode=2 phymode=3 HW CONFIG: channel=4 freq=2427 mode=2 phymode=3 HW CONFIG: channel=5 freq=2432 mode=2 phymode=3 HW CONFIG: channel=6 freq=2437 mode=2 phymode=3 HW CONFIG: channel=7 freq=2442 mode=2 phymode=3 HW CONFIG: channel=8 freq=2447 mode=2 phymode=3 HW CONFIG: channel=9 freq=2452 mode=2 phymode=3 HW CONFIG: channel=10 freq=2457 mode=2 phymode=3 HW CONFIG: channel=11 freq=2462 mode=2 phymode=3 HW CONFIG: channel=12 freq=2467 mode=2 phymode=3 HW CONFIG: channel=13 freq=2472 mode=2 phymode=3 HW CONFIG: channel=11 freq=2462 mode=2 phymode=3 sta0: scan completed HW CONFIG: channel=11 freq=2462 mode=2 phymode=3 HW CONFIG: channel=11 freq=2462 mode=2 phymode=3 sta0: Initial auth_alg=0 sta0: authenticate with AP 00:11:50:5c:a2:e2 sta0: RX authentication from 00:11:50:5c:a2:e2 (alg=0 transaction=2 status=0) sta0: authenticated sta0: associate with AP 00:11:50:5c:a2:e2 sta0: RX ReassocResp from 00:11:50:5c:a2:e2 (capab=0x431 status=0 aid=1) sta0: associated sta0: RX deauthentication from 00:11:50:5c:a2:e2 (reason=15) sta0: deauthenticated sta0: starting scan I also got this when running sta_up.sh: FIXME wpa_driver_dscape_set_countermeasures entered Any ideas on what I may be missing? Thanks in advance, -- Hisham I do not have same problem when I get up, but using wep is giving me a bit of a headache still. Attached is a log of part of dmesg that will show ya what I am talking about. If anyone has any suggestions or possible causes for what is happening here please let me know. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFDsPAOGDfjNg8unQIRAvovAKCRRaezvionQ+r93KSKvzRqJto0WACgqZal gMUxmBYCpPSb89HJqeaFrAc= =kWaA -END PGP SIGNATURE- sta0: using STA entry 0 sta0: MAC address 00:90:4b:f2:30:e9 bcm43xx: FIXME: Possibly broken code in bcm43xx_set_iwmode() at /home/anarchy/bcm43xx-dscape-20051226/bcm43xx_main.c:2449 bcm43xx: FIXME: Possibly broken code in bcm43xx_set_iwmode() at /home/anarchy/bcm43xx-dscape-20051226/bcm43xx_main.c:2449 sta0: starting scan sta0: scan completed sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: RX authentication from 00:0d:72:bf:98:f1 (alg=0 transaction=2 status=0) sta0: authenticated sta0: associate with AP 00:0d:72:bf:98:f1 sta0: associate with AP 00:0d:72:bf:98:f1 sta0: associate with AP 00:0d:72:bf:98:f1 sta0: association with AP 00:0d:72:bf:98:f1 timed out sta0: no IPv6 routers present wlan0.11: no IPv6 routers present sta0: starting scan sta0: scan completed sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: RX authentication from 00:0d:72:bf:98:f1 (alg=0 transaction=2 status=0) sta0: authenticated sta0: associate with AP 00:0d:72:bf:98:f1 sta0: authentication frame received from 00:0d:72:bf:98:f1, but not in authenticate state - ignored sta0: RX AssocResp from 00:0d:72:bf:98:f1 (capab=0x471 status=12 aid=1) sta0: AP denied association (code=12) sta0: associate with AP 00:0d:72:bf:98:f1 sta0: RX AssocResp from 00:0d:72:bf:98:f1 (capab=0x471 status=12 aid=1) sta0: AP denied association (code=12) sta0: associate with AP 00:0d:72:bf:98:f1 sta0: RX AssocResp from 00:0d:72:bf:98:f1 (capab=0x471 status=12 aid=1) sta0: AP denied association (code=12) sta0: association with AP 00:0d:72:bf:98:f1 timed out sta0: starting scan sta0: scan completed sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: RX authentication from 00:0d:72:bf:98:f1 (alg=0 transaction=2 status=0) sta0: authenticated sta0: associate with AP 00:0d:72:bf:98:f1 sta0: authentication frame received from 00:0d:72:bf:98:f1, but not in authenticate state - ignored sta0: associate with AP 00:0d:72:bf:98:f1 sta0: associate with AP 00:0d:72:bf:98:f1 sta0: association with AP 00:0d:72:bf:98:f1 timed out sta0: starting scan sta0: scan completed sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: Initial auth_alg=0 sta0: authenticate with AP 00:0d:72:bf:98:f1 sta0: RX authentication from 00:0d:72:bf:98:f1 (alg=0 transaction=2 status=0) sta0: authenticated sta0: associate with AP 00:0d:72:bf:98:f1 sta0: authentication frame received from 00:0d:72:bf:98:f1, but not in authenticate state -
