[fn] plus F2,F3,F4,F5,F6,F10,F11,F12 not responding - Fresh Install

[Andrew F in Australia]

Gigabyte P57 laptop

Fresh install, 10 days old, updated yesterday so software/kernel should be current.

Some function keys work.
Function plus F1 puts the machine to sleep
Function plus F7, F8, F9 control the volume

However,
Pressing Function plus F2 does not turn off wireless
Pressing Function plus F3,F4 do not change brightness
Function plus F5 does not change output to LCD or Monitor
Pressing Function plus F6 does not toggle touchpad (a separate bug in this machine, but the Elantech touchpad is recognised at the moment.)
Function plus F10 does not turn the display off
Function plus F11 does not turn off bluetooth
Function plus F12 does not disable the camera

Please let me know if you need any further troubleshooting

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-47-generic 4.4.0-47.68
ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
Uname: Linux 4.4.0-47-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: horace 1948 F.... pulseaudio
CurrentDesktop: Unity
Date: Sat Nov 26 07:44:13 2016
HibernationDevice: RESUME=UUID=fba63969-ab35-4aa7-b2f7-e432edba169e
InstallationDate: Installed on 2016-11-13 (12 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 05af:1050 Jing-Mold Enterprise Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: GIGABYTE P57
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-47-generic.efi.signed root=UUID=e9ea66ca-2853-4d85-bc49-74de4c35c442 ro quiet splash i8042.nomux=1 vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-47-generic N/A
 linux-backports-modules-4.4.0-47-generic N/A
 linux-firmware 1.157.5
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FB0B
dmi.board.asset.tag: Default string
dmi.board.name: P57
dmi.board.vendor: GIGABYTE
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 10
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFB0B:bd05/30/2016:svnGIGABYTE:pnP57:pvrDefaultstring:rvnGIGABYTE:rnP57:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:
dmi.product.name: P57
dmi.product.version: Default string
dmi.sys.vendor: GIGABYTE

[Brad Figg (brad-figg)]

This change was made by a bot.

[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 v4.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'.

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/v4.9-rc7

[Andrew F in Australia (gimme-spam)]

Hi Joseph,

Many thanks for this. Install was unsuccessful and no change to behaviur
(see below)

Have just tried but bug 1573206 (unable to install third-party deb
files) didn't run the *.deb file in software update

gdebi crashed also when I tried to run from there

See attached *.txt file - dump of linux commands used to try and install
with error messages.

No change to behaviour - could be due to unsuccessful installation.

Could you please advise other commands that I need to use to
successfully install development package (oh, and the xenial-proposed
developer option was ticked in the Software & Updates tab.)

Regards,

[penalvch (penalvch)]

Andrew F in Australia, to advise, a failure to install the kernel wouldn't fit the criteria of kernel-bug-exists-upstream.

However, to keep this relevant to upstream, one would want to periodically check for, and test the latest mainline kernel (now 4.9) as it is released.

Could you please advise?

[Andrew F in Australia (gimme-spam)]

HI Christopher,

Tested today when I installed the latest upstream kernel today to test for a touchpad bug.

No luck, Function keys still not responding.

Will make a note to install upstream kernels in a month or so to see if it's fixed.

Many thanks,

[penalvch (penalvch)]

Andrew F in Australia, could you please advise which version of the kernel you tested specifically?

[Andrew F in Australia (gimme-spam)]

Hi Christopher.

4.10.something 2 weeks ago.

I'll retest current over the weekend.

Regards,

Andrew F

On 21/02/17 11:07, Christopher M. Penalver wrote:
> Andrew F in Australia, could you please advise which version of the
> kernel you tested specifically?
>

[penalvch (penalvch)]

Andrew F, could you please advise if removing the kernel parameter i8042.nomux=1 impacts this issue?

[Andrew F in Australia (gimme-spam)]

Hi Christopher.

Will do - I'll allocate a couple of hours tomorrow evening to play
around with the kernel.

This laptop has an Elantech touchpad which needs a couple of i8042.xxxxx
commands to get it to work.

I'll install the nightly build kernel tomorrow night and let you know.

Regards,

Andrew F

On 09/03/17 14:38, Christopher M. Penalver wrote:
> Andrew F, could you please advise if removing the kernel parameter
> i8042.nomux=1 impacts this issue?
>

[jamso (jdsherratt3)]

I've been having the same problems on a gigabyte p57 xcf3. Bu

[jamso (jdsherratt3)]

Sorry about the above post. Let me try again

I've been having the same problems on a gigabyte p57 xcf3. Bug #1665530 also reports this. Currently I am running the latest bios for this laptop, Ubuntu 16.10 and kernel 4.10.1-041001-generic.

Initially I did not have the "i8042.nomux=1" parameter. Adding this parameter to just stop the touchpad working for me, but it seems very hit-and-miss whether the touchpad decides to work in general.

Another thing not mentioned, the keyboard backlight keys (fn + space) does not work. However, if I switch on the backllight in windows, it will stay switched on on the first boot of linux, but switches off for the second boot.

[Kai-Heng Feng (kaihengfeng)]

Hi Andrew,

Can you switch to VT (ctrl + alt + F1) and login, then run `sudo showkey -s`, press each non-functional hotkey, and attach the results?

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng,

Attached file with many thanks.

The keyboard did not register the above keystrokes.

It did register F1 - F12

On 12/03/17 18:52, Kai-Heng Feng wrote:
> Hi Andrew,
>
> Can you switch to VT (ctrl + alt + F1) and login, then run `sudo showkey
> -s`, press each non-functional hotkey, and attach the results?
>

[Andrew F in Australia (gimme-spam)]

I just re-read my rushed email post.

What the above was trying to say was:

F1-F12 were registered when the key was pressed.
Fn + F1 registered a response.
Fn + F7 registered a response.
Fn + F8 registered a response.
Fn + F9 registered a response.

Any other combination of function keys did not register any response/input under showkey -s

The logfile attached annotates what I was trying to say

Regards,

Andrew

[Andrew F in Australia (gimme-spam)]

Christopher/Joseph.

The nightly build failed to install correctly. Still pursuing.

A

[Kai-Heng Feng (kaihengfeng)]

We need some information from ACPI then.

Please install acpica-tools and run acpidump,

$ sudo apt install acpica-tools
$ sudo acpidump > acpi-dump

Attach acpi-dump file.

[Andrew F in Australia (gimme-spam)]

Thanks Kai-Heng.

Done (and attached.)

Many thanks,

A

On 13/03/17 15:56, Kai-Heng Feng wrote:
> We need some information from ACPI then.
>
> Please install acpica-tools and run acpidump,
>
> $ sudo apt install acpica-tools
> $ sudo acpidump > acpi-dump
>
> Attach acpi-dump file.
>

[Andrew F in Australia (gimme-spam)]

Installed development kernel 4.11.0-041100rc2-lowlatency overnight as promised - no change in behaviour, buttons still not recognised.

Also same behaviour with 4.11.0-041100rc2-generic module that loaded last

[Brad Figg (brad-figg)]

This change was made by a bot.

[Kai-Heng Feng (kaihengfeng)]

Hi,

Please download the attachment, and follow the steps:

$ tar xf gigabyte-wmi.tar.xz
$ cd gigabyte-wmi
$ make
$ sudo insmod gigabyte-wmi.ko

And attach the output of `dmesg`.

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng,

I downloaded and attempted to install this patch unsuccessfully.

sudo make didn't work - bash ./etc didn't

Could you please advise a 'step-by-step' on how to install this patch.

Regards,

Andrew F

On 17-Mar-17 4:07 PM, Kai-Heng Feng wrote:
> ** Attachment added: "gigabyte-wmi.tar.xz"
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1644919/+attachment/4839208/+files/gigabyte-wmi.tar.xz
>

---
This email has been checked for viruses by AVG.
http://www.avg.com

[Kai-Heng Feng (kaihengfeng)]

Sorry, I make a mistake in the Makefile.
Please use this attachment and try again.

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng,

Attached output from 'make' - assume installed correctly. I'll reboot and let you know if it worked.

root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi# dir
gigabyte-wmi.c Makefile
root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi# sudo make
make -C /lib/modules/4.11.0-041100rc2-lowlatency/build M=`pwd`
make[1]: Entering directory '/usr/src/linux-headers-4.11.0-041100rc2-lowlatency'
  LD /mnt/Data/Linux_drivers/gigabyte-wmi/built-in.o
  CC [M] /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.o
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c: In function ‘gigabyte_wmi_notify’:
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:63:6: warning: unused variable ‘scancode’ [-Wunused-variable]
  u32 scancode;
      ^
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:62:26: warning: unused variable ‘key’ [-Wunused-variable]
  const struct key_entry *key;
                          ^
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:61:6: warning: unused variable ‘device_state’ [-Wunused-variable]
  u16 device_state;
      ^
  Building modules, stage 2.
  MODPOST 1 modules
  CC /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.mod.o
  LD [M] /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.11.0-041100rc2-lowlatency'
root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi# sudo make install
make: *** No rule to make target 'install'. Stop.
root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi#

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng,

Attached output from 'make' below - assume installed correctly. After reboot, there was no change in behaviour. Please let me know if I've made a mistake in installation - have not reinstalled a nightly build since the above.

Regards,

Andrew F

root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi# dir
gigabyte-wmi.c Makefile
root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi# sudo make
make -C /lib/modules/4.11.0-041100rc2-lowlatency/build M=`pwd`
make[1]: Entering directory '/usr/src/linux-headers-4.11.0-041100rc2-lowlatency'
  LD /mnt/Data/Linux_drivers/gigabyte-wmi/built-in.o
  CC [M] /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.o
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c: In function ‘gigabyte_wmi_notify’:
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:63:6: warning: unused variable ‘scancode’ [-Wunused-variable]
  u32 scancode;
      ^
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:62:26: warning: unused variable ‘key’ [-Wunused-variable]
  const struct key_entry *key;
                          ^
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:61:6: warning: unused variable ‘device_state’ [-Wunused-variable]
  u16 device_state;
      ^
  Building modules, stage 2.
  MODPOST 1 modules
  CC /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.mod.o
  LD [M] /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.11.0-041100rc2-lowlatency'
root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi# sudo make install
make: *** No rule to make target 'install'. Stop.
root@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi#

[Kai-Heng Feng (kaihengfeng)]

Hi Andrew,

You need to boot to 4.4.0-XX kernel instead of mainline kernel.

The latest mainline kernel is for testing only - you can safely remove those kernels after testing is done.

To remove mainline kernels, you can run something like this:
$ sudo apt purge $(dpkg -l | grep 041100rc2 | awk '{print $2}')

Do the same for other mainline kernels you installed for testing.

[Andrew F in Australia (gimme-spam)]

Thanks Kai-Heng.

Just tried installing on 4.4.0-66

Messages attached below on installation.

Is it still the commands that I'm using? (didn't work on install - Rebooted and it still didn't work)

Thanks for your patience and perseverance.

A

horace@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi$ uname -r
4.4.0-66-generic

horace@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi$ sudo make
[sudo] password for horace:
make -C /lib/modules/4.4.0-66-generic/build M=`pwd`
make[1]: Entering directory '/usr/src/linux-headers-4.4.0-66-generic'
  CC [M] /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.o
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c: In function ‘gigabyte_wmi_notify’:
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:63:6: warning: unused variable ‘scancode’ [-Wunused-variable]
  u32 scancode;
      ^
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:62:26: warning: unused variable ‘key’ [-Wunused-variable]
  const struct key_entry *key;
                          ^
/mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.c:61:6: warning: unused variable ‘device_state’ [-Wunused-variable]
  u16 device_state;
      ^
  Building modules, stage 2.
  MODPOST 1 modules
  CC /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.mod.o
  LD [M] /mnt/Data/Linux_drivers/gigabyte-wmi/gigabyte-wmi.ko
make[1]: Leaving directory '/usr/src/linux-headers-4.4.0-66-generic'
horace@horace-P57:/mnt/Data/Linux_drivers/gigabyte-wmi$ sudo make install
make: *** No rule to make target 'install'. Stop.

[Kai-Heng Feng (kaihengfeng)]

Well, this is not a fully functional driver yet, but it should help us grab enough information to write a working driver.

Please follow these steps after you run `make`:

$ sudo modprobe wmi
$ sudo insmod gigabyte-wmi.ko

Then press FN+F1 to F12 (except sleep and volume control)
Attach output of `dmesg` here.

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng,

Thanks again - I'm not a Linux expert or software developer - was just confirming that my syntax or installation procedure was not part of the problem. I appreciate the time you're putting in here.

Keys pressed in order.

[fn] plus F2, F3, F4, F5, F6, F10, F11, F12

I just opened the manual (also attached) and noticed that fn+escape is an eject of a CD drive, which I can't check as I've got a SSD mounted in the CD bay.

log attached as well as a screenshot of the relevant manual page on the next post.

With many thanks and best regards,

A

[Kai-Heng Feng (kaihengfeng)]

I made another mistake, I missed another module in earlier instruction ;)

Please do the following, after `make`:

$ sudo modprobe wmi
$ sudo modprobe sparse_keymap
$ sudo insmod gigabyte-wmi.ko

Then press hotkeys & attach output of `dmesg` here.

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng.

Attached - accidentally hit sleep when hitting hot-keys as shown in dmesg.

Also - I pressed [Fn] + [ESC] (eject CD Tray) and [Fn] + [Space] (Toggle keyboard backlight) in this output. sudo showkey -s did not detect output from these either.

If you need this re-run, please let me know. I installed the patch before I installed sparse-keys. Don't know if this makes a difference.

Many thanks,

A

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng.

Attached - accidentally hit sleep when hitting hot-keys as shown in dmesg.

Also - I pressed [Fn] + [ESC] (eject CD Tray) and [Fn] + [Space] (Toggle keyboard backlight) in this output. sudo showkey -s did not detect output from these either.

If you need this re-run, please let me know. I installed the patch before I installed sparse-keys. Don't know if this makes a difference.

Many thanks,

A

[Kai-Heng Feng (kaihengfeng)]

`insmod gigabyte-wmi.ko` should be executed after `modprobe wmi` and `modporbe sparse_keymap`.

Can you do it yet again? Sorry!

[Andrew F in Australia (gimme-spam)]

No problem Kai-Heng. More than happy to help - was just having a shocking Sat.

Attached.

[Kai-Heng Feng (kaihengfeng)]

There's no key event in the log, maybe I am wrong here...

Can you run `acpi_listen`, then press those not working hotkeys?
Does it show anything?

[Andrew F in Australia (gimme-spam)]

Hi Kai-Heng.

Then non-functional keys didn't register - attached is the dmesg log and the acpi_listen output.

Only keys that did register were sleep [F1], Volume [F7] -> [F9]

Regards,

A?field.comment=Hi Kai-Heng.

Then non-functional keys didn't register - attached is the dmesg log and the acpi_listen output.

Only keys that did register were sleep [F1], Volume [F7] -> [F9]

Regards,

A

[Kai-Heng Feng (kaihengfeng)]

Here's a simple way to directly capture the ACPI event, kudos to Alex Hung and Colin King!

== SystemTap AML op-codes ==

1. Clone the pmdebug git repository:

git clone https://github.com/alexhungce/pmdebug

2. Install SystemTap and the appropriate kernel .ddebs

sudo apt-get install systemtap

2.1) Create an /etc/apt/sources.list.d/ddebs.list by running the
following line at a terminal:

echo "deb http://ddebs.ubuntu.com $(lsb_release -cs) main restricted
universe multiverse" | sudo tee -a /etc/apt/sources.list.d/ddebs.list

2.2) Import the debug symbol archive signing key:

sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 428D7C01

2.3) Then run:

sudo apt-get update

2.4) Download and install the debug kernel, e.g.

sudo apt-get install linux-image-`uname -r`-dbgsym

3. Run the script

sudo stap -g pmdebug/systemtap/amltrace/amltrace.stp | tee output

4. Press non-functional hotkeys

5. Attach 'output'

[jamso (jdsherratt3)]

I made an attempt to follow the instructions above, and attached the output.

None of the not-working fn keys registered (I tested fn+delete, which is a key which works).

This was done on ubuntu 17.04 using 4.10.0-21-generic kernel.
Also the instructions for installing systemtap didn't work, so I used this: https://wiki.ubuntu.com/Kernel/Systemtap

[Kai-Heng Feng (kaihengfeng)]

This requires linux kernel debugging symbol to work.
Which step failed?