Re: b43legacy-phy3: Radio hardware status changed to XXX
On 02/06/2010 06:49 PM, strk wrote: > On Sat, Feb 06, 2010 at 06:29:03PM -0600, Larry Finger wrote: >> On 02/06/2010 06:22 PM, strk wrote: >>> On Sat, Feb 06, 2010 at 06:20:15PM -0600, Larry Finger wrote: >>> You could probably avoid the problems by disabling the RFKILL and RFKILL_INPUT options. >>> >>> How do I do that ? Runtime ? Compile-time ? >> >> It needs to be compile time to elimionate that section of b43legacy. > > Thanks. Is there a repository from which I can get *only* > bcm43xx sources and compile against kernel headers ? > I've seen this done with debian module-assistant tool... You can get the wireless-compat sources for kernel 2.6.26 and build that. Othersise, go to kernel.org and get the full sources. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
On Sat, Feb 06, 2010 at 06:29:03PM -0600, Larry Finger wrote: > On 02/06/2010 06:22 PM, strk wrote: > > On Sat, Feb 06, 2010 at 06:20:15PM -0600, Larry Finger wrote: > > > >> You could probably avoid the problems by disabling the RFKILL and > >> RFKILL_INPUT > >> options. > > > > How do I do that ? Runtime ? Compile-time ? > > It needs to be compile time to elimionate that section of b43legacy. Thanks. Is there a repository from which I can get *only* bcm43xx sources and compile against kernel headers ? I've seen this done with debian module-assistant tool... --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
On 02/06/2010 06:22 PM, strk wrote: > On Sat, Feb 06, 2010 at 06:20:15PM -0600, Larry Finger wrote: > >> You could probably avoid the problems by disabling the RFKILL and >> RFKILL_INPUT >> options. > > How do I do that ? Runtime ? Compile-time ? It needs to be compile time to elimionate that section of b43legacy. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
On Sat, Feb 06, 2010 at 06:20:15PM -0600, Larry Finger wrote: > You could probably avoid the problems by disabling the RFKILL and RFKILL_INPUT > options. How do I do that ? Runtime ? Compile-time ? --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
On 02/06/2010 03:14 PM, strk wrote: > On Sat, Feb 06, 2010 at 02:43:36PM -0600, Larry Finger wrote: > >> After bcm43xx was split into b43 and b43legacy, both were upgraded to take >> account of the computers "radio kill switch". Changes in the hardware switch >> input are causing the "Radio hardware ENABLED/DISABLED" messages. >> >> How does the ASUS implement that switch? Some laptops have a slide switch >> with >> an on/off position, while others have a push button with software keeping >> track >> of the state. > > I can see no slide switch, nor sign on any key suggesting > to have that purpose. It seems my problem was already reported here: > > https://lists.berlios.de/pipermail/bcm43xx-dev/2008-November/004843.html > > ... but the thread has no happy end (I add the author of that post in Cc). > > Jorge, have you figured it out lately ? You could probably avoid the problems by disabling the RFKILL and RFKILL_INPUT options. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
[ sorry for repost, Jorge wasn't in recipient list ] On Sat, Feb 06, 2010 at 10:14:12PM +0100, strk wrote: > On Sat, Feb 06, 2010 at 02:43:36PM -0600, Larry Finger wrote: > > How does the ASUS implement that switch? Some laptops have a slide switch > > with > > an on/off position, while others have a push button with software keeping > > track > > of the state. > > I can see no slide switch, nor sign on any key suggesting > to have that purpose. It seems my problem was already reported here: > > https://lists.berlios.de/pipermail/bcm43xx-dev/2008-November/004843.html > > ... but the thread has no happy end (I add the author of that post in Cc). > > Jorge, have you figured it out lately ? --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
On Sat, Feb 06, 2010 at 02:43:36PM -0600, Larry Finger wrote: > After bcm43xx was split into b43 and b43legacy, both were upgraded to take > account of the computers "radio kill switch". Changes in the hardware switch > input are causing the "Radio hardware ENABLED/DISABLED" messages. > > How does the ASUS implement that switch? Some laptops have a slide switch with > an on/off position, while others have a push button with software keeping > track > of the state. I can see no slide switch, nor sign on any key suggesting to have that purpose. It seems my problem was already reported here: https://lists.berlios.de/pipermail/bcm43xx-dev/2008-November/004843.html ... but the thread has no happy end (I add the author of that post in Cc). Jorge, have you figured it out lately ? -- () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: b43legacy-phy3: Radio hardware status changed to XXX
On 02/06/2010 01:08 PM, strk wrote: > Hi everybody, > my excuses in advance for asking something which was likely > asked a lot more in the past. > > I just switched to usin b43legacy from bmcxxx (from linux 2.6.18 > to linux 2.6.26) and am having some problems with the wireless > card. In particular I continually get disable-enable messages: > > Feb 6 20:01:21 xtops kernel: [ 4910.000194] b43legacy-phy3: Radio hardware > status changed to ENABLED > Feb 6 20:01:46 xtops kernel: [ 4935.000441] __ratelimit: 3 messages > suppressed > Feb 6 20:01:46 xtops kernel: [ 4935.000458] b43legacy-phy3: Radio hardware > status changed to DISABLED > > Sometimes this results in a disconnection. -- snip -- > > Any hint on how to further debug or fix ? > Thanks in advance. After bcm43xx was split into b43 and b43legacy, both were upgraded to take account of the computers "radio kill switch". Changes in the hardware switch input are causing the "Radio hardware ENABLED/DISABLED" messages. How does the ASUS implement that switch? Some laptops have a slide switch with an on/off position, while others have a push button with software keeping track of the state. Larry PS: Your address bcm43xx-...@berios.de is wrong. You should use just bcm43xx-...@lists.berlios.de. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: BCM4311/02 ABG disconnects on 2.6.32
On Wednesday 03 February 2010 07:45:46 Larry Finger wrote: > I installed my BCM4311/2 device to try to duplicate your results from > above. I found a problem with performance and have posted a patch for > that. I set my AP, which is a Linksys WRT54GL V1.1 running openWRT > Kamikaze r16206 firmware. I set my network to be unencrypted as you said > that made the failure to occur more quickly. As I write this, my device > has been running for 32 hours with no dropouts. I cannot duplicate your > results. > > My system is wireless-testing 2.6.33-rc5 with the two patches below. Please > add them to your system and try again. Thanks, I've tested wireless-testing with your pathes and they really increase the speed from 8 to 20 Mbps. Great! I used to think that slow speed was the problem with the router, not the laptop. The router is the same as yours, though it runs Tomato 1.27. I've tried to disable secure authentication on it and have to admit that the problem is more specific than I thought — 2.6.32 connects to the insecure router without problem (though disconnects continue to happen with 2.6.32 after a long period of time, not sure about patched wireless-testing). I'll be able to access the unprotected network which I fail to connect in a few days (it might be powered by 3Com, not sure about that), then I'll try wireless-testing with it. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: test
Why would it be misconfigured? On Sat, Feb 6, 2010 at 8:11 PM, strk wrote: > Is it me or this list is misconfigured ? > > --srrk; > ___ > Bcm43xx-dev mailing list > Bcm43xx-dev@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/bcm43xx-dev > -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
b43legacy-phy3: Radio hardware status changed to XXX
Hi everybody, my excuses in advance for asking something which was likely asked a lot more in the past. I just switched to usin b43legacy from bmcxxx (from linux 2.6.18 to linux 2.6.26) and am having some problems with the wireless card. In particular I continually get disable-enable messages: Feb 6 20:01:21 xtops kernel: [ 4910.000194] b43legacy-phy3: Radio hardware status changed to ENABLED Feb 6 20:01:46 xtops kernel: [ 4935.000441] __ratelimit: 3 messages suppressed Feb 6 20:01:46 xtops kernel: [ 4935.000458] b43legacy-phy3: Radio hardware status changed to DISABLED Sometimes this results in a disconnection. # lspci | grep Network 00:0c.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02) # uname -r 2.6.26-2-686 # b43-fwcutter --version b43-fwcutter version 011 The machine is an Asus L5800C laptop. Any hint on how to further debug or fix ? Thanks in advance. --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
b43legacy-phy3: Radio hardware status changed to XXX
Hi everybody, my excuses in advance for asking something which was likely asked a lot more in the past. I just switched to usin b43legacy from bmcxxx (from linux 2.6.18 to linux 2.6.26) and am having some problems with the wireless card. In particular I continually get disable-enable messages: Feb 6 20:01:21 xtops kernel: [ 4910.000194] b43legacy-phy3: Radio hardware status changed to ENABLED Feb 6 20:01:46 xtops kernel: [ 4935.000441] __ratelimit: 3 messages suppressed Feb 6 20:01:46 xtops kernel: [ 4935.000458] b43legacy-phy3: Radio hardware status changed to DISABLED Sometimes this results in a disconnection. # lspci | grep Network 00:0c.0 Network controller: Broadcom Corporation BCM4303 802.11b Wireless LAN Controller (rev 02) # uname -r 2.6.26-2-686 # b43-fwcutter --version b43-fwcutter version 011 The machine is an Asus L5800C laptop. Any hint on how to further debug or fix ? Thanks in advance. --strk; () Free GIS & Flash consultant/developer /\ http://foo.keybit.net/~strk/services.html ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
test
Is it me or this list is misconfigured ? --srrk; ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: [RFC][PATCH] b43: LP-PHY: always adjust gain table on channel switch
On Sat, Feb 6, 2010 at 1:06 AM, Larry Finger wrote: > On 02/05/2010 10:27 AM, Gábor Stefanik wrote: >> On Fri, Feb 5, 2010 at 4:24 AM, Larry Finger >> wrote: >>> On 02/04/2010 02:57 PM, Rafał Miłecki wrote: --- Gábor: I think you missed specs here. Could you check whole routine just for sure, please? I don't understand whole radio and chanspec magic yet. --- drivers/net/wireless/b43/phy_lp.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/net/wireless/b43/phy_lp.c b/drivers/net/wireless/b43/phy_lp.c index 185219e..61009ee 100644 --- a/drivers/net/wireless/b43/phy_lp.c +++ b/drivers/net/wireless/b43/phy_lp.c @@ -2655,8 +2655,8 @@ static int b43_lpphy_op_switch_channel(struct b43_wldev *dev, if (err) return err; lpphy_set_analog_filter(dev, new_channel); - lpphy_adjust_gain_table(dev, channel2freq_lp(new_channel)); } + lpphy_adjust_gain_table(dev, channel2freq_lp(new_channel)); lpphy->channel = new_channel; b43_write16(dev, B43_MMIO_CHANNEL, new_channel); >>> >>> Both the lpphy_set_analog_filter() and lpphy_adjust_gain_table() calls >>> should be >>> outside the if statement. I changed the spec a little. It used to test >>> "radio >>> enabled", but I have found that is always true for our driver. >>> >>> Larry >>> >>> >> >> Isn't set_analog_filter() rev0/1-specific? > > The new routines are described in > > http://bcm-v4.sipsolutions.net/802.11/PHY/LP/TxFilterInit > > http://bcm-v4.sipsolutions.net/802.11/PHY/LP/TxDigFiltUcodeRev2 > > The revised routines are: > > http://bcm-v4.sipsolutions.net/802.11/PHY/LP/SetChanSpecLPPHY > > http://bcm-v4.sipsolutions.net/802.11/PHY/LP/PR41573 > > Larry > > Note to implementors: Chanspec is broadcrap, please do NOT use in b43. Use a struct if you need the extra parameters contained in chanspec. -- Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-) ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
skb_over_panic from b43 after a few hours
Hi, i'm using OpenWRT on an ASUS WL-500gP V2 with the built-in Broadcom BCM3302. After a few hours the b43 driver crashes with a skb_over_panic and i need to reboot the device. The crash happend also, if there is no traffic over the wireless interface. The wireless interface is configured in AP mode and the encryption psk2. The used kernel (Linux OpenWrt 2.6.30.10 #1 Tue Feb 2 01:15:42 CET 2010 mips GNU/Linux) throws the following output: skb_over_panic: text:80c9a8e4 len:2374 put:2374 head:80e79000 data:80e79040 tail:0x80e79986 end:0x80e79980 dev: Kernel bug detected[#1]: Cpu 0 $ 0 : 1000f800 0079 0001 $ 4 : 802880c0 271f 271f $ 8 : 4000 802959b0 0001 $12 : 000f 8022a1d0 7ffb537b $16 : 00e79040 80e79040 0928 80e9a9a0 $20 : 80d84c80 0019 a0df7190 80ca1518 $24 : 0002 80151108 $28 : 80ea 80ea1e60 001b 8018c2d4 Hi: Lo: 0077 epc : 8018c2d4 skb_put+0x74/0x90 Not tainted ra: 8018c2d4 skb_put+0x74/0x90 Status: 1000f803KERNEL EXL IE Cause : 00800024 PrId : 00029029 (Broadcom BCM3302) Modules linked in: pl2303 option ftdi_sio usb_storage usbserial ohci_hcd nf_nat_ tftp nf_conntrack_tftp nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp i pt_MASQUERADE iptable_nat nf_nat xt_NOTRACK iptable_raw xt_state nf_conntrack_ip v4 nf_defrag_ipv4 nf_conntrack ehci_hcd sd_mod pppoe pppox ipt_REJECT xt_TCPMSS ipt_LOG xt_multiport xt_mac xt_limit iptable_mangle iptable_filter ip_tables xt_ tcpudp x_tables ext2 ext3 jbd tun ppp_async ppp_generic slhc vfat fat b43 nls_ut f8 nls_iso8859_15 nls_iso8859_1 nls_cp850 nls_cp437 usbcore scsi_mod nls_base ma c80211 cfg80211 compat_firmware_class compat crc_ccitt arc4 aes_generic deflate ecb cbc switch_robo switch_core diag Process compirq/5-b43 (pid: 812, threadinfo=80ea, task=81f19188, tls=000 0) Stack : 80c9a8e4 0946 0946 80e79000 80e79040 80e79986 80e79980 80266f84 80d84c80 0019 80c9a8e4 80287b88 80286170 1000f800 00fe 80ea1fe0 f800 80d92d2c 80284000 80ca1518 7f816db4 0001 80c7f400 8000 0001 fffc 802c7860 0001 fffe efff 80c87420 81f19188 80c8 80e9ee08 8001c63c 80ea 80ea1f18 8021db88 ... Call Trace: [<8018c2d4>] skb_put+0x74/0x90 [<80c9a8e4>] b43_dma_rx+0x338/0x444 [b43] [<80c87420>] b43_controller_restart+0x7a0/0x974 [b43] Code: afab001c 0c00268d afa20020 <020d> 080630b6 8fbf002c 0120 1021 03e8 Disabling lock debugging due to kernel taint Stefan ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
