Asus laptop: random keyboard problem

Need help with peripherals or devices?
Post Reply
Message
Author
mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Asus laptop: random keyboard problem

#1 Post by mazda1 »

I have an Asus Vivobook X1704VA laptop: my keyboard locks up randomly. At first I thought the problem might be with the xserver-xorg-input-libinput driver. But a few days ago, I found a topic on this forum describing a problem with an Asus Vivobook X1704VAP that looks a lot like mine: viewtopic.php?p=808370.. It pointed to bug #1078696: https://lists.debian.org/debian-kernel/ ... 00202.html. The proposed solution is as follows:
Add the X1704VAP to the irq1_level_low_skip_override[] quirk table to fix this.
I checked the change log for kernel 6.1.0.27 and I found this:

Code: Select all

$ apt changelog linux-image-6.1.0-27-amd64 | grep -i -A 1 'vivobook X1704'
     - ACPI: resource: Add Asus Vivobook X1704VAP to
      irq1_level_low_skip_override[] (Closes: #1078696)
Apparently, for an Asus Vivobook X1704VAP, this problem was solved as of kernel 6.1.0.27, But nothing on my X1704VA laptop. Nevertheless, I thought this problem could be solved for mine too, so I deleted the i8042.dumbkbd=1 option, which seemed to be effective. But this morning I had exactly the same problem: my keyboard froze again.

After rebooting, I checked a log that seems relevant (I'm not very sure):

Code: Select all

/var/log# less Xorg.0.log.old | grep keyboard | tail -n 5
[     9.195] (**) Logitech Wireless Mouse: Applying InputClass "libinput keyboard catchall"
[     9.196] (II) event15 - Logitech Wireless Mouse: device is a keyboard
[     9.237] (II) event15 - Logitech Wireless Mouse: device is a keyboard
[     9.238] (**) Logitech Wireless Mouse: Applying InputClass "libinput keyboard catchall"
[ 39105.554] (II) event0  - AT Translated Set 2 keyboard: device removed
How do I add my X1704VA laptop to the irq1_level_low_skip_override[] table? I don't even know what a “quirk table” is and where to find it. If I have to recompile the kernel, I give up right away. Or should
I report a bug for my laptop?
Debian 12

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#2 Post by Aki »

Hello,
mazda1 wrote: 2024-12-02 10:27 I have an Asus Vivobook X1704VA laptop: my keyboard locks up randomly. At first I thought the problem might be with the xserver-xorg-input-libinput driver. But a few days ago, I found a topic on this forum describing a problem with an Asus Vivobook X1704VAP that looks a lot like mine: viewtopic.php?p=808370.. It pointed to bug #1078696: https://lists.debian.org/debian-kernel/ ... 00202.html.
[..]
You are reporting a "random keyboard lock", while the OP of the referenced discussion reported his/her keyboard was not working at all.

So, yours is probably a different issue.

It may be a firmware/hardware malfunction.

You may analyze or share system logs for other clues.
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#3 Post by mazda1 »

Aki wrote: 2024-12-06 09:40 .........
You are reporting a "random keyboard lock", while the OP of the referenced discussion reported his/her keyboard was not working at all.

So, yours is probably a different issue.

It may be a firmware/hardware malfunction.

You may analyze or share system logs for other clues.
Hello,

I thought that the two laptops might have the same problem because in the first message there is this link: https://lore.kernel.org/linux-acpi/2024 ... edhat.com/, which says this:
Like other Asus Vivobook models the X1704VAP has its keybopard IRQ (1)
described as ActiveLow in the DSDT, which the kernel overrides to EdgeHigh
which breaks the keyboard.

Add the X1704VAP to the irq1_level_low_skip_override[] quirk table to fix
this.
I interpreted that as "all the Asus Vivobook model have the same problem and the fix is...".

I've just had the same problem. Fortunately, some keys still work when this happens, the on/off key is one of them and I can shut down my laptop properly.

Here are some logs concerning this problem:

Code: Select all

# journalctl -S '2024-12-08 12:58:00' -U '2024-12-08 13:03:10'
déc. 08 13:00:22 asus dbus-daemon[1183]: [session uid=1000 pid=1183] Activating service n>
déc. 08 13:00:22 asus dbus-daemon[1183]: [session uid=1000 pid=1183] Successfully activat>
déc. 08 13:00:37 asus dbus-daemon[883]: [system] Activating via systemd: service name='or>
déc. 08 13:00:37 asus systemd[1]: Starting systemd-hostnamed.service - Hostname Service...
déc. 08 13:00:37 asus dbus-daemon[883]: [system] Successfully activated service 'org.free>
déc. 08 13:00:37 asus systemd[1]: Started systemd-hostnamed.service - Hostname Service.
déc. 08 13:01:08 asus systemd[1]: systemd-hostnamed.service: Deactivated successfully.
déc. 08 13:02:03 asus systemd-logind[900]: Power key pressed short.
déc. 08 13:02:03 asus systemd-logind[900]: The system will power off now!
déc. 08 13:02:03 asus systemd-logind[900]: System is powering down.
déc. 08 13:02:03 asus systemd[1]: Stopping session-1.scope - Session 1 of User mmas...
déc. 08 13:02:03 asus polkitd[896]: Unregistered Authentication Agent for unix-session:1 >
déc. 08 13:02:03 asus systemd[1]: Removed slice system-modprobe.slice - Slice /system/mod>
déc. 08 13:02:03 asus at-spi-bus-launcher[1276]: X connection to :0 broken (explicit kill>
déc. 08 13:02:03 asus ModemManager[968]: <info>  caught signal, shutting down...
déc. 08 13:02:03 asus systemd[1]: Stopped target bluetooth.target - Bluetooth Support.
déc. 08 13:02:03 asus lightdm[1140]: pam_unix(lightdm-autologin:session): session closed >
déc. 08 13:02:03 asus systemd[1]: Stopped target graphical.target - Graphical Interface.
déc. 08 13:02:03 asus ModemManager[968]: <info>  ModemManager is shut down

Code: Select all

/var/log# less  Xorg.0.log.old | grep -i keyboard
[     5.853] (II) Initializing extension XKEYBOARD
[     5.938] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     5.946] (II) event3  - Power Button: is tagged by udev as: Keyboard
[     5.946] (II) event3  - Power Button: device is a keyboard
[     5.980] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[     6.003] (II) event3  - Power Button: is tagged by udev as: Keyboard
[     6.003] (II) event3  - Power Button: device is a keyboard
[     6.004] (**) Video Bus: Applying InputClass "libinput keyboard catchall"
[     6.005] (II) event4  - Video Bus: is tagged by udev as: Keyboard
[     6.005] (II) event4  - Video Bus: device is a keyboard
[     6.068] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[     6.069] (II) event4  - Video Bus: is tagged by udev as: Keyboard
[     6.069] (II) event4  - Video Bus: device is a keyboard
[     6.070] (**) Power Button: Applying InputClass "libinput keyboard catchall"
[     6.071] (II) event2  - Power Button: is tagged by udev as: Keyboard
[     6.071] (II) event2  - Power Button: device is a keyboard
[     6.100] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
[     6.101] (II) event2  - Power Button: is tagged by udev as: Keyboard
[     6.101] (II) event2  - Power Button: device is a keyboard
[     6.103] (**) USB2.0 HD UVC WebCam: USB2.0 HD: Applying InputClass "libinput keyboard catchall"
[     6.104] (II) event8  - USB2.0 HD UVC WebCam: USB2.0 HD: is tagged by udev as: Keyboard
[     6.104] (II) event8  - USB2.0 HD UVC WebCam: USB2.0 HD: device is a keyboard
[     6.204] (II) XINPUT: Adding extended input device "USB2.0 HD UVC WebCam: USB2.0 HD" (type: KEYBOARD, id 9)
[     6.205] (II) event8  - USB2.0 HD UVC WebCam: USB2.0 HD: is tagged by udev as: Keyboard
[     6.205] (II) event8  - USB2.0 HD UVC WebCam: USB2.0 HD: device is a keyboard
[     6.209] (**) Asus WMI hotkeys: Applying InputClass "libinput keyboard catchall"
[     6.210] (II) event6  - Asus WMI hotkeys: is tagged by udev as: Keyboard
[     6.210] (II) event6  - Asus WMI hotkeys: device is a keyboard
[     6.312] (II) XINPUT: Adding extended input device "Asus WMI hotkeys" (type: KEYBOARD, id 10)
[     6.313] (II) event6  - Asus WMI hotkeys: is tagged by udev as: Keyboard
[     6.313] (II) event6  - Asus WMI hotkeys: device is a keyboard
[     6.313] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[     6.313] (**) AT Translated Set 2 keyboard: Applying InputClass "libinput keyboard catchall"
[     6.314] (II) Using input driver 'libinput' for 'AT Translated Set 2 keyboard'
[     6.314] (**) AT Translated Set 2 keyboard: always reports core events
[     6.315] (II) event0  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[     6.315] (II) event0  - AT Translated Set 2 keyboard: device is a keyboard
[     6.315] (II) event0  - AT Translated Set 2 keyboard: device removed
[     6.344] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 11)
[     6.345] (II) event0  - AT Translated Set 2 keyboard: is tagged by udev as: Keyboard
[     6.345] (II) event0  - AT Translated Set 2 keyboard: device is a keyboard
[     9.383] (**) Logitech Wireless Mouse: Applying InputClass "libinput keyboard catchall"
[     9.384] (II) event10 - Logitech Wireless Mouse: is tagged by udev as: Keyboard Mouse
[     9.384] (II) event10 - Logitech Wireless Mouse: device is a keyboard
[     9.433] (II) event10 - Logitech Wireless Mouse: is tagged by udev as: Keyboard Mouse
[     9.433] (II) event10 - Logitech Wireless Mouse: device is a keyboard
[     9.434] (**) Logitech Wireless Mouse: Applying InputClass "libinput keyboard catchall"
[     9.434] (II) XINPUT: Adding extended input device "Logitech Wireless Mouse" (type: KEYBOARD, id 15)
[ 63708.924] (II) event0  - AT Translated Set 2 keyboard: device removed
Are there other logs which might be relevant to this problem?

PS1: until I find a solution I will add "i8042.dumbkbd=1" option that seemed to work.
PS2: 2024/12/17 ; 9 problem-free days with this option. Fingers crossed. ----> it didn't last very long, but for the first time I was able to get my keyboard working again: open tty2 as root and restart lightdm.
Last edited by mazda1 on 2024-12-17 14:27, edited 2 times in total.
Debian 12

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#4 Post by Aki »

Hello,

What is the output of the dmidecode command for your computer ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#5 Post by mazda1 »

Aki wrote: 2024-12-11 15:07 Hello,

What is the output of the dmidecode command for your computer ?

Code: Select all

# dmidecode
# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.5.0 present.
Table at 0x7238D000.

Handle 0x0000, DMI type 0, 26 bytes
BIOS Information
	Vendor: American Megatrends International, LLC.
	Version: X1704VA.303
	Release Date: 03/13/2024
	Address: 0xF0000
	Runtime Size: 64 kB
	ROM Size: 32 MB
	Characteristics:
		PCI is supported
		BIOS is upgradeable
		BIOS shadowing is allowed
		Boot from CD is supported
		Selectable boot is supported
		BIOS ROM is socketed
		EDD is supported
		ACPI is supported
		Smart battery is supported
		BIOS boot specification is supported
		Targeted content distribution is supported
		UEFI is supported
	BIOS Revision: 5.27

Handle 0x0001, DMI type 1, 27 bytes
System Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: Vivobook_ASUSLaptop X1704VA_X1704VA
	Version: 1.0       
	Serial Number: S5N0CV10J64421A
	UUID: 8fa67068-67b7-164a-9269-e82488fcbfcb
	Wake-up Type: Power Switch
	SKU Number:  
	Family: Vivobook

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: X1704VA
	Version: 1.0       
	Serial Number: S519NBCV008SANMB
	Asset Tag: ATN12345678901234567
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: MIDDLE              
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

Handle 0x0003, DMI type 3, 22 bytes
Chassis Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Type: Notebook
	Lock: Not Present
	Version: 1.0       
	Serial Number: S5N0CV10J64421A
	Asset Tag: No Asset Tag
	Boot-up State: Safe
	Power Supply State: Safe
	Thermal State: Safe
	Security Status: None
	OEM Information: 0x00000000
	Height: Unspecified
	Number Of Power Cords: 1
	Contained Elements: 0
	SKU Number: NA

Handle 0x0007, DMI type 13, 22 bytes
BIOS Language Information
	Language Description Format: Long
	Installable Languages: 1
		Default string
	Currently Installed Language: Default string

Handle 0x0008, DMI type 32, 11 bytes
System Boot Information
	Status: No errors detected

Handle 0x0009, DMI type 44, 9 bytes
Unknown Type
	Header and Data:
		2C 09 09 00 00 00 01 01 00

Handle 0x000A, DMI type 45, 26 bytes
Firmware Inventory Information
	Firmware Component Name: BIOS Firmware
	Firmware Version: 5.27
	Firmware ID: 1CB94AA5-E0A6-556B-86A3-FA447D674A71
	Release Date: 03/13/2024
	Manufacturer: Default string
	Lowest Supported Firmware Version: 5.27
	Image Size: 16640 kB
	Characteristics:
		Updatable: Yes
		Write-Protect: No
	State: Enabled
	Associated Components: 1
		0x0000

Handle 0x000B, DMI type 16, 23 bytes
Physical Memory Array
	Location: System Board Or Motherboard
	Use: System Memory
	Error Correction Type: None
	Maximum Capacity: 64 GB
	Error Information Handle: Not Provided
	Number Of Devices: 2

Handle 0x000C, DMI type 17, 92 bytes
Memory Device
	Array Handle: 0x000B
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8 GB
	Form Factor: SODIMM
	Set: None
	Locator: Controller0-ChannelA
	Bank Locator: BANK 0
	Type: DDR4
	Type Detail: Synchronous
	Speed: 3200 MT/s
	Manufacturer: Samsung
	Serial Number: 00000000
	Asset Tag: 9876543210
	Part Number: M471A1G44BB0-CWE    
	Rank: 1
	Configured Memory Speed: 3200 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V
	Memory Technology: DRAM
	Memory Operating Mode Capability: Volatile memory
	Firmware Version: Not Specified
	Module Manufacturer ID: Bank 1, Hex 0xCE
	Module Product ID: Unknown
	Memory Subsystem Controller Manufacturer ID: Unknown
	Memory Subsystem Controller Product ID: Unknown
	Non-Volatile Size: None
	Volatile Size: 8 GB
	Cache Size: None
	Logical Size: None

Handle 0x000D, DMI type 17, 92 bytes
Memory Device
	Array Handle: 0x000B
	Error Information Handle: Not Provided
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8 GB
	Form Factor: SODIMM
	Set: None
	Locator: Controller1-ChannelA-DIMM0
	Bank Locator: BANK 0
	Type: DDR4
	Type Detail: Synchronous
	Speed: 3200 MT/s
	Manufacturer: SK Hynix
	Serial Number: 2A5AD5D4
	Asset Tag: 9876543210
	Part Number: HMAG68EXNSA051N     
	Rank: 1
	Configured Memory Speed: 3200 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V
	Memory Technology: DRAM
	Memory Operating Mode Capability: Volatile memory
	Firmware Version: Not Specified
	Module Manufacturer ID: Bank 1, Hex 0xAD
	Module Product ID: Unknown
	Memory Subsystem Controller Manufacturer ID: Unknown
	Memory Subsystem Controller Product ID: Unknown
	Non-Volatile Size: None
	Volatile Size: 8 GB
	Cache Size: None
	Logical Size: None

Handle 0x000E, DMI type 19, 31 bytes
Memory Array Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x003FFFFFFFF
	Range Size: 16 GB
	Physical Array Handle: 0x000B
	Partition Width: 2

Handle 0x000F, DMI type 43, 31 bytes
TPM Device
	Vendor ID: INTC
	Specification Version: 2.0
	Firmware Revision: 600.18
	Description: INTEL
	Characteristics:
		Family configurable via platform software support
	OEM-specific Information: 0x00000000

Handle 0x0010, DMI type 45, 26 bytes
Firmware Inventory Information
	Firmware Component Name: TPM Firmware
	Firmware Version: 2580012:1E0926..
	Firmware ID: Not Specified
	Release Date: 2021-05-15T00:00:00Z
	Manufacturer: INTEL
	Lowest Supported Firmware Version: Not Specified
	Image Size: Unknown
	Characteristics:
		Updatable: No
		Write-Protect: No
	State: Enabled
	Associated Components: 1
		0x000F

Handle 0x0011, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00000000000
	Ending Address: 0x001FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x000C
	Memory Array Mapped Address Handle: 0x000E
	Partition Row Position: Unknown
	Interleave Position: 1
	Interleaved Data Depth: 1

Handle 0x0012, DMI type 20, 35 bytes
Memory Device Mapped Address
	Starting Address: 0x00200000000
	Ending Address: 0x003FFFFFFFF
	Range Size: 8 GB
	Physical Device Handle: 0x000D
	Memory Array Mapped Address Handle: 0x000E
	Partition Row Position: Unknown
	Interleave Position: 2
	Interleaved Data Depth: 1

Handle 0x0013, DMI type 221, 12 bytes
OEM-specific Type
	Header and Data:
		DD 0C 13 00 01 01 00 02 00 00 5C 01
	Strings:
		BIOS Guard

Handle 0x0014, DMI type 221, 12 bytes
OEM-specific Type
	Header and Data:
		DD 0C 14 00 01 01 00 04 00 00 00 00
	Strings:
		FSP Binary Version

Handle 0x0015, DMI type 221, 26 bytes
OEM-specific Type
	Header and Data:
		DD 1A 15 00 03 01 00 0C 00 93 20 00 02 00 00 00
		41 1F 00 03 00 01 12 0D 00 00
	Strings:
		Reference Code - CPU
		uCode Version
		TXT ACM version

Handle 0x0016, DMI type 221, 26 bytes
OEM-specific Type
	Header and Data:
		DD 1A 16 00 03 01 00 0C 00 93 20 00 02 00 00 00
		00 00 00 03 04 10 01 1E 26 09
	Strings:
		Reference Code - ME
		MEBx version
		ME Firmware Version
		Consumer SKU

Handle 0x0017, DMI type 221, 47 bytes
OEM-specific Type
	Header and Data:
		DD 2F 17 00 06 01 00 0C 00 93 20 00 02 03 FF FF
		FF FF FF 04 00 FF FF FF 01 00 05 00 FF FF FF 01
		00 06 00 02 46 00 00 00 07 00 04 00 00 00 00
	Strings:
		Reference Code - PCH
		PCH-CRID Status
		Disabled
		PCH-CRID Original Value
		PCH-CRID New Value
		OPROM - RST - RAID
		PCH Hsio Version

Handle 0x0018, DMI type 221, 82 bytes
OEM-specific Type
	Header and Data:
		DD 52 18 00 0B 01 00 0C 00 93 20 00 02 00 00 00
		04 74 00 03 00 0C 00 93 20 00 04 05 FF FF FF FF
		FF 06 00 00 00 00 01 00 07 00 00 00 00 01 00 08
		00 FF FF FF FF FF 09 00 24 00 07 00 00 0A 00 00
		00 00 00 00 0B 00 00 00 00 00 00 0C 00 FF FF FF
		FF FF
	Strings:
		Reference Code - SA - System Agent
		Reference Code - MRC
		SA - PCIe Version
		SA-CRID Status
		Disabled
		SA-CRID Original Value
		SA-CRID New Value
		OPROM - VBIOS
		IO Manageability Engine FW Version
		PHY Build Version
		Thunderbolt(TM) FW Version
		System Agent Manageability Engine FW Version

Handle 0x0019, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 96 kB
	Maximum Size: 96 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 12-way Set-associative

Handle 0x001A, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 64 kB
	Maximum Size: 64 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x001B, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 2560 kB
	Maximum Size: 2560 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: Other

Handle 0x001C, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L3 Cache
	Configuration: Enabled, Not Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 12 MB
	Maximum Size: 12 MB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 12-way Set-associative

Handle 0x001D, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 256 kB
	Maximum Size: 256 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Data
	Associativity: 8-way Set-associative

Handle 0x001E, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L1 Cache
	Configuration: Enabled, Not Socketed, Level 1
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 512 kB
	Maximum Size: 512 kB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Parity
	System Type: Instruction
	Associativity: 8-way Set-associative

Handle 0x001F, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L2 Cache
	Configuration: Enabled, Not Socketed, Level 2
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 4 MB
	Maximum Size: 4 MB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Single-bit ECC
	System Type: Unified
	Associativity: 16-way Set-associative

Handle 0x0020, DMI type 7, 27 bytes
Cache Information
	Socket Designation: L3 Cache
	Configuration: Enabled, Not Socketed, Level 3
	Operational Mode: Write Back
	Location: Internal
	Installed Size: 12 MB
	Maximum Size: 12 MB
	Supported SRAM Types:
		Synchronous
	Installed SRAM Type: Synchronous
	Speed: Unknown
	Error Correction Type: Multi-bit ECC
	System Type: Unified
	Associativity: 12-way Set-associative

Handle 0x0021, DMI type 4, 48 bytes
Processor Information
	Socket Designation: U3E1
	Type: Central Processor
	Family: Core i5
	Manufacturer: Intel(R) Corporation
	ID: A3 06 0B 00 FF FB EB BF
	Signature: Type 0, Family 6, Model 186, Stepping 3
	Flags:
		FPU (Floating-point unit on-chip)
		VME (Virtual mode extension)
		DE (Debugging extension)
		PSE (Page size extension)
		TSC (Time stamp counter)
		MSR (Model specific registers)
		PAE (Physical address extension)
		MCE (Machine check exception)
		CX8 (CMPXCHG8 instruction supported)
		APIC (On-chip APIC hardware supported)
		SEP (Fast system call)
		MTRR (Memory type range registers)
		PGE (Page global enable)
		MCA (Machine check architecture)
		CMOV (Conditional move instruction supported)
		PAT (Page attribute table)
		PSE-36 (36-bit page size extension)
		CLFSH (CLFLUSH instruction supported)
		DS (Debug store)
		ACPI (ACPI supported)
		MMX (MMX technology supported)
		FXSR (FXSAVE and FXSTOR instructions supported)
		SSE (Streaming SIMD extensions)
		SSE2 (Streaming SIMD extensions 2)
		SS (Self-snoop)
		HTT (Multi-threading)
		TM (Thermal monitor supported)
		PBE (Pending break enabled)
	Version: 13th Gen Intel(R) Core(TM) i5-1335U
	Voltage: 1.0 V
	External Clock: 100 MHz
	Max Speed: 4600 MHz
	Current Speed: 3762 MHz
	Status: Populated, Enabled
	Upgrade: <OUT OF SPEC>
	L1 Cache Handle: 0x001E
	L2 Cache Handle: 0x001F
	L3 Cache Handle: 0x0020
	Serial Number: To Be Filled By O.E.M.
	Asset Tag: To Be Filled By O.E.M.
	Part Number: To Be Filled By O.E.M.
	Core Count: 10
	Core Enabled: 10
	Thread Count: 12
	Characteristics:
		64-bit capable
		Multi-Core
		Hardware Thread
		Execute Protection
		Enhanced Virtualization
		Power/Performance Control

Handle 0x0034, DMI type 10, 26 bytes
On Board Device 1 Information
	Type: Video
	Status: Enabled
	Description: VGA
On Board Device 2 Information
	Type: Ethernet
	Status: Enabled
	Description: GLAN
On Board Device 3 Information
	Type: Ethernet
	Status: Enabled
	Description: WLAN
On Board Device 4 Information
	Type: Sound
	Status: Enabled
	Description: Audio CODEC
On Board Device 5 Information
	Type: SATA Controller
	Status: Enabled
	Description: SATA Controller
On Board Device 6 Information
	Type: Other
	Status: Enabled
	Description: USB 2.0 Controller
On Board Device 7 Information
	Type: Other
	Status: Enabled
	Description: USB 3.0 Controller
On Board Device 8 Information
	Type: Other
	Status: Enabled
	Description: SMBus Controller
On Board Device 9 Information
	Type: Other
	Status: Enabled
	Description: Card Reader
On Board Device 10 Information
	Type: Other
	Status: Enabled
	Description: Cmos Camera
On Board Device 11 Information
	Type: Other
	Status: Enabled
	Description: Bluetooth

Handle 0x0035, DMI type 11, 5 bytes
OEM Strings
	String 1: kPJ-+7X7+EfTa
	String 2: jTyRUBSNi7Ydf
	String 3: fCrOzJ6x1i-eh
	String 4:  
	String 5: 90NB10V2-M00DU0

Handle 0x0036, DMI type 12, 5 bytes
System Configuration Options
	Option 1: SMI:00B26C
	Option 2: DSN:                                
	Option 3: DSN:                                
	Option 4: DSN:                                

Handle 0x0037, DMI type 131, 64 bytes
OEM-specific Type
	Header and Data:
		83 40 37 00 35 00 00 00 00 00 00 00 00 00 00 00
		F8 00 9D 51 00 00 00 00 21 20 00 00 01 00 10 00
		26 09 1E 00 00 00 00 00 FE 00 FF FF 00 00 00 00
		00 00 00 00 26 00 00 00 76 50 72 6F 00 00 00 00

Handle 0x0038, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: VGA
	Type: Video
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:00:02.0

Handle 0x0039, DMI type 41, 11 bytes
Onboard Device
	Reference Designation: WLAN
	Type: Ethernet
	Status: Enabled
	Type Instance: 1
	Bus Address: 0000:02:00.0

Handle 0x003A, DMI type 133, 44 bytes
OEM-specific Type
	Header and Data:
		85 2C 3A 00 F9 B4 95 78 4D 92 0A 41 96 39 12 38
		62 B2 8A 63 00 86 80 08 16 12 20 26 12 86 80 01
		00 00 00 61 72 57 18 03 00 00 00 00

Handle 0x003B, DMI type 136, 8 bytes
OEM-specific Type
	Header and Data:
		88 08 3B 00 00 00 00 00

Handle 0x003C, DMI type 221, 103 bytes
OEM-specific Type
	Header and Data:
		DD 67 3C 00 0E 01 00 FF FF FF FF FF 02 00 FF FF
		FF FF FF 03 04 FF FF FF FF FF 05 06 FF FF FF FF
		FF 07 08 FF FF FF FF FF 09 00 FF FF FF FF FF 0A
		00 FF FF FF FF 00 0B 00 FF FF 00 00 00 0C 00 00
		21 00 61 10 0D 00 FF FF FF FF FF 0E 00 00 07 00
		00 00 0F 00 13 05 00 2C 16 10 00 FF FF FF FF FF
		11 00 FF FF FF FF FF
	Strings:
		Lan Phy Version
		Sensor Firmware Version
		Debug Mode Status
		Disabled
		Performance Mode Status
		Disabled
		Debug Use USB(Disabled:Serial)
		Disabled
		ICC Overclocking Version
		UNDI Version
		EC FW Version
		GOP Version
		Royal Park Version
		Platform Version
		RST PreOS Version
		TCSS PD0 Version
		TCSS PD1 Version

Handle 0x003D, DMI type 14, 8 bytes
Group Associations
	Name: $MEI
	Items: 1
		0x0000 (OEM-specific)

Handle 0x003E, DMI type 219, 106 bytes
OEM-specific Type
	Header and Data:
		DB 6A 3E 00 01 04 01 45 02 00 90 06 01 10 80 20
		00 00 00 00 40 00 00 03 1F 04 00 C9 03 60 44 02
		FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF
		FF FF FF FF FF FF FF FF 03 00 00 00 80 00 00 00
		00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00
		00 00 00 00 00 00 00 00 00 00
	Strings:
		MEI1
		MEI2
		MEI3
		MEI4

Handle 0x003F, DMI type 136, 6 bytes
OEM-specific Type
	Header and Data:
		88 06 3F 00 00 00

Handle 0x0040, DMI type 14, 26 bytes
Group Associations
	Name: Firmware Version Info
	Items: 7
		0x0013 (OEM-specific)
		0x0014 (OEM-specific)
		0x0015 (OEM-specific)
		0x0016 (OEM-specific)
		0x0017 (OEM-specific)
		0x0018 (OEM-specific)
		0x003C (OEM-specific)

Handle 0x0041, DMI type 127, 4 bytes
End Of Table
Debian 12

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#6 Post by Aki »

Hello,

According to the dmidecode output:
mazda1 wrote: 2024-12-12 06:59

Code: Select all

# dmidecode
[..]
Base Board Information
	Manufacturer: ASUSTeK COMPUTER INC.
	Product Name: X1704VA
[..]
your notebook is exactly identified in the patch as in the previous thread, if I read correctly: So, patching your kernel might solve the issue.

You might recompile the kernel after patching it [2]. The patch (I named "X1704VAP.patch" below) is:

Code: Select all

Reported-by: Lamome Julien <julien.lamome@wanadoo.fr>
Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1078696
Closes: https://lore.kernel.org/all/1226760b-4699-4529-bf57-6423938157a3@wanadoo.fr/
Cc: stable@vger.kernel.org
Signed-off-by: Hans de Goede <hdegoede@redhat.com>
---
 drivers/acpi/resource.c | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/drivers/acpi/resource.c b/drivers/acpi/resource.c
index dfe108e2ccde..8e672790ac51 100644
--- a/drivers/acpi/resource.c
+++ b/drivers/acpi/resource.c
@@ -440,6 +440,13 @@ static const struct dmi_system_id irq1_level_low_skip_override[] = {
 			DMI_MATCH(DMI_BOARD_NAME, "S5602ZA"),
 		},
 	},
