Keyboard blocked with kernel 4.19

I am using Manjaro 18 with XFCE.
With every available kernel versions, I am stuck at the connexion screen with a non-working keyboard. It has worked with 4.14, 4.17, 4.18 and 4.19rc. Now I should use 4.18.16-1 rather than 4.18.16-2
I would like to be able to make the next updates, how to fix this ?

$ inxi -Fxxxz

System:
  Host: samspade Kernel: 4.18.16-1-MANJARO x86_64 bits: 64 compiler: gcc 
  v: 8.2.1 Desktop: N/A wm: xfwm4 dm: LightDM 1.28.0 Distro: Manjaro Linux 
Machine:
  Type: Desktop Mobo: ASUSTeK model: P5QL PRO v: Rev 1.xx serial: <filter> 
  BIOS: American Megatrends v: 0902 date: 11/28/2008 
CPU:
  Topology: Quad Core model: Intel Core2 Quad Q9550 bits: 64 type: MCP 
  arch: Penryn rev: A L2 cache: 6144 KiB 
  flags: lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx bogomips: 22654 
  Speed: 2326 MHz min/max: 2003/2833 MHz Core speeds (MHz): 1: 2326 2: 2305 
  3: 1999 4: 2019 
Graphics:
  Device-1: NVIDIA G96 [GeForce 9500 GT] driver: nouveau v: kernel 
  bus ID: 01:00.0 chip ID: 10de:0640 
  Display: x11 server: X.Org 1.20.3 driver: nouveau unloaded: modesetting 
  alternate: fbdev,nv,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: NV96 v: 3.3 Mesa 18.2.4 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel 82801JI HD Audio vendor: ASUSTeK driver: snd_hda_intel 
  v: kernel bus ID: 00:1b.0 chip ID: 8086:3a3e 
  Sound Server: ALSA v: k4.18.16-1-MANJARO 
Network:
  Device-1: Qualcomm Atheros AR8121/AR8113/AR8114 Gigabit or Fast Ethernet 
  vendor: ASUSTeK P5KPL-CM driver: ATL1E v: N/A port: dc00 bus ID: 02:00.0 
  chip ID: 1969:1026 
  IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: <filter> 
  Device-2: Qualcomm Atheros AR9287 Wireless Network Adapter driver: ath9k 
  v: kernel port: e400 bus ID: 04:00.0 chip ID: 168c:002e 
  IF: wlp4s0 state: down mac: <filter> 
Drives:
  Local Storage: total: 9.32 TiB used: 6.66 TiB (71.5%) 
  ID-1: /dev/sda vendor: Samsung model: SSD 850 EVO 250GB size: 232.89 GiB 
  speed: 3.0 Gb/s serial: <filter> rev: 1B6Q scheme: GPT 
  ID-2: /dev/sdb vendor: Toshiba model: HDWE160 size: 5.46 TiB 
  speed: 3.0 Gb/s rotation: 7200 rpm serial: <filter> rev: FS2A scheme: GPT 
  ID-3: /dev/sdg vendor: Western Digital model: WD40EZRZ-00WN9B0 
  size: 3.64 TiB speed: 3.0 Gb/s rotation: 5400 rpm serial: <filter> 
  rev: 0A80 scheme: GPT 
Partition:
  ID-1: / size: 19.56 GiB used: 16.74 GiB (85.6%) fs: ext4 dev: /dev/sda5 
  ID-2: /home size: 999.7 MiB used: 204.0 MiB (20.4%) fs: ext3 
  dev: /dev/sda4 
  ID-3: swap-1 size: 10.00 GiB used: 112.5 MiB (1.1%) fs: swap 
  dev: /dev/sdb2 
Sensors:
  System Temperatures: cpu: 50.0 C mobo: N/A gpu: nouveau temp: 62 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0 
Info:
  Processes: 241 Uptime: 18h 32m Memory: 7.79 GiB used: 2.19 GiB (28.1%) 
  Init: systemd v: 239 Compilers: gcc: 8.2.1 Shell: bash v: 4.4.23 
  running in: xfce4-terminal inxi: 3.0.27 

Is it a PS/2 keyboard. USB, Bluetooth.

Also, you may like to check the output of things like xinput on each kernel and compare

Also also, an update to the BIOS is a good idea: https://www.asus.com/Motherboards/P5QL_PRO/HelpDesk_Download/ (you have v: 0902 and v: 1004 is available)

1 Like

If you can boot with another kernel well, you may check the previous boot journal log for relative info. You should check for errors and if nothing found, check for Keyboard or udev related messages.

