mikael
December 7, 2025, 9:49pm
1
Many weeks ago when I rebooted (and updated) I was met by a kernel panic.
Whenever I try to boot the latest image (42.20251024.1) I get a kernel panic after grub.
42.20250908.1 (my only other version) boots fine. When I try to ujust upgrade from within that image and then reboot I’m still met by the same old 42.20251024.1 and 42.20250908.1 in grub. 42.20251024.1 kernel panics as usual and 42.20250908.1 boots.
Am I forever stuck with 42.20250908.1?
inffy
December 7, 2025, 9:53pm
2
You are probably on a image that is already end of life. So either her image or Nvidia.
Depending your (Nvidia) GPU you need to rebase to nvidia-open or to a main stable image.
1 Like
harold
December 7, 2025, 11:37pm
3
I had to re-image a few weeks ago from a no longer supported series. A simple command and a reboot. It was painless. You’ll need to stay in the same desktop and you can’t rebase from a faster to slower version. You can rebase from gts to stable or latest, but you can’t go from latest to stable or gts. I think that’s right.
inffy
December 8, 2025, 5:32am
4
Aurora doesn’t have GTS and oven if it would, there would be nothing stopping you move between them. Just like in Bluefin you can do it (move between GTS ↔ stable for example
2 Likes
mikael
January 1, 2026, 11:59am
5
Thanks! Seems like that was is. I have a 970M which is no longer supported. I did
sudo bootc switch --enforce-container-sigpolicy ghcr.io/ublue-os/aurora-dx-nvidia-open:stable
and it booted fine with the latest updated snapshot.
However, “skipping this driver” below does not seem good? Quakespasm says it is using my Intel HD Graphics 530. Does *-nvidia-open:stable support the 970M?
vulkaninfo --summary
WARNING: [Loader Message] Code 0 : Path to given binary /usr/lib64/libGLX_nvidia.so.590.48.01 was found to differ from OS loaded path /usr/lib64/libGLX_nvidia.so.0
WARNING: [Loader Message] Code 0 : terminator_CreateInstance: Received return code -3 from call to vkCreateInstance in ICD /usr/lib64/libvulkan_dzn.so. Skipping this driver.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.4.328
Instance Extensions: count = 27
-------------------------------
VK_EXT_acquire_drm_display : extension revision 1
VK_EXT_acquire_xlib_display : extension revision 1
VK_EXT_debug_report : extension revision 10
VK_EXT_debug_utils : extension revision 2
VK_EXT_direct_mode_display : extension revision 1
VK_EXT_display_surface_counter : extension revision 1
VK_EXT_headless_surface : extension revision 1
VK_EXT_layer_settings : extension revision 2
VK_EXT_surface_maintenance1 : extension revision 1
VK_EXT_swapchain_colorspace : extension revision 5
VK_KHR_device_group_creation : extension revision 1
VK_KHR_display : extension revision 23
VK_KHR_external_fence_capabilities : extension revision 1
VK_KHR_external_memory_capabilities : extension revision 1
VK_KHR_external_semaphore_capabilities : extension revision 1
VK_KHR_get_display_properties2 : extension revision 1
VK_KHR_get_physical_device_properties2 : extension revision 2
VK_KHR_get_surface_capabilities2 : extension revision 1
VK_KHR_portability_enumeration : extension revision 1
VK_KHR_surface : extension revision 25
VK_KHR_surface_maintenance1 : extension revision 1
VK_KHR_surface_protected_capabilities : extension revision 1
VK_KHR_wayland_surface : extension revision 6
VK_KHR_xcb_surface : extension revision 6
VK_KHR_xlib_surface : extension revision 6
VK_LUNARG_direct_driver_loading : extension revision 1
VK_NV_display_stereo : extension revision 1
Instance Layers: count = 3
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.4.303 version 1
VK_LAYER_NV_optimus NVIDIA Optimus layer 1.4.325 version 1
VK_LAYER_NV_present NVIDIA Presentation Layer 1.4.325 version 1
Devices:
========
GPU0:
apiVersion = 1.4.318
driverVersion = 25.2.7
vendorID = 0x8086
deviceID = 0x191b
deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU
deviceName = Intel(R) HD Graphics 530 (SKL GT2)
driverID = DRIVER_ID_INTEL_OPEN_SOURCE_MESA
driverName = Intel open-source Mesa driver
driverInfo = Mesa 25.2.7
conformanceVersion = 1.4.0.0
deviceUUID = 86801b19-0600-0000-0002-000000000000
driverUUID = 89861029-0ee7-8073-391a-c857cd43e0aa
GPU1:
apiVersion = 1.4.318
driverVersion = 25.2.7
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 21.1.6, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 25.2.7 (LLVM 21.1.6)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3235-2e32-2e37-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
mikael
January 1, 2026, 12:49pm
6
Here are some possibly interesting outputs:
lspci -k | grep -A 2 -i "VGA"
00:02.0 VGAcompatible controller: Intel Corporation HD Graphics 530 (rev 06)
Subsystem: Acer Incorporated [ALI] Device 1051
Kernel driver in use: i915
--
01:00.0 VGAcompatible controller: NVIDIA Corporation GM204M [GeForce GTX 960 OEM / 970M] (rev a1)
Subsystem: Acer Incorporated [ALI] Device 1051
Kernel modules: nouveau, nvidia_drm, nvidia
nvidia-smi
NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
lsmod | grep nvidia gives no output.
glxinfo | grep "OpenGL renderer"
OpenGL renderer string: Mesa Intel(R) HD Graphics 530 (SKL GT2)
inffy
January 1, 2026, 1:04pm
7
you wont be able to use your nvidia gpu with the nvidia-open image. The nvidia-open image only supports gpus 16XX and up.
We don’t have support for the older gpus anymore on Aurora.
mikael
January 1, 2026, 1:18pm
8
Oh, I see. Would you consider supporting it? Bazzite Desktop does:
inffy
January 1, 2026, 1:19pm
9
No we won’t have support for those anymore. Those images were dropped with F43 images.
mikael
January 1, 2026, 2:04pm
10
Thanks for confirming. I’m rebasing to bazzite-nvidia:stable.