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]

Date:	Mon, 11 May 2009 16:23:14 -0700
From:	Justin Mattock <justinmattock@...il.com>
To:	"Luis R. Rodriguez" <mcgrof@...il.com>
Cc:	Jiri Slaby <jirislaby@...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 3:24 PM, Luis R. Rodriguez <mcgrof@...il.com> wrote:
> 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
>

The AP I use is a
netgear 54g(cheap 40 dollar router from
bestbuy)

attached is dmesg and lspci
disregard the kernel commits
2.6.30-rc4-00004-gfb422e6
(those are from the bluetooth patches a few
days ago) without them the kernel is at
2.6.30-rc4.


-- 
Justin P. Mattock

Download attachment "dmesg" of type "application/octet-stream" (54379 bytes)