From: James <bjlockie@lockie.ca>
To: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: kernel-2.6.36.2 works, later doesn't
Date: Thu, 24 Mar 2011 10:27:21 -0400 [thread overview]
Message-ID: <4D8B54C9.1020203@lockie.ca> (raw)
In-Reply-To: <4D86B222.4070708@lockie.ca>
On 03/20/11 22:04, James wrote:
> On 03/20/11 17:04, James wrote:
>> $ dmesg | grep phy
>> BIOS-provided physical RAM map:
>> modified physical RAM map:
>> phy0: Selected rate control algorithm 'ath9k_rate_control'
>> Registered led device: ath9k-phy0::radio
>> Registered led device: ath9k-phy0::assoc
>> Registered led device: ath9k-phy0::tx
>> Registered led device: ath9k-phy0::rx
>> phy0: Atheros AR5416 MAC/BB Rev:2 AR2133 RF Rev:81
>> mem=0xffffc90001900000, irq=17
>>
>> This is kernel-2.6.36.2.
>> The wireless doesn't work on any later kernel that I have tried.
>> It is very interesting the IRQ is 17 on this kernel but 18 on 2.6.37.3.
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
> I tried
> http://www.orbit-lab.org/kernel/compat-wireless-2.6-stable/v2.6.36/compat-wireless-2.6.36-4.tar.bz2
> but it doesn't work in the 2.6.36.2 kernel or the 2.6.38 kernel.
>
> Where can I get the compat-wireless that is the exact code that is in
> the 2.6.36.2 kernel and then I can try it in the 2.6.38 kernel?
It might be kernel related.
Someone else has the same problem:
https://bugzilla.kernel.org/show_bug.cgi?id=27392
next prev parent reply other threads:[~2011-03-24 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 21:04 kernel-2.6.36.2 works, later doesn't James
2011-03-21 2:04 ` James
2011-03-24 14:27 ` James [this message]
2011-03-24 16:51 ` Sedat Dilek
2011-03-25 3:54 ` James
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D8B54C9.1020203@lockie.ca \
--to=bjlockie@lockie.ca \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).