ath9k - D-link DWA-552

ath9k - D-link DWA-552

[Andy Pyles]

I have recently purchased two of these cards. ( the markings on the
outside indicate they have are same hardware revision). I am noticing
some strange behavior on one of them:

Card One ( this one works)
$lspci -v output"


05:02.0 Network controller: Atheros Communications Inc. AR5008
Wireless Network Adapter (rev 01)
	Subsystem: D-Link System Inc Device 3a6d
	Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18
	Memory at fbde0000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [40] #80 [0000]
	Kernel driver in use: ath9k
	Kernel modules: ath9k

$lspci -n output:
05:02.0 0280: 168c:0023 (rev 01)


Card Two ( this one doesn't work )
$lspci -v output:

05:05.0 Ethernet controller: Atheros Communications Inc. AR5008
Wireless Network Adapter (rev 01)
	Subsystem: Atheros Communications Inc. Device ee1c
	Flags: 66MHz, medium devsel, IRQ 17
	Memory at fbdf0000 (32-bit, non-prefetchable) [size=64K]
	Capabilities: [40] #80 [0000]
	Kernel modules: ath9k

$lspci -n output:
05:05.0 0200: 168c:ff1d (rev 01)
---

Has anyone else seen this behavior with Card Two? I tried swapping to
a different PCI slot, even to a different PC.
Same symptom. I also tried modifying pci.c in ath9k driver to no effect.

Re: ath9k - D-link DWA-552

[Pavel Roskin]

On Wed, 2010-07-21 at 14:58 -0400, Andy Pyles wrote:
> I have recently purchased two of these cards. ( the markings on the
> outside indicate they have are same hardware revision). I am noticing
> some strange behavior on one of them:
...
> $lspci -n output:
> 05:05.0 0200: 168c:ff1d (rev 01)

This looks like some experimental version that was not meant to be sold.

> Has anyone else seen this behavior with Card Two? I tried swapping to
> a different PCI slot, even to a different PC.
> Same symptom. I also tried modifying pci.c in ath9k driver to no effect.

If you add the PCI ID to the driver, something should change.  The
driver would try to initialize the card.  If it fails, you should get
some message in the kernel log, which can be seen by running dmesg.

-- 
Regards,
Pavel Roskin

Re: ath9k - D-link DWA-552

[Andy Pyles]

Hi Pavel,

Incidentally this is the output after adding that id to pci.c:

[ 1211.423855] Backport based on linux-next.git next-20100720
[ 1211.437076] cfg80211: World regulatory domain updated:
[ 1211.437080]     (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 1211.437084]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1211.437087]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1211.437089]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 1211.437092]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1211.437095]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 1211.447705] ath9k 0000:05:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[ 1211.447794] ath9k 0000:05:02.0: Failed to initialize device
[ 1211.447830] ath9k 0000:05:02.0: PCI INT A disabled
[ 1211.447859] ath9k: probe of 0000:05:02.0 failed with error -95



On Fri, Jul 23, 2010 at 10:02 PM, Pavel Roskin <proski@gnu.org> wrote:
> On Wed, 2010-07-21 at 14:58 -0400, Andy Pyles wrote:
>> I have recently purchased two of these cards. ( the markings on the
>> outside indicate they have are same hardware revision). I am noticing
>> some strange behavior on one of them:
> ...
>> $lspci -n output:
>> 05:05.0 0200: 168c:ff1d (rev 01)
>
> This looks like some experimental version that was not meant to be sold.
>
>> Has anyone else seen this behavior with Card Two? I tried swapping to
>> a different PCI slot, even to a different PC.
>> Same symptom. I also tried modifying pci.c in ath9k driver to no effect.
>
> If you add the PCI ID to the driver, something should change.  The
> driver would try to initialize the card.  If it fails, you should get
> some message in the kernel log, which can be seen by running dmesg.
>
> --
> Regards,
> Pavel Roskin
>

Re: ath9k - D-link DWA-552

[Pavel Roskin]

On Fri, 2010-07-23 at 22:30 -0400, Andy Pyles wrote:
> Hi Pavel,
> 
> Incidentally this is the output after adding that id to pci.c:
> 
> [ 1211.423855] Backport based on linux-next.git next-20100720
> [ 1211.437076] cfg80211: World regulatory domain updated:
> [ 1211.437080]     (start_freq - end_freq @ bandwidth),
> (max_antenna_gain, max_eirp)
> [ 1211.437084]     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437087]     (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437089]     (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437092]     (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 1211.437095]     (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
> [ 1211.447705] ath9k 0000:05:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
> [ 1211.447794] ath9k 0000:05:02.0: Failed to initialize device
> [ 1211.447830] ath9k 0000:05:02.0: PCI INT A disabled
> [ 1211.447859] ath9k: probe of 0000:05:02.0 failed with error -95

You may want to post it to ath9k-devel@lists.ath9k.org

It looks like a hardware problem.  Either the device is broken, or it's
an experimental chip that is not supported by ath9k.  There have been
patches removing support for cards that have never been sold (or were
not supposed to be sold).  Maybe your card ended up with an experimental
chip by mistake.

-- 
Regards,
Pavel Roskin