Jump to content

Ubuntu - HP Pavilion 11 x360 - Keyboard & Touchpad not working after install

Go to solution Solved by elsandosgrande,

All right, they seem to be detected at least. Try searching for their device files, as those should show up in the kernel log (the file paths following “Kernel: ” in the device list).

 

Edit

So, after doing some research online, though it was not comprehensive, I saw that one possible solution would be to disable ACPI (third comment). I'd call that a last resort, as ACPI is fairly important. Before that though, we'll just have to see what errors the kernel throws, if any.

I decided to put Ubuntu on to an old HP Pavilion 11 x360 2-in-1 laptop, and the touchpad and keyboard worked fine before I did the official installation. Afterwards, only the touchscreen worked and the keyboard and touchpad were not responsive. the keyboard inputs work in BIOS, so I know it must come down to a Linux kernel/patch for both the touchpad and keyboard. I'm trying to avoid using external devices (except for when I'm fixing this issue of course) so anyone with experience using Linux/Ubuntu that has resources or suggestions how I could solve this issue for this device would be greatly appreciated. Thanks! 

Link to comment
Share on other sites

Link to post
Share on other sites

Well, the first step is to see if they are even being detected at the moment. Try running `libinput list-devices` and seeing if a keyboard and touchpad appear on the list.

Link to comment
Share on other sites

Link to post
Share on other sites

12 hours ago, elsandosgrande said:

Well, the first step is to see if they are even being detected at the moment. Try running `libinput list-devices` and seeing if a keyboard and touchpad appear on the list.

@elsandosgrandeI ran that and neither the keyboard or touchpad appeared. They both started working though after I plugged in an external mouse (and worked after I unplugged it). After I restarted the laptop, they didn't work again, and wouldn't work again even after plugging my external mouse again. Any thoughts?

Link to comment
Share on other sites

Link to post
Share on other sites

2 hours ago, Harrydarth said:

@elsandosgrandeI ran that and neither the keyboard or touchpad appeared. They both started working though after I plugged in an external mouse (and worked after I unplugged it). After I restarted the laptop, they didn't work again, and wouldn't work again even after plugging my external mouse again. Any thoughts?

🤔

What do you see in `sudo dmesg --human` right after you plug the external peripherals in? I imagine that something should appear in there Shift+G gets you to the bottom of the log. Does listing the devices again and plugging the peripherals again result in the internal keyboard and touchpad being detected again? Maybe `libinput list-devices` triggers something?

Link to comment
Share on other sites

Link to post
Share on other sites

@elsandosgrandehere is what `sudo dmesg --human` listed:

