Hi, The BIOS doesn't "read" the EEPROM on the NIC. The NIC is supposed to read the EEPROM upon powerup (and on PCI bus reset?) and setup the initial PCI/register contents from that.
I've seen this before: * sometimes the NIC itself is damaged; * sometimes the type of board it's on is the only difference. So the question really is - what's that BIOS doing that is stopping the NIC from successfully bootstrapping the initial register values from EEPROM? It likely would be solved with the application of a PCI/PCIe bus analyser.. Adrian On 10 January 2012 08:36, Hasan Rashid <hras...@avionica.com> wrote: > Manuel, > > I figured out that the problem is with the BIOS on the motherboard of the > host device. Some BIOS do not fully read the EPROM contents on the Sparklan > radio. I have used the Sparklan PCIe express card on the same embedded > baseboard with Intel Atom Q7 modules and it seems to be properly recognized > by one and not the other from a different manufacturer. The BIOS was on the > Q7 modules and not the baseboard so each module had a different BIOS. > > Apart from that if lspci is showing you 168c:abcd then you have the correct > line added in pci.c. From your dmesg log it appears you force it to load a > hardware with that subvendor id but upon scanning the bus its unable to find > the physical device. I'd say start from making sure, you have it properly > inserted in the PCIe slot, and then work your way up. > > > - Hasan R. > > > >>-----Original Message----- >>From: Manuel Sáez [mailto:manuelsa...@gmail.com] >>Sent: Tuesday, January 10, 2012 11:20 AM >>To: Hasan Rashid >>Cc: Mohammed Shafi; ath9k-devel@lists.ath9k.org >>Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd >> >>Hi, >> >>I am having the same problem with two devices. Sparklan WPA-127N >>(AR9380) and WLE300NX 6B (AR9390). >> >>I added the line >> >>{ PCI_VDEVICE(ATHEROS, 0xabcd) }, /* PCI-E AR9300 */ >> >>in pci.c but it did not work. This is the output of dmesg: >> >>[17464.277232] ath9k 0000:01:00.0: PCI INT A -> GSI 16 (level, >>low) -> IRQ 16 >>[17464.277258] ath9k 0000:01:00.0: setting latency timer to 64 >>[17464.277408] ath: Hardware device ID 0xabcd not supported >>[17464.277426] ath9k 0000:01:00.0: Failed to initialize device >>[17464.277738] ath9k 0000:01:00.0: PCI INT A disabled >>[17464.277770] ath9k: probe of 0000:01:00.0 failed with error -95 >> >>Did you solved the problem? >> >>Thank you and best regards >> >>2011/4/12, Hasan Rashid <hras...@avionica.com>: >>> >>> I found out the issue is not with the hardware or ath9k. It >>is with the >>> tablet that I am using. On my Dell Vostro 1520 the pci >>device ID is reported >>> correctly without any issues. On the tablet the same card is >>reported as an >>> Ethernet Controller and the bogus vendor id. >>> >>> On another note, even with the correct vendor id, regardless of AP or >>> Station mode, the transmit rate is still limited 54MBit/sec. >>> >>> For now, I think we can close this thread on the note that >>the bogus vendor >>> id is not an ath9k issue. >>> >>> Thanks for all the help. >>> >>> -----Original Message----- >>> From: Mohammed Shafi [mailto:shafi.at...@gmail.com] >>> Sent: Tue 4/12/2011 7:46 AM >>> To: Hasan Rashid >>> Cc: ath9k-devel@lists.ath9k.org >>> Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd >>> >>> On Mon, Apr 11, 2011 at 11:24 PM, Hasan Rashid >><hras...@avionica.com> wrote: >>>> >>>> I have attached the driver load output in dmesg. >>>> >>>> By the way why does AR9382 require Kernel 2.6.36 or higher? >>Can you list >>>> the major requirements? >>> >>> because the hardware code(HAL) will be present from that >>kernel version >>> only. >>>> >>>> Hasan R. >>>> >>>> -----Original Message----- >>>> From: ath9k-devel-boun...@lists.ath9k.org >>>> [mailto:ath9k-devel-boun...@lists.ath9k.org] On Behalf Of >>Peter Stuge >>>> Sent: Monday, April 11, 2011 12:20 PM >>>> To: ath9k-devel@lists.ath9k.org >>>> Subject: Re: [ath9k-devel] Sparklan WPEA-121N AR9382 168c:abcd >>>> >>>> Mohammed Shafi wrote: >>>>> to make sure that HT is configured in driver please do this >>>>> >>>>> diff --git a/drivers/net/wireless/ath/ath9k/hw.c >>>>> b/drivers/net/wireless/ath/ath9k/hw.c >>>>> index 1b5bd13..720a866 100644 >>>>> --- a/drivers/net/wireless/ath/ath9k/hw.c >>>>> +++ b/drivers/net/wireless/ath/ath9k/hw.c >>>>> @@ -1855,6 +1855,8 @@ int ath9k_hw_fill_cap_info(struct ath_hw *ah) >>>>> else >>>>> pCap->hw_caps &= ~ATH9K_HW_CAP_HT; >>>>> >>>>> + pCap->hw_caps |= ATH9K_HW_CAP_HT; >>>>> + >>>> >>>> The indentation is off, or do you mean to include the added >>line only >>>> within the else block? If so, remember to add braces. >>>> >>>> >>>> //Peter >>>> _______________________________________________ >>>> ath9k-devel mailing list >>>> ath9k-devel@lists.ath9k.org >>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >>>> >>>> This communication contains information that may be confidential or >>>> privileged. The information is solely intended for the use of the >>>> addressee. If you are not the intended recipient, be >>advised that any >>>> disclosure, copy, distribution, or use of the contents of this >>>> communication is prohibited. If you have received this >>communication in >>>> error, please immediately notify the sender by telephone or >>by electronic >>>> mail. >>>> _______________________________________________ >>>> ath9k-devel mailing list >>>> ath9k-devel@lists.ath9k.org >>>> https://lists.ath9k.org/mailman/listinfo/ath9k-devel >>>> >>>> >>> >>> >>> This communication contains information that may be confidential or >>> privileged. The information is solely intended for the use >>of the addressee. >>> If you are not the intended recipient, be advised that any >>disclosure, copy, >>> distribution, or use of the contents of this communication >>is prohibited. If >>> you have received this communication in >>> error, please immediately notify the sender by telephone or >>by electronic >>> mail. >> > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
