Return-path: Received: from mail-ey0-f174.google.com ([209.85.215.174]:51767 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751107Ab2GZBZk (ORCPT ); Wed, 25 Jul 2012 21:25:40 -0400 Received: by eaak13 with SMTP id k13so74958eaa.19 for ; Wed, 25 Jul 2012 18:25:39 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <501061C8.5010108@lwfinger.net> References: <501030E9.3090707@lwfinger.net> <50103BE8.1020203@lwfinger.net> <501061C8.5010108@lwfinger.net> From: =?ISO-8859-1?Q?G=E1bor_Stefanik?= Date: Thu, 26 Jul 2012 03:25:18 +0200 Message-ID: (sfid-20120726_032618_847982_85B15DCD) Subject: Re: New Laptop and Driver To: Larry Finger Cc: Tim and Alison Bentley , linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Jul 25, 2012 at 11:14 PM, Larry Finger wrote: > On 07/25/2012 01:54 PM, Tim and Alison Bentley wrote: >> >> On 25 July 2012 19:33, Larry Finger 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.