I am a relatively new linux user, so sorry if I miss anything.
I recently bought an ASUS Zenbook 14(UM425) with the intention of dual-booting Windows 10 and Manjaro. I installed the newest version of Manjaro(tried both GNOME and KDE) on another partition, and everything seems to work ok. However, when I suspend or sleep, the screen would not turn back on so I am forced to restart the computer. I have tried using different kernel versions(currently tries 5.10 on both, but for some reason versions older than 5.9 was stuck at boot) but to no avail. The weird thing is that this problem seems to not be an issue for Windows 10.
Here is the output from inxi -Fza and journalctl -p3 -i-1, respectively on GNOME;
System:
Kernel: 5.10.32-1-MANJARO x86_64 bits: 64 compiler: gcc v: 10.2.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
root=UUID=acd17a23-533c-4a5d-81a0-796f9cb63888 rw quiet splash apparmor=1
security=apparmor udev.log_priority=3
Desktop: GNOME 3.38.4 tk: GTK 3.24.29 wm: gnome-shell dm: GDM 40.0
Distro: Manjaro Linux base: Arch Linux
Machine:
Type: Laptop System: ASUSTeK product: ZenBook UX425IA_UM425IA v: 1.0
serial: <filter>
Mobo: ASUSTeK model: UX425IA v: 1.0 serial: <filter>
UEFI: American Megatrends v: UX425IA.306 date: 08/29/2020
Battery:
ID-1: BATT charge: 67.8 Wh (100.0%) condition: 67.8/67.1 Wh (101.0%)
volts: 15.9 min: 15.9 model: ASUSTeK UM425 type: Li-ion serial: <filter>
status: Full cycles: 1
CPU:
Info: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64
type: MCP arch: Zen 2 family: 17 (23) model-id: 60 (96) stepping: 1
microcode: 8600104 cache: L2: 4 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
bogomips: 31941
Speed: 1398 MHz min/max: 1400/2000 MHz boost: enabled Core speeds (MHz):
1: 1398 2: 1397 3: 1397 4: 1397 5: 1397 6: 1398 7: 1397 8: 1397
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
IBRS_FW, STIBP: disabled, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir vendor: ASUSTeK driver: amdgpu v: kernel
bus-ID: 04:00.0 chip-ID: 1002:1636 class-ID: 0300
Device-2: IMC Networks USB2.0 HD UVC WebCam type: USB driver: uvcvideo
bus-ID: 1-3:2 chip-ID: 13d3:56eb class-ID: fe01 serial: <filter>
Display: wayland server: X.org 1.20.11 compositor: gnome-shell driver:
loaded: amdgpu note: n/a (using device driver) - try sudo/root
display-ID: 0 resolution: <missing: xdpyinfo>
OpenGL: renderer: AMD RENOIR (DRM 3.40.0 5.10.32-1-MANJARO LLVM 11.1.0)
v: 4.6 Mesa 21.0.3 direct render: Yes
Audio:
Device-1: AMD vendor: ASUSTeK driver: snd_hda_intel v: kernel
bus-ID: 04:00.1 chip-ID: 1002:1637 class-ID: 0403
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor
vendor: ASUSTeK driver: snd_rn_pci_acp3x v: kernel
alternate: snd_pci_acp3x bus-ID: 04:00.5 chip-ID: 1022:15e2 class-ID: 0480
Device-3: AMD Family 17h HD Audio vendor: ASUSTeK driver: snd_hda_intel
v: kernel bus-ID: 04:00.6 chip-ID: 1022:15e3 class-ID: 0403
Sound Server-1: ALSA v: k5.10.32-1-MANJARO running: yes
Sound Server-2: JACK v: 0.125.0 running: no
Sound Server-3: PulseAudio v: 14.2 running: yes
Sound Server-4: PipeWire v: 0.3.26 running: no
Network:
Device-1: Intel Wi-Fi 6 AX200 driver: iwlwifi v: kernel bus-ID: 01:00.0
chip-ID: 8086:2723 class-ID: 0280
IF: wlp1s0 state: up mac: <filter>
Bluetooth:
Device-1: Intel AX200 Bluetooth type: USB driver: btusb v: 0.8
bus-ID: 1-4:3 chip-ID: 8087:0029 class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
Drives:
Local Storage: total: 953.87 GiB used: 7.16 GiB (0.8%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: HFM001TD3JX013N
size: 953.87 GiB block-size: physical: 512 B logical: 512 B
speed: 31.6 Gb/s lanes: 4 rotation: SSD serial: <filter> rev: 41000C20
temp: 31.9 C scheme: GPT
Partition:
ID-1: / raw-size: 269.08 GiB size: 263.79 GiB (98.04%)
used: 7.13 GiB (2.7%) fs: ext4 dev: /dev/nvme0n1p6 maj-min: 259:6
ID-2: /boot/efi raw-size: 260 MiB size: 256 MiB (98.46%)
used: 25.6 MiB (10.0%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
Alert: No swap data was found.
Sensors:
System Temperatures: cpu: 43.9 C mobo: 39.0 C gpu: amdgpu temp: 35.0 C
Fan Speeds (RPM): cpu: 0
Info:
Processes: 264 Uptime: 24m wakeups: 2850 Memory: 15.13 GiB
used: 2.14 GiB (14.1%) Init: systemd v: 247 tool: systemctl Compilers:
gcc: N/A Packages: pacman: 1130 lib: 292 flatpak: 0 Shell: Zsh v: 5.8
running-in: gnome-terminal inxi: 3.3.04
-- Journal begins at Thu 2021-04-29 18:13:16 PDT, ends at Thu 2021-04-29 18:16:42 PDT. --
Apr 29 18:13:16 kyungbong-zenbookux425iaum425ia kernel: ACPI BIOS Error (bug): Failure creating named object [\SMIB], AE_ALREADY_EXISTS (20200925/dsfield-637)
Apr 29 18:13:16 kyungbong-zenbookux425iaum425ia kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1.WLAN], AE_NOT_FOUND (20200925/dswload2-162)
Apr 29 18:13:16 kyungbong-zenbookux425iaum425ia kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20200925/psobject-220)
Apr 29 18:13:19 kyungbong-zenbookux425iaum425ia systemd-backlight[776]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Apr 29 18:13:19 kyungbong-zenbookux425iaum425ia systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Apr 29 18:13:21 kyungbong-zenbookux425iaum425ia kernel: sd 2:0:0:0: [sda] No Caching mode page found
Apr 29 18:13:21 kyungbong-zenbookux425iaum425ia kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
Apr 29 18:13:30 kyungbong-zenbookux425iaum425ia gdm-password][1317]: gkr-pam: unable to locate daemon control file
Apr 29 18:13:32 kyungbong-zenbookux425iaum425ia systemd[1325]: Failed to start Application launched by gnome-session-binary.
Apr 29 18:13:34 kyungbong-zenbookux425iaum425ia gdm-launch-environment][841]: pam_systemd(gdm-launch-environment:session): Failed to release session: Interrupted system call
Apr 29 18:14:19 kyungbong-zenbookux425iaum425ia kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Apr 29 18:15:16 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on gfx (-110).
Apr 29 18:15:16 kyungbong-zenbookux425iaum425ia kernel: [drm:process_one_work] *ERROR* ib ring test failed (-110).
What should I do?
I also tried to update the BIOS using fwupd from the Archwiki with a few commands:
fwupdmgr get-devices
ZenBook UX425IA_UM425IA
│
├─ASUE140A:00 04F3:3134:
│ Device ID: c8e8b6e0a02fae2dc0e5890012cbfefcfee5d56f
│ Summary: Elan Touchpad
│ Current version: 0x0002
│ Bootloader Version: 0x0001
│ Vendor: HIDRAW:0x04F3
│ GUIDs: 237c6dd4-b11b-5dfc-86c9-b994fe42cc24
│ 5aa826fb-3357-54c5-8ecd-5c8bb41eb051
│ 716fc71a-0e57-5afa-bac8-6c66106f8bd1
│ 4296cbee-f355-5bf6-b62d-a6a286b69414
│ 1a8d392f-f511-5f6f-90da-cc505332dfa0
│ Device Flags: • Internal device
│ • Updatable
│
├─HFM001TD3JX013N:
│ Device ID: 3743975ad7f64f8d6575a9ae49fb3a8856fe186f
│ Summary: NVM Express Solid State Drive
│ Current version: 41000C20
│ Vendor: SK hynix (NVME:0x1C5C)
│ GUIDs: 34f9d6fa-e1d6-5d7d-909e-0406644298c5
│ 34e06406-f620-5b9d-a9cd-7f3a4e648633
│ 4406b8dc-20c5-5f3a-bc9c-8afdcee48684
│ 0ee57466-ca9d-5f10-a005-ec6bacf6fb82
│ 7a80c83f-9add-57b7-99df-b1d7b8fc170c
│ Device Flags: • Internal device
│ • Updatable
│ • System requires external power source
│ • Needs a reboot after installation
│ • Device is usable for the duration of the update
│
├─System Firmware:
│ │ Device ID: 8ac9a223637b171e2132c9cb2afd553603f36002
│ │ Current version: 774
│ │ Minimum Version: 774
│ │ Vendor: ASUSTeK COMPUTER INC. (DMI:American Megatrends Inc.)
│ │ GUIDs: 415afde5-fb11-5268-bd7d-ed498d06e0de
│ │ 230c8b18-8d9b-53ec-838b-6cfc0383493a
│ │ 0a7d6784-10c0-532d-96be-85e5c3f6e379
│ │ Device Flags: • Internal device
│ │ • Updatable
│ │ • System requires external power source
│ │ • Needs a reboot after installation
│ │ • Cryptographic hash verification is available
│ │ • Device is usable for the duration of the update
│ │
│ └─UEFI dbx:
│ Device ID: 362301da643102b9f38477387e2193e57abaa590
│ Summary: UEFI Revocation Database
│ Current version: 83
│ Minimum Version: 83
│ Vendor: UEFI:Linux Foundation
│ Install Duration: 1 second
│ GUIDs: 6c9777b8-19f2-5e2c-9210-66ef3691a9f3
│ c8749f7f-439b-5c3c-a2ea-3baacf663a5a
│ c6682ade-b5ec-57c4-b687-676351208742
│ f8ba2887-9411-5c36-9cee-88995bb39731
│ 7d5759e5-9aa0-5f0c-abd6-7439bb11b9f6
│ 0c7691e1-b6f2-5d71-bc9c-aabee364c916
│ Device Flags: • Internal device
│ • Updatable
│ • Needs a reboot after installation
│
└─USB2.0 HD UVC WebCam:
Device ID: 1f914e619b232dc4da68ec3389b98b20163003a2
Current version: 19.64
Vendor: Azurewave (USB:0x13D3)
GUIDs: d60fd269-904f-5a6f-a1df-1ccc22630fbf
b17d3a6b-ffac-510d-8de5-a578b92c0351
Device Flags: • Updatable
fwupdmgr refresh
Updating lvfs
Downloading… [***************************************] Less than one minute remaining…
Successfully downloaded new metadata: 0 local devices supported
fwupdmgr get-updates
Devices with no available firmware updates:
• ASUE140A:00 04F3:3134
• HFM001TD3JX013N
• System Firmware
• UEFI dbx
• USB2.0 HD UVC WebCam
No updatable devices
It seems to me that the BIOS is up to date. What could be the problem here?
omano
30 April 2021 02:19
3
You tried latest kernels? The most recent available (5.12 or 5.11)?
No I only tried 5.10 because I thought that they would be less stable. Should I try the newer kernels?
omano
30 April 2021 02:27
5
Yes. You have fairly recent hardware there so I would definitely test 5.12. Despite it not being a LTS (Long Term Support ) kernel, and that it will not be supported for long (non LTS kernels usually have a few months lifespan, when LTS kernels are supported for 5 years or more), I would use it and I would try the next ones when they release too later.
The downside in not using a LTS kernel is that you need to keep track of new kernel release and change/remove kernel before it disappears from Manjaro or before it is not updated anymore. It is easy if you read the forum announcements it is usually clearly stated when a kernel becomes EOL (End Of Life) and will be soon removed from Manjaro. Freshly released kernel though, can sometimes contain new bugs due to their nature of being bleeding edge. But Just try and see for yourself it is simple to add or remove them from Manjaro Settings, just click the button
PS: it should automatically start on latest most recent kernel, to switch kernel go to the Advanced kernel options in Grub, which you should have its menu automatically shown when booting if you dual boot with Windows. If it doesn’t for whatever reason, spam the escape and/or shift key on boot to force Grub menu.
PS2: here is the kernel page to see kernels statuses https://www.kernel.org/
Here is the output from journalctl from kernel version 5.11:
-- Journal begins at Thu 2021-04-29 18:13:16 PDT, ends at Thu 2021-04-29 19:55:50 PDT. --
Apr 29 19:31:16 kyungbong-zenbookux425iaum425ia kernel: ACPI BIOS Error (bug): Failure creating named object [\SMIB], AE_ALREADY_EXISTS (20201113/dsfield-637)
Apr 29 19:31:16 kyungbong-zenbookux425iaum425ia kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1.WLAN], AE_NOT_FOUND (20201113/dswload2-162)
Apr 29 19:31:16 kyungbong-zenbookux425iaum425ia kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20201113/psobject-220)
Apr 29 19:31:18 kyungbong-zenbookux425iaum425ia systemd-backlight[889]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Apr 29 19:31:18 kyungbong-zenbookux425iaum425ia systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Apr 29 19:31:19 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Unsupported power profile mode 0 on RENOIR
Apr 29 19:31:26 kyungbong-zenbookux425iaum425ia gdm-password][1294]: gkr-pam: unable to locate daemon control file
Apr 29 19:32:18 kyungbong-zenbookux425iaum425ia kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Apr 29 19:33:56 kyungbong-zenbookux425iaum425ia kernel: amdgpu: cp queue preemption time out.
Apr 29 19:33:56 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.0.0 (-110).
Apr 29 19:33:56 kyungbong-zenbookux425iaum425ia kernel: [drm:process_one_work] *ERROR* ib ring test failed (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu: cp queue preemption time out.
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.1.0 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.2.0 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.3.0 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.0.1 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.1.1 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.2.1 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* IB test failed on comp_1.3.1 (-110).
Apr 29 19:35:32 kyungbong-zenbookux425iaum425ia kernel: [drm:process_one_work] *ERROR* ib ring test failed (-110).
When I try to wake it up, it works only when I do it seconds after I suspend. After some time, the screen stays black.
And here is the output from journalctl from kernel version 5.12:
-- Journal begins at Thu 2021-04-29 18:13:16 PDT, ends at Thu 2021-04-29 20:10:39 PDT. --
Apr 29 20:06:18 kyungbong-zenbookux425iaum425ia kernel: ACPI BIOS Error (bug): Failure creating named object [\SMIB], AE_ALREADY_EXISTS (20210105/dsfield-637)
Apr 29 20:06:18 kyungbong-zenbookux425iaum425ia kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.GPP1.WLAN], AE_NOT_FOUND (20210105/dswload2-162)
Apr 29 20:06:18 kyungbong-zenbookux425iaum425ia kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20210105/psobject-220)
Apr 29 20:06:19 kyungbong-zenbookux425iaum425ia kernel: acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
Apr 29 20:06:19 kyungbong-zenbookux425iaum425ia kernel: acp_pdm_mach acp_pdm_mach.0: snd_soc_register_card(acp) failed: -517
Apr 29 20:06:20 kyungbong-zenbookux425iaum425ia systemd-backlight[867]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Apr 29 20:06:20 kyungbong-zenbookux425iaum425ia systemd-backlight[871]: amdgpu_bl0: Failed to write system 'brightness' attribute: No such device or address
Apr 29 20:06:20 kyungbong-zenbookux425iaum425ia systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
Apr 29 20:06:20 kyungbong-zenbookux425iaum425ia systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:amdgpu_bl0.
Apr 29 20:06:57 kyungbong-zenbookux425iaum425ia gdm-password][1316]: gkr-pam: unable to locate daemon control file
Apr 29 20:07:20 kyungbong-zenbookux425iaum425ia kernel: ucsi_acpi USBC000:00: PPM init failed (-110)
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: failed send message: SetGfxCGPG (47) param: 0x00000001 response 0xff
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Failed to power ungate SDMA!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Failed to update WMTABLE!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: [drm:smu_v12_0_gfx_off_control [amdgpu]] *ERROR* disable gfxoff timeout and failed!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Failed to disable gfxoff!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Fail to set workload type 2
Apr 29 20:07:37 kyungbong-zenbookux425iaum425ia kernel: amdgpu 0000:04:00.0: amdgpu: Msg issuing pre-check failed and SMU may be not in the right state!
Same issue of screen not waking from black after suspending. It looks like all three give similar errors. Any ideas?
omano
30 April 2021 03:28
8
Nope. Time to google, and I already found some leads
TLDR; check if you have some settings in your BIOS to enable S3 support.
Also try manually to go to hibernation mode instead of sleep, and see if that works. If it works then see if you can change the settings in desktop environment for what happens when you close your laptop lid or when it goes to sleep, and switch to hibernation as a workaround.
Is Windows 10 Fast startup disabled?
It seems this issue has been fixed now, if you upgrade to Kernel 5.14 or later. Check “Asus Zenbook 14 UM425” on the Arch Wiki (I can’t post links)
