SCIENTIFIC-LINUX-USERS Archives

August 2010

SCIENTIFIC-LINUX-USERS@LISTSERV.FNAL.GOV

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Alan Bartlett <[log in to unmask]>
Reply To:
Alan Bartlett <[log in to unmask]>
Date:
Tue, 31 Aug 2010 16:40:04 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (52 lines)
On 31 August 2010 07:09, Isaac <[log in to unmask]> wrote:
> On Mon, 30 Aug 2010 08:59:31 -0700 (PDT)
> William Shu wrote:
>
>> Dear All,
>> I forwarded this mail back in July buy got no reply. So I can use the
>> machine, does anyone have a workaround that avoids
>> changing/recompiling stock SL software/kernel? (Googling seems to
>> suggest there is a fundamental problem; I lack the needed networking
>> skills.)
>>
>> Many thanks
>>
>> William.
>>
> ..
>> > I have an atheros 9825 wireless card (on a compaq
>> > CQ60-615DX) which is detected, but somehow fails to connect
>> > to -- or rather immediately disconnects immediately from --
>> > the network when the password is given. I am running it
>> > using linux 5.5 livedvd, but the same device connects
>> > successfully under Windows7.
>
> Atheros 9825? That sounds like it should be wireless-n, supported by
> ath9k (or perhaps madwifi-hal-0.10.5.6, but don't expect the latter to
> be easy).
> Here's a little info:
> http://madwifi-project.org/wiki/Compatibility/Atheros
>
> I'd see whether `ifconfig wlan0 down;modprobe -r ath9k` and
> `modprobe ath9k; ifconfig wlan0 up` will get it working.
> If not, I'd try the CentOS 2.6.32 kernel/some RHEL6 kernel; try another
> distro; or wait a little bit.
>
> Be aware that ath9k is a work in progress.
>
>> >
>> > It seems this issue was discussed sometime before, but I do
>> > not seem to find it. Any help appreciated. Below are details
>> > from wpa_supplicant.log and dmesg that I guess are helpful.

When asking about a driver for a recalcitrant device, it is always
helpful to quote the Vendor:Device ID Pairing (a.k.a. the device
fingerprint). This can be obtained from the output of a lspci / lsusb
command, depending upon the device type.

An example of this can be seen in FAQ #4 at the ELRepo Project's FAQ page [1].

Alan.

[1] http://elrepo.org/tiki/FAQ

ATOM RSS1 RSS2