Ubuntu
linux-restricted-modules-2.6.24 package

Wireless LED does not light up (network connection works)

Bug #177766 reported by SK on 2007-12-20

This bug report is a duplicate of: Bug #176090: WiFi / WLAN LED not working on notebooks with Intel iwl4965 | iwl3945. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	linux-restricted-modules-2.6.24 (Ubuntu)	Triaged	Low	Unassigned

Bug Description

After updating restricted-modules to to 2.26.24 I am happy to report that it did not break anything important.
But the LED on my laptop indicating that the wireless lan interface is active (i.e. kill switch is not set) does not light up. It's a minor issue because the interface is operating normally.

The interface shows up as "Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)" in lspci's output. The laptop is one of HP's Pavilion dv5000 (the dv5188ea to be exact).

I am attaching lspci -vvv output for reference. Please let me know if you need any testing done.

See original description

Revision history for this message

SK (stephantom) wrote on 2007-12-20:

lspci -vvv output Edit (20.5 KiB, text/plain)

description:

updated

Revision history for this message

Nanley Chery (nanoman) wrote on 2007-12-22:

sudo lspci -vvv Edit (10.2 KiB, text/plain)

I'm experiencing the same problem on my Acer Aspire 3004WLCi (BCM4138) I am able to turn my wireless device on and off by pressing the (wireless button in front of it). However, the orange led (that used to come on in earlier kernels) on the button does not turn on. This light should turn on when I am connected and turn off when I turn off the device, otherwise it is very confusing as to when wireless is on or off.

Changed in linux-restricted-modules-2.6.24:
status:	New → Confirmed

Revision history for this message

SK (stephantom) wrote on 2007-12-24:

On the plus side, the interface does now resume correctly after suspend.

Revision history for this message

Nanley Chery (nanoman) wrote on 2007-12-27:

This bug is a duplicate of Bug #175829 because it describes the same problem and was reported after that bug. Please add any helpful information to that bug. Thank you.

Revision history for this message

SK (stephantom) wrote on 2007-12-27:

Sorry, but it is not. Bug #175829 describes a problem with a different driver. Plus, my interface does come up, everything works except for the connection LED.

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2007-12-28:

Stephan, thank you for taking the time to report this bug and helping to make Ubuntu better. Per the kernel team's bug policy, can you also please attach the following information:

* uname -a > uname-a.log
* cat /proc/version_signature > version.log
* dmesg > dmesg.log
* sudo lspci -vvnn > lspci-vvnn.log

Please be sure to attach each file as a separate attachment. For more information regarding the kernel team bug policy, please refer to https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks again and we appreciate your help and feedback.

Changed in linux-restricted-modules-2.6.24:
status:	Confirmed → Incomplete

Revision history for this message

SK (stephantom) wrote on 2007-12-28:

uname -a Edit (81 bytes, text/plain)

Revision history for this message

SK (stephantom) wrote on 2007-12-28:

version.log Edit (26 bytes, text/plain)

Revision history for this message

SK (stephantom) wrote on 2007-12-28:

dmesg.log Edit (34.4 KiB, text/plain)

Revision history for this message

SK (stephantom) wrote on 2007-12-28:

#10

lspci-vnn.log Edit (20.6 KiB, text/plain)

Revision history for this message

SK (stephantom) wrote on 2007-12-28:

#11

The last attachment is mislabeld, it is actually the output of sudo lspci -vvnn, I just forgot the extra 'v' in the filename.

Changed in linux-restricted-modules-2.6.24:
status:	Incomplete → Confirmed

Leann Ogasawara (leannogasawara) on 2007-12-30

Changed in linux-restricted-modules-2.6.24:
assignee:	nobody → ubuntu-kernel-team
importance:	Undecided → Low
status:	Confirmed → Triaged

Revision history for this message

Evgeny Kuznetsov (nekr0z) wrote on 2008-01-17:

#12

I can confirm the same behaviour of this WLAN adapter on Lenovo 3000 N100 laptop running the latest Hardy, with the only difference of WLAN being available after waking up from STR.

Revision history for this message

SK (stephantom) wrote on 2008-02-04:

#13

With 2.6.24-5-generic and the respective restriced-modules, this issue is still present.

Revision history for this message

SK (stephantom) wrote on 2008-02-13:

#14

With 2.6.24-7-generic and the respective restriced-modules, this issue is still present.

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2008-02-16:

#15

You might also want to take a look at bug report https://bugs.launchpad.net/bugs/176090 .

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-12-23: Kernel team bugs

#16

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.