You are not logged in.

#1 2025-04-23 05:02:06

JetGum_386
Member
Registered: 2025-04-23
Posts: 2

Lenovo Yoga Slim Aura Edition: Keyboard backlight broken after suspend

Hello everybody, I have recently bought a Lenovo laptop (Yoga Slim 7 15ILL9) with Lunar Lake CPU. With kernel 6.14.3-arch1-1 basically everything worked out of the box. I have KDE Plasma.
The only issues that I've found are have to do with wake up after suspension:
- the keys controlling screen brightness stop working (but screen brightness can still be adjusted with the touchpad or mouse through the graphical tool in the panel)
- keyboard backlight stops working, and it can't be adjusted (a reboot is needed for it to start working again).

I have already done some debugging. So for example, I have seen that the value of keyboard backlight brightness is correctly modified in

/sys/class/leds/platform::kbd_backlight/brightness

but the light doesn't turn on or changes anyway.

This is my system:

System:
  Kernel: 6.14.3-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: cryptdevice=UUID=bc98d41a-79e4-4e07-b20c-8a4c543b7f20:cryptlvm
    root=/dev/ArchinstallVg/root zswap.enabled=0 rw rootfstype=ext4
  Desktop: KDE Plasma v: 6.3.4 tk: Qt v: N/A info: frameworks v: 6.13.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Arch Linux
Machine:
  Type: Laptop System: LENOVO product: 83HM v: Yoga Slim 7 15ILL9
    serial: <superuser required> Chassis: type: 10 v: Yoga Slim 7 15ILL9
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76574 WIN
    serial: <superuser required> part-nu: LENOVO_MT_83HM_BU_idea_FM_Yoga Slim 7
    15ILL9 uuid: <superuser required> UEFI: LENOVO v: NYCN67WW date: 02/08/2025
Battery:
  ID-1: BAT0 charge: 67.2 Wh (96.0%) condition: 70.0/70.0 Wh (100.0%)
    power: 5.1 W volts: 8.5 min: 7.7 model: SMP L23M4PF3 type: Li-poly
    serial: N/A status: discharging cycles: 1
CPU:
  Info: model: Intel Core Ultra 7 258V bits: 64 type: MCP arch: Lunar Lake
    level: v3 note: check built: 2024+ process: TSMC n3b (3nm) family: 6
    model-id: 0xBD (189) stepping: 1 microcode: 0x11B
  Topology: cpus: 1x dies: 1 clusters: 5 cores: 8 smt: <unsupported> cache:
    L1: 832 KiB desc: d-4x32 KiB, 4x48 KiB; i-8x64 KiB L2: 14 MiB
    desc: 4x2.5 MiB, 1x4 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 400 min/max: 400/4800:4700:3700 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 bogomips: 52838
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: ghostwrite status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB: conditional;
    RSB filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Lunar Lake [Intel Arc Graphics 130V / 140V] vendor: Lenovo
    driver: xe v: kernel arch: Xe2 process: TSMC n3 (3nm) built: 2024+ ports:
    active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 00:02.0 chip-ID: 8086:64a0
    class-ID: 0300
  Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-4:2 chip-ID: 04f2:b7f5
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: modesetting
    alternate: fbdev,intel,vesa dri: iris gpu: xe display-ID: 0
  Monitor-1: eDP-1 model: Tianma Micro 0x2036 serial: <filter> built: 2024
    res: mode: 2880x1800 hz: 120 scale: 165% (1.65) to: 1745x1091 dpi: 222
    gamma: 1.2 size: 330x206mm (12.99x8.11") diag: 389mm (15.3") ratio: 16:10
    modes: 2880x1800
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris wayland:
    drv: iris x11: drv: iris
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.4-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (LNL)
    device-ID: 8086:64a0 memory: 15.08 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.4.309 layers: N/A device: 0 type: integrated-gpu
    name: Intel Graphics (LNL) driver: mesa intel v: 25.0.4-arch1.1
    device-ID: 8086:64a0 surfaces: xcb,xlib,wayland
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel Lunar Lake-M HD Audio vendor: Lenovo
    driver: sof-audio-pci-intel-lnl
    alternate: snd_hda_intel,snd_sof_pci_intel_lnl bus-ID: 00:1f.3
    chip-ID: 8086:a828 class-ID: 0401
  API: ALSA v: k6.14.3-arch1-1 status: kernel-api tools: N/A
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.2 status: off with: wireplumber status: active
    tools: pw-cli,wpctl
  Server-3: PulseAudio v: 17.0-43-g3e2bb status: active tools: pacat,pactl
Network:
  Device-1: Intel BE201 320MHz driver: iwlwifi v: kernel port: N/A
    bus-ID: 00:14.3 chip-ID: 8086:a840 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Info: services: NetworkManager, systemd-timesyncd, wpa_supplicant
Bluetooth:
  Device-1: Intel driver: btusb v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s
    lanes: 1 mode: 1.1 bus-ID: 3-6:3 chip-ID: 8087:0037 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 3 state: down bt-service: disabled
    rfk-block: hardware: no software: no address: see --recommends
Drives:
  Local Storage: total: 953.87 GiB used: 129.75 GiB (13.6%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: PM9C1a 1024GB
    size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 57330709 temp: 31.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 40 GiB size: 39.2 GiB (98.00%) used: 14.62 GiB (37.3%)
    fs: ext4 dev: /dev/dm-1 maj-min: 253:1 mapped: ArchinstallVg-root
  ID-2: /boot raw-size: 1024 MiB size: 1022 MiB (99.80%)
    used: 217.2 MiB (21.3%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
  ID-3: /home raw-size: 900 GiB size: 884.8 GiB (98.31%)
    used: 114.92 GiB (13.0%) fs: ext4 dev: /dev/dm-2 maj-min: 253:2
    mapped: ArchinstallVg-home
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 4 GiB used: 0 KiB (0.0%) priority: 100
    comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 33.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 32 GiB note: est. available: 30.89 GiB used: 5.67 GiB (18.4%)
  Processes: 390 Power: uptime: 16m states: freeze,mem,disk suspend: s2idle
    wakeups: 1 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 12.34 GiB services: org_kde_powerdevil,upowerd Init: systemd v: 257
    default: graphical tool: systemctl
  Packages: 1032 pm: dpkg pkgs: 0 pm: pacman pkgs: 1026 libs: 248
    tools: pamac,yay pm: flatpak pkgs: 6 Compilers: clang: 19.1.7 gcc: 14.2.1
    Shell: Zsh v: 5.9 running-in: konsole inxi: 3.3.38

EDIT: The main issue, as far as i can tell, seems to be that changes in the brightness level of the keyboard backlight are not registered as acpi events.

If I run

acpi_listen

I can see that the system registers events when I change the volume of the speakers or the brightness level of the screen, but not when I change the brightness of the keyboard backlight. This suggests that keyboard backlight is probably controlled by some other lower-level mechanism. And this would explain why the system doesn't wake it up after a suspension. Investigation continues.

Any help is appreciated.

Last edited by JetGum_386 (2025-04-27 07:37:03)

Offline

Board footer

Powered by FluxBB