Amilo Xi 3650: WLAN/BT hotkey doesn't work

Bug #515090 reported by Moritz Baumann
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Since I bought an AMILO Xi 3650 laptop some months ago, I always had to boot Vista to be able to turn WLAN and Bluetooth on and off via Fn+F1 (there's only one key for both, on Windows a window appears asking me which of them I want to be enabled).

In December I upgraded to lucid and at the beginning of January I suddenly noticed that the hotkey was working, turning both WLAN and BT on and off whenever I pressed it. Today I had to find out that it doesn't work anymore again (since I don't need BT most of the time, it could've already been broken for some days).

ProblemType: Bug
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: moritz 2278 F.... kmix
                      moritz 2284 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf4620000 irq 22'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,17341148,00100202'
   Controls : 26
   Simple ctrls : 15
Date: Sun Jan 31 12:16:25 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=74fe59fe-05ba-45ce-a817-6c33f6ebd1c8
MachineType: FUJITSU SIEMENS AMILO Xi 3650
Package: linux-image-2.6.32-12-generic 2.6.32-12.16
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-12-generic root=UUID=29e82293-368a-49f9-8c7c-11c09e185381 ro quiet splash
ProcEnviron:
 LANGUAGE=de_DE:de:en_GB:en
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.16-generic
Regression: Yes
RelatedPackageVersions: linux-firmware 1.28
Reproducible: Yes
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
TestedUpstream: No
Uname: Linux 2.6.32-12-generic i686
dmi.bios.date: 04/07/2009
dmi.bios.vendor: Phoenix
dmi.bios.version: 1.0G-1646-0024
dmi.board.name: XY680
dmi.board.vendor: FUJITSU SIEMENS
dmi.board.version: 0.3B
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU SIEMENS
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnPhoenix:bvr1.0G-1646-0024:bd04/07/2009:svnFUJITSUSIEMENS:pnAMILOXi3650:pvr10600978653:rvnFUJITSUSIEMENS:rnXY680:rvr0.3B:cvnFUJITSUSIEMENS:ct10:cvrVersion1.0:
dmi.product.name: AMILO Xi 3650
dmi.product.version: 10600978653
dmi.sys.vendor: FUJITSU SIEMENS

Revision history for this message
Moritz Baumann (mo42) wrote :
Philip Muškovac (yofel)
affects: ubuntu → linux (Ubuntu)
Surbhi Palande (csurbhi)
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Low
Revision history for this message
Moritz Baumann (mo42) wrote :

A BIOS update has fixed the issue for me, marking as invalid.

Changed in linux (Ubuntu):
status: Triaged → Invalid
Revision history for this message
Moritz Baumann (mo42) wrote :

Okay, reopening, this is becoming weirder and weirder.

After some reboots, suddenly, it stopped working again. So I restored the default BIOS configuration, rebooted – and now I can't switch WLAN/BT OFF anymore!

Changed in linux (Ubuntu):
status: Invalid → New
Revision history for this message
Moritz Baumann (mo42) wrote :

BIOS version is now 1.0H

moritz@Laptop:~$ rfkill list
0: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no
1: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Moritz Baumann, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, 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 (not the daily folder, but the one at the top) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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.13-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

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: latest-bios-1.0h
Revision history for this message
Moritz Baumann (mo42) wrote :

Wow, I completely forgot about this bug report.

As I found out in the meantime, this problem only occurs if you use both Windows and Linux. On Windows, whenever the switch button is pressed, a popup appears which prompts you to select the devices you want to turn on/off. When you do, the driver seems to do something linux doesn't understand, as whenever you actually switch one of the devices on or off on Windows, you lose the ability to use the switch on Linux until you reset the BIOS settings.

Since I'm not using Windows anymore on that particular laptop, I cannot check whether the problem still exists. I suspect it does. However, since I'm not affected anymore, feel free to close this bug due to a lack of interest, if you want. ;-)

Revision history for this message
penalvch (penalvch) wrote :

Moritz Baumann, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/515090/comments/6 regarding you no longer use the same configuration that caused this bug. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

Changed in linux (Ubuntu):
status: Incomplete → Invalid
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.