From mboxrd@z Thu Jan 1 00:00:00 1970 From: Luis R. Rodriguez Date: Wed, 29 Sep 2010 15:08:48 -0700 Subject: [ath9k-devel] [internal-ath9k-devel] PCI device 168c:ff1c ("AR5008", possibly Apple-branded) In-Reply-To: <20100929214230.GA3323065@jupiter.n2.diac24.net> References: <20100926133935.GA2405354@jupiter.n2.diac24.net> <93781E992CBA7843962D8B0E7D683F3C15C6EE4E9C@SC1EXMB-MBCL.global.atheros.com> <20100927195402.GA2933263@jupiter.n2.diac24.net> <20100927200839.GB2933263@jupiter.n2.diac24.net> <20100927202502.GJ2429@tux> <20100927204447.GC2933263@jupiter.n2.diac24.net> <20100929214230.GA3323065@jupiter.n2.diac24.net> Message-ID: <20100929220847.GF2050@tux> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org On Wed, Sep 29, 2010 at 02:42:30PM -0700, David Lamparter wrote: > On Mon, Sep 27, 2010 at 10:44:47PM +0200, David Lamparter wrote: > > there are two atheros device IDs - ff1c > > and ff1d - that designate AR5008 cards (according to pci.ids and google) > > and that are not supported by any driver currently. > > > > Are these cards driver compatible to the 0023/0024 devices? Do they need > > different workarounds? > > On Sun, Sep 26, 2010 at 03:39:35PM +0200, David Lamparter wrote: > > 02:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5008 Wireless Network Adapter [168c:ff1c] (rev 01) > > I've now tried madwifi and ndiswrapper. To sum up: > > - ath9k: ath9k_hw_chip_test fails: > (ath9k modified to add PCI ID 168c:ff1c) > "address test failed addr: 0x00008000 - wr:0xaaaaaaaa != rd:0xaaaaaaab" > > - madwifi trunk: > (madwifi modified to add PCI ID 168c:ff1c) > "MadWifi: unable to attach hardware: '' (HAL status 1434461696) > (1434461696 = 0x55802600) > > - ndiswrapper with 7.7.0.523 WinXP 64-bit driver: > (driver lists 168c:ff1c in .inf file, no modification) > ndiswrapper (link_pe_images:566): fixing KI_USER_SHARED_DATA address in the driver > ndiswrapper: driver netathwx (,06/04/2010,7.7.0.523) loaded > ndiswrapper 0000:02:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > ndiswrapper 0000:02:00.0: setting latency timer to 64 > ndiswrapper (NdisWriteErrorLogEntry:190): log: C000138B, count: 25, return_address: ffffffffa021851b > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x21bd5000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x19 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x21bd5000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x21bd5000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xa020e750 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xc000138b > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x7bcc7000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xffffffff > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x76aec000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x21bd5000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x76aec000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x224e94c6 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x225750a8 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xff1c168c > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x4 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x738d3484 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x19 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x21bd5000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x21bd5000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xa020e750 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xc000138b > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x7bcc7000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0xffffffff > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x76aec000 > ndiswrapper (NdisWriteErrorLogEntry:193): code: 0x7b84c560 > ndiswrapper (mp_init:219): couldn't initialize device: C0010006 > ndiswrapper (pnp_start_device:435): Windows driver couldn't initialize the device (C0000001) > ndiswrapper (mp_halt:262): device ffff880076a04800 is not initialized - not halting Your device is bust then it seems. > Any hints on what this elusive 168c:ff1c device (and :ff1d) actually > is? Mac and Windows drivers *do* list these IDs... No, not sure, perhaps a mistake upon programming the EEPROM somehow? Luis