[Asus N56VZ] fn+F2 doesn't work

Bug #1173107 reported by Alfredo Marchini on 2013-04-26
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Medium
Unassigned

Bug Description

I have just finishing executed do-release-upgrade from 12.10 to 13.04 amd64 on my notebook asus n56vz and fn+F2 doesn't work. doing lsmod I find asus_wmi correctly loaded.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: alfredo 2563 F.... pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=d03440a5-6014-4b16-bd94-82a413bbfb53
InstallationDate: Installed on 2013-04-02 (23 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
MachineType: ASUSTeK COMPUTER INC. N56VZ
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=d4aa775a-613b-448a-8264-5fcbecbbe7fc ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-26 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 12/06/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N56VZ.216
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N56VZ
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.216:bd12/06/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: N56VZ
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

One edit:
The fn+f7,fn+f8 works.
But everything seems very unstable.

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

apport-collect 1173107

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

I have just discovered an interesting thing:
If I set in /etc/default/grub acpi_osi=''
the volume keys doesn't work anymore, but fn+f8 works perfectly (monitor config changes shifts from dual monitor extended, cloned monitor and single laptop monitor) while fn+f7 works in both mode.

In this moment I unset that option, is the better solution at the moment.

apport information

tags: added: apport-collected raring
description: updated

apport information

apport information

apport information

apport information

apport information

description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

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].

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-raring/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete

Hi,
thank you very much, I will try it as soon as possible (probably tomorrow - saturday morning here in Italy).
Instead apt-get upgraded my 3.8.0-19 amd64 kernel (same version), and while upgraded dkms gave me an error.
Running dkms status this is the output:

asus-wmi, 999.01, 3.8.0-19-generic, x86_64: installed
bbswitch, 0.6, 3.8.0-19-generic, x86_64: installed
fwts-efi-runtime-dkms, 0.26.08, 3.8.0-19-generic, x86_64: installedError! Could not locate dkms.conf file.
File: does not exist.

nvidia-304, 304.88, 3.8.0-19-generic, x86_64: installed

Can it be related?

Last news for today:

the last 3.8.0-19 upgraded kernel does not change anything.

This is the kernel I tested.

linux-headers-3.9.0-030900 3.9.0-030900.201304291257 all
linux-headers-3.9.0-030900-generic 3.9.0-030900.201304291257 amd64
linux-image-3.9.0-030900-generic 3.9.0-030900.201304291257 amd64

The situation is worse than the 3.8.0-19 kernel. Because nothing works except the volume fn volume up and down keys.

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Richy Meier (meier-richy) wrote :

Hi,

i have nearly the same problems. On the newest mainline kernel (3.9.0 rc8 the following keys work:

fn-f1
fn-f2
fn-f5
fn-f6
fn-f7
fn-f8 (can't test)

There is no OSD as in stable 3.8.0.19 kernel. Response is very laggish, e.g. brightness-control (fn-f5, fn-f6)

dkms -status shows:

asus-wmi, 0.2, 3.5.0-2-generic, x86_64: built
asus-wmi, 0.2, 3.8.0-19-generic, x86_64: installed
asus-wmi, 0.2, 3.9.0-030900rc7-generic, x86_64: built
asus-wmi, 0.2, 3.9.0-030900rc8-generic, x86_64: built
bbswitch, 0.6, 3.8.0-19-generic, x86_64: installed
bbswitch, 0.6, 3.9.0-030900rc8-generic, x86_64: built
nvidia-304-updates, 304.88, 3.8.0-19-generic, x86_64: installed
nvidia-304-updates, 304.88, 3.9.0-030900rc8-generic, x86_64: installed
vboxhost, 4.2.12, 3.8.0-19-generic, x86_64: installed
vboxhost, 4.2.12, 3.9.0-030900rc8-generic, x86_64: installed
vhba, 20130121, 3.8.0-19-generic, x86_64: installed

I wonder why asus-wmi, 0.2, 3.9.0-030900rc8-generic, x86_64: built <-- is not installed? But don't know how to do it

Richy Meier (meier-richy) wrote :

i did some further testings... this is so strange..

last week i followed the guide: https://help.ubuntu.com/community/AsusZenbookPrime#Ubuntu_13.04
#after the above post i removed this Windows!2012 thing in my grub config to: GRUB_CMDLINE_LINUX_DEFAULT="splash quiet acpi_osi="

i then did a reboot to 3.9.0 rc9 and ...tada... the following worked:
1) Keyboard and Monitor backlight worked even with OSD.
     Wireless toggle (fn-f1) worked, but no OSD
     toggle touchpad (fnf9) didn't work.

Then reboot to 3.8.0.19 -> OSD was gone, no Keyboard backlight, Brightness Backlight worked

reboot to 3.9.0 rc9 -> no OSD, Brightness worked bur very laggish.
some other reboots to 3.9.0 rc9 -> no OSD, Brightness worked bur very laggish.

another reboot 3.9.0 rc9 ->everything worked again like in 1)
here i saved the dmesg :
asus_wmi: ASUS WMI generic driver loaded
asus_wmi: Initialization: 0x1asus_wmi: BIOS WMI version: 7.9
asus_wmi: SFUN value: 0x6a0877<6>[ 3.053346] input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input5
asus_wmi: Backlight controlled by ACPI video driver

