As one of the people why reported some of these issues, I am going to take it upon my self to test the current b43 firmware with an ASUS WL500pv2. This uses the Broadcom 5354 SoC and has a LP-PHY with Both the stable(4.150.10.5) and experimental <meta http-equiv="content-type" content="text/html; charset=utf-8">(4.178.10.4) firmware.<div>
<br></div><div>I will report back in the next couple of days.</div><div><br></div><div>Cheers<br clear="all">----------------------------------------------------------<br>Chris Martin<br>m: 0419812371<br>----------------------------------------------------------<br>
<br><br><div class="gmail_quote">2011/3/2 Rafał Miłecki <span dir="ltr"><<a href="mailto:zajec5@gmail.com">zajec5@gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
W dniu 7 grudnia 2010 20:21 użytkownik Hauke Mehrtens<br>
<<a href="mailto:hauke@hauke-m.de">hauke@hauke-m.de</a>> napisał:<br>
> On 12/07/2010 04:32 PM, Larry Finger wrote:<br>
>> On 12/07/2010 06:28 AM, Rafał Miłecki wrote:<br>
>>> W dniu 7 grudnia 2010 13:21 użytkownik Rafał Miłecki <<a href="mailto:zajec5@gmail.com">zajec5@gmail.com</a>> napisał:<br>
>>>> Currently we tell ppl to use 4.150.10.5 for G-PHY and 4.174.64.19 for<br>
>>>> LP-PHY on our wiki page.<br>
>>>><br>
>>>> Firmware files for G-PHY differ a little between there two versions,<br>
>>>> but did we actually get any problems reports?<br>
>>>><br>
>>>> Can we drop 4.150.10.5 description?<br>
>>><br>
>>> openSUSE 11.3 seems to download 4.174.64.19 only with it's script and<br>
>>> I didn't heard about any reports. One more point for dropping<br>
>>> 4.150.10.5?<br>
>><br>
>> I pushed the patch to change openSUSE's script early in the beta testing for<br>
>> that release. I have heard no complaints either. I agree that 4.150.10.5 should<br>
>> be dropped.<br>
<br>
Sorry for responding so late, that bug reports scared me at first<br>
look, I switched to sth else to forgot that case.<br>
<br>
<br>
> We had serious issues with firmware version 4.174.64.19 in OpenWrt and<br>
> switched back to the old on as the default option. This issue afftected<br>
> mostly LP-PHY devices.<br>
><br>
> See the Bug report: <a href="https://dev.openwrt.org/ticket/6907" target="_blank">https://dev.openwrt.org/ticket/6907</a> This was with<br>
> kernel 2.6.32 and compat-wireless from round about March to May 2010.<br>
> Stable means the old firmware version and experimental the new one in<br>
> the bug report.<br>
<br>
OK, I can see there are 2 bug reports:<br>
<a href="https://dev.openwrt.org/ticket/7117" target="_blank">https://dev.openwrt.org/ticket/7117</a><br>
<a href="https://dev.openwrt.org/ticket/6907" target="_blank">https://dev.openwrt.org/ticket/6907</a><br>
<br>
First one #7117 is about some memory leak and "page allocation<br>
failure" as a result. It really should have nothing to do with<br>
firmware, I guess we just had some memory leak in b43.<br>
<br>
Second one #6907 is much worse...<br>
<br>
1) At beginning it's about hanging router, it seems to be also (the<br>
same?) memory leak. Probably scanning triggers it. Out of memory leads<br>
to killing process but that resulted in router hang. No firmware<br>
related. Not sure if it was fixed.<br>
<br>
2) jbemmel reported issue with card hang (not whole router), it<br>
happened with messages: "Channel switch to default failed" /<br>
"Microcode not responding". It was related to not allowed access to<br>
B43_MMIO_PHY0 register. No firmware related. Fixed by updating<br>
<a href="http://bcm-v4.sipsolutions.net/802.11/PHY/Anacore" target="_blank">http://bcm-v4.sipsolutions.net/802.11/PHY/Anacore</a><br>
<br>
3) Now, (maybe) firmware related...<br>
<br>
a) jbemmel switched to 4.150.10.5 and updated b43 at the same time and<br>
reported success. No idea what really helped.<br>
<br>
b) ldolse reported success when "building with the stable B43". Not<br>
sure if he tried experimental.<br>
<br>
c) anup.vasudev probably tried 4.150.10.5 but reported "It still dosent work"<br>
<br>
d) linchen987 tried experimental firmware only and reported success<br>
for AP, error for STA. Didn't compare to stable firmware.<br>
<br>
e) zooloz tried experimental firmware reported success for few hours,<br>
then duplicated "MAC suspend failed" messages. Didn't compare this to<br>
stable firmware.<br>
<br>
f) anonymous reported "This still dosent work with the latest build<br>
from trunk.", even after trunk witched to stable firmware as default<br>
<br>
g) metamatt posted some reports but he didn't give us direct hint<br>
about firmware version.<br>
<br>
So... generally we know nothing :| Not a single straight report about<br>
relation between firmware and stability.<br>
<font color="#888888"><br>
--<br>
Rafał<br>
<br>
_______________________________________________<br>
b43-dev mailing list<br>
<a href="mailto:b43-dev@lists.infradead.org">b43-dev@lists.infradead.org</a><br>
<a href="http://lists.infradead.org/mailman/listinfo/b43-dev" target="_blank">http://lists.infradead.org/mailman/listinfo/b43-dev</a><br>
</font></blockquote></div><br></div>