I have a new laptop and running the latest version of Fedora 17 it
cannot see the Wireless card.
lspci -k
01:00.0 VGA compatible controller: nVidia Corporation Device 0de9 (rev
a1)
Subsystem: Device 1b0a:20dd
Kernel driver in use: nouveau
03:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev 01)
Subsystem: Lite-On Communications Inc Device 6618
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 07)
Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
Kernel driver in use: r8169
lspci -v
03:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev 01)
Subsystem: Lite-On Communications Inc Device 6618
Flags: bus master, fast devsel, latency 0, IRQ 3
Memory at f7200000 (64-bit, non-prefetchable) [size=512K]
Expansion ROM at f7280000 [disabled] [size=64K]
Capabilities: <access denied>
Is this chip known upstream or a new one?
[18:28][tim@tigger2] ~ $uname -a
Linux tigger2 3.4.6-2.fc17.x86_64 #1 SMP Thu Jul 19 22:54:16 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
[18:29][tim@tigger2] ~ $
--
Tim and Alison Bentley
[email protected]
On Sat, Jul 28, 2012 at 12:01 PM, Tim and Alison Bentley
<[email protected]> wrote:
> On 26 July 2012 06:26, Mohammed Shafi <[email protected]> wrote:
>>> 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
>>> 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
>>
>> can you please try the attached dummy patch. see if the device is working.
>> if its a version of AR9485 it should work. if its properly working, we
>> can add a proper support.
>>
>>>
>>>
>>> --
>>> Tim and Alison Bentley
>>> [email protected]
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>>> the body of a message to [email protected]
>>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
>>
>> --
>> thanks,
>> shafi
>
> It works. Sorry for the delay in replying but I needed to learn how
> to compile a Kernel.
> Patched the 3.4.6.2 fedora kernel and now Wireless works from boot up.
sorry, i missed this thread. thanks for spending time and checking this out.
I will send a patch to wireless-testing.
just curious, I don't have the device, is it possible for you to post
the logs enabling all the ath9k debug
with some traffic running
http://linuxwireless.org/en/users/Drivers/ath9k/debug.
Please initially post the kernel logs when wifi boots up, just need to
ensure its a proper
AR9485.
>
> Any chance this could be fixed in the 3.5 series Kernels as Fedora is
> rolling these out.
I could cc the patch to stable kernel.
>
> Thanks.
>
> --
> Tim and Alison Bentley
> [email protected]
--
thanks,
shafi
On Thu, Jul 26, 2012 at 10:34 AM, Mohammed Shafi
<[email protected]> wrote:
> On Thu, Jul 26, 2012 at 10:31 AM, Tim and Alison Bentley
> <[email protected]> wrote:
>> On 26 July 2012 02:25, G?bor Stefanik <[email protected]> wrote:
>>> On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger
>>> <[email protected]> wrote:
>>>> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote:
>>>>>
>>>>> On 25 July 2012 19:33, Larry Finger <[email protected]> wrote:
>>>>>>
>>>>>> On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
>>>>>>>
>>>>>>>
>>>>>>> 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.
>
>
>> 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
>> [email protected]
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> thanks,
> shafi
--
thanks,
shafi
On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
> 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
On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote:
> On 25 July 2012 19:33, Larry Finger <[email protected]> wrote:
>> On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
>>>
>>> 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
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)
On 25 July 2012 18:46, Larry Finger <[email protected]> wrote:
> On 07/25/2012 12:30 PM, Tim and Alison Bentley wrote:
>>
>> I have a new laptop and running the latest version of Fedora 17 it
>> cannot see the Wireless card.
>>
>> lspci -k
>>
>> 01:00.0 VGA compatible controller: nVidia Corporation Device 0de9 (rev
>> a1)
>> Subsystem: Device 1b0a:20dd
>> Kernel driver in use: nouveau
>> 03:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev
>> 01)
>> Subsystem: Lite-On Communications Inc Device 6618
>> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 07)
>> Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
>> Kernel driver in use: r8169
>>
>> lspci -v
>>
>> 03:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev
>> 01)
>> Subsystem: Lite-On Communications Inc Device 6618
>> Flags: bus master, fast devsel, latency 0, IRQ 3
>> Memory at f7200000 (64-bit, non-prefetchable) [size=512K]
>> Expansion ROM at f7280000 [disabled] [size=64K]
>> Capabilities: <access denied>
>>
>> Is this chip known upstream or a new one?
>>
>> [18:28][tim@tigger2] ~ $uname -a
>> Linux tigger2 3.4.6-2.fc17.x86_64 #1 SMP Thu Jul 19 22:54:16 UTC 2012
>> x86_64 x86_64 x86_64 GNU/Linux
>> [18:29][tim@tigger2] ~ $
>
>
> We need to see the PCI IDs for the Atheros device. Use "lspci -nn".
>
> Larry
>
--
Tim and Alison Bentley
[email protected]
On 25 July 2012 19:33, Larry Finger <[email protected]> wrote:
> On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
>>
>> 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.
--
Tim and Alison Bentley
[email protected]
On 26 July 2012 06:26, Mohammed Shafi <[email protected]> wrote:
>> 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
>> 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
>
> can you please try the attached dummy patch. see if the device is working.
> if its a version of AR9485 it should work. if its properly working, we
> can add a proper support.
>
>>
>>
>> --
>> Tim and Alison Bentley
>> [email protected]
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
>> the body of a message to [email protected]
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
>
> --
> thanks,
> shafi
It works. Sorry for the delay in replying but I needed to learn how
to compile a Kernel.
Patched the 3.4.6.2 fedora kernel and now Wireless works from boot up.
Any chance this could be fixed in the 3.5 series Kernels as Fedora is
rolling these out.
Thanks.
--
Tim and Alison Bentley
[email protected]
On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger
<[email protected]> wrote:
> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote:
>>
>> On 25 July 2012 19:33, Larry Finger <[email protected]> wrote:
>>>
>>> On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
>>>>
>>>>
>>>> 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.
On 07/25/2012 12:30 PM, Tim and Alison Bentley wrote:
> I have a new laptop and running the latest version of Fedora 17 it
> cannot see the Wireless card.
>
> lspci -k
>
> 01:00.0 VGA compatible controller: nVidia Corporation Device 0de9 (rev
> a1)
> Subsystem: Device 1b0a:20dd
> Kernel driver in use: nouveau
> 03:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev 01)
> Subsystem: Lite-On Communications Inc Device 6618
> 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 07)
> Subsystem: Realtek Semiconductor Co., Ltd. Device 0123
> Kernel driver in use: r8169
>
> lspci -v
>
> 03:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev 01)
> Subsystem: Lite-On Communications Inc Device 6618
> Flags: bus master, fast devsel, latency 0, IRQ 3
> Memory at f7200000 (64-bit, non-prefetchable) [size=512K]
> Expansion ROM at f7280000 [disabled] [size=64K]
> Capabilities: <access denied>
>
> Is this chip known upstream or a new one?
>
> [18:28][tim@tigger2] ~ $uname -a
> Linux tigger2 3.4.6-2.fc17.x86_64 #1 SMP Thu Jul 19 22:54:16 UTC 2012
> x86_64 x86_64 x86_64 GNU/Linux
> [18:29][tim@tigger2] ~ $
We need to see the PCI IDs for the Atheros device. Use "lspci -nn".
Larry
> 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
> 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
can you please try the attached dummy patch. see if the device is working.
if its a version of AR9485 it should work. if its properly working, we
can add a proper support.
>
>
> --
> Tim and Alison Bentley
> [email protected]
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
thanks,
shafi
On 26 July 2012 02:25, Gábor Stefanik <[email protected]> wrote:
> On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger
> <[email protected]> wrote:
>> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote:
>>>
>>> On 25 July 2012 19:33, Larry Finger <[email protected]> wrote:
>>>>
>>>> On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
>>>>>
>>>>>
>>>>> 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
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
[email protected]
On Thu, Jul 26, 2012 at 10:31 AM, Tim and Alison Bentley
<[email protected]> wrote:
> On 26 July 2012 02:25, G?bor Stefanik <[email protected]> wrote:
>> On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger
>> <[email protected]> wrote:
>>> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote:
>>>>
>>>> On 25 July 2012 19:33, Larry Finger <[email protected]> wrote:
>>>>>
>>>>> On 07/25/2012 01:00 PM, Tim and Alison Bentley wrote:
>>>>>>
>>>>>>
>>>>>> 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.
> 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
> [email protected]
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
thanks,
shafi
>
> Sorry not been able to work out how to build a debug Kernel.
> Any news on how this patch is progressing upstream.
patch sent to wireless-testing. Ccing stable 2.6.39+
>
>
> --
> Tim and Alison Bentley
> [email protected]
>
--
thanks,
shafi
Hi,
>
> Sorry not been able to work out how to build a debug Kernel.
> Any news on how this patch is progressing upstream.
>
no issues, i had just confirmed internally that AR1111 is indeed AR9485
with very very little difference. will send a patch by today. thanks.
--
thanks,
shafi