after reboot -> only brightness, no OSD
dmesg output:
asus_wmi: ASUS WMI generic driver loaded
asus_wmi: Initialization: 0x1asus_wmi: BIOS WMI version: 7.9
asus_wmi: SFUN value: 0x6a0877<6>[ 2.975072] microcode: CPU1 sig=0x306a9, pf=0x10, revision=0x12
input: Asus WMI hotkeys as /devices/platform/asus-nb-wmi/input/input5
asus-nb-wmi: probe of asus-nb-wmi failed with error -5

i don't know whats the difference between asus_wmi and asus-nb-wmi... nevertheless now it gets strange:

i reinstalled the asus_wmi 0.2 manually (sudo dpkg -i asus-wmi-dkms_0.2_all.deb) which hadn't any effects except that dkms status showed, that asus_wmi is installed in 3.9.0 (see above post only states built)

then i removed asus_wmi manually! my dkms status output now shows:

bbswitch, 0.6, 3.8.0-19-generic, x86_64: installed
bbswitch, 0.6, 3.9.0-030900rc8-generic, x86_64: built
nvidia-304-updates, 304.88, 3.8.0-19-generic, x86_64: installed
nvidia-304-updates, 304.88, 3.9.0-030900rc8-generic, x86_64: installed
vboxhost, 4.2.12, 3.8.0-19-generic, x86_64: installed
vboxhost, 4.2.12, 3.9.0-030900rc8-generic, x86_64: installed
vhba, 20130121, 3.8.0-19-generic, x86_64: installed
vhba, 20130121, 3.9.0-030900rc8-generic, x86_64: installed

(dmesg still shows, that asus_wmi drivers are loaded)

AND FINALLY: On kernel 3.8.0.19 (not on 3.9 rc9) everything works like a charm (except fn-f2 Wireless toggle)
--> Keyboard Backlight with OSD
--> Brighness Control with OSD
--> Touchpad toggle with OSD (!) (fn-f9)
--> Loudness Control with OSD (fn-10 to 12)

hope this helps someone. oh, and sorry for my english :-)

I also tried with acpi_osi='' without any success.
But running dmesg with 3.8.0-19 I found this error:

[ 7.447596] asus_wmi: ASUS WMI generic driver loadedasus_nb_wmi: disagrees about version of symbol asus_wmi_register_driver
[ 7.449262] asus_nb_wmi: Unknown symbol asus_wmi_register_driver (err -22)
[ 7.449266] asus_nb_wmi: disagrees about version of symbol asus_wmi_unregister_driver
[ 7.449268] asus_nb_wmi: Unknown symbol asus_wmi_unregister_driver (err -22)

But I don't know what does it mean.

Hi,
I resolved everything.
The problem for me was the dist-upgrade only.
The kernel 3.8.0-19 amd64 works perfectly on a fresh install.
I reinstalled it when I found a very strange think: nvidia didn't work well with optimus, intel hd 4000 was unstable, and many strange things.
So I tried reinstalling everything from a fresh install and began an odissey: I think the problem was efi not really cleaned, so after the first fresh install the system booted from 3.8.0 kernel but when i was in the system, typing uname -a, showed me 3.5.0-17 (the 12.10 kernel that was installed before do-release-upgrade).
So I deleted and format / partition, removed everything from /boot/efi/EFI/ubuntu, reset windows efi (I had a backup of clean winzoz 7 install because I have dual boot) and performed a new fresh install.
Now everything works fine, all keys working except fn+f2 (wireless switch), but I extremely better than before.
The very strange think was the behaviour of the first fresh install, never seen a system completely crazy, I installed a kernel and found another, I think the problem was the efi.

Manuel Rüger (mrueg) wrote :

I ran git bisect on the kernel's sources and this might be the commit that breaks stuff:

https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=6cae06e603339f99334bc6b276e2ac619cf0d476

Can anyone confirm this? I used git bisect the first time.

Alfredo Marchini, as per http://www.asus.com/Notebooks_Ultrabooks/N56VZ/#support_Download_8 an update is available for your BIOS (2.17). 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.

description: updated
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream
tags: added: bios-outdated-217
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
summary: - Asus N56VZ fn Keys.
+ [Asus N56VZ] fn+F7 doesn't work
summary: - [Asus N56VZ] fn+F7 doesn't work
+ [Asus N56VZ] fn+F2 doesn't work
description: updated

Hi,
I already had installed BIOS 217 version, few days after were published.
With my actually kernel: 3.8.0-27-generic amd64 now every fn+key works perfectly except fn+F2.
All other fn+key, included the fn+space and the fn+calc, works perfectly.

I post the result of the 2 command that you asked me:

N56VZ.217
05/22/2013

Thank you very much for you help.
Bye

Alfredo Marchini, 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.

tags: added: latest-bios-217 regression-potential
removed: bios-outdated-217
Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers