[ltp] T61 Atheros wireless LED
Daniel Castro
linux-thinkpad@linux-thinkpad.org
Thu, 24 Jul 2008 12:29:27 +0100
This is a multi-part message in MIME format.
--------------080305020908020804040202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Ha! Look at that, my wifi LED is working now... I put those commands on
a init.d script and voila...! Thanks Micha!
Now the hardware switch only affecting the bluetooth... yeah same
behaviour in my computer. That switch is useless, I remember on Windows
it will turn on or off both wireless and bluetooth... In my case I need
separate control over wifi and bluetooth so I just don't use it, it's
always on.
________________________
Daniel Castro
Networking and Distributed Systems
Computer Science
Trinity College Dublin
Mobile: 083-318-2058
86.4.3 Trinity Hall, Dartry Road, Dublin 6
________________________
Micha wrote:
> On Thu, 24 Jul 2008 10:25:53 +0100
> Daniel Castro <castromd@tcd.ie> wrote:
>
>
>> Tim,
>>
>> My T61 has an Atheros and it works fairly well.
>> Now that I upgraded to 8.04 it works even better. It does have some
>> minor issues like:
>> - The signal reception is weak. For example if in Windows it reports 90%
>> strength in Ubuntu it will report something like 65-70%.
>> - Some WPA encryptions will not work under Network Manager. But that's
>> fixable but not connecting through NM but rather creating your own
>> wpa_supplicant script and running it.
>> - The led won't work. I'm used now and don't really care, I have visual
>> software indicators on my screen anyway...
>>
>> But in terms of bandwidth and reliability it's fine... so I wonder if
>> you have a different Atheros than me.
>> My lspci shows:
>> 03:00.0 Ethernet controller: Atheros Communications Inc. AR5212
>> 802.11abg NIC (rev 01)
>>
>>
>
> I have the same card, I got the led to work by issuing
> sysctl dev.wifi0.ledpin=1
> sysctl dev.wifi0.softled=3
> (the second line seems to be needed but afterwords I can reset it to any odd
> value I want including the default value 1)
>
> I have a different question though. It seems that on my machine the hardware
> switch is not connected to the wireless antena, only the bluetooth antena
> (wireless keeps working event with the hardware switch set to off).
>
> Do you have the same behaviour or did they forgot the connect the switch
> properly on my machine?
>
> Thanks
>
>
>> ________________________
>>
>> Daniel Castro
>> Networking and Distributed Systems
>> Computer Science
>> Trinity College Dublin
>>
>> Mobile: 083-318-2058
>> 86.4.3 Trinity Hall, Dartry Road, Dublin 6
>> ________________________
>>
>>
>>
>> Robert T. West ("Tim") wrote:
>>
>>> On Wed, Jul 23, 2008 at 10:21 AM, Henrique de Moraes Holschuh
>>> <hmh@hmh.eng.br> wrote:
>>>
>>>
>>>> On Wed, 23 Jul 2008, Micha wrote:
>>>>
>>>>
>>>>> There is also a ath5k driver both in the kernel and compatwireless but
>>>>> although it recognises my card it fails to actually communicate. I've
>>>>> been told not long ago on this list that it's because the card is pci-e
>>>>> and there is an issue with the interrupts at the moment.
>>>>>
>>>>>
>>>> I have seen a patch for that already in the linux-wireless ML, it just
>>>> disables MSI for now on all ath5k and ath9k cards, and that's enough to fix
>>>> the interrupt issues. Which doesn't mean everything will work, but at
>>>> least it will have a non-zero chance to :-)
>>>>
>>>> It might even be on the newest wireless-compat already, but you can look at
>>>> the linux-wireless archives for ath5k: emails and check.
>>>>
>>>>
>>>>
>>> That's of great interest. I haven't had much luck running Ubuntu Hardy
>>> on a T60p. Currently using ndiswrapper (probably because I don't know
>>> better) to get the Atheros pci-e wireless to work at all, and, as of
>>> my last bout with it, it works with no encryption or WEP, but will
>>> only handshake with WPA if it's within a few feet of the router, and
>>> never reliably. I find that... strange.
>>>
>>>
--------------080305020908020804040202
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Ha! Look at that, my wifi LED is working now... I put those commands on
a init.d script and voila...! Thanks Micha!<br>
<br>
Now the hardware switch only affecting the bluetooth... yeah same
behaviour in my computer. That switch is useless, I remember on Windows
it will turn on or off both wireless and bluetooth... In my case I need
separate control over wifi and bluetooth so I just don't use it, it's
always on.<br>
<pre class="moz-signature" cols="72">________________________
Daniel Castro
Networking and Distributed Systems
Computer Science
Trinity College Dublin
Mobile: 083-318-2058
86.4.3 Trinity Hall, Dartry Road, Dublin 6
________________________
</pre>
<br>
<br>
Micha wrote:
<blockquote cite="mid:20080724131525.1fd2a660@vivalunalitshi.luna.local"
type="cite">
<pre wrap="">On Thu, 24 Jul 2008 10:25:53 +0100
Daniel Castro <a class="moz-txt-link-rfc2396E" href="mailto:castromd@tcd.ie"><castromd@tcd.ie></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Tim,
My T61 has an Atheros and it works fairly well.
Now that I upgraded to 8.04 it works even better. It does have some
minor issues like:
- The signal reception is weak. For example if in Windows it reports 90%
strength in Ubuntu it will report something like 65-70%.
- Some WPA encryptions will not work under Network Manager. But that's
fixable but not connecting through NM but rather creating your own
wpa_supplicant script and running it.
- The led won't work. I'm used now and don't really care, I have visual
software indicators on my screen anyway...
But in terms of bandwidth and reliability it's fine... so I wonder if
you have a different Atheros than me.
My lspci shows:
03:00.0 Ethernet controller: Atheros Communications Inc. AR5212
802.11abg NIC (rev 01)
</pre>
</blockquote>
<pre wrap=""><!---->
I have the same card, I got the led to work by issuing
sysctl dev.wifi0.ledpin=1
sysctl dev.wifi0.softled=3
(the second line seems to be needed but afterwords I can reset it to any odd
value I want including the default value 1)
I have a different question though. It seems that on my machine the hardware
switch is not connected to the wireless antena, only the bluetooth antena
(wireless keeps working event with the hardware switch set to off).
Do you have the same behaviour or did they forgot the connect the switch
properly on my machine?
Thanks
</pre>
<blockquote type="cite">
<pre wrap="">________________________
Daniel Castro
Networking and Distributed Systems
Computer Science
Trinity College Dublin
Mobile: 083-318-2058
86.4.3 Trinity Hall, Dartry Road, Dublin 6
________________________
Robert T. West ("Tim") wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, Jul 23, 2008 at 10:21 AM, Henrique de Moraes Holschuh
<a class="moz-txt-link-rfc2396E" href="mailto:hmh@hmh.eng.br"><hmh@hmh.eng.br></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On Wed, 23 Jul 2008, Micha wrote:
</pre>
<blockquote type="cite">
<pre wrap="">There is also a ath5k driver both in the kernel and compatwireless but
although it recognises my card it fails to actually communicate. I've
been told not long ago on this list that it's because the card is pci-e
and there is an issue with the interrupts at the moment.
</pre>
</blockquote>
<pre wrap="">I have seen a patch for that already in the linux-wireless ML, it just
disables MSI for now on all ath5k and ath9k cards, and that's enough to fix
the interrupt issues. Which doesn't mean everything will work, but at
least it will have a non-zero chance to :-)
It might even be on the newest wireless-compat already, but you can look at
the linux-wireless archives for ath5k: emails and check.
</pre>
</blockquote>
<pre wrap="">That's of great interest. I haven't had much luck running Ubuntu Hardy
on a T60p. Currently using ndiswrapper (probably because I don't know
better) to get the Atheros pci-e wireless to work at all, and, as of
my last bout with it, it works with no encryption or WEP, but will
only handshake with WPA if it's within a few feet of the router, and
never reliably. I find that... strange.
</pre>
</blockquote>
</blockquote>
</blockquote>
</body>
</html>
--------------080305020908020804040202--