[Fujitsu LIFEBOOK AH532] Toggle Wireless (Fn F5) doesn't work with 13.04

[riu]

"Fn F5" should toggle wireless on Fujitsu Lifebook AH532 and LED indicator should be on/off accordingly. Nothing happens when I press "Fn F5" with the newest Ubuntu 13.04 amd64 and the Wireless LED indicator is always off. It works fine in Ubuntu 12.04.2 (with 3.5.0 kernel).

I am attaching the list of Fn buttons for Fujitsu Lifebook A532/AH532.
Note that all other buttons except "Fn F11" (ECO) (not tested) and "Fn Pause" (SysRq) work fine. "Fn Pause" behaves the same as Fn Delete (Prt Scr) - it takes screenshot. Even "Fn F12" (Toggle Camera) works fine.

WORKAROUND: Boot option "acpi_osi="!Windows 2012" fixes this issue.

---
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 3332 F.... pulseaudio
CasperVersion: 1.330
DistroRelease: Ubuntu 13.04
LiveMediaBuild: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130324)
MachineType: FUJITSU LIFEBOOK AH532
MarkForUpload: True
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper quiet splash --
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
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.8.0-14-generic N/A
 linux-backports-modules-3.8.0-14-generic N/A
 linux-firmware 1.104
Tags: raring
Uname: Linux 3.8.0-14-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

dmi.bios.date: 10/25/2012
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 2.08
dmi.board.name: FJNBB2A
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion2.08:bd10/25/2012:svnFUJITSU:pnLIFEBOOKAH532:pvr:rvnFUJITSU:rnFJNBB2A:rvr:cvnFUJITSU:ct10:cvr:
dmi.product.name: LIFEBOOK AH532
dmi.sys.vendor: FUJITSU

[Steve Langasek (vorlon)]

acpi-support has not been changed in raring, and wireless key handling has not changed for several cycles. Did this work for you in previous Ubuntu releases?

More likely than not, this should be handled in the kernel, not in acpi-support.

[riu (stanray)]

Yes, "Fn F5" worked fine in 12.04.2 with 3.5.0 kernel.

[Brad Figg (brad-figg)]

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

apport-collect 1159690

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.

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[riu (stanray)]

apport information

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.9 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

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.9-rc4-raring/

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report[0]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

Please follow the instructions on the wiki page[0]. The first step is to email the appropriate mailing list. If no response is received, then a bug may be opened on bugzilla.kernel.org.

[0] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[raven7809 (rav78)]

This but also affects me on my asus K55VJ-SX018D.

[Demersus (demersus)]

This bug also affects me on an HP ENVY 1225dx. The wifi button worked fine in the 3.5 kernels on 12.04 & 12.10. Unfortunately, it no longer works on kernels newer than the 3.5 series. (3.8 with raring, 3.9 upstream).

[penalvch (penalvch)]

riu, as per http://support.ts.fujitsu.com/Download/ShowFiles.asp an update is available for your BIOS (2.09). If you update to this, does it change anything?

If not, could you please both specify what happened, and provide the output of the following terminal command:
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date

Thank you for your understanding.

[riu (stanray)]

I have just updated the bios to 2.09. The problem still exists. I tested with these kernels:

- 3.8.0 kernel (ubuntu 12.04 with linux-image-lts-raring)
- 3.10 kernel (Saucy Daily live, August 5, 2013)
- 3.2.0 kernel (Ubuntu 12.04.1 live)

The problem still exists for 3.8.0 and 3.10. Wireless LED is always on, Fn-F5 don't function.
On kernel 3.2.0 Fn-F5 work fine, and wireless LED is on/off according to whether wifi+bluetooth is enabled.

The output of the command "sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date":

Version 2.09
03/08/2013

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

riu, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc4

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[riu (stanray)]

apport information

[riu (stanray)]

I confirm this bug exists with Saucy Daily live image and with the mainline kernel, currently it is version 3.11.0-031100rc4.

[penalvch (penalvch)]

riu, did this problem not occur in a release prior to Raring?

[riu (stanray)]

