On Wed, Jan 12, 2011 at 12:04 PM, JD <jd1...@gmail.com> wrote:
> How can I extract the manufacturer's device ID from the mini-pci wifi card?
>
> Or could someone at least point me to a working windws XP(32)
> driver, since the Linux ath9k (Kernel 2.6.37) driver is unable to work with
> this card.
>
> On Tue, Jan 11, 2011 at 7:52 PM, JD <jd1...@gmail.com> wrote:
>>
>>
>> On Tue, Jan 11, 2011 at 7:42 PM, Michael Griepentrog
>> <michael.griepent...@gmail.com> wrote:
>>>
>>> On Tue, Jan 11, 2011 at 9:29 PM, JD <jd1...@gmail.com> wrote:
>>> > On Tue, Jan 11, 2011 at 7:22 PM, Michael Griepentrog
>>> > <michael.griepent...@gmail.com> wrote:
>>> >>
>>> >> On Tue, Jan 11, 2011 at 6:57 PM, JD <jd1...@gmail.com> wrote:
>>> >> >
>>> >> >
>>> >> > On Tue, Jan 11, 2011 at 2:34 PM, C Anthony Risinger
>>> >> > <anth...@extof.me>
>>> >> > wrote:
>>> >> >>
>>> >> >> On Tue, Jan 11, 2011 at 2:07 PM, JD <jd1...@gmail.com> wrote:
>>> >> >> > Dear all,
>>> >> >> > I purchased an Atheros card from Ebay. It has AR9220/AR9223
>>> >> >> > chipsets. Apparently, the card is a no-brand made in China.
>>> >> >> >
>>> >> >> > Linux kernel 2.6.37 builds ath9k drivers by default.
>>> >> >> > But for some reason, I cannot get the kernel to see
>>> >> >> > the device ath0.
>>> >> >>
>>> >> >> could be wrong here, but i don't think its called `ath0` anymore;
>>> >> >> it's
>>> >> >> `wlan0`.
>>> >> >>
>>> >> >> what does `iw list` show?
>>> >> >>
>>> >> >> or `dmesg | grep ath9k`
>>> >> >>
>>> >> >> need more infos.
>>> >> >>
>>> >> >> C Anthony
>>> >> >
>>> >> > Here's the info you asked for.
>>> >> > I feel that perhaps the card is DOA
>>> >> >
>>> >> > Script started on Tue 11 Jan 2011 08:45:38 AM PST
>>> >> > # lsmod | grep ath9k
>>> >> > ath9k                  73734  0
>>> >> > mac80211              182277  1 ath9k
>>> >> > ath9k_common            1425  1 ath9k
>>> >> > ath9k_hw              248760  2 ath9k,ath9k_common
>>> >> > ath                    10894  2 ath9k,ath9k_hw
>>> >> > cfg80211              118155  3 ath9k,mac80211,ath
>>> >> > #
>>> >> > # iw list
>>> >> > # iwconfig
>>> >> > lo        no wireless extensions.
>>> >> >
>>> >> > eth0      no wireless extensions.
>>> >> >
>>> >> > # iwlist
>>> >> > Usage: iwlist [interface] scanning [essid NNN] [last]
>>> >> >               [interface] frequency
>>> >> >               [interface] channel
>>> >> >               [interface] bitrate
>>> >> >               [interface] rate
>>> >> >               [interface] encryption
>>> >> >               [interface] keys
>>> >> >               [interface] power
>>> >> >               [interface] txpower
>>> >> >               [interface] retry
>>> >> >               [interface] ap
>>> >> >               [interface] accesspoints
>>> >> >               [interface] peers
>>> >> >               [interface] event
>>> >> >               [interface] auth
>>> >> >               [interface] wpakeys
>>> >> >               [interface] genie
>>> >> >               [interface] modulation
>>> >> > # iwlist ath0
>>> >> > iwlist: unknown command `ath0' (check 'iwlist --help').
>>> >> > # iwlist wlan0
>>> >> > iwlist: unknown command `wlan0' (check 'iwlist --help').
>>> >> > # dmesg | grep ath9
>>> >> > ath9k 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
>>> >> > ath9k 0000:00:0b.0: Failed to initialize device
>>> >> > ath9k 0000:00:0b.0: PCI INT A disabled
>>> >> > ath9k: probe of 0000:00:0b.0 failed with error -22
>>> >> > #
>>> >> >
>>> >> > Script done on Tue 11 Jan 2011 08:46:37 AM PST
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> >
>>> >> > _______________________________________________
>>> >> > ath9k-devel mailing list
>>> >> > ath9k-devel@lists.ath9k.org
>>> >> > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
>>> >> >
>>> >> >
>>> >>
>>> >> You want to run "iw list", not "iwlist" (see:
>>> >> http://wireless.kernel.org/en/users/Documentation/iw).
>>> >>
>>> >> Does it show up under lspci or lsusb? It should considering the
>>> >> modules are getting loaded correctly.
>>> >>
>>> >> -Michael Griepentrog
>>> >
>>> > Did you miss this:
>>> >
>>> > # dmesg | grep ath9
>>> > ath9k 0000:00:0b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
>>> > ath9k 0000:00:0b.0: Failed to initialize device
>>> > ath9k 0000:00:0b.0: PCI INT A disabled
>>> > ath9k: probe of 0000:00:0b.0 failed with error -22
>>> >
>>> > Also, you missed:
>>> > # iw list   <<<<< No output - i.e. no wireless interfaces found.
>>> > # iwconfig
>>> > lo        no wireless extensions.
>>> >
>>> > eth0      no wireless extensions.
>>> >
>>> > iwconfig did not list any other available interface
>>> >
>>> >
>>>
>>> Yes, I did miss that :P. If you see something interesting in
>>> lspci/lsusb, you may want to post it back to the mailing list.
>>>
>>> -Michael Griepentrog
>>
>> I thought I had provided that too, but here it is:
>>
>> # lspci | grep -i atheros
>> 00:0b.0 Network controller: Atheros Communications Inc. AR922X Wireless
>> Network
>>
>> It is not a USB device.
>>

lspci -n will give the vendor and device IDs.

Have you tried re-seating the card?  Sometimes removing the card and
reinserting it helps.

-Brian
_______________________________________________
ath9k-devel mailing list
ath9k-devel@lists.ath9k.org
https://lists.ath9k.org/mailman/listinfo/ath9k-devel

Reply via email to