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@xxxxxxx> 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 > -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
