On http://fedoraproject.org/wiki/Acer_Aspire_One it is said that the wifi LED can be activated by adding these two lines to /etc/sysctl.conf:
dev.wifi0.ledpin = 3 dev.wifi0.softled = 1
and it goes on to say that this works with both F9 and F10. However, it's not clear whether it only works with the madwifi driver. I'm guessing that they have to be changed to
dev.wlan0.ledpin = 3 dev.wlan0.softled = 1
However, I need to be sure that I'm not going to do any harm by trying this.
Anne
On Wed, 2009-01-14 at 16:03 +0000, Anne Wilson wrote:
On http://fedoraproject.org/wiki/Acer_Aspire_One it is said that the wifi LED can be activated by adding these two lines to /etc/sysctl.conf:
dev.wifi0.ledpin = 3 dev.wifi0.softled = 1
and it goes on to say that this works with both F9 and F10. However, it's not clear whether it only works with the madwifi driver. I'm guessing that they have to be changed to
dev.wlan0.ledpin = 3 dev.wlan0.softled = 1
However, I need to be sure that I'm not going to do any harm by trying this.
That change shouldn't hurt anything, although it may also not _do_ anything.
- ajax
On Wed, Jan 14, 2009 at 04:03:19PM +0000, Anne Wilson wrote:
On http://fedoraproject.org/wiki/Acer_Aspire_One it is said that the wifi LED can be activated by adding these two lines to /etc/sysctl.conf:
dev.wifi0.ledpin = 3
That was for the 2.6.26.x kernel. It no longer works with 2.6.27 kernel.
and it goes on to say that this works with both F9 and F10.
If you're using the ath5k driver included with the kernel, you won't be able to get those values in the 2.6.27 kernel. Whether MadWifi's drivers add the sysctl variables, I'm not sure, I would have to check.
You'll get an error that there's no such sysctl option. It seems to not be in the 2.6.27 vanilla kernel either.
On the other hand, we got ath5k in that kernel, so it was a more than even tradeoff IMHO
In Ubuntu's 2.6.28 kernel, it seems to be back. A quick try on Fedora's rawhide, however, indicates that Fedora doesn't have it.
However, Ubuntu pulled ath5k support out of their kernels--I'd much rather they had left that in, though it's easy enough to fix with backports. If I have to choose one or the other, I'd rather have the module right there.
Although some people mentioned that they got better results with MadWifi than the ath5k module, I haven't found that to be the case.
FWIW, getting that working just gives an annoying amber flashing during wireless activity. I quickly turned it off, though of course, some people like flashing lights. :)
However, it's not clear whether it only works with the madwifi driver.
As mentioned above, that I don't know--I would have to test that and see, but I do know that if you use the ath5k driver, the sysctl values aren't there.
However, I need to be sure that I'm not going to do any harm by trying this.
I'm not sure what happens if an unknown variable is in sysctl.conf. I usually did it on the fly with
sysctl -w dev.wifi0.ledpin=3 sysctl -w dev.wifi0.softled=1
On Wednesday 14 January 2009 16:32:53 Scott Robbins wrote:
On Wed, Jan 14, 2009 at 04:03:19PM +0000, Anne Wilson wrote:
On http://fedoraproject.org/wiki/Acer_Aspire_One it is said that the wifi LED can be activated by adding these two lines to /etc/sysctl.conf:
dev.wifi0.ledpin = 3
That was for the 2.6.26.x kernel. It no longer works with 2.6.27 kernel.
and it goes on to say that this works with both F9 and F10.
If you're using the ath5k driver included with the kernel, you won't be able to get those values in the 2.6.27 kernel. Whether MadWifi's drivers add the sysctl variables, I'm not sure, I would have to check.
You'll get an error that there's no such sysctl option. It seems to not be in the 2.6.27 vanilla kernel either.
OK, thanks.
On the other hand, we got ath5k in that kernel, so it was a more than even tradeoff IMHO
In Ubuntu's 2.6.28 kernel, it seems to be back. A quick try on Fedora's rawhide, however, indicates that Fedora doesn't have it.
However, Ubuntu pulled ath5k support out of their kernels--I'd much rather they had left that in, though it's easy enough to fix with backports. If I have to choose one or the other, I'd rather have the module right there.
Although some people mentioned that they got better results with MadWifi than the ath5k module, I haven't found that to be the case.
That may be hardware dependent, of course. I do have one, fairly serious issue, but at this stage I'm suspecting that it's hardware, not driver. I'll do a bug report if it warrants it, but right now I'm still collecting information/evidence.
FWIW, getting that working just gives an annoying amber flashing during wireless activity. I quickly turned it off, though of course, some people like flashing lights. :)
I don't like flashing lights, but I do like to know that wifi is activated - there's that toggle switch that gives you no other indication of its status.
However, it's not clear whether it only works with the madwifi driver.
As mentioned above, that I don't know--I would have to test that and see, but I do know that if you use the ath5k driver, the sysctl values aren't there.
However, I need to be sure that I'm not going to do any harm by trying this.
I'm not sure what happens if an unknown variable is in sysctl.conf. I usually did it on the fly with
sysctl -w dev.wifi0.ledpin=3 sysctl -w dev.wifi0.softled=1
Thanks, everyone for the answers. Not what I wanted to hear, but I'd rather have it 'from the horse's mouth' :-)
Anne
On Wed, Jan 14, 2009 at 11:32:53AM -0500, Scott Robbins wrote:
You'll get an error that there's no such sysctl option. It seems to not be in the 2.6.27 vanilla kernel either.
Using sysctl from drivers is a no-no. But hey, I've come to expect that level of quality from out of tree drivers, so you won't find this sysctl on anything but madwifi.
There's likely another mechanism to enable it on ath5k, but I don't know what it is.
On Wed, Jan 14, 2009 at 12:24:16PM -0500, Kyle McMartin wrote:
On Wed, Jan 14, 2009 at 11:32:53AM -0500, Scott Robbins wrote:
You'll get an error that there's no such sysctl option. It seems to not be in the 2.6.27 vanilla kernel either.
Using sysctl from drivers is a no-no. But hey, I've come to expect that level of quality from out of tree drivers, so you won't find this sysctl on anything but madwifi.
Ah interesting--I'd thought it was in the 2.6.26 kernel, but not the 2.6.27. I hadn't realized till I saw Anne's post that it was from MadWifi.
There's likely another mechanism to enable it on ath5k, but I don't know what it is.
I'm sure. I've also looked but haven't found anything. At one point, I installed a vanilla 2.6.27 kernel and enabled everything with LED in its name, but still had no luck. That doesn't mean it's not there, just that I didn't know where to look.
Scott Robbins (scottro@nyc.rr.com) said:
There's likely another mechanism to enable it on ath5k, but I don't know what it is.
I'm sure. I've also looked but haven't found anything. At one point, I installed a vanilla 2.6.27 kernel and enabled everything with LED in its name, but still had no luck. That doesn't mean it's not there, just that I didn't know where to look.
Is there a led device in /sys/class/leds associated with the wireless card? (I have neither a AAO, nor a ath5k device, but if there was something upstream-ish, that would be where to look)
Bill
On Wed, Jan 14, 2009 at 12:46:29PM -0500, Bill Nottingham wrote:
Scott Robbins (scottro@nyc.rr.com) said:
I've also looked but haven't found anything. At one point, I installed a vanilla 2.6.27 kernel and enabled everything with LED in its name, but still had no luck. That doesn't mean it's not there, just that I didn't know where to look.
Is there a led device in /sys/class/leds associated with the wireless card? (I have neither a AAO, nor a ath5k device, but if there was something upstream-ish, that would be where to look)
I'll have to check tonight--at present, I don't have an ath5k device here. Thanks very much for the hint.
On Wednesday 14 January 2009 17:46:29 Bill Nottingham wrote:
Scott Robbins (scottro@nyc.rr.com) said:
There's likely another mechanism to enable it on ath5k, but I don't know what it is.
I'm sure. I've also looked but haven't found anything. At one point, I installed a vanilla 2.6.27 kernel and enabled everything with LED in its name, but still had no luck. That doesn't mean it's not there, just that I didn't know where to look.
Is there a led device in /sys/class/leds associated with the wireless card? (I have neither a AAO, nor a ath5k device, but if there was something upstream-ish, that would be where to look)
There's nothing at all in /sys/class/leds
Anne
On Wed, Jan 14, 2009 at 12:46:29PM -0500, Bill Nottingham wrote:
Scott Robbins (scottro@nyc.rr.com) said:
There's likely another mechanism to enable it on ath5k, but I don't know what it is.
I'm sure. I've also looked but haven't found anything. At one point, I installed a vanilla 2.6.27 kernel and enabled everything with LED in its name, but still had no luck. That doesn't mean it's not there, just that I didn't know where to look.
Is there a led device in /sys/class/leds associated with the wireless card? (I have neither a AAO, nor a ath5k device, but if there was something upstream-ish, that would be where to look)
No, the directory was empty. It does turn out that the LED is connected with the MadWifi module. Upon blacklisting ath5k and install MadWifi, I saw that I suddenly had a bunch of sysctl variables for it. :)
Thanks to all, I'd never imagined that it was associated with MadWifi and had always figured it was the 2.6.26 vs. 2.6.27 kernel--the reason being that since the 2.6.27 had ath5k, I'd never used MadWifi with it.
On Wed, Jan 14, 2009 at 11:03 AM, Anne Wilson cannewilson@googlemail.com wrote:
On http://fedoraproject.org/wiki/Acer_Aspire_One it is said that the wifi LED can be activated by adding these two lines to /etc/sysctl.conf:
dev.wifi0.ledpin = 3 dev.wifi0.softled = 1
and it goes on to say that this works with both F9 and F10. However, it's not clear whether it only works with the madwifi driver. I'm guessing that they have to be changed to
dev.wlan0.ledpin = 3 dev.wlan0.softled = 1
However, I need to be sure that I'm not going to do any harm by trying this.
Anne
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
I have a Sony VGN-FW139E laptop with an Atheros Ar9281 chip using the ath9k module in F10. For some weird reason, the WiFi led lights have come "alive" in the last update.
Partha
On Wednesday 14 January 2009 22:56:29 Partha Bagchi wrote:
On Wed, Jan 14, 2009 at 11:03 AM, Anne Wilson
cannewilson@googlemail.com wrote:
On http://fedoraproject.org/wiki/Acer_Aspire_One it is said that the wifi LED can be activated by adding these two lines to /etc/sysctl.conf:
dev.wifi0.ledpin = 3 dev.wifi0.softled = 1
and it goes on to say that this works with both F9 and F10. However, it's not clear whether it only works with the madwifi driver. I'm guessing that they have to be changed to
dev.wlan0.ledpin = 3 dev.wlan0.softled = 1
However, I need to be sure that I'm not going to do any harm by trying this.
Anne
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
I have a Sony VGN-FW139E laptop with an Atheros Ar9281 chip using the ath9k module in F10. For some weird reason, the WiFi led lights have come "alive" in the last update.
I used to bemoan the fact that the wifi indicator on this laptop (Intel 2200) didn't work. One day I realised it was working. Nice surprise! :-)
Anne