Keyboard not working after initial boot

[TomTheDragon]

Hello there,

i am having the same problem on my Asus Zenbook UM325S and after quite a bit of researching this problem, i decided to finally reach out on this forum.
I already have tried many different kernels and boot parameters (atkbd.reset, i8042.nomux, i8042.reset, i8042.nopnp, i8042.dumbkbd,.. and any combination of those) but no matter what i do, i cant get the keyboard working at a cold boot.
Maybe there is a slight difference in my system, since its AMD based but the error message at boot ("Can't read CTR while initializing i8042") is exactly the same.
Oh and i am running Mint 21 now, but i already had the same problem on 20.3.
Any type of help or ideas what i else can try would be appreciated.

[deepakdeshp]

The error message may not be connected to kbd problem.
https://support.hpe.com/hpesc/public/do ... 41662en_us
Does kbd work with booting from live USB?

[SMG]

Oh and i am running Mint 21 now, but i already had the same problem on 20.3.

Welcome to the forum, TomTheDragon.

Is your system running the most recent BIOS/UEFI available for it?

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click Copy and paste the results into a reply window here so we can see how Linux Mint views your hardware.

[TomTheDragon]

The error message may not be connected to kbd problem.
https://support.hpe.com/hpesc/public/do ... 41662en_us
Does kbd work with booting from live USB?

I just gave a quick test and no it does not, this is true for 20.3, 20.3 edge and 21.
I also tried other Ubuntu 22.04 based distros as well as Fedora with no success.

Oh and i am running Mint 21 now, but i already had the same problem on 20.3.

Welcome to the forum, TomTheDragon.

Is your system running the most recent BIOS/UEFI available for it?

Please open the System Reports app and click the System Information tab on the left. Your computer's information should come up in the right pane. Then click Copy and paste the results into a reply window here so we can see how Linux Mint views your hardware.

Thanks for welcoming me to the forum and sorry about my initial mistake regarding my post.

Yes my device is running the latest bios version i can get (almost a year old now).

Here is the system report:

Code: Select all

System:
  Kernel: 5.18.15-051815-generic x86_64 bits: 64 compiler: N/A Desktop: Cinnamon 5.4.9
    tk: GTK 3.24.33 wm: Mutter dm: LightDM Distro: Linux Mint 21 Vanessa base: Ubuntu 22.04 jammy
Machine:
  Type: Laptop System: ASUSTeK product: ZenBook UX325SA_UM325SA v: 1.0
    serial: <superuser required>
  Mobo: ASUSTeK model: UX325SA v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: UX325SA.302 date: 11/09/2021
Battery:
  ID-1: BATT charge: 17.0 Wh (27.0%) condition: 62.9/67.1 Wh (93.7%) volts: 15.9 min: 15.9
    model: ASUSTeK UX325 serial: <filter> status: Discharging
