[ASUS G75VW] Regression Fn+F2 doesn't toggle WiFi

[Rainer Rohde]

Folks,

I am currently on kernel version 3.11.0-2-generic, and the following (what I assume are) ACPI calls no longer work via Fn keys:

Fn+F2 = Toggle wifi on/off (works manually from the Network Indicator)
Fn+F5/F6 = Adjust screen brightness (doesn't work at all, not even from the System Settings)
Fn+F9 = Toggle mousepad on/off (works manually from the System Settings)

Up until 3.11.0-1-generic, my Fn+F3/F4 = Adjust keyboard backlight didn't work, either. This might be fixed in 3.11.0-2-generic, but I need to verify this.

My /etc/default/grub entry for "GRUB_CMDLINE_LINUX_DEFAULT reads "quiet splash acpi_osi=Linux acpi_backlight=vendor resume=/swapfile.swap" -- not sure if that makes a difference towards the ACPI calls...

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-2-generic 3.11.0-2.5
ProcVersionSignature: Ubuntu 3.11.0-2.5-generic 3.11.0-rc5
Uname: Linux 3.11.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.12-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rrohde 2215 F.... pulseaudio
 /dev/snd/controlC0: rrohde 2215 F.... pulseaudio
Date: Fri Aug 16 16:47:52 2013
MachineType: ASUSTeK COMPUTER INC. G75VW
MarkForUpload: True
ProcEnviron:
 LANGUAGE=en_US
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-2-generic root=UUID=4dac4492-a4d7-4a6d-97bf-ed5c1ee0b1a0 ro elevator=noop quiet splash acpi_osi=Linux acpi_backlight=vendor resume=/swapfile.swap vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-2-generic N/A
 linux-backports-modules-3.11.0-2-generic N/A
 linux-firmware 1.113
SourcePackage: linux
StagingDrivers: zram
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/07/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: G75VW.223
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: G75VW
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.:bvrG75VW.223:bd01/07/2013:svnASUSTeKCOMPUTERINC.:pnG75VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG75VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: G75VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[Brad Figg (brad-figg)]

This change was made by a bot.

[Rainer Rohde (rainer-rohde)]

I forgot to add that when pressing the power button now, the laptop simply shuts down. Previously, when pressing the power button, a menu would pop up, allowing me to select various shutdown option -- not anymore.

[penalvch (penalvch)]

Rainer Rohde, if you go back to the default kernel parameters of only:
quiet splash

does this change anything?

[Rainer Rohde (rainer-rohde)]

@Christopher --

I already tried that, with my current kernel parameters looking like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=/swapfile.swap"

The only thing that changes is that I am now getting an indicator for the screen brightness, however, the actual screen brightness does not change with it. In fact, when looking at System Settings > Brightness & Lock, the Brightness slider is there, but it does not work whatsoever.

PS: Aforementioned keyboard backlight does seem to work with kernel release 3.11.0-2-generic, which is an improvement.

[Rainer Rohde (rainer-rohde)]

Forgot to mention that pretty much everything Fn key related worked back in 12.10, with the exception of the screen brightness, which -- oddly enough -- required going into suspend, and coming out of suspend, before the screen brightness would work.

Starting with 13.04 and now 13.10, I pretty much lost all the other Fn functions as listed in my initial post, as well as the functionality of the power button triggering a shutdown dialog.

[penalvch (penalvch)]

Rainer Rohde, could you please test the latest mainline kernel via http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-rc5-saucy/ and advise on the results?

[Rainer Rohde (rainer-rohde)]

FYI (not sure if this helps at all) -- When I run "acpi_listen", and press the Fn keys for screen brightness (F5/F6), I get the following:

video LCDD 00000087 00000000
video LCDD 00000086 00000000

[Rainer Rohde (rainer-rohde)]

@Christopher --

I am unable to load the desktop with the kernel rc. It just hangs indefinitely.
Don'tI need the linux-image-extra package for this kernel so my laptop can complete the boot process?

[Rainer Rohde (rainer-rohde)]

Here's the output from tree /proc/acpi/, if that info is useful:

/proc/acpi/
├── button
│   └── lid
│   └── LID
│   └── state
├── event
└── wakeup

[Rainer Rohde (rainer-rohde)]

Another thing I tried out of curiosity -- I downgraded the BIOS to ver 210.

Results: Fn+F2 (toggle wifi) came back to life, however, no other function returned to operations.

It seemed as if Fn+F5/F6 felt smoother, more fine-grained, however, the actual screen brightness function still didn't work.

I've since returned the laptop to BIOS ver 223.

[penalvch (penalvch)]

Rainer Rohde, given how each of the problems mentioned in your Bug Description are driven by different actors:
1) Fn+F2 = Toggle wifi on/off (works manually from the Network Indicator) -> Network Manager, WiFi driver, BIOS, and udev
2) Fn+F5/F6 = Adjust screen brightness (doesn't work at all, not even from the System Settings) -> Kernel, kernel quirk (or lack there of), BIOS, video driver, and udev
3) Fn+F9 = Toggle mousepad on/off (works manually from the System Settings) -> Kernel, BIOS, and udev

I would like to split each of these problems into their own separate report to track and fix, as this would make it immensely easier for all in isolating, triaging, and ultimately fixing.

Hence, let this report focus on 1) . Given this, with the 223 BIOS, did this problem not occur in a release prior to Saucy?

[Rainer Rohde (rainer-rohde)]

That sounds like a good idea, Christopher.

Regarding Problem #1, I do remember that this was working just fine in 12.10. Once I stepped up to 13.04, this functionality was lost. But along the way I might have stepped up the BIOS version, too. I think I remember that I bought the ASUS G75VW with the 210 BIOS revision, and stepped up to 221 right away. I can't tell you whether that feature got "lost" due to the BIOS or due to any Ubuntu kernel.
I guess the fact that it still works on Saucy when using the 210 BIOS is reassuring that it might not be a kernel issue...

[penalvch (penalvch)]

Rainer Rohde, the next step would be to bisect from Quantal to Raring, in order to identify the offending commit. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection ?

[fademind (fademind)]

ASUS X54C have same problem. Fn + F9 not working.

tomasz@ASUS-X54C:~/tmp$ tree /proc/acpi/
/proc/acpi/
├── button
│   └── lid
│   └── LID
│   └── state
├── event
└── wakeup

Kernel: Linux ASUS-X54C 3.11.0-4-generic #9-Ubuntu SMP Mon Aug 26 15:21:06 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
OS: Ubuntu 13.10 x64

[penalvch (penalvch)]

Tomasz Przybył, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[fademind (fademind)]

Christopher M. Penalver (penalvch) Thank you for the quick reply and links. I'm sorry for the mess in this thread. I will create a new report on my device.

[Launchpad Janitor (janitor)]

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