From: Larry Finger <Larry.Finger@lwfinger.net>
To: Tim and Alison Bentley <Home@TRARBentley.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: New Laptop and Driver
Date: Wed, 25 Jul 2012 16:14:48 -0500 [thread overview]
Message-ID: <501061C8.5010108@lwfinger.net> (raw)
In-Reply-To: <CAAT9HsjQ_tkm77NT_Rn5_Pi9BHGhY9Vz7jcVzkwdDUjUoKamtw@mail.gmail.com>
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
next prev parent reply other threads:[~2012-07-25 21:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=501061C8.5010108@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=Home@TRARBentley.net \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).