+	{
+		/* Asus Vivobook X1704VAP */
+		.matches = {
+			DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
+			DMI_MATCH(DMI_BOARD_NAME, "X1704VAP"),
+		},
+	},
 	{
 		/* Asus ExpertBook B1402CBA */
 		.matches = {
-- 
2.46.0
You can use the following commands (replace linux-6.1.119 with the kernel version whose sources are downloaded):

Code: Select all

$ sudo apt install packaging-dev
$ apt source linux
$ sudo apt build-dep linux
$ cd linux-6.1.119/
$ quilt import ../X1704VAP.patch
$ quilt push
$ dch -i "local rebuild for X1704VAP keyboard patching"
$ dpkg-buildpackage -B -uc -us
Rebuilding the kernel will require some time (probably many hours, depending on your hardware capability) and enough disk space (probably many gigabytes).

Previous command will create debian packages for the rebuilt unsigned kernel. You are mainly interested in a sub-version of linux-image-$(uname -r).deb

If you are booting Debian with secure boot, you will need create and register a MOK (machine owner key) into the UEFI NVRAM and then sign the unsigned kernel image and rebuild the kernel package (containing the signed kernel image): Then, you need to install the debian package containing the rebuilt signed kernel, using dpkg.

Hope this helps.

--
EDIT Fri Dec 13 18:14:23 CET 2024:

According to the Debian Bug Tracking System: the patch should be already included in kernel (upstream version) 6.1.15 and next versions. So, the Debian packages linux-image-6.1.0-27-amd64 and subsequent linux-image-6.1.0-28-amd64 (currently in debian-proposed-updates) should already include the patch.

What is the version you are currently using ? You can check with the command:

Code: Select all

uname -a
--
[1] https://lore.kernel.org/linux-acpi/2024 ... edhat.com/
[2] https://www.debian.org/doc/manuals/main ... ld.en.html
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#7 Post by mazda1 »

Aki wrote: 2024-12-13 17:07 ...........
So, patching your kernel might solve the issue.
...........
According to the Debian Bug Tracking System: the patch should be already included in kernel (upstream version) 6.1.15 and next versions. So, the Debian packages linux-image-6.1.0-27-amd64 and subsequent linux-image-6.1.0-28-amd64 (currently in debian-proposed-updates) should already include the patch.
hello!

as I'm using linux-image-6.1.0.28-amd64 the patch should be included and the bug fixed, but I still have a problem. Does it come from the driver xserver-xorg-input-libinput, as I first thought? I could try the version 1.4 in trixie, but a dependency is not satisfied: dep: libinput10 (>= 1.23.0). In debian 12 the version of this package is 1.22. Everything else is correct.
Debian 12

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#8 Post by Aki »

Hello,

Does the keyboard issue appear with grub (boot loader) or typing in a virtual console [1] ?

--
[1] https://wiki.debian.org/Console
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#9 Post by mazda1 »

Aki wrote: 2024-12-14 08:07 Hello,

Does the keyboard issue appear with grub (boot loader) or typing in a virtual console [1] ?
The issue does not appear with grub.

When the problem occurs, among other things, I can't open and write to a terminal tty7. Stangely, I can sometimes open a tty2/3 console and use it, that's another random effect of the problem. Normally I can highlight tabs in Firefox one by one, but with this problem I can't: once highlighted a tab stays in this state and I can highlight all the tabs that are open, one by one. I have many such erratic events occurring.
Debian 12

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#10 Post by Aki »

How soon after installing Debian did the problem start?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#11 Post by mazda1 »

Aki wrote: 2024-12-14 08:44 How soon after installing Debian did the problem start?
it started 2 or 3 days after the installation.

Could this have anything to do with the problem: on the right-hand side of the keyboard, the first four keys above the numeric keypad are, from left to right: Calculator (launches calculator), CE (= Clear Entry), -/+ (Change Sign) and On/Off. The problem is that F9 and + / - keys have the exact same function and also CE and Del key act the exact same: their keycodes and scancodes are identical.
Debian 12

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#12 Post by Aki »

mazda1 wrote: 2024-12-14 09:00
Aki wrote: 2024-12-14 08:44 How soon after installing Debian did the problem start?
it started 2 or 3 days after the installation.
Which packages did you install within the first 3 days after installing Debian? You can check here:
  • /var/log/apt/history.log
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#13 Post by mazda1 »

Aki wrote: 2024-12-14 09:21
Which packages did you install within the first 3 days after installing Debian? You can check here:
  • /var/log/apt/history.log
I've found the log but first I need to learn how to copy from line 93 to line 329 with the less editor viewer, so I can only keep what is relevant

history log : https://forums.debian.net/app.php/paste ... view&s=131
Last edited by mazda1 on 2024-12-14 17:34, edited 3 times in total.
Debian 12

arzgi
Posts: 1614
Joined: 2008-02-21 17:03
Location: Finland
Has thanked: 1 time
Been thanked: 85 times

Re: Asus laptop: random keyboard problem

#14 Post by arzgi »

less is a viewer, would not say it is an editor. But you can show starting by line number: less +nnn file, where nnn is the page number.

mazda1
Posts: 70
Joined: 2023-04-09 21:29
Has thanked: 7 times
Been thanked: 1 time

Re: Asus laptop: random keyboard problem

#15 Post by mazda1 »

arzgi wrote: 2024-12-14 10:45 less is a viewer, would not say it is an editor. But you can show starting by line number: less +nnn file, where nnn is the page number.
the command below did the job:

Code: Select all

# zless  history.log.3.gz > f1 ; sed -n '93,329p' f1 > f2
Debian 12

arzgi
Posts: 1614
Joined: 2008-02-21 17:03
Location: Finland
Has thanked: 1 time
Been thanked: 85 times

Re: Asus laptop: random keyboard problem

#16 Post by arzgi »

Nice! You can save the file to pastebin, link is the at the top.

Aki
Global Moderator
Global Moderator
Posts: 4057
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 113 times
Been thanked: 535 times

Re: Asus laptop: random keyboard problem

#17 Post by Aki »

Hello @mazda1,

Did you make any progress ?
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Post Reply