Ticket #153 (closed defect: fixed)

Opened 7 years ago

Last modified 6 years ago

Softled does not work

Reported by: debian-io@fionn.de Assigned to: mrenzmann
Priority: minor Milestone: version 1.0.0 - first stable release
Component: madwifi: driver Version: trunk
Keywords: softled Cc:
Patch is attached: Pending:

Description

I use a Thinkpad with a softled. Unfortunately I can not get it to work properly. The led seems to live on pin0, and when I issue "sysctl -w dev.wifi0.softled=1" the LED flashes like like three or four times in about two seconds. During this short period, all wifi network transmissions break down. Then the LED goes off and never on again (unless i do softled=0 and softled=1 again). This happens both with 10.31.2005cvs version as well as with my svn.v1325 checkout. Since the LED flashes I presume it is a software issue.

Attachments

madwifi-thinkpad-led-rfkill.patch (1.7 kB) - added by svens@gmx.de on 12/04/05 14:41:07.
Changes i've made to get this LED working. Please note that there are also some debugging code in there - for example setting gpio pins over sysctl.
madwifi-thinkpad-led-rfkill.patch2 (3.7 kB) - added by svens@gmx.de on 12/04/05 14:45:18.
this is the right one... please ignore first one.

Change History

11/20/05 11:04:05 changed by mrenzmann

  • milestone set to version 1.0.0 - first stable release.

12/04/05 14:39:02 changed by svens@gmx.de

I encountered the same problem. I installed a non IBM Wifi Card in my IBM and the behaviour was exactly the same. It looks like the HAL uses pin 0 as RF Kill input - which is in Thinkpads used for the Wifi (Soft)LED. I disabled the RF Kill feature with a HAL call, now i ts running fine.

12/04/05 14:41:07 changed by svens@gmx.de

  • attachment madwifi-thinkpad-led-rfkill.patch added.

Changes i've made to get this LED working. Please note that there are also some debugging code in there - for example setting gpio pins over sysctl.

12/04/05 14:45:18 changed by svens@gmx.de

  • attachment madwifi-thinkpad-led-rfkill.patch2 added.

this is the right one... please ignore first one.

12/15/05 09:24:17 changed by mrenzmann

  • status changed from new to assigned.
  • owner set to mrenzmann.

As reported by svens in IRC, both patches should be ignored. He sent a patch which fixes this issue to madwifi-devel, requesting for comments. See: http://article.gmane.org/gmane.linux.drivers.madwifi.devel/1803

12/21/05 21:56:39 changed by svens

  • status changed from assigned to closed.
  • resolution set to fixed.

12/21/05 22:01:45 changed by svens

fixed with r1362