Freeze at boot

Aurora
1

Hello,

I have been using Aurora with great success until version 43.20260106.
But with a newer version it freezes at start on the aurora page before asking for password.
Using the gru menu to get back to version 43.20260106 managed to get it working again.
I did rpm-ostree rollback to have 43.20260106 as default boot version.
However, any new version got me to the same problem and I did finally disable the updates.
How could I troubleshoot what s going on with the latest updates ? Did anyone experience the same problem ?

Thanks for any help.

Can't update from bluefin gts-42.20260106 upwards (Bug: kernel NULL pointer dereference)
2

Hi Biff and welcome. You might get some clues as to the cause of the regression from the boot logs. Could be that a kernel driver update is bad. Boot back into your old system and check the logs.

3

Had the same issue, but only when my usb mouse was plugged in. I’ve seen others where having a monitor connected produces the same problem.
https://universal-blue.discourse.group/t/sddm-not-starting-if-usb-mouse-connected/11217

https://github.com/ublue-os/bazzite/issues/3376#issuecomment-3591905221

The solution for me was to:
create /etc/systemd/system/sddm.service.d/udev-settle-wait.conf
[Unit]
Wants=systemd-udev-settle.service
After=systemd-udev-settle.service

and reboot

4

Thank you for the welcome and for the advice!

5

Many thanks for the info ,I will get onto it.

Cheers

6

This is propably one of the race conditions that sddm is having.

We should get rid of them once Fedora 44 comes and removes sddm from KDE (replaced with plasma-login-manager)

7

Thanks all,
I have looked in the kernel boot logs and here are the errors I found :

Jan 29 11:20:51 aurora kernel: ACPI BIOS Error (bug): Could not resolve symbol [_SB.PCI0.GFX0.DD02._BCL], AE_NOT_FOUND (20250404/psargs-332)
Jan 29 11:20:51 aurora kernel: ACPI Error: Aborting method _SB.PCI0.PEG0.PEGP.DD02._BCL due to previous error (AE_NOT_FOUND) (20250404/psparse-529)

Jan 29 11:20:57 aurora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
Jan 29 11:20:57 aurora kernel: NVRM: No NVIDIA GPU found.
Jan 29 11:20:57 aurora kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 511
Jan 29 11:20:58 aurora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
Jan 29 11:20:58 aurora kernel: NVRM: No NVIDIA GPU found.
Jan 29 11:20:58 aurora kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 511
Jan 29 11:20:59 aurora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
Jan 29 11:20:59 aurora kernel: NVRM: No NVIDIA GPU found.
Jan 29 11:20:59 aurora kernel: nvidia-nvlink: Unregistered Nvlink Core, major device number 511
Jan 29 11:20:59 aurora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
Jan 29 11:20:59 aurora kernel: NVRM: No NVIDIA GPU found.

Jan 29 11:21:02 aurora systemd[1]: systemd-remount-fs.service: Main process exited, code=exited, status=1/FAILURE
Jan 29 11:21:02 aurora systemd[1]: systemd-remount-fs.service: Failed with result ‘exit-code’.
Jan 29 11:21:02 aurora systemd[1]: Failed to start systemd-remount-fs.service - Remount Root and Kernel File Systems.

Jan 29 11:21:28 Bert kernel: snd_hda_intel 0000:00:1b.0: IRQ timing workaround is activated for card #1. Suggest a bigger bdl_pos_adj.
Jan 29 11:21:29 Bert kernel: [drm:uvd_v3_1_hw_init [amdgpu]] ERROR amdgpu: UVD Firmware validate fail (-22).
Jan 29 11:21:29 Bert kernel: amdgpu 0000:01:00.0: amdgpu: resume of IP block <uvd_v3_1> failed -22
Jan 29 11:21:29 Bert kernel: amdgpu 0000:01:00.0: amdgpu: amdgpu_device_ip_resume failed (-22).

8

and then in the boot logs :

