All of lore.kernel.org
 help / color / mirror / Atom feed
* did my hardware die?
@ 2011-09-17 22:40 James
  2011-09-17 23:22 ` James
  0 siblings, 1 reply; 4+ messages in thread
From: James @ 2011-09-17 22:40 UTC (permalink / raw)
  To: linux-wireless Mailing List

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)

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: did my hardware die?
  2011-09-17 22:40 did my hardware die? James
@ 2011-09-17 23:22 ` James
  2011-09-17 23:48   ` Larry Finger
  0 siblings, 1 reply; 4+ messages in thread
From: James @ 2011-09-17 23:22 UTC (permalink / raw)
  To: linux-wireless Mailing List

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.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: did my hardware die?
  2011-09-17 23:22 ` James
@ 2011-09-17 23:48   ` Larry Finger
  2011-09-18  5:15     ` James
  0 siblings, 1 reply; 4+ messages in thread
From: Larry Finger @ 2011-09-17 23:48 UTC (permalink / raw)
  To: James; +Cc: linux-wireless Mailing List

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


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: did my hardware die?
  2011-09-17 23:48   ` Larry Finger
@ 2011-09-18  5:15     ` James
  0 siblings, 0 replies; 4+ messages in thread
From: James @ 2011-09-18  5:15 UTC (permalink / raw)
  To: linux-wireless Mailing List

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.


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2011-09-18  5:13 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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 is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.