Lenovo ThinkPad P16 Gen 2 Upgraded to Fedora 42?

I have a Lenovo ThinkPad P16 Gen 2 with 128 GB Ram and 8 TB of internal NVME storage. It’s pretty beefy. I have been a Fedora Linux Power User for several years, a former CentOS User before that for many years and recently a former SE for Red Hat Software. I have had many Lenovo laptops running Fedora and CentOS and they have always worked very well. I retired in 2024 and purchased this Lenovo ThinkPad P16 Gen 2 Model in December 2024 so it’s not quite a year old which may be a reason for my issues. Anyway, when I received this unit in December 2024, I built it with the then Stable Fedora Release at that time which I think might have been Fedora 40. Everything has worked very well after multiple “dnf updates” about every two weeks to stay fairly current and secure. Throughout the year, I then decided to upgrade to Fedora Release 41, after monitoring it’s progress to GA, unaware that I was crossing over into unsupported territory! It also has worked very well up to recently even after multiple “dnf updates” about every two weeks to stay fairly current and secure. According to my “dnf history list” command, on 10-19-2025 while on the Fedora 41 Release, I did a “dnf update” and days later noticed that my Bluetooth no longer worked? I didn’t notice it at first so I later suspected that I had a hardware failure so I contacted Lenovo Support since I had a Premier Support Contract. After going back and forth a couple of times with their Support personnel for things for me to try, they pointed me to this information below which says that Lenovo has only Certified up to Fedora Release 40 on this laptop platform! Bummer! Looks like I got a little ahead of myself by already be utilizing Fedora Release 41 before it was tested on this laptop. There is no Docking Hardware involved here for now.

image

As per this table, I downloaded the Live Fedora 40 image here on this table, created a Live Bootable USB stick, booted it and verified that my Bluetooth now worked. This now lets Lenovo Support off the hook since I was now on an unsupported/untested Fedora Release as verified via the Fedora Live Release 40 USB stick that my Bluetooth now worked. Now my last Full Backup was dated 9-29-2025, which was still on the Fedora 41 Release but everything at least worked at that point, so I had a decision to make. Do I either try to reverse the “dnf updates” to a point where everything worked or possibly just upgrade to Release 42 which was now GA since April of 2025? At this point, I decided to do both an incremental Backup dated 10-20-2025 and a separate Full Backup dated 10-23-2025. Since I previously had successes upgrading to newer stable Releases on previous Lenovo laptops, I decided to go that route and upgraded to Release 42. My problems then worsened beyond just the Bluetooth no longer working, I encountered Suspend no longer functioning as well as various system hangs when connecting to my external monitor. This Fedora 42 upgrade turned out to be a Bad decision. So now rather than trying to troubleshoot this scenario myself, I decided to revert to my Full Backup dated 10-23-2025. The backup restoration worked perfectly and I was now back to the point before I upgraded to Release 42. At least, I thought I was was? So all the data was as expected as per the restoration to the Full Backup dated 10-23-2025 but my Bluetooth still did not work, my Suspend still did not function and I would lockup after connecting to my external monitor? So my question is, it appears that the “dnf update” command updates not only the software packages on the NVME storage devices but also in the firmware as well that won’t be reverted to the state in my Full Backup dated 10-23-2025 because it is located in firmware somewhere and not on the NVME storage devices? Is that a true statement and would this result in my experience? Do you Guys agree with my conclusion here? If so, what would you recommend? Will Lenovo and Fedora eventually support Fedora 42 based upon your experiences?

1 Like

Gnome software updates some firmware, but dnf update does not.

Is your computer part of the ‘Fedora Ready’ program between Fedora and Lenovo? I think there is a proposal to make such computers be maintained to the latest release, but in reality we see this a lot with Lenovos.

The cli command for that is fwupdmgr --help

To see some possibilities to update see: fwupdmgr get-devices

1 Like

Problems with BlueTooth, networking, and sound are not unusual after major linux updates. I have learned to have USB dongles to use while waiting for vendor firmware updates and/or kernel bug fixes. You can use the LHDB to search for your BT hardware to see if others are having problems. Sometimes there are user comments with workarounds.

1 Like

Not being able to suspend my laptop is a major obstacle for me! Any ideas on how to do that? After I restored my last Full Backup dated 10-23-2025, I’m very surprised that I didn’t regain that functionality because I thought it functioned at that point? I do have another Full Backup dated 9-29-2025 where I was positive I had this functionality. Do you Guys think I should revert to that Backup or do you think there is an easier way to regain this Suspend functionality? Maybe revert system firmware back to an earlier version perhaps? I’m assuming that system firmware would be the best option to regain functionality that existed before my Upgrade to Fedora 42? You Guys agree?

