Can't boot F43 with new kernel

Ask Fedora
,
1

Currently I have 3 non-rescue kernels:

6.18.16-200.fc43.x86_64
6.19.8-200.fc43.x86_64
6.19.7-200.fc43.x86_64

Only the oldest one (6.18.16) boots, the other 2 give a black screen, as if no display was detected. I’m concerned that as more updates come, I’ll eventually lose the only kernel that works.

Pressing Esc or trying to change tty (ctrl+alt+F[1-12]) don’t work. Booting with nomodeset or without rhgb also doesn’t work.

Since I use LUKS for disk encryption, I don’t know how to even look for any clues (logs) as I don’t even get to the decryption prompt.

I have Librem Mini v2 PC: Purism - – Librem Mini

It’s worked flawlessly with Fedora for years, but suddenly this problem. What can I do?

2

To not overwrite the working kernel, you can make it active and automatically bot with it. Remember to activate it again when updating a kernel. The kernel on which you log in, never gets overwritten.

List all installed kernels
--------------------------

To get the index number of all the installed kernels:

  sudo grubby --info=ALL | grep -E "^kernel|^index"

The output should be something like this:

index=0
kernel="/boot/vmlinuz-6.11.11-200.fc40.x86_64"
index=1
kernel="/boot/vmlinuz-6.11.10-200.fc40.x86_64"
index=2
kernel="/boot/vmlinuz-6.11.8-200.fc40.x86_64"
index=3
kernel="/boot/vmlinuz-0-rescue-6a0d0e8a953c43e682bd4f1a6e0143be"

Change the default kernel using index
-------------------------------------

Now we can change the default kernel by using the index number:

 sudo grubby --set-default-index=1

Verify the default kernel
-------------------------

Verify that the right kernel has been set as default:

   sudo grubby --default-title

The output will be the default kernel title:

Fedora Linux (6.11.10-200.fc40.x86_64) 40 (Workstation Edition)

When you install a new kernel, boot into it and test if your system works as it should. Otherwise you boot into the working Kernel and do the steps above again.

3

Black screen usually means a problem with GPU drivers.
Which GPU do you have?
If its nvidia has the drivers been built for the new kernels?

4 
Hardware Specifications  (https://puri.sm/products/librem-mini/)

Processor
Intel Core i7-10510U (Comet Lake), Active (fan) Cooling 4 Cores, 8 Threads, up to 4.9GHz

Graphics
Intel UHD Graphics 620

Memory
DDR4-2400, 2 SO-DIMM slot Max 64GB Support 1.2V DDR4 L2133/2400MHz

Storage
1 SATA III 6Gbps SSD/HDD (7mm) 1 M.2 SSD (SATA III/NVMe x4)

Video
1 HDMI 2.0 4K@60Hz 1 DisplayPort 1.2 4K@60Hz

USB Ports
USB 3.0
4 Ports
USB 2.0
2 Ports
TypeC 3.1
1 Port

Audio
3.5mm AudioJack (Mic-in & Headphone-out combo)

Networking
1 RJ45 (Gigabit Ethernet LAN), with optional Intel AX200 Wi-Fi 6 Module (2.4/5.0 GHz)

Bluetooth
Intel AX200 Bluetooth 5.2 (optional)

Power
1 Powerbutton, DC-IN Jack
5 
Intel UHD Graphics 620

I think it must have something to do with a regression.

As Kernel 6.18.16 still works.

6

Integrated Intel’s like ilikelinux said: https://www.intel.com/content/www/us/en/products/sku/196449/intel-core-i710510u-processor-8m-cache-up-to-4-90-ghz/specifications.html

Should I report this on Fedora’s bugzilla? Hopefully not upstream…

7

two easy fixes:

  1. Increase the number of kernels that the system retains… or
  2. remove the kernels that are not working (19.7 and 18.8)

Do you need support for 1. or 2.?

8

I’ve already done grubby --set-default=vmlinuz-6.18.16-200.fc43.x86_64.

Should I just wait for newer kernels and check one by one if they start working? Doesn’t seem like a good long term approach, especially if I need to ever reinstall

9

Yes - that’s how I would do it.

10

Your issue may need a firmware update. Others with the same hardware will also encounter the problem with recent kernels, so it is worth contacting the vendor or posting on vender forums. If a newer kernel does fix the issue, there are installer respins using current packages.

11

Turns out I can’t boot live Fedora 44 either, but replugging my DisplayPort cable solves it for current boot. I can then see the display. I can’t use HDMI because my PC doesn’t support it for 4K resolution.

On my old install, even replugging the DP cable doesn’t work with new kernel, but that’s mostly irrelevant as I should reinstall onto F44 anyway. However, I wonder if there is a permanent solution to this replug-every-time scenario.

I should probably first test this on my test USB drive install of F44. I’m afraid of suddenly not being able to revive the display even after replugging DP cable on runtime, as happens now for me on F43 7.x kernel.