Can not boot after latest update on Fedora 41

As the title says after today’s updates I rebooted and after bios starts I get a black screen.I restored the system back to 10/14/24 using timeshift.

Package                                     Arch   Version                 Reposit      Size
Upgrading:
 fwupd                                      x86_64 1.9.26-1.fc41           updates   7.5 MiB
   replacing fwupd                          x86_64 1.9.25-1.fc41           <unknow   7.4 MiB
 fwupd-plugin-flashrom                      x86_64 1.9.26-1.fc41           updates  35.8 KiB
   replacing fwupd-plugin-flashrom          x86_64 1.9.25-1.fc41           <unknow  35.8 KiB
 fwupd-plugin-modem-manager                 x86_64 1.9.26-1.fc41           updates 137.3 KiB
   replacing fwupd-plugin-modem-manager     x86_64 1.9.25-1.fc41           <unknow 133.3 KiB
 fwupd-plugin-uefi-capsule-data             x86_64 1.9.26-1.fc41           updates   2.0 MiB
   replacing fwupd-plugin-uefi-capsule-data x86_64 1.9.25-1.fc41           <unknow   2.0 MiB
 libjcat                                    x86_64 0.2.2-1.fc41            updates 217.8 KiB
   replacing libjcat                        x86_64 0.2.1-3.fc41            <unknow 213.8 KiB
 libnbd                                     x86_64 1.21.6-1.fc41           updates 453.7 KiB
   replacing libnbd                         x86_64 1.21.5-1.fc41           <unknow 453.7 KiB
 libxmlb                                    x86_64 0.3.20-1.fc41           updates 288.6 KiB
   replacing libxmlb                        x86_64 0.3.19-3.fc41           <unknow 288.7 KiB
 selinux-policy                             noarch 41.21-1.fc41            updates  31.4 KiB
   replacing selinux-policy                 noarch 41.20-1.fc41            <unknow  31.4 KiB
 selinux-policy-targeted                    noarch 41.21-1.fc41            updates  18.4 MiB
   replacing selinux-policy-targeted        noarch 41.20-1.fc41            <unknow  18.7 MiB

Transaction Summary:
 Upgrading:          9 packages
 Replacing:          9 package

Total size of inbound packages is 11 MiB. Need to download 11 MiB.
Is this ok [y/N]: n
Operation aborted by the user.


These are the updates and unless fwupd or the flash-plugin-flashrom I do not know what the issue is.

What gpu? If nvidia did the drivers fail to build?

Edit: no kernel in your updates, should not be gpu drivers.

Selinux would be worth investigating.

You could install the other updates one by one and check which one broke it.

Here is my system

System:
  Kernel: 6.11.3-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.43.1-2.fc41 clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=(hd2,gpt2)/vmlinuz-6.11.3-300.fc41.x86_64
    root=/dev/mapper/fedora_localhost--live-root ro
    rd.lvm.lv=fedora_localhost-live/root rhgb quiet
    rd.driver.blacklist=nouveau modprobe.blacklist=nouveau
  Console: pty pts/0 wm: gnome-shell DM: GDM v: 46.2 Distro: Fedora Linux 41
    (Workstation Edition Prerelease)
Machine:
  Type: Desktop Mobo: Gigabyte model: B450 AORUS ELITE serial: N/A
    uuid: 032e02b4-0499-054f-9006-600700080009 UEFI: American Megatrends LLC.
    v: F66 date: 03/22/2024
