ACPI BIOS Errors in journalctl

Ask Fedora
,
1

Hi,
I get errors and warnings in journalctl and was wondering if they have to be addressed or that they are not hindering a normal use of the computer.
This is my computer:
inxi -ze

System:
  Kernel: 6.15.10-200.fc42.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.4.4 Distro: Fedora Linux 42 (KDE Plasma Desktop
    Edition)
Machine:
  Type: Laptop System: LENOVO product: 82RG v: Legion 5 Pro 16ARH7H
    serial: <superuser required>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76461 WIN
    serial: <superuser required> UEFI: LENOVO v: JUCN51WW date: 08/29/2022
Battery:
  ID-1: BAT0 charge: 76.5 Wh (100.0%) condition: 76.5/80.0 Wh (95.6%)
CPU:
  Info: 8-core model: AMD Ryzen 7 6800H with Radeon Graphics bits: 64
    type: MT MCP cache: L2: 4 MiB
  Speed (MHz): avg: 1096 min/max: 404/4787 cores: 1: 1096 2: 1096 3: 1096
    4: 1096 5: 1096 6: 1096 7: 1096 8: 1096 9: 1096 10: 1096 11: 1096 12: 1096
    13: 1096 14: 1096 15: 1096 16: 1096
Graphics:
  Device-1: NVIDIA GA106M [GeForce RTX 3060 Mobile / Max-Q] driver: nvidia
    v: 575.64.05
  Device-2: Advanced Micro Devices [AMD/ATI] Rembrandt [Radeon 680M]
    driver: amdgpu v: kernel
  Display: wayland server: Xwayland v: 24.1.8 compositor: kwin_wayland
    driver: gpu: amdgpu,nvidia,nvidia-nvswitch resolution: 1: 2560x1440~144Hz
    2: 2560x1600~165Hz
  API: EGL v: 1.5 drivers: nvidia,radeonsi,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: amd mesa v: 25.1.7 renderer: AMD
    Radeon 680M (radeonsi rembrandt LLVM 20.1.8 DRM 3.63
    6.15.10-200.fc42.x86_64)
  API: Vulkan v: 1.4.313 drivers: radv,nvidia,llvmpipe surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
    wl: wayland-info x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
  Device-1: NVIDIA GA106 High Definition Audio driver: snd_hda_intel
  Device-2: Advanced Micro Devices [AMD/ATI] Radeon High Definition Audio
    [Rembrandt/Strix] driver: snd_hda_intel
  Device-3: Advanced Micro Devices [AMD] Audio Coprocessor
    driver: snd_pci_acp6x
  Device-4: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio
    driver: snd_hda_intel
  API: ALSA v: k6.15.10-200.fc42.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.4.7 status: active
Network:
  Device-1: MEDIATEK MT7922 802.11ax PCI Express Wireless Network Adapter
    driver: mt7921e
  IF: wlp2s0 state: up mac: <filter>
  Device-2: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    driver: r8169
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: tun0 state: unknown speed: 10000 Mbps duplex: full mac: N/A
Bluetooth:
  Device-1: Foxconn / Hon Hai Bluetooth 5.2 Adapter [MediaTek MT7922]
    driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: <filter> bt-v: 5.2