Christopher, I tested Precice with linux-image-lts-quantal installed, which I think is the same as running quantal in regard to this bug. So, I think saying that the problem didn't occur prior to Raring is correct.

[penalvch (penalvch)]

riu, the next step is to bisect between Quantal and Raring, in order to identify the commit that caused this regression. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[riu (stanray)]

I tested these kernels (http://kernel.ubuntu.com/~kernel-ppa/mainline/):

3.6.11 good
3.7.10 bad
3.7.1 bad
3.7.0-030700 bad

So, the commit is somewhere between 3.6.11 and 3.7.0.

I use the source from git://kernel.ubuntu.com/ubuntu/ubuntu-raring.git
The source was merged between 3.6.0 and 3.7.0. I have problems building the kernel.

[penalvch (penalvch)]

riu, you may want to switch to commit bisect the mainline kernels https://wiki.ubuntu.com/Kernel/KernelBisection#Commit_bisecting_upstream_kernel_versions . Would this allow you to continue commit bisecting?

[riu (stanray)]

I have bisected the kernel as you suggested.

Bisecting yielded two commits that could be connected with this bug. One of them (c468fb1375f1b4de851e3e0dbe9d1293d414a160) is unbuildable. At least, the compiler complains that in /include/linux/of_mdio.h:50: multiple definition of `of_phy_connect_fixed_link'

I attach the bisect log file, in case you are interested.
The last message from git bisect was:

$ git bisect skip
There are only 'skip'ped commits left to test.
The first bad commit could be any of:
c468fb1375f1b4de851e3e0dbe9d1293d414a160
2a5cf8016c745191605f312a7cd7bd22e9be94a5
We cannot bisect more!

commit 2a5cf8016c745191605f312a7cd7bd22e9be94a5
Author: Mark Brown <email address hidden>
Date: Tue Oct 9 18:33:38 2012 +0000

    of/mdio: Staticise !CONFIG_OF stubs

    The !CONFIG_OF stubs aren't static so if multiple files include the
    header with this configuration then the linker will see multiple
    definitions of the stubs.

    Reported-by: Fengguang Wu <email address hidden>
    Signed-off-by: Mark Brown <email address hidden>
    Acked-by: Thomas Petazzoni <email address hidden>
    Acked-by: Srinivas Kandagatla <email address hidden>
    Signed-off-by: David S. Miller <email address hidden>

commit c468fb1375f1b4de851e3e0dbe9d1293d414a160
Author: Amerigo Wang <email address hidden>
Date: Tue Oct 9 17:48:20 2012 +0000

    pktgen: replace scan_ip6() with in6_pton()

    Cc: David S. Miller <email address hidden>
    Signed-off-by: Cong Wang <email address hidden>
    Signed-off-by: David S. Miller <email address hidden>

[penalvch (penalvch)]

riu, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/ and advise to the results?

[riu (stanray)]

The mainline kernel http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.12-rc1-saucy/ is still affected.

[penalvch (penalvch)]

riu, the issue you are reporting is an upstream one. Could you please report this problem through the appropriate channel by following the instructions _verbatim_ at https://wiki.ubuntu.com/Bugs/Upstream/kernel#KernelTeam.2BAC8-KernelTeamBugPolicies.Overview_on_Reporting_Bugs_Upstream ?

Thank you for your understanding.

[Jan Hinnerk Stosch (janhinnerk-stosch)]

Did your report this upstream? If so could you point me to the bugreport as I have the same problem?
Does it help when you add "acpi_osi="!Windows 2012" to the boot options in grub? I bisected the problem and it was added by the kernel commit a57f7f9175b8ccbc9df83ac13860488913115de4.

[riu (stanray)]

Jan, I reported this bug to developers connected with commits I found by bisecting, but I received no responces, because they have nothing to do with this bug, I think, I made a mistake when bisected this bug.

[Jan Hinnerk Stosch (janhinnerk-stosch)]

Ok.
Have you tried with the named boot option? If it helps I probably will ask at the linux-acpi mailing list.

[riu (stanray)]

Yes, the boot option "acpi_osi="!Windows 2012" fixes this issue.