journalctl -b -1 -p3
journalctl -b -1 -g keyboard
journalctl -b -1 -g udev
journalctl -b -1 -g found

You can also check from chroot, or just mounting the root partition and inspect journal

journalctl -D /mnt/var/log/journal -b -p 3
...etc...
1 Like

It is a USB keyboard

Please post the input/outputs of all requested commands.

Information on how to post hardware specs and logs on the forum:

I updated the BIOS a long time ago to v1004 and I noticed that ethernet connector was not recognized anymore under linux so I downgraded back to v902. Since that time I never had any problem with keyboard under linux, so it is not the first thing I thought about to fix it. Though I can try to re-update, but I abandoned real Windows.
Can I update asus BIOS through VirtualBox or is there a linux tool to achieve that ?

kernel v4.18:

$ xinput
|⎡ Virtual core pointer                    |id=2|[master pointer  (3)]|
|---|---|---|
|⎜   ↳ Virtual core XTEST pointer              |id=4|[slave  pointer  (2)]|
|⎜   ↳ USB OPTICAL MOUSE                       |id=9|[slave  pointer  (2)]|
|⎜   ↳ HID 04f3:0103 Consumer Control          |id=11|[slave  pointer  (2)]|
|⎣ Virtual core keyboard                   |id=3|[master keyboard (2)]|
|    ↳ Virtual core XTEST keyboard             |id=5|[slave  keyboard (3)]|
|    ↳ Power Button                            |id=6|[slave  keyboard (3)]|
|    ↳ Power Button                            |id=7|[slave  keyboard (3)]|
|    ↳ Wacom Volito2 4x5 Pen                   |id=8|[slave  keyboard (3)]|
|    ↳ HID 04f3:0103                           |id=10|[slave  keyboard (3)]|
|    ↳ HID 04f3:0103 System Control            |id=12|[slave  keyboard (3)]|
|    ↳ HID 04f3:0103 Consumer Control          |id=13|[slave  keyboard (3)]|

kernel v4.19:

$ xinput
|⎡ Virtual core pointer                    |id=2|[master pointer  (3)]|
|---|---|---|
|⎜   ↳ Virtual core XTEST pointer              |id=4|[slave  pointer  (2)]|
|⎜   ↳ USB OPTICAL MOUSE                       |id=9|[slave  pointer  (2)]|
|⎣ Virtual core keyboard                   |id=3|[master keyboard (2)]|
|    ↳ Virtual core XTEST keyboard             |id=5|[slave  keyboard (3)]|
|    ↳ Power Button                            |id=6|[slave  keyboard (3)]|
|    ↳ Power Button                            |id=7|[slave  keyboard (3)]|
|    ↳ Wacom Volito2 4x5 Pen                   |id=8|[slave  keyboard (3)]|

So I booted under v4.19 then back to v4.18 and I run the following commands:

$ journalctl -b -1 -p3
-- Logs begin at Fri 2018-07-27 17:18:12 CEST, end at Fri 2018-11-16 18:01:01 CET. --
nov. 16 17:40:35 samspade kernel: watchdog: watchdog0: watchdog did not stop!
$ journalctl -b -1 -g keyboard
-- Logs begin at Fri 2018-07-27 17:18:12 CEST, end at Fri 2018-11-16 18:01:01 CET. --
nov. 16 17:38:40 samspade kernel: audit: type=1130 audit(1542386320.687:9): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=keyboardctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade kernel: audit: type=1131 audit(1542386320.687:10): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=keyboardctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=keyboardctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=keyboardctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade systemd[1]: Started Setup keyboard layout.
nov. 16 17:38:41 samspade systemd[1]: Starting Setup keyboard layout...
nov. 16 17:38:41 samspade systemd[1]: Started Setup keyboard layout.
nov. 16 17:38:41 samspade audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=keyboardctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:41 samspade audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=keyboardctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
$ journalctl -b -1 -g udev
-- Logs begin at Fri 2018-07-27 17:18:12 CEST, end at Fri 2018-11-16 18:01:01 CET. --
nov. 16 17:38:40 samspade systemd[1]: Listening on udev Kernel Socket.
nov. 16 17:38:40 samspade kernel: audit: type=1130 audit(1542386320.677:8): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udev-trigger comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-udevd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
nov. 16 17:38:40 samspade systemd[1]: Started udev Coldplug all Devices.
nov. 16 17:38:40 samspade systemd[1]: Started udev Kernel Device Manager.
$ journalctl -b -1 -g found
-- Logs begin at Fri 2018-07-27 17:18:12 CEST, end at Fri 2018-11-16 18:01:01 CET. --
nov. 16 17:38:40 samspade kernel: Found optimal setting for mtrr clean up
nov. 16 17:38:40 samspade kernel: found SMP MP-table at [mem 0x000ff780-0x000ff78f] mapped at [(____ptrval____)]
nov. 16 17:38:40 samspade kernel: No NUMA configuration found
nov. 16 17:38:40 samspade kernel: acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
nov. 16 17:38:40 samspade kernel: pnp: PnP ACPI: found 9 devices
nov. 16 17:38:40 samspade kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
nov. 16 17:38:40 samspade kernel: x86/mm: Checked W+X mappings: passed, no W+X pages found.
nov. 16 17:38:40 samspade kernel: usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 1-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 2-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb3: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 3-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb4: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 4-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb5: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 5-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb6: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 6-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb7: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 7-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb usb8: New USB device found, idVendor=1d6b, idProduct=0001, bcdDevice= 4.19
nov. 16 17:38:40 samspade kernel: hub 8-0:1.0: USB hub found
nov. 16 17:38:40 samspade kernel: usb 1-1: New USB device found, idVendor=058f, idProduct=6364, bcdDevice= 1.00
nov. 16 17:38:40 samspade kernel: usb 7-1: New USB device found, idVendor=056a, idProduct=0062, bcdDevice= 2.00
nov. 16 17:38:40 samspade kernel: usb 7-2: New USB device found, idVendor=275d, idProduct=0ba6, bcdDevice= 1.00
nov. 16 17:38:40 samspade kernel: usb 8-2: New USB device found, idVendor=04f3, idProduct=0103, bcdDevice= 1.07
nov. 16 17:38:40 samspade kernel: PM: Image not found (code -22)
nov. 16 17:38:40 samspade kernel: vboxdrv: Found 4 processor cores
nov. 16 17:38:40 samspade kernel: vboxpci: IOMMU not found (not registered)
nov. 16 17:38:41 samspade systemd[1]: Found device Samsung_SSD_850_EVO_250GB Ubuntu.
nov. 16 17:38:41 samspade systemd[1]: Found device Samsung_SSD_850_EVO_250GB home.
nov. 16 17:38:41 samspade systemd[1]: Found device Samsung_SSD_850_EVO_250GB Home.
nov. 16 17:38:41 samspade systemd[1]: Found device WDC_WD40EZRZ-00WN9B0 Video.
nov. 16 17:38:41 samspade systemd[1]: Found device Samsung_SSD_850_EVO_250GB VBMachines.
nov. 16 17:38:41 samspade systemd[1]: Found device TOSHIBA_HDWE160 LinSwap.
nov. 16 17:38:41 samspade systemd[1]: Found device TOSHIBA_HDWE160 BackupC.
nov. 16 17:38:41 samspade systemd[1]: Found device WDC_WD40EZRZ-00WN9B0 Photos.
nov. 16 17:38:41 samspade systemd[1]: Found device WDC_WD40EZRZ-00WN9B0 GrosFichiers.
nov. 16 17:38:41 samspade systemd[1]: Found device TOSHIBA_HDWE160 BackupJ.
nov. 16 17:38:41 samspade systemd[1]: Found device TOSHIBA_HDWE160 Partage.
nov. 16 17:38:41 samspade systemd[1]: Found device WDC_WD40EZRZ-00WN9B0 Audio.
nov. 16 17:38:41 samspade kernel: iTCO_wdt: Found a ICH10 TCO device (Version=2, TCOBASE=0x0860)
nov. 16 17:38:41 samspade kernel: nouveau 0000:01:00.0: bios: M0203T not found
nov. 16 17:38:49 samspade avahi-daemon[632]: Found user 'avahi' (UID 993) and group 'avahi' (GID 993).
nov. 16 17:38:49 samspade avahi-daemon[632]: No service file found in /etc/avahi/services.
nov. 16 17:38:49 samspade NetworkManager[631]: <info>  [1542386329.8686] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:04:00.0/ieee80211/phy0/rfkill0) (driver ath9k)
nov. 16 17:40:14 samspade python[1368]: backintime (sspadem/1): WARNING: Command "rsync -rtDHh --links --no-p --no-g --no-o --info=progress2 --no-i-r  --delete --delete-excluded  -i --dry-run --out-format="BACKINTIME: %i %n%L" --chmod=Du+wx  --exclude="/mnt/BackupC" --exclude="/home/sspadem/.local/share/backintime" --exclude=".local/share/backintime/mnt" --include="/Home/sspade/Codes/" --include="/Home/sspade/" --include="/Home/" --include="/Home/sspade/Doc/" --include="/Home/sspade/Scripts/" --include="/mnt/Photos/" --include="/mnt/" --include="/mnt/Audio/" --include="/mnt/GrosFichiers/TV/" --include="/mnt/GrosFichiers/" --include="/mnt/GrosFichiers/Films/Pourquoi Israel/" --include="/mnt/GrosFichiers/Films/" --include="/Home/sspade/amsn/" --include="/Home/sspade/Bibliothèque calibre/" --include="/home/sspadeu18/" --include="/home/" --exclude="*[tT]humb*" --exclude="*[tT][eE]?[mM][pP]*" --exclude="*[cC]ache*" --exclude="*lost+found*" --exclude=".gvfs" --exclude="System Volume Information"