Firmware or Kernel. If you have been updating with dnf update, then you would had to run another command to update firmware.

So try older kernels, possibly with a F40 iso installed on a live USB. You can find these still on some mirrors via mirrormanager.fedoraproject.org

If it is the Kernel, file a bug at bugzilla.redhat.com

It is difficult to say that F42 is the culprit. However reading your description, gives hope to fix it while digging into it and search new drivers.
It might be a good idea to use the live iso to check your gear first, if we do release a new version of fedora.

What I would do is to give more information about your docking station and about your hardware in general.
Inxi -Fzxx gives a quite good overview of your system. Then you could share the output with us.

If you have frequent problems with your Bluetooth, it might be an idea to change the Wifi adapter if the BT chip is on it. Do hardware check as @gnwiii proposed.

The firmware might be on your NVME, it gets written into the EFI partition. To remove that you would have to create the partition newly. Before that do the checks and deliver us the info’s that we can help you debug.

Please create a F43 Live ISO and have a look if you face the same issues.

The LTS Kernel might be a alternative if you prefer a system with less kernel updates.

But then CentOS or Alma Linux would be a good alternative. This way you would not have to follow the fast forward way we do on Fedora.

Sorry for the delay. I was on the road. So today, I created Live USB sticks for Fedora 41, 42 and 43. I tried them all with the same results. They all worked fine with no failures of Bluetooth, my Suspend worked fine and connecting an external monitor worked fine as well! I was incorrect in saying I had a Docking Station in the mix, I do not. I could not see any failures in operation whatsoever! So here is the output for the inxi -Fzxx command:

inxi -Fzxx
System:
Kernel: 6.17.4-100.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc v: 14.3.1
Desktop: Cinnamon v: 6.4.9 tk: GTK v: 3.24.43 wm: Muffin dm: 1: GDM
2: LightDM note: stopped Distro: Fedora Linux 41 (Workstation Edition)
Machine:
Type: Laptop System: LENOVO product: 21FACTO1WW v: ThinkPad P16 Gen 2
serial: Chassis: type: 10 serial:
Mobo: LENOVO model: 21FACTO1WW serial:
part-nu: LENOVO_MT_21FA_BU_Think_FM_ThinkPad P16 Gen 2 UEFI: LENOVO
v: N3TET61W (1.61 ) date: 08/22/2025
Battery:
ID-1: BAT0 charge: 94.3 Wh (97.0%) condition: 97.2/93.5 Wh (103.9%)
volts: 12.7 min: 11.5 model: SMP 5B11M90090 serial: status: full
CPU:
Info: 24-core (8-mt/16-st) model: 13th Gen Intel Core i9-13980HX bits: 64
type: MST AMCP arch: Raptor Lake rev: 1 cache: L1: 2.1 MiB L2: 32 MiB
L3: 36 MiB
Speed (MHz): avg: 800 min/max: 800/5400:5600:4000 cores: 1: 800 2: 800
3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 800 10: 800 11: 800 12: 800
13: 800 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800 21: 800
22: 800 23: 800 24: 800 25: 800 26: 800 27: 800 28: 800 29: 800 30: 800
31: 800 32: 800 bogomips: 154828
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Raptor Lake-S UHD Graphics vendor: Lenovo driver: i915
v: kernel arch: Xe ports: active: eDP-1 empty: DP-1, DP-2, HDMI-A-1,
HDMI-A-2, HDMI-A-3 bus-ID: 00:02.0 chip-ID: 8086:a788
Device-2: Chicony Integrated Camera driver: uvcvideo type: USB rev: 2.0
speed: 480 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 04f2:b74f
Device-3: Logitech BRIO Ultra HD Webcam driver: snd-usb-audio,uvcvideo
type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-7.2:7
chip-ID: 046d:085e
Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8 driver: X:
loaded: modesetting alternate: fbdev,vesa dri: iris gpu: i915 display-ID: :0
screens: 1
Screen-1: 0 s-res: 2560x1600 s-dpi: 96
Monitor-1: eDP-1 model: AU Optronics 0x2ea5 res: 2560x1600 hz: 60 dpi: 189
diag: 406mm (16")
API: OpenGL v: 4.6 vendor: intel mesa v: 25.0.1 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel Graphics (RPL-S)
device-ID: 8086:a788
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo x11: xdriinfo, xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Raptor Lake High Definition Audio vendor: Lenovo
driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3 chip-ID: 8086:7a50
Device-2: Logitech BRIO Ultra HD Webcam driver: snd-usb-audio,uvcvideo
type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-7.2:7
chip-ID: 046d:085e
API: ALSA v: k6.17.4-100.fc41.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.2.8 status: active with: 1: wireplumber
status: active 2: pipewire-alsa type: plugin 3: pw-jack type: plugin
Server-3: PulseAudio v: 17.0 status: active with: pulseaudio-alsa
type: plugin
Network:
Device-1: Intel Raptor Lake-S PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:7a70
IF: wlp0s20f3 state: up mac:
IF-ID-1: tailscale0 state: unknown speed: -1 duplex: full mac: N/A
IF-ID-2: virbr0 state: up speed: 10000 Mbps duplex: unknown mac:
IF-ID-3: vnet0 state: unknown speed: 10000 Mbps duplex: full mac:
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 1-14:11 chip-ID: 8087:0033
Report: hciconfig ID: hci0 rfk-id: 3 state: up address: bt-v: 5.4
lmp-v: 13 sub-v: 3085
Drives:
Local Storage: total: 7.45 TiB used: 943.6 GiB (12.4%)
ID-1: /dev/nvme0n1 vendor: KIOXIA model: N/A size: 3.73 TiB
speed: 63.2 Gb/s lanes: 4 serial: temp: 50.9 C
ID-2: /dev/nvme1n1 vendor: KIOXIA model: N/A size: 3.73 TiB
speed: 63.2 Gb/s lanes: 4 serial: temp: 46.9 C
Partition:
ID-1: / size: 1.82 TiB used: 943.21 GiB (50.7%) fs: btrfs dev: /dev/dm-0
mapped: luks-c7bb61e3-3f00-4e9f-a656-45bb067f48d3
ID-2: /boot size: 973.4 MiB used: 376 MiB (38.6%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.4 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 1.82 TiB used: 943.21 GiB (50.7%) fs: btrfs
dev: /dev/dm-0 mapped: luks-c7bb61e3-3f00-4e9f-a656-45bb067f48d3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 69.0 C mobo: 64.0 C
Fan Speeds (rpm): fan-1: 0 fan-2: 3063
Info:
Memory: total: 128 GiB note: est. available: 125.45 GiB
used: 20.21 GiB (16.1%)
Processes: 679 Power: uptime: 47m wakeups: 0 Init: systemd v: 256
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 94
Compilers: clang: 20.1.2 alt: 17/18 gcc: 14.3.1 Shell: Bash v: 5.2.32
running-in: gnome-terminal inxi: 3.3.38

When I booted from these Live USB Sticks I noticed with the lshw command the System Firmware was the same as if I booted from the internal drive. I updated to the 1.61 UEFI: LENOVO v: N3TET61W (1.61 ) date: 08/22/2025

On November 2nd, 2025, I used the Grub feature to boot to an alternate older kernel and now my Bluetooth and Suspend functions work as well as the connection to a directly connected monitor without any stability issues. Using any Grub Kernel selection newer than this, results in my issues returning. I also installed the hardware probe from the Fedora Hardware Hub, performed a Probe function and then uploaded the Probe afterwards.

The is the kernel that works for now via a Grub selection: Linux fedora 6.16.8-100.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 19 16:41:07 UTC 2025 x86_64 GNU/Linux

sudo -E hw-probe -all -upload

Probe for hardware … Ok

Reading logs … Ok

WARNING: Unknown vendor ‘320C’

Uploaded to DB, Thank you!

Probe URL: https://linux-hardware.org/?probe=45b3b1cf1c

Should I have any security concerns here by utilizing an older kernel for now?

So after using my system all day today, after determining that rebooting with an older kernel via the Grub menu now made it operationally stable, I have a couple of questions. I’m assuming it would not be wise to perform a “sudo dnf update” at this point because it could cause a FIFO situation where a new kernel gets loaded into Grub and pushes out the older kernel I need to operate in a stable environment, correct? Should I only perform Security Updates through the cockpit interface to stay secure? Should I assume that there will be better support for my Lenovo Mobile Workstation in the near future since I uploaded a Hardware Probe to the Fedora Hardware Probe Database? So my bluetooth works and pairs with my bluetooth headset as it did before, my laptop behaves now when I connect an external monitor directly to it and the Suspend functions as it should now as well. I am now at sudo uname -a
Linux fedora 6.16.8-100.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Fri Sep 19 16:41:07 UTC 2025 x86_64 GNU/Linux

Anything newer than this becomes problematic.

Thank you for your recommendations, your expertise and efforts here!

If you boot into a working kernel, update will never delete it while you are using it.

You can also look up how to increase the max kernels kept.

6.17.6 is out now, I dont know if it will fix your issue.

Uploading your hardware details is more to let other users know if the hardware works.
Bugs get looked at and fixed via bugzilla.redhat.com