* New Laptop and Driver
@ 2012-07-25 17:30 Tim and Alison Bentley
2012-07-25 17:46 ` Larry Finger
0 siblings, 1 reply; 15+ messages in thread
From: Tim and Alison Bentley @ 2012-07-25 17:30 UTC (permalink / raw)
To: linux-wireless
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
Home@TRARBentley.net
^ permalink raw reply [flat|nested] 15+ messages in thread* Re: New Laptop and Driver 2012-07-25 17:30 New Laptop and Driver Tim and Alison Bentley @ 2012-07-25 17:46 ` Larry Finger 2012-07-25 18:00 ` Tim and Alison Bentley 0 siblings, 1 reply; 15+ messages in thread From: Larry Finger @ 2012-07-25 17:46 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: linux-wireless 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-25 17:46 ` Larry Finger @ 2012-07-25 18:00 ` Tim and Alison Bentley 2012-07-25 18:33 ` Larry Finger 0 siblings, 1 reply; 15+ messages in thread From: Tim and Alison Bentley @ 2012-07-25 18:00 UTC (permalink / raw) To: Larry Finger; +Cc: linux-wireless 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 <Larry.Finger@lwfinger.net> 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 Home@TRARBentley.net ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-25 18:00 ` Tim and Alison Bentley @ 2012-07-25 18:33 ` Larry Finger 2012-07-25 18:54 ` Tim and Alison Bentley 0 siblings, 1 reply; 15+ messages in thread From: Larry Finger @ 2012-07-25 18:33 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: linux-wireless 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-25 18:33 ` Larry Finger @ 2012-07-25 18:54 ` Tim and Alison Bentley 2012-07-25 21:14 ` Larry Finger 0 siblings, 1 reply; 15+ messages in thread From: Tim and Alison Bentley @ 2012-07-25 18:54 UTC (permalink / raw) To: Larry Finger; +Cc: linux-wireless On 25 July 2012 19:33, Larry Finger <Larry.Finger@lwfinger.net> 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 Home@TRARBentley.net ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-25 18:54 ` Tim and Alison Bentley @ 2012-07-25 21:14 ` Larry Finger 2012-07-26 1:25 ` Gábor Stefanik 0 siblings, 1 reply; 15+ messages in thread From: Larry Finger @ 2012-07-25 21:14 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: linux-wireless On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote: > On 25 July 2012 19:33, Larry Finger <Larry.Finger@lwfinger.net> 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-25 21:14 ` Larry Finger @ 2012-07-26 1:25 ` Gábor Stefanik 2012-07-26 5:01 ` Tim and Alison Bentley 0 siblings, 1 reply; 15+ messages in thread From: Gábor Stefanik @ 2012-07-26 1:25 UTC (permalink / raw) To: Larry Finger; +Cc: Tim and Alison Bentley, linux-wireless On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger <Larry.Finger@lwfinger.net> wrote: > On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote: >> >> On 25 July 2012 19:33, Larry Finger <Larry.Finger@lwfinger.net> 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. ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-26 1:25 ` Gábor Stefanik @ 2012-07-26 5:01 ` Tim and Alison Bentley 2012-07-26 5:04 ` Mohammed Shafi 2012-07-26 5:26 ` Mohammed Shafi 0 siblings, 2 replies; 15+ messages in thread From: Tim and Alison Bentley @ 2012-07-26 5:01 UTC (permalink / raw) To: Gábor Stefanik; +Cc: Larry Finger, linux-wireless On 26 July 2012 02:25, Gábor Stefanik <netrolller.3d@gmail.com> wrote: > On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger > <Larry.Finger@lwfinger.net> wrote: >> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote: >>> >>> On 25 July 2012 19:33, Larry Finger <Larry.Finger@lwfinger.net> 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 Home@TRARBentley.net ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-26 5:01 ` Tim and Alison Bentley @ 2012-07-26 5:04 ` Mohammed Shafi 2012-07-26 5:17 ` Mohammed Shafi 2012-07-26 5:26 ` Mohammed Shafi 1 sibling, 1 reply; 15+ messages in thread From: Mohammed Shafi @ 2012-07-26 5:04 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: Gábor Stefanik, Larry Finger, linux-wireless On Thu, Jul 26, 2012 at 10:31 AM, Tim and Alison Bentley <Home@trarbentley.net> wrote: > On 26 July 2012 02:25, Gábor Stefanik <netrolller.3d@gmail.com> wrote: >> On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger >> <Larry.Finger@lwfinger.net> wrote: >>> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote: >>>> >>>> On 25 July 2012 19:33, Larry Finger <Larry.Finger@lwfinger.net> 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 > 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-26 5:04 ` Mohammed Shafi @ 2012-07-26 5:17 ` Mohammed Shafi 0 siblings, 0 replies; 15+ messages in thread From: Mohammed Shafi @ 2012-07-26 5:17 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: Gábor Stefanik, Larry Finger, linux-wireless On Thu, Jul 26, 2012 at 10:34 AM, Mohammed Shafi <shafi.wireless@gmail.com> wrote: > On Thu, Jul 26, 2012 at 10:31 AM, Tim and Alison Bentley > <Home@trarbentley.net> wrote: >> On 26 July 2012 02:25, Gábor Stefanik <netrolller.3d@gmail.com> wrote: >>> On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger >>> <Larry.Finger@lwfinger.net> wrote: >>>> On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote: >>>>> >>>>> On 25 July 2012 19:33, Larry Finger <Larry.Finger@lwfinger.net> 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 >> 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-26 5:01 ` Tim and Alison Bentley 2012-07-26 5:04 ` Mohammed Shafi @ 2012-07-26 5:26 ` Mohammed Shafi 2012-07-28 6:31 ` Tim and Alison Bentley 1 sibling, 1 reply; 15+ messages in thread From: Mohammed Shafi @ 2012-07-26 5:26 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: Gábor Stefanik, Larry Finger, linux-wireless [-- Attachment #1: Type: text/plain, Size: 1712 bytes --] > 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 > 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 [-- Attachment #2: temp.patch --] [-- Type: application/octet-stream, Size: 937 bytes --] diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c index cfa91ab..7311ca9 100644 --- a/drivers/net/wireless/ath/ath9k/hw.c +++ b/drivers/net/wireless/ath/ath9k/hw.c @@ -730,6 +730,7 @@ int ath9k_hw_init(struct ath_hw *ah) case AR9300_DEVID_QCA955X: case AR9300_DEVID_AR9580: case AR9300_DEVID_AR9462: + case 0x37: break; default: if (common->bus_ops->ath_bus_type == ATH_USB) diff --git a/drivers/net/wireless/ath/ath9k/pci.c b/drivers/net/wireless/ath/ath9k/pci.c index 87b89d5..cb3d9d6 100644 --- a/drivers/net/wireless/ath/ath9k/pci.c +++ b/drivers/net/wireless/ath/ath9k/pci.c @@ -37,6 +37,7 @@ static DEFINE_PCI_DEVICE_TABLE(ath_pci_id_table) = { { PCI_VDEVICE(ATHEROS, 0x0032) }, /* PCI-E AR9485 */ { PCI_VDEVICE(ATHEROS, 0x0033) }, /* PCI-E AR9580 */ { PCI_VDEVICE(ATHEROS, 0x0034) }, /* PCI-E AR9462 */ + { PCI_VDEVICE(ATHEROS, 0x0037) }, /* PCI-E ? */ { 0 } }; ^ permalink raw reply related [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-26 5:26 ` Mohammed Shafi @ 2012-07-28 6:31 ` Tim and Alison Bentley 2012-07-30 4:59 ` Mohammed Shafi 0 siblings, 1 reply; 15+ messages in thread From: Tim and Alison Bentley @ 2012-07-28 6:31 UTC (permalink / raw) To: Mohammed Shafi; +Cc: Gábor Stefanik, Larry Finger, linux-wireless On 26 July 2012 06:26, Mohammed Shafi <shafi.wireless@gmail.com> 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 >> 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 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 Home@TRARBentley.net ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver 2012-07-28 6:31 ` Tim and Alison Bentley @ 2012-07-30 4:59 ` Mohammed Shafi [not found] ` <CAAT9HsjseVS1V6NOAB3+X94qjzwMYZCjOOQEj3NHTwDW2MTh2A@mail.gmail.com> 0 siblings, 1 reply; 15+ messages in thread From: Mohammed Shafi @ 2012-07-30 4:59 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: Gábor Stefanik, Larry Finger, linux-wireless On Sat, Jul 28, 2012 at 12:01 PM, Tim and Alison Bentley <Home@trarbentley.net> wrote: > On 26 July 2012 06:26, Mohammed Shafi <shafi.wireless@gmail.com> 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 >>> 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 > > 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 > Home@TRARBentley.net -- thanks, shafi ^ permalink raw reply [flat|nested] 15+ messages in thread
[parent not found: <CAAT9HsjseVS1V6NOAB3+X94qjzwMYZCjOOQEj3NHTwDW2MTh2A@mail.gmail.com>]
* Re: New Laptop and Driver [not found] ` <CAAT9HsjseVS1V6NOAB3+X94qjzwMYZCjOOQEj3NHTwDW2MTh2A@mail.gmail.com> @ 2012-08-01 5:13 ` Mohammed Shafi 2012-08-02 6:30 ` Mohammed Shafi 1 sibling, 0 replies; 15+ messages in thread From: Mohammed Shafi @ 2012-08-01 5:13 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: Gábor Stefanik, Larry Finger, linux-wireless 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 ^ permalink raw reply [flat|nested] 15+ messages in thread
* Re: New Laptop and Driver [not found] ` <CAAT9HsjseVS1V6NOAB3+X94qjzwMYZCjOOQEj3NHTwDW2MTh2A@mail.gmail.com> 2012-08-01 5:13 ` Mohammed Shafi @ 2012-08-02 6:30 ` Mohammed Shafi 1 sibling, 0 replies; 15+ messages in thread From: Mohammed Shafi @ 2012-08-02 6:30 UTC (permalink / raw) To: Tim and Alison Bentley; +Cc: Gábor Stefanik, Larry Finger, linux-wireless > > 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 > Home@TRARBentley.net > -- thanks, shafi ^ permalink raw reply [flat|nested] 15+ messages in thread
end of thread, other threads:[~2012-08-02 6:30 UTC | newest]
Thread overview: 15+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-07-25 17:30 New Laptop and Driver Tim and Alison Bentley
2012-07-25 17:46 ` Larry Finger
2012-07-25 18:00 ` Tim and Alison Bentley
2012-07-25 18:33 ` Larry Finger
2012-07-25 18:54 ` Tim and Alison Bentley
2012-07-25 21:14 ` Larry Finger
2012-07-26 1:25 ` Gábor Stefanik
2012-07-26 5:01 ` Tim and Alison Bentley
2012-07-26 5:04 ` Mohammed Shafi
2012-07-26 5:17 ` Mohammed Shafi
2012-07-26 5:26 ` Mohammed Shafi
2012-07-28 6:31 ` Tim and Alison Bentley
2012-07-30 4:59 ` Mohammed Shafi
[not found] ` <CAAT9HsjseVS1V6NOAB3+X94qjzwMYZCjOOQEj3NHTwDW2MTh2A@mail.gmail.com>
2012-08-01 5:13 ` Mohammed Shafi
2012-08-02 6:30 ` Mohammed Shafi
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).