CPU:
  Info: model: AMD Ryzen 7 5700X socket: AM4 bits: 64 type: MT MCP arch: Zen 3+
    gen: 3 level: v3 note: check built: 2022 process: TSMC n6 (7nm)
    family: 0x19 (25) model-id: 0x21 (33) stepping: 0 microcode: 0xA20102B
  Topology: cpus: 1x dies: 1 clusters: 1 cores: 8 threads: 16 tpc: 2
    smt: enabled cache: L1: 512 KiB desc: d-8x32 KiB; i-8x32 KiB L2: 4 MiB
    desc: 8x512 KiB L3: 32 MiB desc: 1x32 MiB
  Speed (MHz): avg: 3600 min/max: 550/4663 boost: enabled
    base/boost: 3400/4650 scaling: driver: amd-pstate-epp governor: powersave
    volts: 1.1 V ext-clock: 100 MHz cores: 1: 3600 2: 3600 3: 3600 4: 3600
    5: 3600 6: 3600 7: 3600 8: 3600 9: 3600 10: 3600 11: 3600 12: 3600 13: 3600
    14: 3600 15: 3600 16: 3600 bogomips: 108808
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW;
    STIBP: always-on; RSB filling; PBRSB-eIBRS: Not affected; BHI: Not
    affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: NVIDIA TU117 [GeForce GTX 1650] vendor: ASUSTeK driver: nvidia
    v: 560.35.03 alternate: nouveau,nvidia_drm non-free: 550.xx+ status: current
    (as of 2024-09; EOL~2026-12-xx) arch: Turing code: TUxxx
    process: TSMC 12nm FF built: 2018-2022 pcie: gen: 1 speed: 2.5 GT/s
    lanes: 16 link-max: gen: 3 speed: 8 GT/s ports: active: none off: HDMI-A-1
    empty: DP-1,DVI-D-1 bus-ID: 08:00.0 chip-ID: 10de:1f82 class-ID: 0300
  Display: unspecified server: X.Org v: 24.1.3 with: Xwayland v: 24.1.3
    compositor: gnome-shell driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa alternate: nv
    gpu: nvidia,nvidia-nvswitch display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x286mm (20.00x11.26")
    s-diag: 583mm (22.95")
  Monitor-1: HDMI-A-1 mapped: HDMI-1 note: disabled model: Samsung S24C350
    serial: <filter> built: 2013 res: 1920x1080 hz: 60 dpi: 94 gamma: 1.2
    size: 520x290mm (20.47x11.42") diag: 598mm (23.5") ratio: 16:9 modes:
    max: 1920x1080 min: 640x480
  API: OpenGL v: 4.6.0 vendor: nvidia v: 560.35.03 glx-v: 1.4
    direct-render: yes renderer: NVIDIA GeForce GTX 1650/PCIe/SSE2
    memory: 3.91 GiB
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: NVIDIA vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3
    speed: 8 GT/s lanes: 16 bus-ID: 08:00.1 chip-ID: 10de:10fa class-ID: 0403
  Device-2: Advanced Micro Devices [AMD] Starship/Matisse HD Audio
    vendor: Gigabyte driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s
    lanes: 16 bus-ID: 0a:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.11.3-300.fc41.x86_64 status: kernel-api
    tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.5 status: off with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
    lanes: 1 port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
  Info: services: NetworkManager, smbd, wpa_supplicant
Drives:
  Local Storage: total: 5.46 TiB used: 651.76 GiB (11.7%)
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 970 EVO 500GB
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 2B2QEXE7 temp: 26.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 48d 11h cycles: 427
    read-units: 4,607,866 [2.35 TB] written-units: 7,929,761 [4.06 TB]
  ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Samsung model: SSD 980 1TB
    size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 1B4QFXO7 temp: 27.9 C
    scheme: GPT
  SMART: yes health: PASSED on: 6d 8h cycles: 159
    read-units: 1,962,993 [1.00 TB] written-units: 4,290,105 [2.19 TB]
  ID-3: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 860 EVO 500GB
    family: based SSDs size: 465.76 GiB block-size: physical: 512 B
    logical: 512 B sata: 3.2 speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 3B6Q temp: 21 C scheme: GPT
  SMART: yes state: enabled health: PASSED on: 3y 177d 16h cycles: 453
    written: 3.9 TiB
  ID-4: /dev/sdb maj-min: 8:16 vendor: Seagate model: BUP BK size: 3.64 TiB
    block-size: physical: 4096 B logical: 512 B type: USB rev: 3.0 spd: 5 Gb/s
    lanes: 1 mode: 3.2 gen-1x1 tech: N/A serial: <filter> fw-rev: 0108
    scheme: GPT
  SMART Message: A mandatory SMART command failed. Various possible causes.
Partition:
  ID-1: / raw-size: 70 GiB size: 69.97 GiB (99.95%) used: 13.64 GiB (19.5%)
    fs: xfs block-size: 512 B dev: /dev/dm-0 maj-min: 253:0
    mapped: fedora_localhost--live-root
  ID-2: /boot raw-size: 1024 MiB size: 1014 MiB (99.02%)
    used: 450.1 MiB (44.4%) fs: xfs block-size: 512 B dev: /dev/sda2 maj-min: 8:2
  ID-3: /boot/efi raw-size: 600 MiB size: 598.8 MiB (99.80%)
    used: 19.3 MiB (3.2%) fs: vfat block-size: 512 B dev: /dev/sda1 maj-min: 8:1
  ID-4: /home raw-size: 858.93 GiB size: 858.51 GiB (99.95%)
    used: 222.75 GiB (25.9%) fs: xfs block-size: 512 B dev: /dev/dm-1
    maj-min: 253:1 mapped: fedora_localhost--live-home
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: zram size: 8 GiB used: 256 KiB (0.0%) priority: 100
    comp: lzo-rle avail: lzo,lz4,lz4hc,842,zstd max-streams: 16 dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 34.6 C mobo: 25.0 C
  Fan Speeds (rpm): cpu: 0 fan-1: 0 fan-3: 0
  Power: 12v: N/A 5v: N/A 3.3v: 3.36 vbat: 3.33
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 3.04 GiB (9.7%)
  Processes: 431 Power: uptime: 23h 33m states: freeze,mem,disk suspend: deep
    avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
    suspend, test_resume image: 12.47 GiB services: gsd-power,upowerd
    Init: systemd v: 256 target: graphical (5) default: graphical
    tool: systemctl
  Packages: pm: rpm pkgs: N/A note: see --rpm tools: dnf,yum pm: flatpak
    pkgs: 0 Compilers: gcc: 14.2.1 Shell: Bash (su) v: 5.2.32
    running-in: gnome-terminal inxi: 3.3.36

It looked like today the only other update i had was google which I updated.When I get time I will try and update them one at a time as I will have to reboot after each one.It seemed when i updated and rebooted it hung at the bios startup screen then I hit esc to watch the boot and I did not see anything unusual before it went to a blank screen.

Check to see if the boot got as far as journactl. There might be details that point to the problem update.

It does not seem to show any logs I can find with errors after I updated.It seems after I restored with timeshift and rebooted the logs start from there which was yesterday and I did not see any errors although I may also not know what I am looking for and where to find it.

You should collect log data before running timeshift – “experience is the best teacher”.

Please do post the requested details when you get a chance. Since they are text, others with similar hardware and issues can find this topic with a web search, and “given enough eyeballs, all problems are shallow”.

I do not know what really happened to cause the issue.I ran the update today and rebooted to make sure that I could get all the logs as to what caused the issue.I rebooted and there was no issue as it rebooted normal.
Thank you for the help and suggestions and if anything happens again I will make sure to find the right logs or make sure I find the update that caused the issue.

If you are dual booting some issues only show up after running another OS. Sometimes vendor firmware doesn’t properly reset on warm boots. If you only have Fedora, warm and cold boots can sometimes behave differently.

In the future it could be useful to attempt data collection before time travelling. If you can get to the grub editor try editing the kernel command line:

  • remove rhgb quiet so you see error messages. In my opinion the rhgb quiet setting is for system where you just report any issues to IT. Permanently removing those 10 characters means you see errors and things stalling the boot right away.
  • try adding 3 at the end of the command line to boot to a text console. This lets you runjournalctl to see what is failing.

You can also try booting the Live USB. With that you can mount the system drive and use journalctl -D <directory> to see what if anything has been logged (see man journalctl).

1 Like