On Thu, Jul 26, 2012 at 10:34 AM, Mohammed Shafi
[off-list ref] wrote:

On Thu, Jul 26, 2012 at 10:31 AM, Tim and Alison Bentley
[off-list ref] wrote:

quoted

On 26 July 2012 02:25, Gábor Stefanik [off-list ref] wrote:

quoted

On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger
[off-list ref] wrote:

quoted

On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote:

quoted

On 25 July 2012 19:33, Larry Finger [off-list ref] wrote:

quoted

On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:

quoted

01:00.0 VGA compatible controller [0300]: nVidia Corporation Device
[10de:0de9] (rev a1)
03:00.0 Network controller [0280]: Atheros Communications Inc. Device
[168c:0037] (rev 01)
04:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev
07)

The Realtek device is the one used for your wired network.

The Atheros device is not in the tables for the latest version of any
wireless driver. Perhaps it will work if you do the following:

su -
modprobe -v ath9k
echo "168c 0037" > /sys/bus/pci/drivers/ath9k/new_id
exit

The above will work if the driver handles the device, but it is not yet
in
the tables. Perhaps the Atheros developers will know the status of that
device.

When replying to E-mail in this list, and most other technical mailing
lists, please do not top post. Always put your answer below the quoted
material as I did here.

Larry

Sorry for top posting, bad habbit
No luck with the suggestion and I tried a reboot for luck with no success.

The effect of those commands would have disappeared after a reboot. One last
thing to do is to check /var/log/messages to see if it complained about
missing firmware after you entered the new_id. There should be some kind of
error messages at that point, but it is likely that no Linux driver handles
this device.

You might try ndiswrapper and the Windows driver, but if the system is
64-bit, then that might not work either.

Larry

168c:0037 appears to be a chipset called "AR1111", based on Windows
drivers. However, I suspect this is a provisional/placeholder name.

Re ran the commands and have the /var/log/messages output

Jul 26 05:58:23 tigger2 kernel: [ 1546.876477] cfg80211: Calling CRDA
to update world regulatory domain
Jul 26 05:58:23 tigger2 kernel: [ 1546.916447] cfg80211: World
regulatory domain updated:
Jul 26 05:58:23 tigger2 kernel: [ 1546.916450] cfg80211:   (start_freq
- end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Jul 26 05:58:23 tigger2 kernel: [ 1546.916453] cfg80211:   (2402000
KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 26 05:58:23 tigger2 kernel: [ 1546.916455] cfg80211:   (2457000
KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jul 26 05:58:23 tigger2 kernel: [ 1546.916457] cfg80211:   (2474000
KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Jul 26 05:58:23 tigger2 kernel: [ 1546.916459] cfg80211:   (5170000
KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 26 05:58:23 tigger2 kernel: [ 1546.916461] cfg80211:   (5735000
KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Jul 26 05:58:30 tigger2 kernel: [ 1553.767939] ath: phy0: Hardware
device ID 0x0037 not supported

it wasn't there in the device ID table in pci.c of ath9k, lets see
this chip is actually
has h/w code support in ath9k.

yes indeed its AR1111, seems like a AR9485 chip.

quoted

Jul 26 05:58:30 tigger2 kernel: [ 1553.767948] ath9k 0000:03:00.0:
Failed to initialize device
Jul 26 05:58:30 tigger2 kernel: [ 1553.768137] ath9k: probe of
0000:03:00.0 failed with error -95


--
Tim and Alison Bentley
Home@TRARBentley.net
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
thanks,
shafi

-- 
thanks,
shafi