sudo dmesg --human
[Nov20 20:43] microcode: microcode updated early to revision 0x838, date = 2>
[  +0.000000] Linux version 5.4.0-54-generic (buildd@lcy01-amd64-024) (gcc v>
[  +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic root=U>
[  +0.000000] KERNEL supported cpus:
[  +0.000000]   Intel GenuineIntel
[  +0.000000]   AMD AuthenticAMD
[  +0.000000]   Hygon HygonGenuine
[  +0.000000]   Centaur CentaurHauls
[  +0.000000]   zhaoxin   Shanghai  
[  +0.000000] x86/fpu: x87 FPU will use FXSAVE
[  +0.000000] BIOS-provided physical RAM map:
[  +0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable
[  +0.000000] BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS
[  +0.000000] BIOS-e820: [mem 0x0000000000070000-0x0000000000085fff] usable
[  +0.000000] BIOS-e820: [mem 0x0000000000086000-0x000000000009ffff] reserved
[  +0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usable
[  +0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff] reserved
[  +0.000000] BIOS-e820: [mem 0x0000000020100000-0x0000000078595fff] usable
[  +0.000000] BIOS-e820: [mem 0x0000000078596000-0x0000000079295fff] reserved
[  +0.000000] BIOS-e820: [mem 0x0000000079296000-0x0000000079395fff] ACPI NVS
:...skipping...
[Nov20 20:43] microcode: microcode updated early to revision 0x838, date >
[  +0.000000] Linux version 5.4.0-54-generic (buildd@lcy01-amd64-024) (gc>
[  +0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic roo>
[  +0.000000] KERNEL supported cpus:
[  +0.000000]   Intel GenuineIntel
[  +0.000000]   AMD AuthenticAMD
[  +0.000000]   Hygon HygonGenuine
[  +0.000000]   Centaur CentaurHauls
[  +0.000000]   zhaoxin   Shanghai  
[  +0.000000] x86/fpu: x87 FPU will use FXSAVE
[  +0.000000] BIOS-provided physical RAM map:
[  +0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usab>
[  +0.000000] BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI>
[  +0.000000] BIOS-e820: [mem 0x0000000000070000-0x0000000000085fff] usab>
[  +0.000000] BIOS-e820: [mem 0x0000000000086000-0x000000000009ffff] rese>
[  +0.000000] BIOS-e820: [mem 0x0000000000100000-0x000000001fffffff] usab>
[  +0.000000] BIOS-e820: [mem 0x0000000020000000-0x00000000200fffff] rese>
[  +0.000000] BIOS-e820: [mem 0x0000000020100000-0x0000000078595fff] usab>
[  +0.000000] BIOS-e820: [mem 0x0000000078596000-0x0000000079295fff] rese>
[  +0.000000] BIOS-e820: [mem 0x0000000079296000-0x0000000079395fff] ACPI>
[  +0.000000] BIOS-e820: [mem 0x0000000079396000-0x00000000793d5fff] ACPI>
[  +0.000000] BIOS-e820: [mem 0x00000000793d6000-0x0000000079ffffff] usab>
[  +0.000000] BIOS-e820: [mem 0x00000000e00f8000-0x00000000e00f8fff] rese>
[  +0.000000] BIOS-e820: [mem 0x00000000fed01000-0x00000000fed01fff] rese>
[  +0.000000] BIOS-e820: [mem 0x00000000ffb80000-0x00000000ffffffff] rese>
[  +0.000000] BIOS-e820: [mem 0x0000000100000000-0x000000017fffffff] usab>
[  +0.000000] NX (Execute Disable) protection: active
[  +0.000000] efi: EFI v2.31 by INSYDE Corp.
[  +0.000000] efi:  ACPI 2.0=0x793d5014  ESRT=0x788a7e18  SMBIOS=0x792950>
[  +0.000000] secureboot: Secure boot enabled
[  +0.000000] Kernel is locked down from EFI Secure Boot mode; see man ke>
[  +0.000000] SMBIOS 2.7 present.
[  +0.000000] DMI: Hewlett-Packard HP Pavilion 11 x360 PC/2209, BIOS F.14>
[  +0.000000] tsc: Detected 2166.667 MHz processor
[  +0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[  +0.000004] e820: remove [mem 0x000a0000-0x000fffff] usable
[  +0.000010] last_pfn = 0x180000 max_arch_pfn = 0x400000000
 

here is what list-devices listed:
Usage: /usr/bin/list-devices cd|disk|partition|floppy|maybe-usb-floppy|usb-partition|mmc-partition

 

 

here is what ibinput list-devices listed:
Failed to open /dev/input/event2 (Permission denied)
Failed to open /dev/input/event4 (Permission denied)
Failed to open /dev/input/event0 (Permission denied)
Failed to open /dev/input/event1 (Permission denied)
Failed to open /dev/input/event17 (Permission denied)
Failed to open /dev/input/event18 (Permission denied)
Failed to open /dev/input/event19 (Permission denied)
Failed to open /dev/input/event20 (Permission denied)
Failed to open /dev/input/event21 (Permission denied)
Failed to open /dev/input/event13 (Permission denied)
Failed to open /dev/input/event14 (Permission denied)
Failed to open /dev/input/event15 (Permission denied)
Failed to open /dev/input/event16 (Permission denied)
Failed to open /dev/input/event6 (Permission denied)
Failed to open /dev/input/event7 (Permission denied)
Failed to open /dev/input/event11 (Permission denied)
Failed to open /dev/input/event9 (Permission denied)
Failed to open /dev/input/event3 (Permission denied)
Failed to open /dev/input/event8 (Permission denied)
Failed to open /dev/input/event5 (Permission denied)
Failed to open /dev/input/event10 (Permission denied)
Failed to open /dev/input/event12 (Permission denied)

 

in total, internal keyboard, touch pad, as well as Bluetooth now are not functional in OS. Tried recreating with list-devices and external peripheral and no changes. 

 

 

Link to comment
Share on other sites

Link to post
Share on other sites

  1. I forgot that you need to prepend `sudo` to `libinput list-devices` if you're not in the `input` group 😅.
  2. You need to use code block when pasting something from the terminal.
  3. `sudo dmesg --human` uses the same navigation as Vim does, so you need to press Shift+G to get to the bottom of the log. If you see your internal keyboard listed by libinput, then you can search for it in dmesg by typing Slash (Shift+7 on my Bosnian keyboard), typing the query, and pressing Enter. You move between matches by pressing N for the next match and Shift+N for the previous one. For example, this is what I get when searching for my touchpad as listed in `sudo libinput list-devices` (I only copied the first part of the name as listed by libinput to increase the chances of getting a match):

Screenshot from 2020-11-21 13-22-59.png

 

Edit

Oh, I forgot to also paste what the “mouse” (I only have a touchpad and no mice, so ¯\_(ツ)_/¯) and touchpad are listed as on my laptop for comparison's sake:

***
Device:           DELL097A:00 04F3:30C4 Mouse
Kernel:           /dev/input/event8
Group:            7
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           DELL097A:00 04F3:30C4 Touchpad
Kernel:           /dev/input/event11
Group:            7
Seat:             seat0, default
Size:             104x78mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation:         n/a
***

 

Edited by elsandosgrande
Added additional information
Link to comment
Share on other sites

Link to post
Share on other sites

10 hours ago, elsandosgrande said:
  1. I forgot that you need to prepend `sudo` to `libinput list-devices` if you're not in the `input` group 😅.
  2. You need to use code block when pasting something from the terminal.
  3. `sudo dmesg --human` uses the same navigation as Vim does, so you need to press Shift+G to get to the bottom of the log. If you see your internal keyboard listed by libinput, then you can search for it in dmesg by typing Slash (Shift+7 on my Bosnian keyboard), typing the query, and pressing Enter. You move between matches by pressing N for the next match and Shift+N for the previous one. For example, this is what I get when searching for my touchpad as listed in `sudo libinput list-devices` (I only copied the first part of the name as listed by libinput to increase the chances of getting a match):

Screenshot from 2020-11-21 13-22-59.png

 

Edit

Oh, I forgot to also paste what the “mouse” (I only have a touchpad and no mice, so ¯\_(ツ)_/¯) and touchpad are listed as on my laptop for comparison's sake:




***
Device:           DELL097A:00 04F3:30C4 Mouse
Kernel:           /dev/input/event8
Group:            7
Seat:             seat0, default
Capabilities:     pointer 
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   *button
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   flat *adaptive
Rotation:         n/a

Device:           DELL097A:00 04F3:30C4 Touchpad
Kernel:           /dev/input/event11
Group:            7
Seat:             seat0, default
Size:             104x78mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge 
Click methods:    *button-areas clickfinger 
Disable-w-typing: enabled
Accel profiles:   flat *adaptive
Rotation:         n/a
***

 

@elsandosgrande  Managed to get 'sudo libinput list-devices' to work :')

 

(still learning my way around Linux so all of this is super helpful)

 

(realized I didn't use code break but here's what I got):

 

Device:           AT Translated Set 2 keyboard
Kernel:           /dev/input/event3
Group:            9
Seat:             seat0, default
Capabilities:     keyboard
Tap-to-click:     n/a
Tap-and-drag:     n/a
Tap drag lock:    n/a
Left-handed:      n/a
Nat.scrolling:    n/a
Middle emulation: n/a
Calibration:      n/a
Scroll methods:   none
Click methods:    none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation:         n/a

 

Device:           SynPS/2 Synaptics TouchPad
Kernel:           /dev/input/event13
Group:            10
Seat:             seat0, default
Size:             98x58mm
Capabilities:     pointer gesture
Tap-to-click:     disabled
Tap-and-drag:     enabled
Tap drag lock:    disabled
Left-handed:      disabled
Nat.scrolling:    disabled
Middle emulation: disabled
Calibration:      n/a
Scroll methods:   *two-finger edge
Click methods:    *button-areas clickfinger
Disable-w-typing: enabled
Accel profiles:   none
Rotation:         n/a

 

Checked sudo dmesg --human and neither device appears in any form in this input. Happy to send a screenshot when able.

Link to comment
Share on other sites

Link to post
Share on other sites

All right, they seem to be detected at least. Try searching for their device files, as those should show up in the kernel log (the file paths following “Kernel: ” in the device list).

 

Edit

So, after doing some research online, though it was not comprehensive, I saw that one possible solution would be to disable ACPI (third comment). I'd call that a last resort, as ACPI is fairly important. Before that though, we'll just have to see what errors the kernel throws, if any.

Edited by elsandosgrande
Added additional information
Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×