Re: I need some help stabaizing b43 for a 4306
On Saturday 28 February 2009 21:07:41 Larry Finger wrote: > > One more question and i hope you don't mind, it's off topic but it's > > related to my quest. I hadven't done any C programming in 10 years but when > > I used to do a lot of it, if I patche a source file and ran 'make', it > > figured out what needed to be done and just recompiled and liknked the > > changed bits. Over the last week, every time I changed phy_g.c, make calmly > > repied, 'nothing to be done.' What am I forgetting? > > That would indicate that your Makefile doesn't have a dependency on phy_g.c. No dependencies don't work in compat wireless. You need to make clean first. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > I want to thank you guys once again for your advice, last week on my BCM4306 > problem. I've tried 20dBm, 15, 12, and 10dBm, with varying degrees of > success. Which, is just a fancy way of saying, no real success. > > I'm going back to the unpatched, 2-23 sources of last week to get to a known > state and will try the open source firmware which is reported to work with > b43. Getting open-source firmware won't make a difference as firmware is not your problem. The main advantage is that the new firmware will have a GPL license and can be included with the distros. No one is expecting it to be better than the proprietary firmware. > If it doesn't, and frankly, I'm not hopefull, is there any way of going back > to bcm43xx. It'd be a shame to abandon a card which worked perfectly well, > before, even if it's not as open as we'd like. A lot of us are stuck with > this device in otherwise perfectly good laptops. The short answer is "No". With bcm43xx, the MAC layer was controlled by something called SoftMAC. It was buggy and limited, which is why it was replaced by mac80211. It would require a great deal of work to get SoftMAC to work with modern kernels. You could modify bcm43xx to work with mac80211, but then you would have the equivalent of b43 as that is essentially how b43 and b43legacy were produced. What I would suggest is that you build a 2.6.23 kernel and test bcm43xx that way to see if something changed in your hardware, or if it really is b43 that fails with your device. > One more question and i hope you don't mind, it's off topic but it's related > to my quest. I hadven't done any C programming in 10 years but when I used to > do a lot of it, if I patche a source file and ran 'make', it figured out what > needed to be done and just recompiled and liknked the changed bits. Over the > last week, every time I changed phy_g.c, make calmly repied, 'nothing to be > done.' What am I forgetting? That would indicate that your Makefile doesn't have a dependency on phy_g.c. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
I want to thank you guys once again for your advice, last week on my BCM4306 problem. I've tried 20dBm, 15, 12, and 10dBm, with varying degrees of success. Which, is just a fancy way of saying, no real success. I'm going back to the unpatched, 2-23 sources of last week to get to a known state and will try the open source firmware which is reported to work with b43. If it doesn't, and frankly, I'm not hopefull, is there any way of going back to bcm43xx. It'd be a shame to abandon a card which worked perfectly well, before, even if it's not as open as we'd like. A lot of us are stuck with this device in otherwise perfectly good laptops. One more question and i hope you don't mind, it's off topic but it's related to my quest. I hadven't done any C programming in 10 years but when I used to do a lot of it, if I patche a source file and ran 'make', it figured out what needed to be done and just recompiled and liknked the changed bits. Over the last week, every time I changed phy_g.c, make calmly repied, 'nothing to be done.' What am I forgetting? All the best, John - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 2:30:05 PM Subject: Re: I need some help stabaizing b43 for a 4306 John Mountcastle wrote: > Can I just edit Michael's patch and apply it again just like I did the first > time: > > cd $(COMPAT_SRC_DIR) > patch -p1 < $(PATCH_FILE) > > Regards > > John Yes. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > Can I just edit Michael's patch and apply it again just like I did the first > time: > > cd $(COMPAT_SRC_DIR) > patch -p1 < $(PATCH_FILE) > > Regards > > John Yes. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Can I just edit Michael's patch and apply it again just like I did the first time: cd $(COMPAT_SRC_DIR) patch -p1 < $(PATCH_FILE) Regards John - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 1:54:54 PM Subject: Re: I need some help stabaizing b43 for a 4306 John Mountcastle wrote: > Yes, I'd say results are mixed. B43 now says it wants 20dBm and it's getting > 16.75 but iwconfig says rate is only 1Mb/s and I can't keep the link up long > enough to be usefull. > > If the SPROM was wrong all along, why does it work fine with bcm43xx? Many parts of the power control have undergone major changes. For most interfaces, these changes made them work better; however, yours may be different. If you want to try what happens with lower power, you can change the line in Michaels patch that looks like +max_pwr = INT_TO_Q52(20); You started with the equivalent of "INT_TO_Q52(15)" - what happens if the 20 is replaced by 12 or 10? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
OK, it sounds like a pretty tough nut to crack. I'm not sure if I can get a new card as it's kinda built into this laptop, or, maybe I'm wrong. Do you think I might be able to crack this thing open and put in a replacement device? Anyway, thanks a lot for your help. I learned a little in the bargain so I won't call the adventure a total loss. Probably my best move is just to go back to openSUSE 10.3 with the bcm43xx driver. Or I might try blacklisting b43 and usng ndiswrapper. I've used it before with excellent results. Regards John - Original Message From: Michael Buesch To: Larry Finger Cc: John Mountcastle ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 1:47:39 PM Subject: Re: I need some help stabaizing b43 for a 4306 On Monday 23 February 2009 18:36:12 Larry Finger wrote: > More food for thought: > > My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. > It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed > the > SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 > Mb/s. It looked as if the radio was overheating. This has nothing to do with overheating, so let's reduce FUD a bit. ;) The attenuation is not linear. There's a certain threshold where it inverts. Let's explain it in simple numbers. Let's say the attenuation A is from 0-9. The actual power output O would looke something like this: A= 0 1 2 3 4 5 6 7 8 9 O= 0 1 2 3 4 4 3 2 1 0 This is true for broadcom cards and some atheros cards. So as we decrease attennuation, there's a point where output power is inverted. In this simple example we must not go below an A value of 5. The actual threshold is different for each device and you're pretty much likely hitting it. The control algorithm is unaware of this threshold and it will scale the attenuation down which results in lower power which will result in scaling down... So John, back to your problem. I think you're pretty much lost with it. Like thousands of other people (including me) are lost with crappy broadcom devices. I suggest you go and buy something sane instead. I cannot help you anymore with this. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > Yes, I'd say results are mixed. B43 now says it wants 20dBm and it's getting > 16.75 but iwconfig says rate is only 1Mb/s and I can't keep the link up long > enough to be usefull. > > If the SPROM was wrong all along, why does it work fine with bcm43xx? Many parts of the power control have undergone major changes. For most interfaces, these changes made them work better; however, yours may be different. If you want to try what happens with lower power, you can change the line in Michaels patch that looks like + max_pwr = INT_TO_Q52(20); You started with the equivalent of "INT_TO_Q52(15)" - what happens if the 20 is replaced by 12 or 10? Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 18:36:12 Larry Finger wrote: > More food for thought: > > My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. > It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed > the > SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 > Mb/s. It looked as if the radio was overheating. This has nothing to do with overheating, so let's reduce FUD a bit. ;) The attenuation is not linear. There's a certain threshold where it inverts. Let's explain it in simple numbers. Let's say the attenuation A is from 0-9. The actual power output O would looke something like this: A= 0 1 2 3 4 5 6 7 8 9 O= 0 1 2 3 4 4 3 2 1 0 This is true for broadcom cards and some atheros cards. So as we decrease attennuation, there's a point where output power is inverted. In this simple example we must not go below an A value of 5. The actual threshold is different for each device and you're pretty much likely hitting it. The control algorithm is unaware of this threshold and it will scale the attenuation down which results in lower power which will result in scaling down... So John, back to your problem. I think you're pretty much lost with it. Like thousands of other people (including me) are lost with crappy broadcom devices. I suggest you go and buy something sane instead. I cannot help you anymore with this. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Yes, I'd say results are mixed. B43 now says it wants 20dBm and it's getting 16.75 but iwconfig says rate is only 1Mb/s and I can't keep the link up long enough to be usefull. If the SPROM was wrong all along, why does it work fine with bcm43xx? Incidentally, when I rebooted and while the 4306 was still connected, NetworkManager said he saw 100%. b43-phy0 debug: [TX power] current = 16.75 dBm, desired = 20.0 dBm, max = 20.0 b43-phy0 debug: [TX power deltas] 3.25 dBm => bbatt-delta = 2, rfatt-delta = -2 b43-phy0 debug: Adjusting TX power b43-phy0 debug: Tuning TX-power to bbatt(2), rfatt(0), tx_control(0x30), tx_bias(0x00), tx_magn(0x00) sybill:~ # iwconfig wlan0 wlan0 IEEE 802.11bg ESSID:"MBR-6d2" Mode:Managed Frequency:2.417 GHz Access Point: 00:30:44:02:76:D2 Bit Rate=1 Mb/s Tx-Power=27 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:7761-7465-7266-616C-6C30-3030-30 Security mode:open Power Management:off Link Quality=85/70 Signal level:-45 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 Regards John - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 12:36:12 PM Subject: Re: I need some help stabaizing b43 for a 4306 More food for thought: My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed the SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 Mb/s. It looked as if the radio was overheating. It is possible that the patch of today will make things worse, not better. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
More food for thought: My BCM4306/2 in a Cardbus format has a maxpbg value that translates to 10 dBm. It routinely transmits at 5-6 Mb/s in my normal setting. When I reprogrammed the SPROM to 20 dBm, it would start out at the above rate, then rapidly drop to 1 Mb/s. It looked as if the radio was overheating. It is possible that the patch of today will make things worse, not better. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > Here's a thought, every time I unload b43 and reload it, my indicated signal > strength (NetworkManager) is 85%. Shortly it drops off to 65%, then 51%. then > it usually fails. I ad to go find a wire because I couldn't keep the 4306 up, > long enough to reach yahoo. > > Michael, I applied you patch and compiled. I'll install and load the ne > drivers and let you know what TXmit power indicates. > > Larry, here's the SPROM you wanted. Your SPROM contains a maxpbg value of 0x3C, which translates to 15 dBm - exactly what the program is trying to maintain. I have data for a number of BCM4306 SPROM's due to my fixing of the Bluetooth coexistence problem for Ubuntu users. Every one of them that I looked at has that same value for maxpbg, which probably explains the poor performance. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Here's a thought, every time I unload b43 and reload it, my indicated signal strength (NetworkManager) is 85%. Shortly it drops off to 65%, then 51%. then it usually fails. I ad to go find a wire because I couldn't keep the 4306 up, long enough to reach yahoo. Michael, I applied you patch and compiled. I'll install and load the ne drivers and let you know what TXmit power indicates. Larry, here's the SPROM you wanted. Password: sybill:~ # SPROM=$(find /sys -name ssb_sprom) sybill:~ # echo $SPROM /sys/devices/pci:00/:00:1e.0/:02:06.0/ssb_sprom sybill:~ # cat $SPROM 0140F4123C10204300800200021000189000944BA62C60369A1193FBA5FE3C003E000D000152 sybill:~ # - Original Message From: Larry Finger To: John Mountcastle Cc: Michael Buesch ; bcm43xx-dev@lists.berlios.de Sent: Monday, February 23, 2009 10:31:05 AM Subject: Re: I need some help stabaizing b43 for a 4306 John, I would like to see what is in your SPROM concerning the power settings. Please run the following commands: SPROM=$(find /sys -name ssb_sprom) echo $SPROM sudo cat $SPROM and post the output. Thanks, Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John, I would like to see what is in your SPROM concerning the power settings. Please run the following commands: SPROM=$(find /sys -name ssb_sprom) echo $SPROM sudo cat $SPROM and post the output. Thanks, Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 13:52:04 mtcs...@yahoo.com wrote: > Good morning Michael. So, to be sure I've got it right; I want the second > patch and not the first. I need to apply it to this morning's compat sources, > not two days ago? right. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Good morning Michael. So, to be sure I've got it right; I want the second patch and not the first. I need to apply it to this morning's compat sources, not two days ago? Cheers John Sent via BlackBerry by AT&T -Original Message- From: Michael Buesch Date: Mon, 23 Feb 2009 13:31:05 To: Subject: Re: I need some help stabaizing b43 for a 4306 On Monday 23 February 2009 13:25:36 Michael Buesch wrote: > On Monday 23 February 2009 12:15:54 Michael Buesch wrote: > > On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > > > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > > > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > > > Mode:Managed Frequency:2.417 GHz Access Point: > > > 00:30:44:02:76:D2 > > > Bit Rate=1 Mb/s Tx-Power=27 dBm > > > Retry min limit:7 RTS thr:off Fragment thr=2352 B > > > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security > > > mode:open > > > Power Management:off > > > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig > > > says it's askigng for 27. > > > > Right, that's what I suspected. > > > > Can you try wireless-compat? It prints additional debugging info for this. > > compat is easy to install, usually. Just download it and do make; make > > install in the > > extracted source tree. You don't need to change your kernel for this. You > > can run it > > on a standard distribution kernel, usually. > > > > I made a patch which fixes up a possible PROM screwup: > http://bu3sch.de/patches/wireless-testing/20090223-1324/patches/018-b43-txpwr-sprom-fixes.patch > > You can apply that to compat-wireless: > cd compat-wireless-2009-02-XX > patch -p1 < 018-b43-txpwr-sprom-fixes.patch > Ok, seems this doesn't apply to compat-wireless. Use this one, which was diffed against today's compat-wireless: http://bu3sch.de/patches/misc/018-b43-txpwr-sprom-fixes.patch -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 13:25:36 Michael Buesch wrote: > On Monday 23 February 2009 12:15:54 Michael Buesch wrote: > > On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > > > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > > > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > > > Mode:Managed Frequency:2.417 GHz Access Point: > > > 00:30:44:02:76:D2 > > > Bit Rate=1 Mb/s Tx-Power=27 dBm > > > Retry min limit:7 RTS thr:off Fragment thr=2352 B > > > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security > > > mode:open > > > Power Management:off > > > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig > > > says it's askigng for 27. > > > > Right, that's what I suspected. > > > > Can you try wireless-compat? It prints additional debugging info for this. > > compat is easy to install, usually. Just download it and do make; make > > install in the > > extracted source tree. You don't need to change your kernel for this. You > > can run it > > on a standard distribution kernel, usually. > > > > I made a patch which fixes up a possible PROM screwup: > http://bu3sch.de/patches/wireless-testing/20090223-1324/patches/018-b43-txpwr-sprom-fixes.patch > > You can apply that to compat-wireless: > cd compat-wireless-2009-02-XX > patch -p1 < 018-b43-txpwr-sprom-fixes.patch > Ok, seems this doesn't apply to compat-wireless. Use this one, which was diffed against today's compat-wireless: http://bu3sch.de/patches/misc/018-b43-txpwr-sprom-fixes.patch -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 12:15:54 Michael Buesch wrote: > On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > > Mode:Managed Frequency:2.417 GHz Access Point: > > 00:30:44:02:76:D2 > > Bit Rate=1 Mb/s Tx-Power=27 dBm > > Retry min limit:7 RTS thr:off Fragment thr=2352 B > > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security > > mode:open > > Power Management:off > > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig > > says it's askigng for 27. > > Right, that's what I suspected. > > Can you try wireless-compat? It prints additional debugging info for this. > compat is easy to install, usually. Just download it and do make; make > install in the > extracted source tree. You don't need to change your kernel for this. You can > run it > on a standard distribution kernel, usually. > I made a patch which fixes up a possible PROM screwup: http://bu3sch.de/patches/wireless-testing/20090223-1324/patches/018-b43-txpwr-sprom-fixes.patch You can apply that to compat-wireless: cd compat-wireless-2009-02-XX patch -p1 < 018-b43-txpwr-sprom-fixes.patch -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Monday 23 February 2009 03:40:01 John Mountcastle wrote: > mtcs...@sybill:~/Desktop> sudo /usr/sbin/iwconfig wlan0 > wlan0 IEEE 802.11bg ESSID:"MBR-6d2" > Mode:Managed Frequency:2.417 GHz Access Point: 00:30:44:02:76:D2 > > Bit Rate=1 Mb/s Tx-Power=27 dBm > Retry min limit:7 RTS thr:off Fragment thr=2352 B > Encryption key:7761-7465-7266-616C-6C30-3030-30 Security mode:open > Power Management:off > Link Quality=51/100 Signal level:-5 dBm Noise level=-17 dBm > Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 > Tx excessive retries:0 Invalid misc:0 Missed beacon:0 > > Note that while b43-phy0 debug says desired output is 15.0dBm, iwconfig says > it's askigng for 27. Right, that's what I suspected. Can you try wireless-compat? It prints additional debugging info for this. compat is easy to install, usually. Just download it and do make; make install in the extracted source tree. You don't need to change your kernel for this. You can run it on a standard distribution kernel, usually. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
t b43-phy0 debug: Current TX power output: 15.0 dBm, Desired TX power output: 15.0 dBm b43-phy0 debug: Disabling hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authenticate with AP 00:30:44:02:76:d2 b43-phy0 debug: Using hardware based encryption for keyidx: 0, mac: ff:ff:ff:ff:ff:ff wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authenticated wlan0: associate with AP 00:30:44:02:76:d2 wlan0: RX AssocResp from 00:30:44:02:76:d2 (capab=0x431 status=0 aid=2) wlan0: associated b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 debug: Current TX power output: 14.75 dBm, Desired TX power output: 15.0 dBm b43-phy0 debug: Tuning TX-power to bbatt(5), rfatt(4), tx_control(0x30), tx_bias(0x00), tx_magn(0x00) b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error martian source 255.255.255.255 from 192.168.0.1, on dev wlan0 ll header: ff:ff:ff:ff:ff:ff:00:30:44:02:76:d2:08:00 b43-phy0 debug: Current TX power output: 15.0 dBm, Desired TX power output: 15.0 dBm b43-phy0 debug: Current TX power output: 15.0 dBm, Desired TX power output: 15.0 dBm b43-phy0 debug: Current TX power output: 15.0 dBm, Desired TX power output: 15.0 dBm b43-phy0 debug: Current TX power output: 15.0 dBm, Desired TX power output: 15.0 dBm b43-phy0 debug: Current TX power output: 15.0 dBm, Desired TX power output: 15.0 dBm - Original Message From: Michael Buesch To: John Mountcastle Cc: bcm43xx-dev@lists.berlios.de Sent: Sunday, February 22, 2009 3:58:21 PM Subject: Re: I need some help stabaizing b43 for a 4306 On Sunday 22 February 2009 21:45:44 John Mountcastle wrote: > > Michael, configuring a new kernel was a real blast from the past. I haven't > done that in several years but I think I got it done. Funny thing, when I > booted the debug kernel, the interface was rock solid for almost an hour, not > one single error, then it went sour again. I switched on br43 debugging as > you suggested, about half way through the capture. You can see the Tx-mit > power messages start. About 60% into the capture I unloaded b43 > (rmmod/insmod) and reloaded it in order to get the interface to come back up. > > I hope you can tell me something about what if anything this capture tells > us? Or, the net step in debuggging > > b43-phy1 debug: Current TX power output: 14.75 dBm, Desired TX power output: > 15.0 dBm > b43-phy1 debug: Tuning TX-power to bbatt(5), rfatt(4), tx_control(0x30), > tx_bias(0x00), tx_magn(0x00) The first thing I notice, of course, is the very low TX power output of 15dBm. Can you check iwconfig to check which TX power was selected? It should write something like this: wlan0 IEEE 802.11bg ESSID:"" Mode:Managed Frequency:2. GHz Access Point: X Bit Rate=XX Mb/s Tx-Power=20 dBm . So if there's a higher value than 15, please tell me so. If the value is 15 there, too. Try manually setting the TX power: iwconfig wlan0 txpower 20 This might be a bug in the card's PROM or possibly the code reading it. I also have a card where it incorrectly reads the TX power value (but it's 19dBm for me, so it doesn't matter that much for me...). Besides that, please tell me exactly at which point in the log messages it starts to break. That's essential information for me. Also, moving to latest b43 development code might help, too. It has improved TX power control code which might scale a bit better on your device. You can do so by downloading compat-wireless: http://wireless.kernel.org/en/users/Download -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Sunday 22 February 2009 21:45:44 John Mountcastle wrote: > > Michael, configuring a new kernel was a real blast from the past. I haven't > done that in several years but I think I got it done. Funny thing, when I > booted the debug kernel, the interface was rock solid for almost an hour, not > one single error, then it went sour again. I switched on br43 debugging as > you suggested, about half way through the capture. You can see the Tx-mit > power messages start. About 60% into the capture I unloaded b43 > (rmmod/insmod) and reloaded it in order to get the interface to come back up. > > I hope you can tell me something about what if anything this capture tells > us? Or, the net step in debuggging > > b43-phy1 debug: Current TX power output: 14.75 dBm, Desired TX power output: > 15.0 dBm > b43-phy1 debug: Tuning TX-power to bbatt(5), rfatt(4), tx_control(0x30), > tx_bias(0x00), tx_magn(0x00) The first thing I notice, of course, is the very low TX power output of 15dBm. Can you check iwconfig to check which TX power was selected? It should write something like this: wlan0 IEEE 802.11bg ESSID:"" Mode:Managed Frequency:2. GHz Access Point: X Bit Rate=XX Mb/s Tx-Power=20 dBm . So if there's a higher value than 15, please tell me so. If the value is 15 there, too. Try manually setting the TX power: iwconfig wlan0 txpower 20 This might be a bug in the card's PROM or possibly the code reading it. I also have a card where it incorrectly reads the TX power value (but it's 19dBm for me, so it doesn't matter that much for me...). Besides that, please tell me exactly at which point in the log messages it starts to break. That's essential information for me. Also, moving to latest b43 development code might help, too. It has improved TX power control code which might scale a bit better on your device. You can do so by downloading compat-wireless: http://wireless.kernel.org/en/users/Download -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
On Saturday 21 February 2009 20:17:53 John Mountcastle wrote: > > Thanks Larry, what about the part right there at the endwher it says assume > out of range when nothing has moved. It's like the receeption begins to drop > of until it can no longer support the connection. Please turn on b43 debugging in the kernel config, mount debugfs to /sys/kernel/debug and enable xmit debugging with this knob: echo 1 > /sys/kernel/debug/b43/phy*/debug_xmitpower Then see if the kernel tells you something interesting. -- Greetings, Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
The latest versions of mac80211 are better at recovering from loss of contact with the AP. You would get the latest with compat-wireless. As to getting firmware from bcmwl5.sys, I doubt that it would make a difference. >From what I know, the ucode5 and XXinitvals5 files have not changed. Is your device getting hotter than it used to? That might explain the loss of signal strength with time. You could test this by strategic placement of a fan. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
Thanks Larry, what about the part right there at the endwher it says assume out of range when nothing has moved. It's like the receeption begins to drop of until it can no longer support the connection. SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 b43-phy0 ERROR: PHY transmission error wlan0: No ProbeResp from current AP 00:30:44:02:76:d2 - assume out of range wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authenticate with AP 00:30:44:02:76:d2 wlan0: authentication with AP 00:30:44:02:76:d2 timed out mtcs...@sybill:~/Desktop> That shows up right before the link drops? You know, it has occurred to me that it might not be b43 that's causing the problem. It might be the firmware. On a whim, I tried to cut firmware out of bcmwl5.sys, the driver that has always worked with this device and b43-fwcutter wouldn't cut it. As I remember, the version that worked with bcm43xx had about a dozen firmwares it would use, the new one only has about four. What do you suppose might happen if I massaged teh code for bw43-fwcutter to accept teh firmware I want to use? Regards John - Original Message From: Larry Finger To: John Mountcastle Cc: bcm43xx-dev@lists.berlios.de Sent: Saturday, February 21, 2009 1:53:47 PM Subject: Re: I need some help stabaizing b43 for a 4306nks John Mountcastle wrote: > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > martian source 255.255.255.255 from 192.168.0.1, on dev wlan0 > ll header: ff:ff:ff:ff:ff:ff:00:30:44:02:76:d2:08:00 > martian source 255.255.255.255 from 192.168.0.1, on dev wlan0 > ll header: ff:ff:ff:ff:ff:ff:00:30:44:02:76:d2:08:00 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=248 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=228 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=472 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=452 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=472 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=452 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=472 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=452 > wlan0: no IPv6 routers present > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > b43-phy0 ERROR: PHY transmission error > wlan0: No ProbeResp from current AP 00:30:44:02:76:d2 - assume out of range > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authentication with AP 00:30:44:02:76:d2 timed out You can get the latest code from compat-wireless (http://linuxwireless.org/en/users/Download). I don't see any "disturbing" messages in your log. The martian source lines arise because you have IPV6 enabled. The DROP-DEFLT messages come from your firewall. An occasional PHY transmission error can be ignored. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: I need some help stabaizing b43 for a 4306
John Mountcastle wrote: > ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready > martian source 255.255.255.255 from 192.168.0.1, on dev wlan0 > ll header: ff:ff:ff:ff:ff:ff:00:30:44:02:76:d2:08:00 > martian source 255.255.255.255 from 192.168.0.1, on dev wlan0 > ll header: ff:ff:ff:ff:ff:ff:00:30:44:02:76:d2:08:00 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=248 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=228 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=472 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=452 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=472 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=452 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=472 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 > LEN=452 > wlan0: no IPv6 routers present > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > SFW2-INext-DROP-DEFLT IN=wlan0 OUT= MAC= SRC=192.168.0.189 DST=224.0.0.251 > LEN=64 TOS=0x00 PREC=0x00 TTL=255 ID=0 DF PROTO=UDP SPT=5353 DPT=5353 LEN=44 > b43-phy0 ERROR: PHY transmission error > wlan0: No ProbeResp from current AP 00:30:44:02:76:d2 - assume out of range > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authenticate with AP 00:30:44:02:76:d2 > wlan0: authentication with AP 00:30:44:02:76:d2 timed out You can get the latest code from compat-wireless (http://linuxwireless.org/en/users/Download). I don't see any "disturbing" messages in your log. The martian source lines arise because you have IPV6 enabled. The DROP-DEFLT messages come from your firewall. An occasional PHY transmission error can be ignored. Larry ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
I need some help stabaizing b43 for a 4306
I've got an HP pavilion ze4904us. This device has a Broadcom 4306 which worked perfectly under Suse 10.3 with the bcm43xx module. Under Suse 11.1 with b43, it loads the module starts the nic and works just fine for ten to twenty minutes. After that, the signal strength appears to deteriorate, disurbing messages begin to appear in dmesg, and finally the connection dies. Sometimes I can get it to come back by reactivateing the connection through NetworkManager, sometimes not. I'm including uname, lspci, and dmesg, as suggested. Any help or advice is appreciated. I can't be the only person to have had this problem, the 4306 is not an uncommon device. Maybe it's already been fixed. Can someone point me at the latest stable, or even not so stable, code? sybill:~ # uname -a Linux sybill 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 i686 i686 i386 GNU/Linux sybill:~ # lspci -vvn |grep 43 -A7 02:06.0 0280: 14e4:4320 (rev 03) Subsystem: 103c:12f4 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- node 0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs *10) ACPI: PCI Interrupt Link [LNKB] (IRQs *5) ACPI: PCI Interrupt Link [LNKC] (IRQs *11) ACPI: PCI Interrupt Link [LNKD] (IRQs *11) ACPI: PCI Interrupt Link [LNKE] (IRQs 11) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 11) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 11) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs *11) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: bus type pnp registered pnp: PnP ACPI: found 7 devices ACPI: ACPI bus type pnp unregistered PnPBIOS: Disabled by ACPI PNP PCI: Using ACPI for IRQ routing AppArmor: AppArmor Filesystem Enabled ACPI: RTC can wake from S4 system 00:04: ioport range 0x600-0x60f has been reserved system 00:04: ioport range 0x800-0x80f has been reserved system 00:04: ioport range 0x1000-0x107f has been reserved system 00:04: ioport range 0x1180-0x11bf has been reserved system 00:04: iomem range 0xfec1-0xfec1 has been reserved pci :02:05.0: CardBus bridge, secondary bus :03 pci :02:05.0: IO window: 0x003400-0x0034ff pci :02:05.0: IO window: 0x003800-0x0038ff pci :02:05.0: PREFETCH window: 0x5000-0x53ff pci :02:05.0: MEM window: 0x5800-0x5bff pci :00:1e.0: PCI bridge, secondary bus :02 pci :00:1e.0: IO window: 0x3000-0x3fff pci :00:1e.0: MEM window: 0xe020-0xe02f pci :00:1e.0: PREFETCH window: 0x005000-0x0053ff pci :00:1e.0: setting latency timer to 64 ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 11 vendor=8086 device=2448 PCI: setting IRQ 11 as level-triggered pci :02:05.0: PCI INT A -> Link[LNKE] -> GSI 11 (level, low) -> IRQ 11 bus: 00 index 0 io port: [0, ] bus: 00 index 1 mmio: [0, ] bus: 02 index 0 io port: [3000, 3fff] bus: 02 index 1 mmio: [e020, e02f] bus: 02 index 2 mmio: [5000, 53ff] bus: 02 index 3 io port: [0, ] bus: 02 index 4 mmio: [0, ] bus: 03 index 0 io port: [3400, 34ff] bus: 03 index 1 io port: [3800, 38ff] bus: 03 index 2 mmio: [5000, 53ff] bus: 03 index 3 mmio: [5800, 5bff] NET: Registered protocol family 2 IP route cache hash table entries: 32768 (order: 5, 131072 bytes) TCP established hash table entries: 131072 (order: 8, 1048576 bytes) TCP bind hash table entries: 65536 (order: 7, 524288 bytes) TCP: Hash tables configured (established 131072 bind 65536) TCP reno registered NET: Registered protocol family 1 Unpacking initramfs... done Freeing initrd memory: 5713k freed Simple Boot Flag at 0x36 set to 0x1 Machine check exception polling timer started. audit: initializing netlink socket (disabled) type=2000 audit(1235066728.772:1): initialized highmem bounce pool size: 64 pages HugeTLB registered 4 MB page size, pre-allocated 0 pages VFS: Disk quotas dquot_6.5.1 Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) msgmni has been set to 440 Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254) io scheduler noop registered io scheduler anticipatory registered io scheduler deadline registered io scheduler cfq registered (default) pci :00:02.0: Boot video device vesafb: framebuffer at 0xe800, mapped to 0xf888, using 6144k, total 32576k vesafb: mode is 1024x768x16, linelength=2048, pages=20 vesafb: scrolling: redraw vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 bootsplash 3.1.6-2004/03/31: looking for picture... bootsplash: silentjpeg size 100719 bytes bootsplash: ...found (1024x768, 38691 bytes, v3). Console: switching to colour frame buffer device 124x44 Switched to high resolution mode on CPU 0 fb0: VESA VGA frame buffer device isapnp: Scanning for PnP cards... isapnp: No Plug & Play device found Serial: 8250/
