Re: b43-phy0 error : PHY transmission error

--===============4580115072861511022==
Content-Type: multipart/alternative; boundary=00504502ae8e4ddc5a047a19f5d9

--00504502ae8e4ddc5a047a19f5d9
Content-Type: text/plain; charset=ISO-8859-1

Thanks for your patient explainations. I am now begin my linux on a
virtualbox to study it :)

2009/12/6 Albert Herranz <[email protected]>

> <cailei1983 <at> gmail.com> writes:
>
> >
> > Hi
> > After I configure my wifi with /root/whiite-ez-wifi-config, I am now able
> > to use wifi on my wii. However, there is a problem when I am trying to
> use
> > MLDonkey to download through ED2K or BT. There have been successful
> downloads
> > which are smaller than 200MB, but that is only for my testing purpose.
> Then
> > with the larger files, I got lots of following error:b43-phy0 ERROR : PHY
> > transmission errorI have google the problem, it seems that this error is
> caused
> > by some kernel wireless card problem. I wonder if that could be fix on
> the
> > whiite (sorry, I am such a newbie to linux just start to learn it because
> of
> > my wii and the wonderful whiite ~). If the answer is yes, then is there
> any
> > documents or hints on how to do it?Many Thanks ~~~
> >
>
> Hi,
>
> The error message you are seeing is caused by how the b43 does VCO
> calibration
> every 60 seconds.
> At that time, the driver switches from your current channel to channel 1 or
> 13
> (depending on your current channel). If a transmission takes place during
> that
> time frame, the data frame is dropped and the "PHY transmission error" is
> generated
> because the current channel and the channel for which the frame is targeted
> do
> not match.
>
> Note that the message is harmless and causes no problem except a drop of a
> transmission frame, which the higher level protocols can recover from.
> The message does actually only show up when the driver is compiled with
> DEBUG
> on.
>
> So, this is an "error" of b43 (it shouldn't try transmitting while the
> channel
> switch happens), but shouldn't be an actual problem. Just annoying dmesg
> spam.
>
> Cheers,
> Albert
>
>
>

--00504502ae8e4ddc5a047a19f5d9
Content-Type: text/html; charset=ISO-8859-1

Thanks for your patient explainations. I am now begin my linux on a virtualbox to study it :)<br><br><div class="gmail_quote">2009/12/6 Albert Herranz <span dir="ltr">&lt;<a href="mailto:[email protected]">[email protected]</a>&gt;</span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">&lt;cailei1983 &lt;at&gt; <a href="http://gmail.com" target="_blank">gmail.com</a>&gt; writes:<br>

<br>
&gt;<br>
&gt; Hi<br>
&gt; After I configure my wifi with /root/whiite-ez-wifi-config, I am now able<br>
&gt; to use wifi on my wii. However, there is a problem when I am trying to use<br>
&gt; MLDonkey to download through ED2K or BT. There have been successful downloads<br>
&gt; which are smaller than 200MB, but that is only for my testing purpose. Then<br>
&gt; with the larger files, I got lots of following error:b43-phy0 ERROR : PHY<br>
</div>&gt; transmission errorI have google the problem, it seems that this error is caused<br>
<div class="im">&gt; by some kernel wireless card problem. I wonder if that could be fix on the<br>
&gt; whiite (sorry, I am such a newbie to linux just start to learn it because of<br>
&gt; my wii and the wonderful whiite ~). If the answer is yes, then is there any<br>
&gt; documents or hints on how to do it?Many Thanks ~~~<br>
&gt;<br>
<br>
</div>Hi,<br>
<br>
The error message you are seeing is caused by how the b43 does VCO calibration<br>
every 60 seconds.<br>
At that time, the driver switches from your current channel to channel 1 or 13<br>
(depending on your current channel). If a transmission takes place during that<br>
time frame, the data frame is dropped and the &quot;PHY transmission error&quot; is generated<br>
because the current channel and the channel for which the frame is targeted do<br>
not match.<br>
<br>
Note that the message is harmless and causes no problem except a drop of a<br>
transmission frame, which the higher level protocols can recover from.<br>
The message does actually only show up when the driver is compiled with DEBUG<br>
on.<br>
<br>
So, this is an &quot;error&quot; of b43 (it shouldn&#39;t try transmitting while the channel<br>
switch happens), but shouldn&#39;t be an actual problem. Just annoying dmesg spam.<br>
<br>
Cheers,<br>
<font color="#888888">Albert<br>
<br>
<br>
</font></blockquote></div><br>

--00504502ae8e4ddc5a047a19f5d9--


--===============4580115072861511022==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing. 
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
--===============4580115072861511022==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
gc-linux-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gc-linux-devel

--===============4580115072861511022==--