From: James <bjlockie@lockie.ca>
To: linux-wireless Mailing List <linux-wireless@vger.kernel.org>
Subject: Re: did my hardware die?
Date: Sun, 18 Sep 2011 01:15:28 -0400 [thread overview]
Message-ID: <4E757E70.9000400@lockie.ca> (raw)
In-Reply-To: <4E7531E9.8010708@lwfinger.net>
On 09/17/11 19:48, Larry Finger wrote:
> On 09/17/2011 06:22 PM, James wrote:
>> On 09/17/11 18:40, James wrote:
>>> Does it mean my hardware died since dmesg shows nothing related to ath?
>>>
>>> # dmesg | grep ath
>>>
>>> # lspci
>>> 02:09.0 Network controller: Atheros Communications Inc. AR5008 Wireless
>>> Network Adapter (rev 01)
>>> --
>>> 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
>>>
>> Kernel 3.6.36.4 sees the hardware:
>>
>> ath9k 0000:02:08.0: PCI INT A -> Link[LNKA] -> GSI 18 (level, low) ->
>> IRQ 18
>> ath: EEPROM regdomain: 0x10
>> ath: EEPROM indicates we should expect a direct regpair map
>> ath: Country alpha2 being used: CO
>> ath: Regpair used: 0x10
>> ieee80211 phy0: Selected rate control algorithm 'ath9k_rate_control'
>> Registered led device: ath9k-phy0
>>
>> Kernel-3.0.4 does not.
>
> What are the PCI ID's for that device? That comes from 'lspci -nn'.
>
> What is the source of your 3.0.4 kernel?
>
> Larry
I recompiled 3.0.4 and it works.
I took out ath9k debugging (and maybe other stuff) and put it back.
I got the kernel directly from kernel.org a while ago.
prev parent reply other threads:[~2011-09-18 5:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 22:40 did my hardware die? James
2011-09-17 23:22 ` James
2011-09-17 23:48 ` Larry Finger
2011-09-18 5:15 ` James [this message]
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=4E757E70.9000400@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).