Thinkpad L14 Gen5 (Meteor Lake) does not boot

[doktor5000]

Dear Mageia team

My Lenovo Thinkpad L14 Gen. 5 with Intel Ultra 5 125U (Meteor Lake) does not boot on Mageia 9 or Cauldron. The PC has Intel WiFi 6E via the AX211 device onboard. My feeling is that this wireless device is part of the problem, if not the cause.

I have tried the full 64-bit ISO, netinstall (trying release 9 and cauldron), as well as the Plasma 64-bit live iso. The kernels I have tried are 6.4.9 (the Plasma live iso) and 6.6.83 (cauldron and full update after installing the Mageia 9). The machine recognizes Mageia, but the boot process stops at some point, and I get a message about a firmware bug (see output of 'journalctl' at the bottom of this post).

I have tried different non-Mageia distros (sorry!) with kernels 6.4.0 and 6.12.11 for testing, and the WiFi device is working on these.

Could you help me out with this one? That would be great!

I ran the following commands in recovery mode on Mageia 9 (full 64-bit ISO, updated yesterday to kernel 6.6.83):

Code: Select all

lspcidrake -v | grep -i -e net -e wireless -e wifi
e1000e        : Intel Corporation|Device 550b [NETWORK_ETHERNET] (vendor:8086 device:550b subv:17aa subd:50e3) (rev: 20)
iwlwifi         : Intel Corporation|Device 7e40 [NETWORK_OTHER] (vendor:8086 device:7e40 subv:8086 subd:0090) (rev: 20)
btusb           : Intel Corp.|AX211 Bluetooth [Wireless|Radio Frequency|Bluetooth] (vendor:8087 device:0033)


Code: Select all

 urpmq --list-media active --list-url
Core Release https://mirror2.tuxinator.org/mageia/distrib/9/x86_64/media/core/release
Core Updates https://mirror2.tuxinator.org/mageia/distrib/9/x86_64/media/core/updates
Nonfree Release https://mirror2.tuxinator.org/mageia/distrib/9/x86_64/media/nonfree/release
Nonfree Updates https://mirror2.tuxinator.org/mageia/distrib/9/x86_64/media/nonfree/updates


Code: Select all

rfkill list all
0: tpacpi_bluetooth_sw: Bluetooth
   Soft blocked: no
   Hard blocked: no
1: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
2: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no


Code: Select all

 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host noprefixroute
       valid_lft forever preferred_lft forever
2: enp0s31f6: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 84:ba:59:5d:f9:f4 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether c8:6e:08:4f:83:7d brd ff:ff:ff:ff:ff:ff


Code: Select all

systemctl status network.service -al -n25
network.service - LSB: Bring up/down networking
     Loaded: loaded (/etc/rc.d/init.d/network; generated)
     Active: inactive (dead)
       Docs: man:systemd-sysv-generator(8)

Code: Select all

journalctl -ab | grep -iE "fw|firmware|iwl|wire|80211"
Mar 30 21:46:33 localhost.localdomain kernel: [Firmware Bug]: TSC ADJUST: CPU0: -7336504823 force to 0
Mar 30 21:46:33 localhost.localdomain kernel: [Firmware Bug]: TSC ADJUST differs within socket(s), fixing all errors
Mar 30 21:46:33 localhost.localdomain kernel: ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
Mar 30 21:46:33 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2
Mar 30 21:46:33 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2
Mar 30 21:46:33 localhost.localdomain systemd[1]: systemd-pcrmachine.service was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 30 21:46:34 localhost.localdomain kernel: cfg80211: Loading compiled-in X.509 certificates for regulatory database
Mar 30 21:46:34 localhost.localdomain kernel: Intel(R) Wireless WiFi driver for Linux
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id 0x1080800 wfpm id 0x80005b20
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: PCI dev 7e40/0090, rev=0x441, rfid=0x2010d000
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.88.3.1
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: loaded firmware version 83.d24e06ed.0 ma-b0-gf-a0-83.ucode op_mode iwlmvm
Mar 30 21:46:34 localhost.localdomain kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Mar 30 21:46:34 localhost.localdomain kernel: Bluetooth: hci0: Found device firmware: intel/ibt-0180-0041.sfi
Mar 30 21:46:34 localhost.localdomain kernel: Bluetooth: hci0: Firmware Version: 171-18.24
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x441
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: Not valid error log pointer 0x002798A8 for RT uCode
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x1f
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x80
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: loaded PNVM version 35148b80
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
Mar 30 21:46:34 localhost.localdomain kernel: psmouse serio1: trackpoint: Elan TrackPoint firmware: 0x00, buttons: 3/3
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3: base HW address: c8:6e:08:4f:83:7d
Mar 30 21:46:34 localhost.localdomain systemd[1]: systemd-pcrmachine.service was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 30 21:46:34 localhost.localdomain kernel: iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
Mar 30 21:46:35 localhost.localdomain kernel: Bluetooth: hci0: Waiting for firmware download to complete
Mar 30 21:46:35 localhost.localdomain kernel: Bluetooth: hci0: Firmware loaded in 1695246 usecs
Mar 30 21:46:36 localhost.localdomain systemd[1]: systemd-pcrphase-sysinit.service was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 30 21:46:36 localhost.localdomain systemd[1]: systemd-pcrphase.service was skipped because of an unmet condition check (ConditionPathExists=/sys/firmware/efi/efivars/StubPcrKernelImage-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f).
Mar 30 21:46:36 localhost.localdomain kernel: Bluetooth: hci0: Firmware timestamp 2024.18 buildtype 1 build 3243
Mar 30 21:46:36 localhost.localdomain systemd[1]: Startup finished in 11.442s (firmware) + 5.794s (loader) + 1.737s (kernel) + 2.666s (userspace) = 21.642s.