Drives:
  Local Storage: total: 982.74 GiB used: 381.39 GiB (38.8%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVL21T0HCLR-00BL2
    size: 953.87 GiB
  ID-2: /dev/sda vendor: Kingston model: DataTraveler 3.0 size: 28.88 GiB
    type: USB
Partition:
  ID-1: / size: 48.91 GiB used: 20.48 GiB (41.9%) fs: ext4 dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 465.4 MiB (47.8%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 51.3 MiB (8.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 887.05 GiB used: 360.4 GiB (40.6%) fs: ext4
    dev: /dev/nvme0n1p4
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 44.8 C mobo: 40.0 C gpu: amdgpu temp: 42.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB note: est. available: 14.8 GiB used: 3.62 GiB (24.5%)
  Processes: 458 Uptime: 2m Shell: Bash inxi: 3.3.38

After installing Fedora 42 KDE yesterday I get these error messages when I type:
journalctl -b -0 -p err

Aug 25 07:27:03 Fedora-KDE kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20240827/dswload2-162)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20240827/dswload2-162)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Aug 25 07:27:03 Fedora-KDE kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
Aug 25 07:27:06 Fedora-KDE kernel: lenovo_wmi_hotkey_utilities CE6C0974-0407-4F50-88BA-4FC3B6559AD8: probe with driver lenovo_wmi_hotkey_utilities failed with error -5
Aug 25 07:27:06 Fedora-KDE kernel: 
Aug 25 07:27:25 Fedora-KDE org_kde_powerdevil[2914]: busno=7, sleep-multiplier =  1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"

The first 4 I have had since I bought this laptop using different Linux distro’s, asked about it on the internet but it wasn’t a severe problem (or similar words). I just don’t understand what it means.

This is the result of:
journalctl -b -0 -p warning

Aug 25 07:27:03 Fedora-KDE kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20240827/dswload2-162)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.PB2], AE_NOT_FOUND (20240827/dswload2-162)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI Error: AE_NOT_FOUND, During name lookup/catalog (20240827/psobject-220)
Aug 25 07:27:03 Fedora-KDE kernel: ACPI: \_SB_.PCI0.GP11: Overriding _PRW sleep state (S3) by S0 from power resources
Aug 25 07:27:03 Fedora-KDE kernel: ACPI: \_SB_.PCI0.GP12: Overriding _PRW sleep state (S3) by S0 from power resources
Aug 25 07:27:03 Fedora-KDE kernel: ACPI: \_SB_.PCI0.GP19.NHI0: Overriding _PRW sleep state (S3) by S0 from power resources
Aug 25 07:27:03 Fedora-KDE kernel: ACPI: \_SB_.PCI0.GP19.NHI1: Overriding _PRW sleep state (S4) by S0 from power resources
Aug 25 07:27:03 Fedora-KDE kernel: hub 6-0:1.0: config failed, hub doesn't have any ports! (err -19)
Aug 25 07:27:03 Fedora-KDE kernel: i8042: PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp
Aug 25 07:27:03 Fedora-KDE kernel: device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
Aug 25 07:27:03 Fedora-KDE rpc.idmapd[639]: Setting log level to 0
Aug 25 07:27:03 Fedora-KDE rpc.idmapd[639]: libnfsidmap: Unable to determine the NFSv4 domain; Using 'localdomain' as the NFSv4 domain which means UIDs will be mapped to the 'Nobody-User' user defined in /etc/idmapd.conf
Aug 25 07:27:04 Fedora-KDE kernel: wmi_bus wmi_bus-PNP0C14:01: [Firmware Bug]: WQA0 data block query control method not found
Aug 25 07:27:04 Fedora-KDE rpc.idmapd[639]: exiting on signal 15
Aug 25 07:27:04 Fedora-KDE kernel: GPT:Primary header thinks Alt. header is not at the end of the disk.
Aug 25 07:27:04 Fedora-KDE kernel: GPT:5555739 != 60555263
Aug 25 07:27:04 Fedora-KDE kernel: GPT:Alternate GPT header not at the end of the disk.
Aug 25 07:27:04 Fedora-KDE kernel: GPT:5555739 != 60555263
Aug 25 07:27:04 Fedora-KDE kernel: GPT: Use GNU Parted to correct GPT errors.
Aug 25 07:27:06 Fedora-KDE kernel: lenovo_wmi_hotkey_utilities CE6C0974-0407-4F50-88BA-4FC3B6559AD8: probe with driver lenovo_wmi_hotkey_utilities failed with error -5
Aug 25 07:27:06 Fedora-KDE kernel: nvidia: loading out-of-tree module taints kernel.
Aug 25 07:27:06 Fedora-KDE kernel: 
Aug 25 07:27:06 Fedora-KDE kernel: NVRM: loading NVIDIA UNIX Open Kernel Module for x86_64  575.64.05  Release Build  (dvs-builder@U22-A23-13-1)  Fri Jul 18 16:00:10 UTC 2025
Aug 25 07:27:07 Fedora-KDE kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
Aug 25 07:27:07 Fedora-KDE kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
Aug 25 07:27:09 Fedora-KDE (-wrapper)[1330]: lm_sensors.service: Referenced but unset environment variable evaluates to an empty string: BUS_MODULES, HWMON_MODULES
Aug 25 07:27:09 Fedora-KDE kernel: nvme nvme0: using unchecked data buffer
Aug 25 07:27:09 Fedora-KDE (qbalance)[1323]: irqbalance.service: Referenced but unset environment variable evaluates to an empty string: IRQBALANCE_ARGS
Aug 25 07:27:09 Fedora-KDE kernel: NVRM: testIfDsmSubFunctionEnabled: GPS ACPI DSM called before _acpiDsmSupportedFuncCacheInit subfunction = 11.
Aug 25 07:27:09 Fedora-KDE boltd[1443]: [de723804-d0e6-domain0                    ] udev: failed to determine if uid is stable: unknown NHI PCI id '0x162e'
Aug 25 07:27:14 Fedora-KDE nm-openvpn[1963]: DEPRECATED OPTION: --cipher set to 'AES-256-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM:CHACHA20-POLY1305). OpenVPN ignores --cipher for cipher negotiations.
Aug 25 07:27:14 Fedora-KDE nm-openvpn[1963]: WARNING: --ping should normally be used with --ping-restart or --ping-exit
Aug 25 07:27:14 Fedora-KDE nm-openvpn[1963]: NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Aug 25 07:27:15 Fedora-KDE systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Aug 25 07:27:15 Fedora-KDE systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Aug 25 07:27:15 Fedora-KDE (atd)[2042]: atd.service: Referenced but unset environment variable evaluates to an empty string: OPTS
Aug 25 07:27:15 Fedora-KDE systemd[1]: iscsi.service: Unit cannot be reloaded because it is inactive.
Aug 25 07:27:16 Fedora-KDE dbus-broker-launch[2103]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Aug 25 07:27:16 Fedora-KDE dbus-broker-launch[2103]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Aug 25 07:27:16 Fedora-KDE dbus-broker-launch[2103]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Aug 25 07:27:16 Fedora-KDE sddm-helper-start-wayland[2102]: "No backend specified, automatically choosing drm\n"
Aug 25 07:27:16 Fedora-KDE sddm-helper-start-wayland[2102]: "Accepting client connections on sockets: QList(\"wayland-0\")\n"
Aug 25 07:27:18 Fedora-KDE sddm-helper-start-wayland[2102]: "QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav\n"
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 73 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 73 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 63 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 63 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 71 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 71 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 61 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 61 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 68 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 68 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 66 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 66 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 64 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 64 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 72 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 72 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 62 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 62 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 70 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 70 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 60 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 60 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 69 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 69 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 59 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 59 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 67 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 67 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: Cannot change IRQ 65 affinity: Permission denied
Aug 25 07:27:19 Fedora-KDE irqbalance[1323]: IRQ 65 affinity is now unmanaged
Aug 25 07:27:19 Fedora-KDE sddm-helper-start-wayland[2102]: "QSGContext::initialize: depth buffer support missing, expect rendering errors\nQSGContext::initialize: stencil buffer support missing, expect rendering errors\n"
Aug 25 07:27:22 Fedora-KDE sddm-greeter-qt6[2111]: file:///usr/share/sddm/themes/breeze/Main.qml:232:17 Parameter "username" is not declared. Injection of parameters into signal handlers is deprecated. Use JavaScript functions with formal parameters instead.
Aug 25 07:27:22 Fedora-KDE sddm-helper-start-wayland[2102]: "kwin_scene_opengl: Could not delete render time query because no context is current\n"
Aug 25 07:27:22 Fedora-KDE sddm-helper-start-wayland[2102]: "kwin_scene_opengl: Could not delete render time query because no context is current\nkwin_scene_opengl: Could not delete render time query because no context is current\n"
Aug 25 07:27:22 Fedora-KDE dbus-broker-launch[2338]: Service file '/usr/share//dbus-1/services/org.kde.dolphin.FileManager1.service' is not named after the D-Bus name 'org.freedesktop.FileManager1'.
Aug 25 07:27:22 Fedora-KDE dbus-broker-launch[2338]: Service file '/usr/share//dbus-1/services/org.kde.kscreen.service' is not named after the D-Bus name 'org.kde.KScreen'.
Aug 25 07:27:22 Fedora-KDE dbus-broker-launch[2338]: Service file '/usr/share//dbus-1/services/org.kde.plasma.Notifications.service' is not named after the D-Bus name 'org.freedesktop.Notifications'.
Aug 25 07:27:22 Fedora-KDE sddm[2067]: Authentication information: SDDM::Auth::INFO_UNKNOWN "Last failed login: Sun Aug 24 09:25:15 CEST 2025"
Aug 25 07:27:22 Fedora-KDE sddm[2067]: Authentication information: SDDM::Auth::INFO_UNKNOWN "There was 1 failed login attempt since the last successful login."
Aug 25 07:27:24 Fedora-KDE maliit-keyboard[2688]: QSoundEffect(pulseaudio): Error decoding source file:///usr/share/maliit/keyboard2/sounds/key_tick2_quiet.wav
Aug 25 07:27:24 Fedora-KDE kded6[2801]: QDBusObjectPath: invalid path "/modules/kded_plasma-welcome"
Aug 25 07:27:24 Fedora-KDE kded6[2801]: kf.dbusaddons: The kded module name "kded_plasma-welcome" is invalid!
Aug 25 07:27:25 Fedora-KDE kded6[2801]: QDBusObjectPath: invalid path "/modules/wpad-detector"
Aug 25 07:27:25 Fedora-KDE kded6[2801]: kf.dbusaddons: The kded module name "wpad-detector" is invalid!
Aug 25 07:27:25 Fedora-KDE kded6[2801]: QDBusObjectPath: invalid path "/modules/oom-notifier"
Aug 25 07:27:25 Fedora-KDE kded6[2801]: kf.dbusaddons: The kded module name "oom-notifier" is invalid!
Aug 25 07:27:25 Fedora-KDE kded6[2801]: QDBusObjectPath: invalid path "/modules/plasma-session-shortcuts"
Aug 25 07:27:25 Fedora-KDE kded6[2801]: kf.dbusaddons: The kded module name "plasma-session-shortcuts" is invalid!
Aug 25 07:27:25 Fedora-KDE (rpcbind)[3091]: rpcbind.service: Referenced but unset environment variable evaluates to an empty string: RPCBIND_OPTIONS
Aug 25 07:27:25 Fedora-KDE rpc.statd[3092]: Flags: TI-RPC
Aug 25 07:27:25 Fedora-KDE kconf_update[3234]: kf.config.kconf_update: /usr/share/kconf_update/filepicker.upd defined Version=5 but Version=6 was expected
Aug 25 07:27:25 Fedora-KDE org_kde_powerdevil[2914]: busno=7, sleep-multiplier =  1,30. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Aug 25 07:27:25 Fedora-KDE org_kde_powerdevil[2914]: org.kde.powerdevil: [DDCutilDetector]: Failed to initialize callback
Aug 25 07:27:26 Fedora-KDE org_kde_powerdevil[2914]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Aug 25 07:27:26 Fedora-KDE org_kde_powerdevil[2914]: org.kde.powerdevil: Handle button events action could not check for screen configuration
Aug 25 07:27:26 Fedora-KDE org_kde_powerdevil[2914]: org.kde.powerdevil: org.kde.powerdevil.chargethresholdhelper.getthreshold failed "Charge thresholds are not supported by the kernel for this hardware"
Aug 25 07:27:26 Fedora-KDE systemd[2283]: app-nvidia\x2dsettings\x2duser@autostart.service: Failed with result 'exit-code'.
Aug 25 07:27:26 Fedora-KDE abrt-applet[3400]: g_app_info_should_show: assertion 'G_IS_APP_INFO (appinfo)' failed
Aug 25 07:27:26 Fedora-KDE kwin_wayland[2587]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Aug 25 07:27:27 Fedora-KDE plasmashell[2863]: No QSGTexture provided from updateSampledImage(). This is wrong.
Aug 25 07:27:27 Fedora-KDE wireplumber[2580]: spa.bluez5.native: RFCOMM receive command but modem not available: AT+CSCS="UTF-8"
Aug 25 07:27:29 Fedora-KDE plasmashell[2863]: org.kde.UserFeedback: failed to probe user feedback submission interface: "Connection closed" ""
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_scene_opengl: 0x500: GL_INVALID_ENUM error generated. Invalid <face>.
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_MISSING_ATTACHMENT"
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_scene_opengl: 0x502: GL_INVALID_OPERATION error generated. <image> and <target> are incompatible
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_scene_opengl: Invalid framebuffer status:  "GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT"
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Aug 25 07:27:36 Fedora-KDE kwin_wayland[2587]: kwin_wayland_drm: Failed to create framebuffer: Invalid argument
Aug 25 07:27:39 Fedora-KDE plasmashell[2863]: QGridLayoutEngine::addItem: Can't add Body_QMLTYPE_628(0x55cd05ee2c60, id="bodyLabel", parent=0x55cd06e88360, geometry=0,0 649.453x18) at cell (1, 0) because it's already taken by Summary_QMLTYPE_633(0x55cd09bc5d60, id="summary", paren>
Aug 25 07:27:43 Fedora-KDE maliit-keyboard[2688]: QSGContext::initialize: depth buffer support missing, expect rendering errors
Aug 25 07:27:43 Fedora-KDE maliit-keyboard[2688]: QSGContext::initialize: stencil buffer support missing, expect rendering errors
Aug 25 07:28:25 Fedora-KDE drkonqi-coredump-launcher[3844]: Unable to find file for pid 10299 expected at "kcrash-metadata/soffice.bin.41b906b914dc4c7ba2be68f9d0fe413a.10299.ini"
Aug 25 07:28:25 Fedora-KDE drkonqi-coredump-launcher[3846]: Unable to find file for pid 12084 expected at "kcrash-metadata/soffice.bin.41b906b914dc4c7ba2be68f9d0fe413a.12084.ini"
Aug 25 07:28:25 Fedora-KDE drkonqi-coredump-launcher[3845]: Unable to find file for pid 11272 expected at "kcrash-metadata/soffice.bin.41b906b914dc4c7ba2be68f9d0fe413a.11272.ini"
Aug 25 07:28:25 Fedora-KDE drkonqi-coredump-launcher[3847]: Unable to find file for pid 3763 expected at "kcrash-metadata/clementine.1c218e783346405589de5c74a033fb60.3763.ini"
Aug 25 07:30:49 Fedora-KDE kwalletd6[4138]: g_dbus_proxy_get_object_path: assertion 'G_IS_DBUS_PROXY (proxy)' failed
Aug 25 07:30:50 Fedora-KDE kwin_wayland[2587]: kf.windowsystem: static bool KX11Extras::mapViewport() may only be used on X11
Aug 25 07:30:50 Fedora-KDE systemd[2283]: dbus-:1.2-org.freedesktop.portal.IBus@0.service: Failed with result 'exit-code'.
Aug 25 07:32:59 Fedora-KDE irqbalance[1323]: Cannot change IRQ 74 affinity: Permission denied
Aug 25 07:32:59 Fedora-KDE irqbalance[1323]: IRQ 74 affinity is now unmanaged

Do I need to worry that things don’t work as I hope they work, or isn’t it that bad?
Who can decipher these messages? Thanks.

2

Updating your BIOS should fix the ACPI errors. There was a similar issue for Thinksystems earlier in the year and a BIOS update was required.

Looking at Lenovo’s workaround in the link above and the details, it’s UEFI adding devices to the ACPI table. But it can safely be ignored. That’s for the Thinksystems.

Your BIOS is reported to be JUCN51WW by inxi, but a quick Google for the Legion 5 Pro 16ARH7H shows that the current BIOS is JUCN68WW released right around the same time as the fix for the Thinksystems. The change-log for the new BIOS reports fixing a couple of CVEs and an LEN.

Looking on the Linux Vendor Firmware Service website, there are a few entries for Lenovo Legion laptops, but maybe not for your device.

You can check with sudo fwupdmgr refresh to update the LVFS repo. You can list any updates with sudo fwupdmgr get-updates and then install updates with sudo fwupdmgr update.

That said, if you use Workstation and GNOME Software isn’t pushing you a firmware update, or you use KDE and Plasma Discover isn’t pushing you a firmware update, it’s unlikely that fwupdmgr will either, since they act as GUI front ends for it. And it also depends on whether or not Lenovo push the updates to the LVFS.

We had a thread a week or so ago where another user and myself hadn’t had, them a critical BIOS update, and me just a recommended BIOS update, pushed to the LVFS.

If so, you’ll have to update manually. If you dual boot with Windows, that’s easy enough. You can just boot into your Windows partition and use the ThinkVantage software or whatever it is. If you’re strictly Linux, then you’ll have to make a bootable USB stick img and go through the process manually (see the thread I linked above for an example of how to manually do it).

Unfortunately it looks like Lenovo don’t provide a bootable *.iso for updating your machine, like they do the Thinkpad (which is what I’m using).

There may be a way to download the *.exe and extract it (which I did with 7zip just to have a look-see) and then re-package it into an *.img, but that’s way above my technical know how and I wouldn’t try flashing it to a machine I was worried about bricking.

3

Thank you Brian,
I have been looking at fwupdmgr before but I don’t think I can update the firmware with it. This is what I get:

sudo fwupdmgr refresh
[sudo] password for jan: 
Metadata is up to date; use --force to refresh again.

 User jan @ Server Fedora-KDE in Folder ~ : Mon Aug 25 - 09:42:56
$ sudo fwupdmgr refresh --force
Updating lvfs
Downloading…             [***************************************]
Successfully downloaded new metadata: Updates have been published for 2 of 11 local devices

 User jan @ Server Fedora-KDE in Folder ~ : Mon Aug 25 - 09:43:07
$ sudo fwupdmgr get-updates
Devices with no available firmware updates: 
 • MSFT0001:00 04F3:31AD
 • Certificate JU
 • KEK CA
 • MZVL21T0HCLR-00BL2
 • Option ROM UEFI CA
 • System Firmware
 • UEFI Device Firmware
 • UEFI Device Firmware
 • Windows Production PCA
Devices with the latest available firmware version:
 • UEFI CA
 • UEFI dbx
No updates available

 User jan @ Server Fedora-KDE in Folder ~ : Mon Aug 25 - 09:43:32
$ sudo fwupdmgr update
Devices with the latest available firmware version:
 • UEFI CA
 • UEFI dbx
Devices with no available firmware updates: 
 • MSFT0001:00 04F3:31AD
 • Certificate JU
 • KEK CA
 • MZVL21T0HCLR-00BL2
 • Option ROM UEFI CA
 • System Firmware
 • UEFI Device Firmware
 • UEFI Device Firmware
 • Windows Production PCA

It looks to me it tells me there are 2 updates, it also tells me there are no updates, and when I type update nothing happens. Do I miss something or doesn’t it work on my computer?
To be honest I am also a bit scary to do it cause I know it can go south on me.

4

Obviously these devices listed here have no updates available.

These seem to be the only thing that the LVFS will serve up to you (either by command line, or through a GUI such as GNOME Software or Plasma Discover).

Both those apparently have the latest version available.

Yup. Only the UEFI certificate authority (CA) and UEFI forbidden signature database (dbx).

Correct.

Nothing to update, nothing will happen.

It doesn’t look like it provides much for your specific laptop (only those UEFI [CA/dbx] updates for secure boot). Even as I mentioned in my above post, I had to manually update my own BIOS not long back because, I’m assuming, Lenovo hadn’t pushed the updated firmware to the LVFS, which they’re usually good at for Thinkpads. The rest of their product lines are a lot more spotty in terms of what they support through the LVFS.

Having looked at the Thinksystem change-log and what it was causing the issue, and their response to it and the fact that the most up-to-date BIOS for your system isn’t a critical update, I’d just live with it. The other two options if you want the latest BIOS, is to either get on the support forums, or email Lenovo support and ask if they have another means of updating the BIOS on Linux (like a bootable CD iso they have for Thinkpads), or create a small partition for Windows (that’s an oxymoron) that you can boot into when you need to apply newer firmware.

One final option is a Windows live USB. I believe Rufus can create a “Windows To Go” live environment you can boot into with persistence, so it saves files and things you install on the USB. The only thing I haven’t got a clue about is how that would work installing firmware.

5

Hi again, I managed to download a Windows .exe file from Lenovo for my laptop and I downloaded Hirens boot cd, to make a bootable windows like system. Placing the boot cd software on a USB drive failed however and after reading your message about the not important updates I better leave it like it is.
The USB drive has become useless, when I plug it in the system recognizes the drive and the size, but KDE partitionmanager doesn’t see it anymore. In Dolphin I can mount it and see the contents, but I can not empty it with the partitionmanager.
Well, doesn’t matter, I won’t be continuing anyway. Thank you for the help so far.

Have you also looked at the other messages in my first post, and do you know what it’s about? I can look and look but no idea what they are telling me.

6

You can “purge” the USB on the command line. lsblk will list the block devices. Your USB will be under /dex/sd[x] or something I suspect. You can use the wipefs tool to quickly erase all signatures from the devices with sudo wipefs -a /dev/sd[x]. Unplug it and plug it back in and then try Partition Manager again. If that doesn’t work you can zero out the entire disk by writing data over the whole thing with sudo dd if=/dev/zero of=/dev/sd[x] bs=4M status=progress ; sync ;. You can also write random data over it by replacing the /dev/zero bit with /dev/urandom.

The “hub config failed” error looks to just be an AMD issue and how it communicates with a virtual device. You can see a similar thread about this issue a few months back.

The “Lenovo hotkey utilities” message seems to have been patched a couple of months back in the Kernel. From the patch file provided in that link is the following text…

Not all devices support audio mute and microphone mute LEDs, so the
explicitly checks for hardware support while probing. However missing
hardware features are treated as errors, causing the driver so fail
probing on devices that do not support both LEDs.

Fix this by simply ignoring hardware features that are not present.
This way the driver will properly load on devices supporting not both
LEDs and will stop throwing error messages on devices with no LEDS
at all.

The other stuff I’m clueless about.

1 Like
7

Thanks again Brian, but unfortunately it still doesn’t work:

sudo wipefs -a /dev/sda
wipefs: error: /dev/sda: probing initialization failed: Read-only file system

sudo dd if=/dev/zero of=/dev/sda bs=4M status=progress ; sync ;
dd: failed to open '/dev/sda': Read-only file system

It seems my tiny USB stick is pretty strong in keeping its data. But, don’t work on it anymore, it is a very tiny (4GB) stick and no loss if it won’t work again.

I will start reading the links you sent about the other error messages now, thanks for that.

8

Usually, when a usb flash drive fails it reverts to read-only and can never be written to again.

Fail Safe to not lose what is already there.

9

Hi Jeff, that’s the first time I hear about that. Well, if it is like that than I can throw it in the garbage. No real loss, it is a very small 4GB stick/drive which once attached to the computer is barely seen, the USB-A plug is 2 times as big as the housing of the chip.
Well, happily there is nothing of value on it, just the not working Hiren BCD software to imitate a Windows system.
Thank you for the info.

10

Well, a big step. I managed to update the BIOS/EFI system in the Lenovo. On their site they show an update which I downloaded, turned out to be a Windows .exe file. I then downloaded Hiren Windows imitation, the so called HBCD system and placed that on a USB drive, well 2 times but the first USB one crashed. I could boot up the laptop and placed a second USB with the Lenovo .exe file. After the start followed a reboot and the installer started. After a reboot it did start up until and including the log-in. After the Enter-key both screens turned black. What to do? Stupid me, I did not check the BIOS since that was the part which was changed. I decided to do a fast re-install with keeping my home-disk intact. Booted again, logged-in again and it worked. I installed the flatpaks, I installed the Nvidia driver, waited for the module to be ready and rebooted, logged-in and black screens. So it is Nvidia. Suddenly it hit me: did the BIOS update switch on secure boot? I rebooted and entered the BIOS. First I saw the setting for the GPU’s was changed from Switchable to dedicated GPU. Aha, they do change stuff. Then I saw the setting for Secure Boot and indeed it was on. Fedora has keys built in, Nvidia doesn’t. So Secure boot off and start. Now after logging-in I still had something on screen, so I could continue.
Now all is working again and I gained a new experience: updating the BIOS. I used the Windows way which is normally safe, but since I don’t have a true Windows installation it is still nerve wrecking. But it works.

Thanks for helping me @brianallenby . :+1:

2 Likes
12

For future reference, please remember that any time bios is updated it gets reset to factory settings and any user changes will need to be done again. This especially applies to secure boot and the module signing keys.

1 Like