On 7 May 2011 06:53, Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote: [top post] Ok, there's likely some PCI init bugs going on here; would someone with more background in this please take a look? Adrian >>> This and the previous AR93xx "0xabcd" device id post is starting to >>> sound a lot like something's not waking up the PCI bus and/or chip >>> "right" in order to get the PCI vendor id init'ed from the EEPROM.. >> >> Well, I put in one NIC, it works fine, I put in the other, and it doesn't. >> >> Same system, reproducible on other systems from same manufacturer >> (Lanner, LEC 2010E). >> >> Haven't tried it on a totally different motherboard. I'll send you this >> broken NIC if you want...I'm too tight on time to hack on it now... > > So, you were right. I put this NIC in another system (VIA C3) and it comes > up > as AR9160 and loads ath9k driver just fine. > > 00:0c.0 Network controller: Atheros Communications Inc. AR9160 802.11abgn > Wireless PCI Adapter (rev 01) > Subsystem: Device 0777:4082 > Flags: bus master, 66MHz, medium devsel, latency 168, IRQ 18 > Memory at f6000000 (32-bit, non-prefetchable) [size=64K] > Capabilities: [44] Power Management version 2 > Kernel driver in use: ath9k > Kernel modules: ath9k > > Thanks, > Ben > >> >> Ben >> >> > > > -- > Ben Greear <greearb@xxxxxxxxxxxxxxx> > Candela Technologies Inc http://www.candelatech.com > > -- > 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 > -- 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