Moved and edited topic. ~Germ

[doktor5000]

What is the actual symptom that it does not boot? You probably don't get a graphical session, no? Or does it directly end in recovery mode?

The wireless/bluetooth chipset should not cause that by itself, but it would be helpful to see complete journalctl logs to determine the cause.

[morgano]

Note: It is not uncommon for kernel to report issues with firmware, but the system works well anyway.

We see the command line works, and you wrote you have updated the system.
I assume you mean it do not boot up to desktop login.
So you updated using command line?
And desktop never worked?

Do the system try to go to desktop login and fail (maybe wrong graphics driver), or just lands you at the prompt (maybe not set to load a desktop)?

Some of this may help then
https://wiki.mageia.org/en/How_to_chang ... hic_driver
https://wiki.mageia.org/en/Setup_the_graphical_server

[dude]

Dear morgano, dear doktor5000

I have attached the full journalctl from the last failed boot this morning. I have also attached a list of all installed packages (not sure this helps, but hey...).

Sorry about my unclear statements! Some clarifications and answers to your questions, I hope:

(a) I updated the system during the installation process, when asked to enable networking to retrieve updates. The installation has worked fine. I did not update via the command line.
(b) Desktop never worked on this PC (neither after full ISO install, netinstall, nor from Live medium). The system has never made it to a login screen. I have tried with Plasma and Xfce.
(c) The system tries to go to Desktop (Plasma or Xfce), but does not get there. I do not get a graphical session. It has also never entered command line or rescue mode automatically.
(d) The only way to get a command line after installing Mageia 9, until now, has been to enter recovery mode from the grub2 menu. Then, I can use the command line in recovery mode without problems
(e) As far as I can tell, the boot behaviour is very repeatable: it seems to be the same at every boot, I have not noticed any difference.

Thanks so much for your help!

[dude]

I have tried to change the graphical driver (using drakconf from the recovery mode command line) from "Vendor|Intel|Kernel mode setting (Xorg modesetting)" to "Xorg|vesa", as mentioned in the link posted by morgano. This has not changed the boot behaviour.

I was probably wrong about WiFi being the issue, as doktor5000 has mentioned.

Not sure this is relevant, but journalctl also shows that my PC encounters errors like these:

2025-04-01T07:06:41+0200 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: enabling device (0000 -> 0002)
2025-04-01T07:06:41+0200 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_fw_request(): Failed to request firmware: -2
2025-04-01T07:06:41+0200 localhost.localdomain kernel: fbcon: Taking over console
2025-04-01T07:06:41+0200 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_dev_init(): Failed to initialize firmware: -2
2025-04-01T07:06:41+0200 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: [drm] ivpu_hw_37xx_power_down(): VPU not idle during power down
2025-04-01T07:06:41+0200 localhost.localdomain kernel: intel_vpu 0000:00:0b.0: Failed to initialize VPU device: -2

I see that there are quite some posts in various Linux distro fora about Intel's Neural Processing Unit (NPU) or "Versatile Processing Unit (VPU)", which apparently has caused "problems" on other distributions.

[doktor5000]

NPU/VPU is not relevant. You issue is pretty clearly explained in the log:

Code: Select all

2025-04-01T07:06:41+0200 localhost.localdomain kernel: i915 0000:00:02.0: Your graphics device 7d45 is not properly supported by i915 in this
                                                       kernel version. To force driver probe anyway, use i915.force_probe=7d45
                                                       module parameter or CONFIG_DRM_I915_FORCE_PROBE=7d45 configuration option,
                                                       or (recommended) check for kernel updates.

As this also happens with the most recent cauldron kernel, you should create a bugreport and request an update of the i915 driver and it's dependencies as it prevents booting on recent hardware.
https://wiki.mageia.org/en/How_to_report_a_bug_properly

Also see some upstream explanation about this: https://github.com/intel/compute-runtime/issues/811 - from what I understand if you use some kernel after 6.8 you're fine.
Official list says you need kernel 6.7 at least: https://dgpu-docs.intel.com/devices/hardware-table.html

[dude]

Thanks a lot, doktor! I will file a bug report.

Should I update the title of this thread and the first post somwhat? They do not reflect properly the real issue.

[doktor5000]

I've changed the thread title. It's not that important as you have all the relevant information in post so it should be found via search function either way.

[Germ]

Link to bug report:
https://bugs.mageia.org/show_bug.cgi?id=34160