The today update of kernel 4.19 (4.19.2-1) did not fix the problem

Hello petsam,
the returns of the commands you asked for did not help to troubleshoot ?

Hello cscs,
the returns of the command xinput you asked for did not help to troubleshoot ?

NO, from Virtual environment you can’t write BIOS onto the host.
Asus has the tool EzFlash AFAIK, you find it in BIOS settings …

If you unplug and plug back in the Keyboard, does work? Have you tried a different USB port? Usually on that MB, for keyboard and mouse you should use the top 2 USB ports, right under the PS2 ports.

It shows that kernel 4.19 doesn’t detect the devices correctly as the 4.18 kernel does. Try the above mentioned workarounds.

Actually I forgot to check…
Anyways you can always use your working kernels, you can update your system with no problems for several years.
Nevertheless post lsusb

1 Like

Yes I tried to:
-unplug and plug the keyboard on other USB ports
-plug keyboard and mouse to the USB ports under the PS2 ports
Result is the same.
I should add that the keyboard is active under GRUB and I can use it to choose a different boot option, edit them, etc.
Do you know a linux tool to update BIOS ?

Many Asus BIOS can simply be flashed by putting the BIOS file on a USB stick (fat32), and choosing the option to update BIOS in the BIOS itself.

You can just as well stay on 4.14 if that one works for you.

1 Like

The problem is not urgent but that means that, even if I can update all other packages, I am stuck with an not up-to-date 4.18 kernel ?
It is not satisfying and not reassuring about my future with Manjaro. The version I use is even not in the repo anymore. Despite I blocked the update of v4.18, imagine that it is still updated for some reason and then Manjaro suddenly becomes unusable for me.
Moreover, the problem is the same with versions from 4.9 to 4.19 under Manjaro but there is no problem with Ubuntu and last “usual” available kernel v4.15. I noticed that the Manjaro problem is with recent minor kernel updates, but not with major ones.

Under 4.18 as well as under 4.19, “lsusb” returns the same results and sees the keyboard:

$ lsusb
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 003: ID 275d:0ba6  
Bus 008 Device 002: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 002: ID 056a:0062 Wacom Co., Ltd CTF-420 [Volito2]
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 058f:6364 Alcor Micro Corp. AU6477 Card Reader Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

4.18 will be EOL soon.
4.14 will be supported for at least another year.

4.19 is very new.

I would just stay with 4.14 for another few months and then see again whether there’s an improvement in subsequent versions of 4.19+.

Unfortunately, I have no idea why your keyboard doesn’t work. Except maybe checking various BIOS settings.
Or get a PS/2-USB adapter and try with that.

1 Like

Unfortunately the very last version of 4.14 does not work anymore for me. It definitely worked with most of previous 4.14 minor versions, so I will downgrade it to try to get one working version.
The way working kernels are replaced with not working versions of them in the repo is strange and not very safe. I understand why there are 6 major versions available in the repo, but it is not useful at all if they are all updated, and moreover at the same time.
Anyway, one year of support for 4.14 is not much. 4.19 version worked too in their RC flavours and then stopped with the final release. At the time of the 4.19 release, the keyboard stopped to work with every version.
I will try the PS2 adapter and the BIOS tracks.
Thank for your help

Since it is recognized, there shoul be some point that this breaks, hopefully with a message in a log…
Have you tried if it works in TTY?
Either using another keyboard to switch, or booting straight to TTY editing grub menu.

That’s not how things work.
Minor updates are released almost every week by the kernel developers, and almost immediately updated by Manjaro and also Arch.

Also, you can’t just say that because it doesn’t work for you, that it is a “non-working” version for everyone.

Would be good if you could find out what the last working version was, and then have a look at the kernel changelog to see what was patched.

EDIT: can we have a complete dmesg log from the non-working kernel please?

2 Likes