CPU:
  Info: 8-core model: AMD Ryzen 7 5800U with Radeon Graphics bits: 64 type: MT MCP arch: Zen 3
    rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 16 MiB
  Speed (MHz): avg: 1392 high: 1597 min/max: 1600/4505 boost: enabled cores: 1: 1408 2: 1390
    3: 1330 4: 1328 5: 1330 6: 1330 7: 1597 8: 1596 9: 1330 10: 1330 11: 1331 12: 1330 13: 1476
    14: 1518 15: 1330 16: 1331 bogomips: 60680
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Cezanne vendor: ASUSTeK driver: amdgpu v: kernel pcie: speed: 8 GT/s lanes: 16
    ports: active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 04:00.0 chip-ID: 1002:1638
  Device-2: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo bus-ID: 1-3:2
    chip-ID: 13d3:56eb
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: amdgpu,ati
    unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96
  Monitor-1: eDP res: 1920x1080 dpi: 166 diag: 337mm (13.3")
  OpenGL: renderer: RENOIR (renoir LLVM 14.0.6 DRM 3.46 5.18.15-051815-generic)
    v: 4.6 Mesa 22.3.0-devel (git-00d8fce 2022-08-12 jammy-oibaf-ppa) direct render: Yes
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: ASUSTeK driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.1 chip-ID: 1002:1637
  Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor vendor: ASUSTeK
    driver: snd_rn_pci_acp3x v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 04:00.5
    chip-ID: 1022:15e2
  Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie:
    speed: 8 GT/s lanes: 16 bus-ID: 04:00.6 chip-ID: 1022:15e3
  Sound Server-1: ALSA v: k5.18.15-051815-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Intel Wireless 8265 / 8275 driver: iwlwifi v: kernel pcie: speed: 2.5 GT/s lanes: 1
    bus-ID: 01:00.0 chip-ID: 8086:24fd
  IF: wlp1s0 state: up mac: <filter>
  IF-ID-1: lxcbr0 state: down mac: <filter>
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb v: 0.8 bus-ID: 1-4:3
    chip-ID: 8087:0a2b
  Report: hciconfig ID: hci0 rfk-id: 1 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
Drives:
  Local Storage: total: 476.94 GiB used: 322.39 GiB (67.6%)
  ID-1: /dev/nvme0n1 vendor: SK Hynix model: HFM512GD3JX013N size: 476.94 GiB speed: 31.6 Gb/s
    lanes: 4 serial: <filter> temp: 25.9 C
Partition:
  ID-1: / size: 402.8 GiB used: 291.65 GiB (72.4%) fs: ext4 dev: /dev/nvme0n1p6
  ID-2: /boot/efi size: 96 MiB used: 43.9 MiB (45.8%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: partition size: 16 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme0n1p5
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Device-1: 1-3:2 info: IMC Networks USB2.0 HD UVC WebCam type: Video driver: uvcvideo rev: 2.0
    speed: 480 Mb/s chip-ID: 13d3:56eb
  Device-2: 1-4:3 info: Intel Bluetooth wireless interface type: Bluetooth driver: btusb
    rev: 2.0 speed: 12 Mb/s chip-ID: 8087:0a2b
  Hub-2: 2-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
  Hub-3: 3-0:1 info: Hi-speed hub with single TT ports: 4 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Hub-4: 4-0:1 info: Super-speed hub ports: 2 rev: 3.1 speed: 10 Gb/s chip-ID: 1d6b:0003
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A gpu: amdgpu temp: 34.0 C
  Fan Speeds (RPM): N/A
Repos:
  Packages: 3661 apt: 3571 flatpak: 90
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/appimagelauncher-team-stable-focal.list
    1: deb http: //ppa.launchpad.net/appimagelauncher-team/stable/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/cappelikan-ppa-jammy.list
    1: deb http: //ppa.launchpad.net/cappelikan/ppa/ubuntu jammy main
    2: deb-src http: //ppa.launchpad.net/cappelikan/ppa/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/kisak-kisak-mesa-focal.list
    1: deb http: //ppa.launchpad.net/kisak/kisak-mesa/ubuntu jammy main
    2: deb-src http: //ppa.launchpad.net/kisak/kisak-mesa/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/linrunner-tlp-focal.list
    1: deb http: //ppa.launchpad.net/linrunner/tlp/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb http: //linux-mint.froonix.org vanessa main upstream import backport
    2: deb http: //mirror.23media.com/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirror.23media.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirror.23media.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/official-source-repositories.list
    1: deb-src http: //linux-mint.froonix.org vanessa main upstream import backport
    2: deb-src http: //mirror.23media.com/ubuntu jammy main restricted universe multiverse
    3: deb-src http: //mirror.23media.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb-src http: //mirror.23media.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb-src http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/oibaf-graphics-drivers-focal.list
    1: deb http: //ppa.launchpad.net/oibaf/graphics-drivers/ubuntu jammy main
    2: deb-src http: //ppa.launchpad.net/oibaf/graphics-drivers/ubuntu jammy main
  Active apt repos in: /etc/apt/sources.list.d/samoilov-lex-retrogames-focal.list
    1: deb http: //ppa.launchpad.net/samoilov-lex/retrogames/ubuntu jammy main
  No active apt repos in: /etc/apt/sources.list.d/tuxinvader-lts-mainline-focal.list
Info:
  Processes: 374 Uptime: 4m Memory: 15.01 GiB used: 1.49 GiB (9.9%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.2.0 alt: 11/9 Client: Unknown python3.10 client inxi: 3.3.13

[SMG]

Here is the system report:

It's really better to try the available Canonical-maintained kernels before using mainline kernels. Linux Mint is not a "bleeding edge" distro.

Have you tried the 5.17-oem kernel? You can install it with sudo apt-get install linux-oem-22.04 and then you would have to boot to the grub menu and select Advanced Options so you can select it for booting (because you have a higher number kernel currently installed). Sometimes the OEM kernels have fixes other kernels do not have.

You may have seen this already, but in case not, here's quite a bit of info about what apparently is a common problem Keyboard not working after shutdown (ASUS Zenbook 13 OLED UM325S).

[petedecember]

I know this is an old post but I want to put my fix out there for others who cannot find a work-around:
If you are having trouble with your Asus Zenbook keyboard working after a cold boot make a change:

in /etc/default/grub

change

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.probe_defer"

I hope this helps someone!

[TomTheDragon]

Sorry for the late answer but i simply had no time to do the testing earlier.. but here is my response now.

You may have seen this already, but in case not, here's quite a bit of info about what apparently is a common problem Keyboard not working after shutdown (ASUS Zenbook 13 OLED UM325S).

I did search around quite a bit like i said earlier and i did also come across this thread before. I did also try quite a bit from the ideas in there but nothing seemed to work so far.
The most surprising part to me is that there is someone with the exact same laptop and he got it to work by adding i8042.reset i8042.nomux i8042.nopnp i8042.noloop as extra kernel parameters, he is also runnung Kubuntu 22.04 ..so it "should work", but it did not.
So i did do some more experiments and after braking my partition, fixing it again, installing Kubuntu (like that one person did) besides Mint, doing some more boot tests and so one.. i found out that there had to be something wrong with updating my Grub config.
I have been changing the file under /etc/defaults/grub in the past, because i needed to add some other kernel parameters, to get hibernation working and also for fixing the big power draw in standby. After examining the Grub config that came out of this, i was able to find my earlier additions but not the newest ones, in which i tried to fix the keyboard problems.
After searching all my system files, i found out that there was a second GRUB_CMDLINE_LINUX_DEFAULT line in the config, near the bottom of the file and it contained all my earlier changes.. i have no idea how that line got there, but it of course overwrote the changes i did in the line above..

So yeah, to make it short:
Just open /etc/defaults/grub and add i8042.reset i8042.nomux i8042.nopnp i8042.noloop to the GRUB_CMDLINE_LINUX_DEFAULT line and it will fix the keyboard problem after refreshing the Grub config.
But make sure that there is no second GRUB_CMDLINE_LINUX_DEFAULT line in that file, which could potentially overwrite your changes from above

It's really better to try the available Canonical-maintained kernels before using mainline kernels. Linux Mint is not a "bleeding edge" distro.

Have you tried the 5.17-oem kernel? You can install it with sudo apt-get install linux-oem-22.04 and then you would have to boot to the grub menu and select Advanced Options so you can select it for booting (because you have a higher number kernel currently installed). Sometimes the OEM kernels have fixes other kernels do not have.

I did not know that there are "more modern" kernels that are maintained by Canonical as well, thanks for that info, i am giving it a try right now

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.probe_defer"

This seems to work as well, i will go with this for now since its sorter, thanks for the tip

[hglee]

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.probe_defer"

This seems to work as well, i will go with this for now since its sorter, thanks for the tip

I've shared that info in another thread where an Asus VivoBook owner is experiencing a similar problem.

Anyone unfamiliar with modifying /etc/defaults/grub can use my simple copy-and-paste code to add the i8042.probe_defer kernel parameter. Two lines of code creates a date-stamped backup of the grub file, adds the kernel parameter, and then invokes update-grub. Removal code is also included.

As I mention in that other thread, a fix is expected in kernel 6.0 (aka kernel 5.20), at least for the VivoBook series.

[petedecember]

Well, I found another problem--
When you change

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.probe_defer"

in /etc/default/grub, the lighted touchpad number pad no longer works.

Does anyone have a fix for this? Maybe a bash file that runs the number pad installation?

Thanks in advance!

[hglee]

Does anyone have a fix for this? Maybe a bash file that runs the number pad installation?

Is that Asus "number pad installation" publicly documented?


My post in that other thread includes simple copy-and-paste (two lines of text) to safely remove that kernel parameter from the grub file.

[petedecember]

Thanks, Hglee, for getting back to me.

Here is the installation process for the touchpad number pad:

https://www.linuxuprising.com/2021/05/h ... -into.html

I am able to remove the kernel parameter using root access to the 'grub' file and editing with the Text Editor.

[TomTheDragon]

When you change

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash i8042.probe_defer"

in /etc/default/grub, the lighted touchpad number pad no longer works.

Does anyone have a fix for this? Maybe a bash file that runs the number pad installation?

I dont have that problem on my system, the number pad works fine.
This is the full entry in my grub config:
GRUB_CMDLINE_LINUX_DEFAULT="i8042.probe_defer mem_sleep_default=deep resume=UUID=[SWAPUUIDHERE]"

This is the driver i used to get the number pad working really early on, when i was still on Mint 20.3
https://github.com/mohamed-badaoui/asus ... pad-driver

[petedecember]

Thanks for the reply, TomTheDragon--

I tried both your line in my grub file and the driver you use for the number pad, to not avail.

I did notice that I can turn on the numberpad by pressing the upper right hand corner while waiting for the login page to appear. If I leave the number pad on the touchpad until after the login page appears, then it just stays on the touchpad but doesn't function as a numberpad. It just acts like the touchpad.

Any other thoughts?

Thanks in advance!

[SMG]

Any other thoughts?

ASUS Zenbook encompasses a lot of models. I do not see where you listed what you have. One should not necessarily assume they will all respond the same way just because they are Zenbooks.

[petedecember]

You're right, SMG--
my model is ASUS ZenBook UM425Q. It is a Ryzen 9, 16gb and a 1tb SSD with Radeon graphics running LM 21 with Cinnamon 5.4.12.

[hglee]

HyGlee, I think that you might be a bit confused as to which thread is which....

Oops, misplaced edit. Fixed it. Has the script you requested, back now.

Thanks.

EDIT: Grrr, SMG deleted my corrected post.

[hglee]

This is the driver i used to get the number pad working really early on, when i was still on Mint 20.3
https://github.com/mohamed-badaoui/asus ... pad-driver

That's the same github page referred to by logix, author of the LinuxUprising article linked above by petedecember. Same code. The only difference is that the github page includes instructions on how to run the Python code for a touchpad "logger". The code is sparsely commented but, after a skim of it, I'm thinking it was used by the original patch coder for debugging purposes. This typically isn't needed by the end-user, and logix doesn't even mention it.

The original patch, written in Python, was posted on reddit (source code on gitlab) in early 2020 by someone with the handle Globibluk. In the LinuxUprising article, logix links to mohamed-badaoui's github page per the Terminal step-by-step.


Here's the Terminal process to install the patch, written as a Bash script file. It installs the necessary software from the Mint repository, then downloads (into your ~/Downloads folder) and runs the github patch code:

Code: Select all

#!/bin/bash
sudo apt install libevdev2 python3-libevdev i2c-tools git
sudo modprobe i2c-dev
sudo i2cdetect -l
cd $HOME/Downloads
git clone https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver
cd asus-touchpad-numpad-driver
chmod +x ./install.sh
sudo ./install.sh
exit
#

Let's say you save that code in a text file named pasus_on, then to make it executable (runnable) you do chmod +x pasus_on. Then run ./pasus_on


Here's the Terminal process to uninstall the patch, written as a Bash script file. It downloads and runs the necessary github code:

Code: Select all

#!/bin/bash
cd $HOME/Downloads
git clone https://github.com/mohamed-badaoui/asus-touchpad-numpad-driver
cd asus-touchpad-numpad-driver
chmod +x ./uninstall.sh
sudo ./uninstall.sh
exit
#

Let's say you save that code in a text file named pasus_off, then to make it executable you do chmod +x pasus_off. Then run ./pasus_off

These scripts don't "clean up" after running, so the folder created by the github code (asus-touchpad-numpad-driver in your ~/Downloads) remains. To remove that folder: rm -rf ~/Downloads/asus-touchpad-numpad-driver/


I don't have an Asus to test, so all I can do is duplicate the Terminal steps posted by logix & mohamed-badaoui, and read Globibluk's Python source code.

In the installation code, I can see that it will prompt for "Select models keypad layout:" and will accept one of five responses: gx701, m433ia, ux433fa, ux581l, or Q to quit. It also asks if you have a Qwerty or Azerty keyboard layout.

[hglee]

I dont have that problem on my system, the number pad works fine.
This is the full entry in my grub config:
GRUB_CMDLINE_LINUX_DEFAULT="i8042.probe_defer mem_sleep_default=deep resume=UUID=[SWAPUUIDHERE]"

About that resume=UUID=[SWAPUUIDHERE] kernel parameter, do you still have a link to the info source?

The SWAPUUIDHERE part looks like a "Swap UUID Here" placeholder which should have been replaced by some actual UUID value.

That surely effects its ability to do the intended function.


Edit: Indeed.

[SMG]

my model is ASUS ZenBook UM425Q. It is a Ryzen 9, 16gb and a 1tb SSD with Radeon graphics running LM 21 with Cinnamon 5.4.12.

The person in this topic Asus UM425Q keyboard problems/numberpad [solved] was able to get it working in Neptune Linux which is based on Debian Bullseye (same base as LMDE5). Maybe the keyboard config they loaded made the difference although they said it was not needed.

[petedecember]

Thanks for the idea, SMG-
I put together and tried the .conf file and it didn't do anything.
Any other thoughts?
Thanks in advance.