Need help troubleshooting power management and keyboard on Zenbook 13 Ryzen 7 5800U

Hello,

I am quite surprised that I could install qubes on this rather new Zenbook 13.
You can find the HCL entry here:

https://forum.qubes-os.org/t/asus-zenbook-um325sa/10840

Still, there are some issues I would like to troubleshoot. Unfortunately, I don’t have that much experience tracking down hardware issues on Linux, so I would be happy if someone could give me some pointers or recommend logs that I should check.

The most annoying issue is that the internal keyboard ist not recognized.
Here some lines out of journalctl

Apr 19 20:33:21 dom0 kernel: ACPI: AC: AC Adapter [ACAD] (on-line)
Apr 19 20:33:21 dom0 kernel: input: Lid Switch as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:33/PNP0C09:00/PNP0C0D:00/input/input0
Apr 19 20:33:21 dom0 kernel: ACPI: button: Lid Switch [LID0]
Apr 19 20:33:21 dom0 kernel: input: Power Button as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
Apr 19 20:33:21 dom0 kernel: ACPI: button: Power Button [PWRB]
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P000: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P001: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P002: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P003: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P004: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P005: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P006: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: [Firmware Bug]: ACPI MWAIT C-state 0x0 not supported by HW (0x0)
Apr 19 20:33:21 dom0 kernel: ACPI: \_SB_.PLTF.P007: Found 3 idle states
Apr 19 20:33:21 dom0 kernel: thermal LNXTHERM:00: registered as thermal_zone0
Apr 19 20:33:21 dom0 kernel: ACPI: thermal: Thermal Zone [TZ0] (0 C)
Apr 19 20:33:21 dom0 kernel: Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
Apr 19 20:33:21 dom0 kernel: ACPI: battery: Slot [BATT] (battery present)
Apr 19 20:33:21 dom0 kernel: hpet_acpi_add: no address or irqs in _CRS
Apr 19 20:33:21 dom0 kernel: Non-volatile memory driver v1.3
Apr 19 20:33:21 dom0 kernel: Linux agpgart interface v0.103
Apr 19 20:33:21 dom0 kernel: ACPI: bus type drm_connector registered
Apr 19 20:33:21 dom0 kernel: usbcore: registered new interface driver usbserial_generic
Apr 19 20:33:21 dom0 kernel: usbserial: USB Serial support registered for generic
Apr 19 20:33:21 dom0 kernel: i8042: PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 1
Apr 19 20:33:21 dom0 kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Apr 19 20:33:21 dom0 kernel: i8042: Can't read CTR while initializing i8042
Apr 19 20:33:21 dom0 kernel: i8042: probe of i8042 failed with error -5
Apr 19 20:33:21 dom0 kernel: mousedev: PS/2 mouse device common for all mice

I tried i8042.reset in GRUB_CMDLINE_LINUX at /etc/default/grub but the keyboard still doesn’t work.
(Again, if somecone can suggest other logs that I should provide, let me know)

If the power management issues are related to

https://forum.qubes-os.org/t/amd-psp-not-restarting-correctly/8254/12

https://github.com/QubesOS/qubes-issues/issues/7390

my question would be, if it is possible to at least get cpu fan/c-states behave correctly.
Here the output of xl dmesg:


(XEN) Built-in command line: ept=exec-sp
(XEN) parameter "no-real-mode" unknown!
 Xen 4.14.4
