linux-kernel - Re: ath9k seems to be broken on 2.6.30-rc4 with a macbook pro

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <43e72e890905111524t27c2659crad86643771d14a31@mail.gmail.com>
Date:	Mon, 11 May 2009 15:24:59 -0700
From:	"Luis R. Rodriguez" <mcgrof@...il.com>
To:	Jiri Slaby <jirislaby@...il.com>
Cc:	Justin Mattock <justinmattock@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ath9k-devel@...ts.ath9k.org, linux-wireless@...r.kernel.org
Subject: Re: ath9k seems to be broken on 2.6.30-rc4 with a macbook pro

On Mon, May 11, 2009 at 2:53 PM, Jiri Slaby <jirislaby@...il.com> wrote:
> Adding some CCs.
>
> On 05/11/2009 07:02 PM, Justin Mattock wrote:
>> I've been trying to diagnose an issue
>> with 2.6.30-rc4. At first thinking it
>> was not the kernel, but the network manager
>> (in my case I use wicd).
>> with 2.6.29-rc8 the system starts up,
>> connects no problem.
>> but as soon as I load 2.6.30-rc4
>> I get limited connection to none.
>> in dmesg I see:
>>
>> [   36.337419] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 1
>> [   36.530106] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 2
>> [   36.730100] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 3
>> [   36.930101] wlan0: direct probe to AP 00:1e:2a:00:67:f0 timed out
>> [   44.421728] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 1
>> [   44.620080] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 2
>> [   44.820080] wlan0: direct probe to AP 00:1e:2a:00:67:f0 try 3
>> [   45.020076] wlan0: direct probe to AP 00:1e:2a:00:67:f0 timed out
>>
>> The type of encryption used is just
>> a standard WEP key(no WPA).
>>
>> has this been resolved already?

Can you provide more details, like the AP you used, and card you have?
(dmesg log would be nice).

  Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/