Boot process stuck after upgrade from 39 to 40

Ask Fedora
, ,
1

Hi,
I just upgrade from 39 to 40. all upgrade process seems fine (after I remove incompatible package (just 1 package and it is relate with font)). But the boot the process (after upgrade) is stuck.
but if i go to previous kernel (which actually the same kernel version (I did upgrade kernel version first prior to upgrade the fedora), it works fine.
I have attach grub list and /etc/cmdline (boot using 2nd (index=1) kernel))

(i notice that the 1st kernel try to boot to kernel 6.10.3-200 …?? i thought available is the latest kernel is 6.10.3-10 …)

sudo grubby --info=ALL
[sudo] password for agun76:
index=0
kernel="/boot/vmlinuz-6.10.3-200.fc40.x86_64"
args="ro rootflags=subvol=root rhgb initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=no
uveau"
root="UUID=f1859066-b338-47a4-a628-da8bff7d0044"
initrd="/boot/initramfs-6.10.3-200.fc40.x86_64.img"
title="Fedora Linux (6.10.3-200.fc40.x86_64) 40 (KDE Plasma)"
id="548201f2a00d49c399cbd863bd1356ad-6.10.3-200.fc40.x86_64"
index=1
kernel="/boot/vmlinuz-6.10.3-100.fc39.x86_64"
args="ro rootflags=subvol=root rhgb initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=no
uveau"
root="UUID=f1859066-b338-47a4-a628-da8bff7d0044"
initrd="/boot/initramfs-6.10.3-100.fc39.x86_64.img"
title="Fedora Linux (6.10.3-100.fc39.x86_64) 39 (KDE Plasma)"
id="548201f2a00d49c399cbd863bd1356ad-6.10.3-100.fc39.x86_64"
index=2
kernel="/boot/vmlinuz-6.9.9-100.fc39.x86_64"
args="ro rootflags=subvol=root rhgb initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=no
uveau"
root="UUID=f1859066-b338-47a4-a628-da8bff7d0044"
initrd="/boot/initramfs-6.9.9-100.fc39.x86_64.img"
title="Fedora Linux (6.9.9-100.fc39.x86_64) 39 (KDE Plasma)"
id="548201f2a00d49c399cbd863bd1356ad-6.9.9-100.fc39.x86_64"

agun76@fedora:~$ cat /proc/cmdline 
BOOT_IMAGE=(hd2,msdos2)/vmlinuz-6.10.3-100.fc39.x86_64 root=UUID=f1859066-b338-47a4-a628-da8bff7d0044 ro rootflags=subvol=root rhgb initcall_blacklist=simpledrm_platform_driver_init nvidia-drm.modeset=1 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
agun76@fedora:~$ cat /etc/fedora-release 
Fedora release 40 (Forty)
agun76@fedora:~$ uname -r
6.10.3-100.fc39.x86_64
![grub-info|689x265](upload://mN5Ja8SsK5BX6drzAocg7mrD5gL.png)
![cmd-line|690x133](upload://9VaDZqKjguecPdVTc0rgFMqOX3e.png)

update 1 : even i try to update grub.cfg by remove rhgb , still it stuck …no screen process load or anything …

update 2 : i try to remove “nvidia-drm.modeset=1” from grub, but still boot process is stuck

agun76@fedora:~$ inxi -FGzz
System:
  Kernel: 6.10.3-100.fc39.x86_64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.1.3 Distro: Fedora Linux 40 (KDE Plasma)
Machine:
  Type: Desktop Mobo: Micro-Star model: PRO B660M-G DDR4 (MS-7D45) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.20
    date: 02/18/2022
CPU:
  Info: 12-core (8-mt/4-st) model: 12th Gen Intel Core i7-12700F bits: 64
    type: MST AMCP cache: L2: 12 MiB
  Speed (MHz): avg: 809 min/max: 800/4800:4900:3600 cores: 1: 800 2: 800
    3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 9: 900 10: 800 11: 800 12: 800
    13: 892 14: 800 15: 800 16: 800 17: 800 18: 800 19: 800 20: 800
Graphics:
  Device-1: NVIDIA GA106 [Geforce RTX 3050] driver: nvidia v: 555.58.02
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 24.1.2
    compositor: kwin_wayland driver: X: loaded: modesetting dri: nouveau
    gpu: nvidia resolution: 1: 1920x1080 2: 1920x1080
  API: EGL v: 1.5 drivers: nvidia,swrast,zink
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 555.58.02
    renderer: NVIDIA GeForce RTX 3050/PCIe/SSE2
  API: Vulkan v: 1.3.283 drivers: N/A surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Alder Lake-S HD Audio driver: snd_hda_intel
  Device-2: NVIDIA GA106 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.10.3-100.fc39.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active
Network:
  Device-1: Realtek RTL8125 2.5GbE driver: r8169
  IF: enp3s0 state: down mac: <filter>
  Device-2: Realtek 802.11ac NIC driver: rtw_8821cu type: USB
  IF: wlp0s20f0u7 state: up mac: <filter>
Bluetooth:
  Device-1: Realtek Bluetooth Radio driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: <filter> bt-v: 5.1
Drives:
  Local Storage: total: 2.29 TiB used: 835.06 GiB (35.7%)
  ID-1: /dev/nvme0n1 vendor: Toshiba model: N/A size: 476.94 GiB
  ID-2: /dev/sda vendor: Western Digital model: WD10EZEX-08WN4A0
    size: 931.51 GiB
  ID-3: /dev/sdb vendor: Samsung model: ST1000LM024 HN-M101MBB
    size: 931.51 GiB type: USB
Partition:
  ID-1: / size: 292.38 GiB used: 101.51 GiB (34.7%) fs: btrfs
    dev: /dev/nvme0n1p4
  ID-2: /boot size: 973.4 MiB used: 419.5 MiB (43.1%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19.1 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 292.38 GiB used: 101.51 GiB (34.7%) fs: btrfs
    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: 40.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 16 GiB available: 15.47 GiB used: 3.36 GiB (21.7%)
  Processes: 519 Uptime: 5m Shell: Bash inxi: 3.3.34

please help, many thanks

2

Please use the preformatted text button </> when copying text from your screen so it retains the on-screen formatting. It makes things much easier to read and understand.

I edited your post above to add the preformatted text tags for readability.

First off, you need to understand kernel naming.
f39 uses the kernel named 6.10.3-100.fc39.x86_64
while f40 uses the kernel named 6.10.3-200.fc40.x86_64

The -100 represents the next to latest fedora release while the -200 represents the current fedora release. Those numbers are different because that is the build number for the kernel. The kernels are actually the same in all other respects.

You said the boot process is stuck with the newer release but have provided no details about that. I also see from the kernel command line that you apparently are using an nvidia gpu.
First try this.
sudo akmods --force --rebuild --kernels 6.10.3-200.fc40.x86_64 to rebuild the driver for that f40 kernel. After that completes then try rebooting again to see if it will properly boot with the f40 kernel.

If booting still is not acceptable then post the details of what is happening so we can dig deeper into the cause.

1 Like
3

You highlight the text and hit </>. It took me quite a while before I figured that out.

2 Likes
4

Thanks Jeff for your response, after I rebuild the kernel : it works !!

actually I already saw the recommendation for similiar issue, but then I realize if I execute that command (without option kernel), it will impact to my existing kernel (which is f39) not the problem one (f40).

another question : should i return previous setting of grub : nvidia-drm.modeset=1 ?

again many thanks for your help !!

5

I have that option in my command line. Some say it is not needed, so I guess it may depend on your system exactly and not a confirmed yes or no.