(XEN) Xen version 4.14.4 (mockbuild@[unknown]) (gcc (GCC) 10.3.1 20210422 (Red Hat 10.3.1-1)) debug=n  Tue Apr  5 00:00:00 UTC 2022
(XEN) Latest ChangeSet: 
(XEN) Bootloader: GRUB 2.04
(XEN) Command line: placeholder console=none dom0_mem=min:1024M dom0_mem=max:4096M ucode=scan smt=off gnttab_max_frames=2048 gnttab_max_maptrack_frames=4096 no-real-mode edd=off
(XEN) Xen image load base address: 0xc8c00000
(XEN) Video information:
(XEN)  VGA is graphics mode 1920x1080, 32 bpp
(XEN) Disc information:
(XEN)  Found 0 MBR signatures
(XEN)  Found 1 EDD information structures
(XEN) Enabling Supervisor Shadow Stacks
(XEN) EFI RAM map:
(XEN)  [0000000000000000, 000000000009ffff] (usable)
(XEN)  [00000000000a0000, 00000000000fffff] (reserved)
(XEN)  [0000000000100000, 0000000009bfefff] (usable)
(XEN)  [0000000009bff000, 000000000a000fff] (reserved)
(XEN)  [000000000a001000, 000000000a1fffff] (usable)
(XEN)  [000000000a200000, 000000000a20efff] (ACPI NVS)
(XEN)  [000000000a20f000, 00000000c983efff] (usable)
(XEN)  [00000000c983f000, 00000000cae3efff] (reserved)
(XEN)  [00000000cae3f000, 00000000caedefff] (ACPI data)
(XEN)  [00000000caedf000, 00000000cc4defff] (ACPI NVS)
(XEN)  [00000000cc4df000, 00000000ccdfefff] (reserved)
(XEN)  [00000000ccdff000, 00000000cdffffff] (usable)
(XEN)  [00000000ce000000, 00000000cfffffff] (reserved)
(XEN)  [00000000f0000000, 00000000f7ffffff] (reserved)
(XEN)  [00000000fd000000, 00000000fdffffff] (reserved)
(XEN)  [00000000feb80000, 00000000fec01fff] (reserved)
(XEN)  [00000000fec10000, 00000000fec10fff] (reserved)
(XEN)  [00000000fed00000, 00000000fed00fff] (reserved)
(XEN)  [00000000fed40000, 00000000fed44fff] (reserved)
(XEN)  [00000000fed80000, 00000000fed8ffff] (reserved)
(XEN)  [00000000fedc4000, 00000000fedc9fff] (reserved)
(XEN)  [00000000fedcc000, 00000000fedcefff] (reserved)
(XEN)  [00000000fedd5000, 00000000fedd5fff] (reserved)
(XEN)  [00000000ff000000, 00000000ffffffff] (reserved)
(XEN)  [0000000100000000, 000000040e2fffff] (usable)
(XEN)  [000000040e300000, 000000042fffffff] (reserved)
(XEN) ACPI: RSDP CAEDE014, 0024 (r2 _ASUS_)
(XEN) ACPI: XSDT CAEDD728, 010C (r1 _ASUS_ Notebook  1072009 AMI   1000013)
(XEN) ACPI: FACP CAECE000, 0114 (r6 _ASUS_ Notebook  1072009 AMI     10013)
(XEN) ACPI: DSDT CAEC0000, D03D (r2 _ASUS_ Notebook  1072009 INTL 20200717)
(XEN) ACPI: FACS CC494000, 0040
(XEN) ACPI: MSDM CAEDC000, 0055 (r3 _ASUS_ Notebook  1072009 ASUS        1)
(XEN) ACPI: SSDT CAED4000, 7229 (r2    AMD AmdTable        2 MSFT  4000000)
(XEN) ACPI: IVRS CAED3000, 01A4 (r2  AMD   AmdTable        1 AMD         0)
(XEN) ACPI: SSDT CAECF000, 3A21 (r1    AMD  AMD AOD        1 INTL 20200717)
(XEN) ACPI: FIDT CAEBF000, 009C (r1 _ASUS_ Notebook  1072009 AMI     10013)
(XEN) ACPI: MCFG CAEBE000, 003C (r1 _ASUS_ Notebook  1072009 MSFT    10013)
(XEN) ACPI: HPET CAEBD000, 0038 (r1 _ASUS_ Notebook  1072009 AMI         5)
(XEN) ACPI: VFCT CAEAF000, D884 (r1 _ASUS_ Notebook        1  AMD 31504F47)
(XEN) ACPI: BGRT CAEAE000, 0038 (r1 _ASUS_ Notebook  1072009 AMI     10013)
(XEN) ACPI: TPM2 CAEAD000, 004C (r4 _ASUS_ Notebook        1 AMI         0)
(XEN) ACPI: SSDT CAEA7000, 5354 (r2    AMD AmdTable        1 AMD         1)
(XEN) ACPI: CRAT CAEA6000, 0EE8 (r1    AMD AmdTable        1 AMD         1)
(XEN) ACPI: CDIT CAEA5000, 0029 (r1    AMD AmdTable        1 AMD         1)
(XEN) ACPI: SSDT CAEA4000, 0149 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAEA3000, 048C (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAEA1000, 1486 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE9F000, 14F6 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE9B000, 36E3 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: WSMT CAE9A000, 0028 (r1 _ASUS_ Notebook  1072009 AMI     10013)
(XEN) ACPI: APIC CAE99000, 00DE (r3 _ASUS_ Notebook  1072009 AMI     10013)
(XEN) ACPI: SSDT CAE98000, 00C6 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE97000, 0917 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE95000, 1215 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE94000, 004A (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE93000, 0241 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE92000, 067A (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: SSDT CAE91000, 07E4 (r1    AMD AmdTable        1 INTL 20200717)
(XEN) ACPI: FPDT CAE90000, 0044 (r1 _ASUS_   A M I   1072009 AMI   1000013)
(XEN) System RAM: 15752MB (16130876kB)
(XEN) Domain heap initialised
(XEN) ACPI: 32/64X FACS address mismatch in FADT - cc494000/0000000000000000, using 32
(XEN) IOAPIC[0]: apic_id 33, version 33, address 0xfec00000, GSI 0-23
(XEN) IOAPIC[1]: apic_id 34, version 33, address 0xfec01000, GSI 24-55
(XEN) Enabling APIC mode:  Phys.  Using 2 I/O APICs
(XEN) CPU0: 1600 ... 1900 MHz
(XEN) xstate: size: 0x988 and states: 0x207
(XEN) Speculative mitigation facilities:
(XEN)   Hardware hints: STIBP_ALWAYS IBRS_FAST IBRS_SAME_MODE
(XEN)   Hardware features: IBPB IBRS STIBP SSBD PSFD
(XEN)   Compiled-in support: INDIRECT_THUNK
(XEN)   Xen settings: BTI-Thunk JMP, SPEC_CTRL: IBRS+ STIBP+ SSBD-, Other: IBPB BRANCH_HARDEN
(XEN)   Support for HVM VMs: MSR_SPEC_CTRL RSB
(XEN)   Support for PV VMs: None
(XEN)   XPTI (64-bit PV only): Dom0 disabled, DomU disabled (without PCID)
(XEN)   PV L1TF shadowing: Dom0 disabled, DomU disabled
(XEN) Using scheduler: SMP Credit Scheduler rev2 (credit2)
(XEN) Initializing Credit2 scheduler
(XEN) Platform timer is 14.318MHz HPET
(XEN) Detected 1896.436 MHz processor.
(XEN) AMD-Vi: IOMMU Extended Features:
(XEN) - Peripheral Page Service Request
(XEN) - x2APIC
(XEN) - NX bit
(XEN) - Invalidate All Command
(XEN) - Guest APIC
(XEN) - Performance Counters
(XEN) - Host Address Translation Size: 0x2
(XEN) - Guest Address Translation Size: 0
(XEN) - Guest CR3 Root Table Level: 0x1
(XEN) - Maximum PASID: 0xf
(XEN) - SMI Filter Register: 0x1
(XEN) - SMI Filter Register Count: 0x1
(XEN) - Guest Virtual APIC Modes: 0x1
(XEN) - Dual PPR Log: 0x2
(XEN) - Dual Event Log: 0x2
(XEN) - User / Supervisor Page Protection
(XEN) - Device Table Segmentation: 0x3
(XEN) - PPR Log Overflow Early Warning
(XEN) - PPR Automatic Response
(XEN) - Memory Access Routing and Control: 0
(XEN) - Block StopMark Message
(XEN) - Performance Optimization
(XEN) - MSI Capability MMIO Access
(XEN) - Guest I/O Protection
(XEN) - Enhanced PPR Handling
(XEN) - Attribute Forward
(XEN) - Invalidate IOTLB Type
(XEN) - VM Table Size: 0
(XEN) - Guest Access Bit Update Disable
(XEN) AMD-Vi: IOMMU 0 Enabled.
(XEN) I/O virtualisation enabled
(XEN)  - Dom0 mode: Relaxed
(XEN) Interrupt remapping enabled
(XEN) ENABLING IO-APIC IRQs
(XEN)  -> Using new ACK method
(XEN) Allocated console ring of 32 KiB.
(XEN) HVM: ASIDs enabled.
(XEN) SVM: Supported advanced features:
(XEN)  - Nested Page Tables (NPT)
(XEN)  - Last Branch Record (LBR) Virtualisation
(XEN)  - Next-RIP Saved on #VMEXIT
(XEN)  - VMCB Clean Bits
(XEN)  - DecodeAssists
(XEN)  - Virtual VMLOAD/VMSAVE
(XEN)  - Virtual GIF
(XEN)  - Pause-Intercept Filter
(XEN)  - Pause-Intercept Filter Threshold
(XEN)  - TSC Rate MSR
(XEN)  - MSR_SPEC_CTRL virtualisation
(XEN) HVM: SVM enabled
(XEN) HVM: Hardware Assisted Paging (HAP) detected
(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Brought up 8 CPUs
(XEN) Scheduling granularity: cpu, 1 CPU per sched-resource
(XEN) xenoprof: Initialization failed. AMD processor family 25 is not supported
(XEN) Dom0 has maximum 1096 PIRQs
(XEN)  Xen  kernel: 64-bit, lsb, compat32
(XEN)  Dom0 kernel: 64-bit, PAE, lsb, paddr 0x1000000 -> 0x4000000
(XEN) PHYSICAL MEMORY ARRANGEMENT:
(XEN)  Dom0 alloc.:   00000003f0000000->00000003f8000000 (1004059 pages to be allocated)
(XEN)  Init. ramdisk: 000000040b41b000->000000040e1ffca3
(XEN) VIRTUAL MEMORY ARRANGEMENT:
(XEN)  Loaded kernel: ffffffff81000000->ffffffff84000000
(XEN)  Init. ramdisk: 0000000000000000->0000000000000000
(XEN)  Phys-Mach map: 0000008000000000->0000008000800000
(XEN)  Start info:    ffffffff84000000->ffffffff840004b8
(XEN)  Xenstore ring: 0000000000000000->0000000000000000
(XEN)  Console ring:  0000000000000000->0000000000000000
(XEN)  Page tables:   ffffffff84001000->ffffffff84026000
(XEN)  Boot stack:    ffffffff84026000->ffffffff84027000
(XEN)  TOTAL:         ffffffff80000000->ffffffff84400000
(XEN)  ENTRY ADDRESS: ffffffff831551c0
(XEN) Dom0 has maximum 8 VCPUs
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Scrubbing Free RAM in background
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input to DOM0 (type 'CTRL-a' three times to switch input)
(XEN) Freed 580kB init memory
(XEN) AMD-Vi: IO_PAGE_FAULT: 0000:01:00.0 d1 addr fffffffdf8000000 flags 0x8 I
(XEN) AMD-Vi: IO_PAGE_FAULT: 0000:01:00.0 d1 addr fffffffdf8000000 flags 0x8 I

Any help would be very much appreciated.

Just filling a gap.

Is your keyboard working elsewhere; specifically in BIOS and grub?

It worked in win10, it is working with bios & grub but not beyond.
i tested a fedora live install which had the same issues as qubes.

Interesting. Are you willing to try Debian live and to get back?

Tested this one:

https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-11.3.0-amd64-netinst.iso

Presumed, it’s the recent version. During installation I couldn’t type anything from the internal keyboard, just use the trackpad.

On a side note, the internal keyboard is working sporadically in Qubes. Don’t have a clue why it starts working sometimes… Might be related to the i8042.reset in CMDLINE_LINUX?

Are you now willing to try to add

i8042.reset i8042.nomux i8042.nopnp i8042.noloop

to your GRUB_CMDLINE_LINUX after the word quiet

and then to update grub with

$ sudo grub2-mkconfig -o /boot/grub2/grub.cfg

and then reboot?

1 Like

yeah, tried that already. sorry, i was about to put that into my hcl post, but i cannot edit it at the moment.

Sorry to hear.
Beside to suggest you to try one of the daily builds with kernel-latest (which I doubt), the last thing on my mind would be to try something with this new option

https://lore.kernel.org/lkml/20211112180022.10850-1-tiwai@suse.de/T/

1 Like

That might be worth a try.

What I did find out is that the keyboard (function keys and also backlight) and cpu/fan for that matter work perfectly fine with the newest fedora beta live from here:

https://download.fedoraproject.org/pub/fedora/linux/releases/test/36_Beta/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-36_Beta-1.4.iso

So, i guess I would have to look for kernel version 5.17 at least.
Is there a daily build with 5.17 I could try?

Kernel-latest should already be 5.17.x? Did you try it?

what i did first was to enable the current-testing repos. if i remember correctly there was some kernel 5.17.4 which crashed during boot, but made the keyboard work when i afterwards booted into kernel 5.16.8.

then i gave the weekly builds a shot with Qubes-20220430-kernel-latest-x86_64.iso (i guess kernel 5.17.5), but that did not help regarding the keyboard.

now i switched to Qubes-20220507-x86_64.iso (kernel 5.10.112-1) with the advantage that finally “syncthing” is working again and i switched templates to fedora 35. still, no functioning internal keyboard.

as a side note, the keyboard is working perfectly fine with function keys, backlight etc. using a recent tails live-usb (kernel 5-10-0-13).