Bug 469020 - Need a YaST user interface for tuning the wireless LED functionality.
Summary: Need a YaST user interface for tuning the wireless LED functionality.
Status: RESOLVED FEATURE
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i686 openSUSE 11.1
: P5 - None : Enhancement with 5 votes (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-23 21:47 UTC by Robert Lewis
Modified: 2009-02-23 09:22 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Lewis 2009-01-23 21:47:20 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.0.5) Gecko/2008121300 SUSE/3.0.5-2.5 Firefox/3.0.5

The LED blinking is very distracting and needs to be controlable.

The LED blinks when traffic goes through the wireless card. However you can
configure the LED behavior in /sys/class/net/wlanX/device/leds.

For example something like

echo none > /sys/class/net/wlanX/device/leds/*TX/trigger
echo none > /sys/class/net/wlanX/device/leds/*RX/trigger
echo none > /sys/class/net/wlanX/device/leds/*assoc/trigger

should deactivate the blinking while traffic is received or transmitted. Just
play with the LED triggers to get the desired behavior.

This is a work around for a few people not afraid to muck with such things
but a GUI user interface to turn this on/off will be needed for most people.
I think we need YaST options in the wireless network area to tune the
LED behavior.

> Agreed. A graphical user interface would be very nice for tuning the LED
> behavior. I suggest to open a feature request at [2] for that.
>
>Thanks,
> Helmut






Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Comment 1 Katarina Machalkova 2009-02-23 09:22:38 UTC
This is a feature and as such, it should be handled via openFATE