On Fri, 2008-12-12 at 15:04 -0500, Bob Copeland wrote:
> On Fri, Dec 12, 2008 at 2:34 PM, Maxim Levitsky
> wrote:
>
> > It does seem to be RS related, as I see that rate changes rapidly from 1
> > to 24 and back, also when I set rate to 24 or above nothing gets
> > transmitted/received through t
On Fri, Dec 12, 2008 at 03:28:13PM -0800, Lucio Torre wrote:
> Hi,
>
> Im running intrepid on a lenovo x200, using the wifi drivers from
> http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2
> and keep having some strange issues. Most of the time what happens is
> t
Hi,
Im running intrepid on a lenovo x200, using the wifi drivers from
http://wireless.kernel.org/download/compat-wireless-2.6/compat-wireless-2.6.tar.bz2
and keep having some strange issues. Most of the time what happens is
that wifi suddendly dies and i have to restart my machine to get wifi
back
On Fri, Dec 12, 2008 at 2:34 PM, Maxim Levitsky wrote:
> It does seem to be RS related, as I see that rate changes rapidly from 1
> to 24 and back, also when I set rate to 24 or above nothing gets
> transmitted/received through the wireless card.
Ok, thanks, there could be bugs with how we repor
On Fri, 2008-12-12 at 14:49 -0500, Bob Copeland wrote:
> On Fri, Dec 12, 2008 at 2:40 PM, Maxim Levitsky
> wrote:
> > It sometimes happen on resume from ram.
> >
> > It is NOT noise calibration, but a gain calibration timeout
> > Only fix is to reboot the system, as module reload doesn't help.
>
On Fri, Dec 12, 2008 at 2:40 PM, Maxim Levitsky wrote:
> It sometimes happen on resume from ram.
>
> It is NOT noise calibration, but a gain calibration timeout
> Only fix is to reboot the system, as module reload doesn't help.
I really think it is various sides of the same coin with multiple
man
On Fri, 2008-11-21 at 21:58 +0200, Maxim Levitsky wrote:
> Hi,
>
> I captured few errors in dmesg, will post them here.
> If I see more errors, I add them to this thread.
>
>
> [ 69.516498] ath5k phy0: gain calibration timeout (2412MHz)
> [ 69.516509] ath5k phy0: can't reset hardware (-11)
>
On Thu, 2008-12-11 at 22:41 -0500, Bob Copeland wrote:
> > So, any ideas?
>
> I may have missed it but, as I asked before, which rate
> controller are you using? Try minstrel if you are using pid.
>
> ANI will presumably help some, that's a work in progress...
>
Still use pid, I will test mins
On Fri, Dec 12, 2008 at 3:49 AM, Benoit PAPILLAULT
wrote:
> Nice catch! I wonder how it was working in my preliminary tests. Sorry
> for the duplicates with the same patch for ath9k. The padding/unpadding
> stuff is needed by the hardware, ie the hardware insert padding on RX
> and expect padding
Johannes Berg a écrit :
> On Thu, 2008-12-11 at 14:08 -0800, Harvey Harrison wrote:
>> On Thu, 2008-12-11 at 22:58 +0100, Benoit PAPILLAULT wrote:
>>> Padding the 802.11 header to a multiple of 4 bytes needs to be done only
>>> for DATA frames. This fixes a bug where 2 bytes were missing in monitor
10 matches
Mail list logo
