[Asus UX360UA] Some Keyboard and hardware not recognised automatically

[tjiagoM]

I've just installed Ubuntu 16.04.1 in dualboot on top of an Asus UX360UA, alongside with Windows 10. I've already installed the updates meanwhile.

The following sequence of keys are not working:

FN+F2 (activate flight mode?) - I think in a way it stops my internet connection but I don't see any visual feedback on the screen nor the light in the "F2" key is turned on/off

FN+F5 / FN+F6 (adjust brightness)

FN+F7 (turn off screen)

Also, the hardware buttons on left side of the laptop for changing the volume are not working. I click on them and the volume keeps the same
---
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tjiagom 1895 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=0eaf9255-c29a-41b7-8449-1eb52f637933
InstallationDate: Installed on 2017-02-04 (0 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp.
 Bus 001 Device 002: ID 04f2:b56b Chicony Electronics Co., Ltd
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. UX360UA
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed root=UUID=6ca1f963-632a-401d-80db-610ef37f1f26 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-62-generic N/A
 linux-backports-modules-4.4.0-62-generic N/A
 linux-firmware 1.157.6
Tags: xenial
Uname: Linux 4.4.0-62-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/17/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX360UA.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX360UA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX360UA.300:bd06/17/2016:svnASUSTeKCOMPUTERINC.:pnUX360UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX360UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: UX360UA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

[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 1661864

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.

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[tjiagoM (tjiagom)]

apport information

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.10 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.10-rc7

[tjiagoM (tjiagom)]

Hi,

I tested the upstream kernel and why some keys are now working, others don't.

So, in a nutshell:
FN+F2 (activate flight mode?) - It seems it is working now, at least I see wireless and bluetooth turning off/on. However, if I do the following: press it (turn flight mode off), and press it again (turn on), the light is on... Shouldn't the light be on just when flight mode is on? When the computer starts, the light is off

FN+F5 / FN+F6 - working now! However, it doesn't go to the minimum of brightness. If I open the "Brightness & Lock" I can reduce it more than with the keys

FN+F7 (turn off screen) - still not working

Hardware buttons in the left side of the laptop still don't work.

[tjiagoM (tjiagom)]

* Forget about the part "why some keys are now working, others don't". My mistake

[tjiagoM (tjiagom)]

An update on this issue now that I have kernel 4.14:

After executing `uname -a`, I have the following output:
`Linux tjiagom-UX360UA 4.14.0-041400-generic #201711122031 SMP Sun Nov 12 20:32:29 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux`

So, with kernel 4.14, the hardware buttons are now working, but FN+F7 (turn off the screen) still doesn't work.

About FN+F2 (flight mode), seems it's working but the light doesn't turn on or off.

About FN+F5 / FN+F6, it's the same of my last comment.

[tjiagoM (tjiagom)]

An update: I now have kernel 4.16rc1 and the situation is exactly as I said in my last comment #19