F5F Stay Refreshed Software Operating Systems Ubuntu installation issues on HP Pavilion 11 x360 keyboard and touchpad problems

Ubuntu installation issues on HP Pavilion 11 x360 keyboard and touchpad problems

Ubuntu installation issues on HP Pavilion 11 x360 keyboard and touchpad problems

X
xBioTeK
Member
136
08-31-2020, 09:35 AM
#1
I chose to install Ubuntu on an old HP Pavilion 11 x360 2-in-1 laptop. The touchpad and keyboard functioned properly initially, but after the official setup only the touchscreen remained active while the keyboard and touchpad became unresponsive. Since keyboard input still works in BIOS, the issue likely stems from a Linux kernel or patch for both devices. I’m avoiding external hardware except during troubleshooting and would appreciate advice from experienced Ubuntu users on resolving this problem. Thanks!
X
xBioTeK
08-31-2020, 09:35 AM #1

I chose to install Ubuntu on an old HP Pavilion 11 x360 2-in-1 laptop. The touchpad and keyboard functioned properly initially, but after the official setup only the touchscreen remained active while the keyboard and touchpad became unresponsive. Since keyboard input still works in BIOS, the issue likely stems from a Linux kernel or patch for both devices. I’m avoiding external hardware except during troubleshooting and would appreciate advice from experienced Ubuntu users on resolving this problem. Thanks!

G
GWMagic
Junior Member
47
08-31-2020, 11:05 AM
#2
Check if any devices are currently detected by running `libinput list-devices`. Look for keyboard and touchpad entries.
G
GWMagic
08-31-2020, 11:05 AM #2

Check if any devices are currently detected by running `libinput list-devices`. Look for keyboard and touchpad entries.

A
Ayqse
Junior Member
23
09-13-2020, 10:18 AM
#3
I tested that setup and neither the keyboard nor the touchpad showed up. They eventually began functioning once I connected an external mouse, but only after unplugging and plugging it back in. After restarting the laptop, they stopped working again, even when I reused the external mouse. Any advice?
A
Ayqse
09-13-2020, 10:18 AM #3

I tested that setup and neither the keyboard nor the touchpad showed up. They eventually began functioning once I connected an external mouse, but only after unplugging and plugging it back in. After restarting the laptop, they stopped working again, even when I reused the external mouse. Any advice?

J
Juan2610
Posting Freak
875
09-13-2020, 02:05 PM
#4
You notice entries about hardware after connecting peripherals. Pressing Shift+G may navigate deeper into the logs. Repeating device listings and plugging devices often reappears the internal keyboard and touchpad. Running `libinput list-devices` might trigger related actions.
J
Juan2610
09-13-2020, 02:05 PM #4

You notice entries about hardware after connecting peripherals. Pressing Shift+G may navigate deeper into the logs. Repeating device listings and plugging devices often reappears the internal keyboard and touchpad. Running `libinput list-devices` might trigger related actions.

C
crazyhunterMN
Member
53
09-13-2020, 05:11 PM
#5
Here is a revised version of your text:

