Lenovo Legion 5 Pro

Hi, I have a problem with Linux support for my Lenovo Legion

My Spec:

LENOVO Legion 5 Pro 16IAH7H
CPU: Intel Core i7 Tetradeca Core Processor 12700H
GPU: Nvidia GeForce RTX 3070 Ti
RAM: 32 GB

I tried Fedora and Mint, and the problem with Fedora is I can’t shut down or restart my system. It’s just stuck in the process. Same for Mint but when I want to turn it on again I enter some weird menu about MOK management.

Does anyone have this problem? Does anyone know how to solve this?

Thanks!

It isn’t clear what this means. Does keyboard respond to caplock and numlock? Can you get a text console with <Ctrl Alt F3>? Can you connect from another system using ssh?

When reporting problems, you should provide enough detail to allow others with access to similar hardware to reproduce the issue:

  • make sure the problem still exists with all updates from Fedora and Lenovo (firmware) applied.

  • tell us if the system boots multiple OS’s or exclusively Fedora. whether you are using default Fedora Workstation (Xorg or Wayland Gnome), or some other Desktop environment.

  • post (as text using the </> button) the output from running inxi -Fzxx in a terminal. This provides precise details of the hardware configuration and the graphics driver being used. If you have installed Nvidia drivers, describe how those were installed.

  • look for relevant error messages using journalctl. It can take some effort to find filters that trim the output to just the relevant entries.

For us to understand that it would be nice to see an image. Doing so would allow us to know the exact message you see and possibly make suggestions.

Hi guys, for personal reasons I wasn’t able to post it soon. When I run journalctl I get this:

Mar 08 07:36:11 fedora kernel: microcode: updated early: 0x424 -> 0x42c, date = 2023-04-18
Mar 08 07:36:11 fedora kernel: Linux version 6.5.6-300.fc39.x86_64 (mockbuild@fe458d2eae0b4ff0bb0a00a41dbf974>
Mar 08 07:36:11 fedora kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.5.6-300.fc39.x86_64 root=UUID=90>
Mar 08 07:36:11 fedora kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and w>
Mar 08 07:36:11 fedora kernel: BIOS-provided physical RAM map:
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003d2c8fff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000003d2c9000-0x000000003dbc8fff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000003dbc9000-0x000000003f9defff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000003f9df000-0x0000000041a7efff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000041a7f000-0x0000000044a2efff] ACPI NVS
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000044a2f000-0x0000000044afefff] ACPI data
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000044aff000-0x0000000044afffff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000044b00000-0x0000000048ffffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000049200000-0x00000000493fffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000004a000000-0x00000000503fffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008afbfffff] usable
Mar 08 07:36:11 fedora kernel: NX (Execute Disable) protection: active
Mar 08 07:36:11 fedora kernel: efi: EFI v2.7 by INSYDE Corp.
Mar 08 07:36:11 fedora kernel: efi: ACPI=0x44afe000 ACPI 2.0=0x44afe014 TPMFinalLog=0x44966000 SMBIOS=0x40086>
Mar 08 07:36:11 fedora kernel: random: crng init done
Mar 08 07:36:11 fedora kernel: efi: Remove mem88: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
lines 1-27...skipping...
Mar 08 07:36:11 fedora kernel: microcode: updated early: 0x424 -> 0x42c, date = 2023-04-18
Mar 08 07:36:11 fedora kernel: Linux version 6.5.6-300.fc39.x86_64 (mockbuild@fe458d2eae0b4ff0bb0a00a41dbf9744) (gcc (GCC) 13.2.1 20230918 (Red Hat 13.2.1-3), GNU ld version 2.40-13.fc39) #1 SMP PREEMPT_DYNAM>
Mar 08 07:36:11 fedora kernel: Command line: BOOT_IMAGE=(hd1,gpt2)/vmlinuz-6.5.6-300.fc39.x86_64 root=UUID=903a2863-26da-4470-adb6-e7a713a5b658 ro rootflags=subvol=root rhgb quiet
Mar 08 07:36:11 fedora kernel: x86/split lock detection: #AC: crashing the kernel on kernel split_locks and warning on user-space split_locks
Mar 08 07:36:11 fedora kernel: BIOS-provided physical RAM map:
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000000100000-0x000000003d2c8fff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000003d2c9000-0x000000003dbc8fff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000003dbc9000-0x000000003f9defff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000003f9df000-0x0000000041a7efff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000041a7f000-0x0000000044a2efff] ACPI NVS
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000044a2f000-0x0000000044afefff] ACPI data
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000044aff000-0x0000000044afffff] usable
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000044b00000-0x0000000048ffffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000049200000-0x00000000493fffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x000000004a000000-0x00000000503fffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000fe010000-0x00000000fe010fff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Mar 08 07:36:11 fedora kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008afbfffff] usable
Mar 08 07:36:11 fedora kernel: NX (Execute Disable) protection: active
Mar 08 07:36:11 fedora kernel: efi: EFI v2.7 by INSYDE Corp.
Mar 08 07:36:11 fedora kernel: efi: ACPI=0x44afe000 ACPI 2.0=0x44afe014 TPMFinalLog=0x44966000 SMBIOS=0x40086000 MEMATTR=0x38def018 ESRT=0x38e03a98 MOKvar=0x40085000 RNG=0x44a3a018 TPMEventLog=0x38999018 
Mar 08 07:36:11 fedora kernel: random: crng init done
Mar 08 07:36:11 fedora kernel: efi: Remove mem88: MMIO range=[0xc0000000-0xcfffffff] (256MB) from e820 map
Mar 08 07:36:11 fedora kernel: e820: remove [mem 0xc0000000-0xcfffffff] reserved
Mar 08 07:36:11 fedora kernel: efi: Not removing mem89: MMIO range=[0xfe010000-0xfe010fff] (4KB) from e820 map
Mar 08 07:36:11 fedora kernel: efi: Remove mem91: MMIO range=[0xff000000-0xffffffff] (16MB) from e820 map
Mar 08 07:36:11 fedora kernel: e820: remove [mem 0xff000000-0xffffffff] reserved
Mar 08 07:36:11 fedora kernel: secureboot: Secure boot disabled
Mar 08 07:36:11 fedora kernel: SMBIOS 3.3 present.
Mar 08 07:36:11 fedora kernel: DMI: LENOVO 82RF/LNVNB161216, BIOS J2CN56WW 09/18/2023
Mar 08 07:36:11 fedora kernel: tsc: Detected 2700.000 MHz processor
Mar 08 07:36:11 fedora kernel: tsc: Detected 2688.000 MHz TSC
Mar 08 07:36:11 fedora kernel: [Firmware Bug]: TSC ADJUST: CPU0: -4471825072 force to 0
Mar 08 07:36:11 fedora kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Mar 08 07:36:11 fedora kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Mar 08 07:36:11 fedora kernel: last_pfn = 0x8afc00 max_arch_pfn = 0x400000000
Mar 08 07:36:11 fedora kernel: MTRR map: 5 entries (3 fixed + 2 variable; max 23), built from 10 variable MTRRs
Mar 08 07:36:11 fedora kernel: x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WP  UC- WT  
Mar 08 07:36:11 fedora kernel: last_pfn = 0x44b00 max_arch_pfn = 0x400000000
Mar 08 07:36:11 fedora kernel: esrt: Reserving ESRT space from 0x0000000038e03a98 to 0x0000000038e03b20.
Mar 08 07:36:11 fedora kernel: e820: update [mem 0x38e03000-0x38e03fff] usable ==> reserved
Mar 08 07:36:11 fedora kernel: Using GB pages for direct mapping
Mar 08 07:36:11 fedora kernel: Incomplete global flushes, disabling PCID
Mar 08 07:36:11 fedora kernel: secureboot: Secure boot disabled
Mar 08 07:36:11 fedora kernel: RAMDISK: [mem 0x33d73000-0x3660dfff] 

My Legion is older, but try using a newer ISO that will include a newer kernel. Did you install the NVIDIA drivers from RPMFusion? The kernel command line there does not show the parameters that are added when the drivers are installed.
There are the Respins, which are updated ISOs here Index of /pub/alt/live-respins

We can’t help you without more information.

The journalctl output you provide looks like the first few lines of a normal startup. It is not unusual to see messages like kernel: [Firmware Bug]: TSC ADJUST: CPU0: -4471825072 force to 0 and most are rendered harmless by kernel workarounds. It does take some experimentation to filter the mass of data journalctl provides. Start with journalctl -b -p 3 to see high priority messages.

Hi guys,
I don’t know why but now everything works without any problems. Maybe some update fixed the problem.