hardware switch of wireless not working for Centrino Advanced-N 6235

Bug #1258675 reported by Martin Konôpka
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Linux
New
Undecided
Unassigned
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

I have ubuntu 13.10 64-bit running on a HP ZBook 15. The notebook uses an Intel Corporation Centrino Advanced-N 6235 (rev 24) wireless adapter.

The wireless networking principally works. The issue is that it is not possible to enable or disable it using the hardware button. The only way is the software control (clicking on "Enable Wi-Fi").

BTW, when I click on "Enable Wi-Fi", it indicates the changes status of the wifi radio by changing the colour of the light on the hardware button. (This is the correct and expected behaviour. What is wrong is that I can not change the status by pressing the hardware button.)

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-firmware 1.116
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Fri Dec 6 23:04:18 2013
Dependencies:

InstallationDate: Installed on 2013-12-04 (2 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MarkForUpload: True
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: No upgrade log present (probably fresh install)
---
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-01-31 (11 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140130)
Package: linux (not installed)
Tags: trusty
Uname: Linux 3.14.0-031400rc2-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Martin Konôpka (martin.konopka) wrote :
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.12 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.13-rc3-trusty/

Changed in linux-firmware (Ubuntu):
importance: Undecided → Medium
affects: linux-firmware (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Konôpka (martin.konopka) wrote :

I have now tested the latest mainline kernel, namely I used the image

linux-image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_amd64.deb

E.g. I can see

vmlinuz -> boot/vmlinuz-3.13.0-031300rc3-generic

in the / directory.

The system behaves in the same way as with the ordinary kernel:
I can not turn the wireless radio on/off using the hardware switch.
The software control works.

tags: added: kernel-bug-exists-upstream
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Martin Konôpka (martin.konopka) wrote :

I confirm that the bug still exists in the latest development version of ubuntu with 3.13.0-8-generic kernel . Tomorrow I will test latest mainline kernel. Is it possible to cancel the expiration of the bug?

Changed in linux (Ubuntu):
status: Expired → New
Revision history for this message
Brad Figg (brad-figg) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1258675

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Martin Konôpka (martin.konopka) wrote :

The bug exists also with the latest mainline kernel 3.14.0-031400rc2-generic (amd64 version) . Therefore I changed the bug status from Expired to New.

Revision history for this message
Martin Konôpka (martin.konopka) wrote : ProcEnviron.txt

apport information

tags: added: apport-collected trusty
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
Spindizzy (spindizzy-wizard) wrote :

This bug is still present in 14.04 with the 3.13.0-30 kernel on a fully updated system.

Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Spindizzy (spindizzy-wizard) wrote : apport information

ApportVersion: 2.14.1-0ubuntu3.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: wilesed 4500 F.... pulseaudio
 /dev/snd/controlC0: wilesed 4500 F.... pulseaudio
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-31 (47 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Hewlett-Packard HP ZBook 15
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-30-generic root=UUID=b94bed6e-22c5-4428-9375-97a578348dcd ro acpi_backlight=vendor
ProcVersionSignature: Ubuntu 3.13.0-30.55-generic 3.13.11.2
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-30-generic N/A
 linux-backports-modules-3.13.0-30-generic N/A
 linux-firmware 1.127.4
Tags: trusty
Uname: Linux 3.13.0-30-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 01/10/2014
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: L70 Ver. 01.07
dmi.board.name: 1909
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 94.50
dmi.chassis.asset.tag: ITE00364303
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvrL70Ver.01.07:bd01/10/2014:svnHewlett-Packard:pnHPZBook15:pvrA3009CD10002:rvnHewlett-Packard:rn1909:rvrKBCVersion94.50:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ZBook 15
dmi.product.version: A3009CD10002
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : AlsaInfo.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : BootDmesg.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : CRDA.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : CurrentDmesg.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : IwConfig.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : Lspci.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : Lsusb.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : ProcCpuinfo.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : ProcInterrupts.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : ProcModules.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : RfKill.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : UdevDb.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : UdevLog.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote : WifiSyslog.txt

apport information

Revision history for this message
Spindizzy (spindizzy-wizard) wrote :

(ping) Still occurs 3.13.0-44-generic.

Revision history for this message
Spindizzy (spindizzy-wizard) wrote :

Just noticed this... The WiFi button works, AFTER you've logged in. It really needs to work BEFORE you log in as well.

In addition, while the mute button changes colors when the sound is muted, the WiFi button does not appear to change colors when WiFi is disabled.

Revision history for this message
Spindizzy (spindizzy-wizard) wrote :

Interesting... If you've used the network menu in the widgets to turn off WiFi, then the button will not do anything for WiFi, but it will continue to switch Bluetooth off/on. The color of the button does not change.

If you then turn ON WiFi through the menu, the WiFi button will work for both Bluetooth and WiFi, but still does not change color.

The mute button appears to work correctly, turning color to orange when mute is on.

Revision history for this message
Spindizzy (spindizzy-wizard) wrote :

Just logged out, with WiFi turned ON, and the WiFi button worked, but still didn't change color.

WORKAROUND: If you have turned WiFi off via the network widget, turn it back on, then ONLY use the WiFi button to turn WiFi on/off. It will work both when you are logged in, and when you are not. It still won't change color though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.