@elsandosgrande this is the output from `sudo dmesg --human`:
sudo dmesg --human [Nov20 20:43]
Microcode updated to revision 0x838, dated 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>
Kernel supported cpus: [ +0.000000] Intel GenuineIntel
AMD AuthenticAMD [ +0.000000] Hygon HygonGenuine
Centaur CentaurHauls [ +0.000000] zhaoxin Shanghai
x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map: [ +0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable
BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS
BIOS-e820: [mem 0x0000000070000000-0x0000000085fff] usable
BIOS-e820: [mem 0x0000000086000000-0x000000009ffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x00000000200fffff] reserved
BIOS-e820: [mem 0x0000000078596000-0x0000000079295fff] usable
BIOS-e820: [mem 0x0000000020100000-0x0000000078595fff] reserved
BIOS-e820: [mem 0x0000000079296000-0x0000000079395fff] reserved
ACPI NVS :...skipping...

[Nov20 20:43]
Microcode updated early to revision 0x838, date > [ +0.000000] Linux version 5.4.0-54-generic (buildd@lcy01-amd64-024) (gc>
Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic roo>
KERNEL supported cpus: [ +0.000000] Intel GenuineIntel
AMD AuthenticAMD [ +0.000000] Hygon HygonGenuine
Centaur CentaurHauls [ +0.000000] zhaoxin Shanghai
x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map: [ +0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usab>
BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI
[ +0.000000] BIOS-e820: [mem 0x0000000000070000-0x0000000085fff] usab>
BIOS-e820: [mem 0x0000000000086000-0x000000009ffff]
rese> [ +0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000000200fffff]
rese> [ +0.000000] BIOS-e820: [mem 0x0000000078596000-0x0000000079295fff]
rese> [ +0.000000] BIOS-e820: [mem 0x0000000079296000-0x0000000079395fff]
ACPI NVS :...skipping...]
C
crazyhunterMN
09-13-2020, 05:11 PM #5

Here is a revised version of your text:

@elsandosgrande this is the output from `sudo dmesg --human`:
sudo dmesg --human [Nov20 20:43]
Microcode updated to revision 0x838, dated 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>
Kernel supported cpus: [ +0.000000] Intel GenuineIntel
AMD AuthenticAMD [ +0.000000] Hygon HygonGenuine
Centaur CentaurHauls [ +0.000000] zhaoxin Shanghai
x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map: [ +0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usable
BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI NVS
BIOS-e820: [mem 0x0000000070000000-0x0000000085fff] usable
BIOS-e820: [mem 0x0000000086000000-0x000000009ffff] reserved
BIOS-e820: [mem 0x0000000100000000-0x00000000200fffff] reserved
BIOS-e820: [mem 0x0000000078596000-0x0000000079295fff] usable
BIOS-e820: [mem 0x0000000020100000-0x0000000078595fff] reserved
BIOS-e820: [mem 0x0000000079296000-0x0000000079395fff] reserved
ACPI NVS :...skipping...

[Nov20 20:43]
Microcode updated early to revision 0x838, date > [ +0.000000] Linux version 5.4.0-54-generic (buildd@lcy01-amd64-024) (gc>
Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic roo>
KERNEL supported cpus: [ +0.000000] Intel GenuineIntel
AMD AuthenticAMD [ +0.000000] Hygon HygonGenuine
Centaur CentaurHauls [ +0.000000] zhaoxin Shanghai
x86/fpu: x87 FPU will use FXSAVE
BIOS-provided physical RAM map: [ +0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000006efff] usab>
BIOS-e820: [mem 0x000000000006f000-0x000000000006ffff] ACPI
[ +0.000000] BIOS-e820: [mem 0x0000000000070000-0x0000000085fff] usab>
BIOS-e820: [mem 0x0000000000086000-0x000000009ffff]
rese> [ +0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000000200fffff]
rese> [ +0.000000] BIOS-e820: [mem 0x0000000078596000-0x0000000079295fff]
rese> [ +0.000000] BIOS-e820: [mem 0x0000000079296000-0x0000000079395fff]
ACPI NVS :...skipping...]

R
ripa5000
Posting Freak
884
09-21-2020, 03:01 PM
#6
sudo dmesg --human requires being part of the input group. If not, press Shift+G to navigate the log. To locate entries for your touchpad, type a query in dmesg using Slash (Shift+7) and press Enter. Use N to jump to the next match and Shift+N for the previous one. For instance, searching for "touchpad" in the output will show relevant results. If you need details about your mouse or touchpad, let me know.
R
ripa5000
09-21-2020, 03:01 PM #6

sudo dmesg --human requires being part of the input group. If not, press Shift+G to navigate the log. To locate entries for your touchpad, type a query in dmesg using Slash (Shift+7) and press Enter. Use N to jump to the next match and Shift+N for the previous one. For instance, searching for "touchpad" in the output will show relevant results. If you need details about your mouse or touchpad, let me know.

I
IzADerpCookie
Member
228
09-28-2020, 03:05 PM
#7
Managed to run 'sudo libinput list-devices' successfully. Still learning Linux, but your notes are really useful. I didn’t use a code break, here’s what appeared: Device AT Translated Set 2 keyboard Kernel /dev/input/event3 Group 9 Seat seat0 default Capabilities Tap-to-click n/a Tap-and-drag n/a Tap drag lock n/a Left-handed n/a Scroll methods none Click methods none Disable-w-typing n/a Accel profiles none Rotation none 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 No scrolling, no middle emulation. Calibration not applied. Scroll methods: two-finger edge; click methods: *button-areas clickfinger Disable-w-typing enabled No accel profiles.
I
IzADerpCookie
09-28-2020, 03:05 PM #7

Managed to run 'sudo libinput list-devices' successfully. Still learning Linux, but your notes are really useful. I didn’t use a code break, here’s what appeared: Device AT Translated Set 2 keyboard Kernel /dev/input/event3 Group 9 Seat seat0 default Capabilities Tap-to-click n/a Tap-and-drag n/a Tap drag lock n/a Left-handed n/a Scroll methods none Click methods none Disable-w-typing n/a Accel profiles none Rotation none 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 No scrolling, no middle emulation. Calibration not applied. Scroll methods: two-finger edge; click methods: *button-areas clickfinger Disable-w-typing enabled No accel profiles.

K
Klitaurus
Member
69
09-30-2020, 04:27 AM
#8
They appear to be detected at least. Look for their device files in the kernel log—those listed after “Kernel:” should show up. After some online research, a potential fix is disabling ACPI (the third comment mentioned). This would be a last resort since ACPI is crucial. Before making changes, check what errors the kernel reports. Updated November 21, 2020 by elsandosgrande Added further details
K
Klitaurus
09-30-2020, 04:27 AM #8

They appear to be detected at least. Look for their device files in the kernel log—those listed after “Kernel:” should show up. After some online research, a potential fix is disabling ACPI (the third comment mentioned). This would be a last resort since ACPI is crucial. Before making changes, check what errors the kernel reports. Updated November 21, 2020 by elsandosgrande Added further details