an 29 22:00:02 Bert kdeconnectd[2650]: Cannot find Bluez 5 adapter for device search false
Jan 29 22:00:32 Bert systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jan 29 22:00:32 Bert kdeconnectd[2650]: Cannot find Bluez 5 adapter for device search false
Jan 29 22:00:53 Bert plasmashell[2388]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:208: TypeError: Cannot read property ‘fullRepresentationItem’ of null
Jan 29 22:00:53 Bert plasmashell[2388]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:201: TypeError: Cannot read property ‘compactRepresentationItem’ of null
Jan 29 22:00:53 Bert plasmashell[2388]: file:///usr/share/plasma/plasmoids/org.kde.plasma.systemtray/contents/ui/items/PlasmoidItem.qml:24: TypeError: Cannot read property ‘toolTipMainText’ of null
Jan 29 22:00:54 Bert systemd[1979]: app-flatpak-org.mozilla.firefox-1018056901.scope: Consumed 1h 18min 35.700s CPU time, 2.3G memory peak.
Jan 29 22:01:02 Bert systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jan 29 22:01:02 Bert kdeconnectd[2650]: Cannot find Bluez 5 adapter for device search false
Jan 29 22:01:32 Bert systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jan 29 22:01:32 Bert kdeconnectd[2650]: Cannot find Bluez 5 adapter for device search false
Jan 29 22:02:00 Bert systemd[1979]: app-flatpak-org.mozilla.Thunderbird-945835555.scope: Consumed 4min 52.362s CPU time, 1.4G memory peak.
Jan 29 22:02:02 Bert systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jan 29 22:02:02 Bert kdeconnectd[2650]: Cannot find Bluez 5 adapter for device search false
Jan 29 22:02:04 Bert systemd[1979]: Started dbus-:1.3-org.kde.LogoutPrompt@0.service.
Jan 29 22:02:05 Bert ksmserver-logout-greeter[21249]: static bool KX11Extras::compositingActive() may only be used on X11
Jan 29 22:02:32 Bert systemd[1]: bluetooth.service - Bluetooth service was skipped because of an unmet condition check (ConditionPathIsDirectory=/sys/class/bluetooth).
Jan 29 22:02:32 Bert kdeconnectd[2650]: Cannot find Bluez 5 adapter for device search false
Jan 29 22:02:35 Bert systemd[1979]: Started dbus-:1.3-org.kde.Shutdown@0.service.
Jan 29 22:02:35 Bert systemd[1979]: dbus-:1.3-org.kde.LogoutPrompt@0.service: Consumed 524ms CPU time, 113M memory peak.
Jan 29 22:02:37 Bert xwaylandvideobridge[2656]: QObject::disconnect: Unexpected nullptr parameter

9

Hi Biff, has a usb bluetooth adaptor being pluged on your computer ?

10

Hi Joe

No I have double checked. The only USB used has been for my portable and an external hard drive.

Hope this helps.

Thanks

Biff

11

Hi there @biff , I’m also having problems with updating from my 43.20260106 release (but with Bluefin, see here https://universal-blue.discourse.group/t/cant-update-from-bluefin-gts-42-20260106-upwards-bug-kernel-null-pointer-dereference/11585). I’m suspecting something related to my AMD graphics card. Do you have one as well? What (temporarily) worked for me is rebasing to the latest branch (latest-43.20260131.1). Maybe worth a try for you? Good luck.

12

So if a latest streams build works and stable doesn’t, its might be a kernel regression that happens with the 6.17.x kernel. latest is already on 6.18.7 currently and the next CoreOS release should be tomorrow (3rd of Feb) which will bring 6.18.5 kernel.

13

Screenshot_20260202_180022
Screenshot_20260202_180022449×250 21.6 KB

Here is my hardware : no AMD graphic card
Did you rebuild you kernel yourself to rebase on latest branch ?

14

ok thanks, I will try tomorrow s update

15

you can just rebase to latest to test.

First pin your current image
sudo ostree admin pin 0

so it is kept safe and not getting removed by new updates.

Once that is done switch to latest stream
sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/aurora:latest

or if you use aurora-dx
sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/aurora-dx:latest

16

Interesting. The newest latest (latest-43.20260202.1) is working for me as well. @inffy when do you think will this latest version reach the stable (weekly) channel?

17

No, i just rebased with the ujust rebase-helper command from the terminal. There you can choose what you want to rebase to. But you can also use the commands @inffy mentioned.

18

Well coreOS releases every two weeks so to get the kernel that is currently on latest will taje atleast 2weeks.

3 Likes