I’ve been upgrading Fedora releases a few times now and did the 35->36 this week.
I tested the Fedora 36 LiveCD and the i915 graphics work there.
But for some reason I only get llvmpipe in the upgrade.
There’s also an AMD Radeon HD 8750M… but I’ve never gotten that to work.
The boot options match those in the LiveCD, but glxinfo in the LiveCD shows the Intel Graphics.
It also looks like it has fallen back to the legacy radeon driver. Now, we need to figure out why. Can you paste the output of dmesg | grep -i -e amd -e radeon?
dmesg --level=err,warn
[ 0.142659] x86/cpu: SGX disabled by BIOS.
[ 0.178415] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
[ 0.178415] MMIO Stale Data CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/processor_mmio_stale_data.html for more details.
[ 0.178418] #5 #6 #7
[ 0.185612] ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
[ 1.034424] usb: port power management may be unreliable
[ 1.038022] i8042: Warning: Keylock active
[ 1.042097] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[ 1.660317] usb 1-10: config 0 interface 0 altsetting 0 bulk endpoint 0x81 has invalid maxpacket 64
[ 1.660328] usb 1-10: config 0 interface 0 altsetting 0 bulk endpoint 0x1 has invalid maxpacket 64
[ 1.660335] usb 1-10: config 0 interface 1 altsetting 0 bulk endpoint 0x82 has invalid maxpacket 64
[ 1.660340] usb 1-10: config 0 interface 1 altsetting 0 bulk endpoint 0x2 has invalid maxpacket 64
[ 1.660345] usb 1-10: config 0 interface 2 altsetting 0 bulk endpoint 0x83 has invalid maxpacket 64
[ 1.660350] usb 1-10: config 0 interface 2 altsetting 0 bulk endpoint 0x3 has invalid maxpacket 64
[ 1.660355] usb 1-10: config 0 interface 3 altsetting 0 bulk endpoint 0x84 has invalid maxpacket 64
[ 1.660359] usb 1-10: config 0 interface 3 altsetting 0 bulk endpoint 0x4 has invalid maxpacket 64
[ 1.676953] usb 1-10: config 0 descriptor??
[ 3.209503] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control method not found
[ 3.209638] acpi PNP0C14:02: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[ 3.214725] acpi PNP0C14:03: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:01)
[ 3.395047] ATPX version 1, functions 0x00000033
[ 3.395125] ATPX Hybrid Graphics
[ 3.825724] ATPX version 1, functions 0x00000033
[ 3.825780] ATPX Hybrid Graphics
[ 3.826980] kfd kfd: amdgpu: OLAND not supported in kfd
[ 5.217211] kauditd_printk_skb: 25 callbacks suppressed
[ 6.682689] systemd-sysv-generator[577]: SysV service '/etc/rc.d/init.d/livesys' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 6.682869] systemd-sysv-generator[577]: SysV service '/etc/rc.d/init.d/livesys-late' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.
[ 7.730169] i801_smbus 0000:00:1f.4: Accelerometer lis3lv02d is present on SMBus but its address is unknown, skipping registration
[ 8.258587] thermal thermal_zone8: failed to read out thermal zone (-61)
[ 8.297290] Bluetooth: hci0: Failed to send firmware data (-19)
[ 8.297303] Bluetooth: hci0: sending frame failed (-19)
[ 8.297310] Bluetooth: hci0: FW download error recovery failed (-19)
vulkaninfo --summary
WARNING: radv is not a conformant Vulkan implementation, testing use only.
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.204
Instance Extensions: count = 19
-------------------------------
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_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_surface : extension revision 25
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
Instance Layers: count = 1
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
Devices:
========
GPU0:
apiVersion = 4206803 (1.3.211)
driverVersion = 92278791 (0x5801007)
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 22.1.7
conformanceVersion = 1.3.0.0
deviceUUID = 7450d249-b957-0fa9-6c7b-d2e31620dbf5
driverUUID = 4bb42d09-c7a1-618d-f1d1-05403a44aa75
GPU1:
apiVersion = 4206803 (1.3.211)
driverVersion = 92278791 (0x5801007)
vendorID = 0x1002
deviceID = 0x6600
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD RADV OLAND
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 22.1.7
conformanceVersion = 0.0.0.0
deviceUUID = 00000000-0100-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU2:
apiVersion = 4206803 (1.3.211)
driverVersion = 1 (0x0001)
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 14.0.0, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 22.1.7 (LLVM 14.0.0)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3232-2e31-2e37-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
Interesting note. With the new kernel available today, the system will not boot and kicks to recovery.
5.18.19-100.fc35 works
5.18.19-200.fc36 works
5.19.4-200.fc36 will not boot
I just want basic 2D and 3D acceleration. GUI and video would be nice.
I just can’t find the different between my upgraded installation and the acceleration in the LiveUSB.
Found that after the upgrade, the default kernel options were not being added. So “ro rootflags=subvol=root” was missing from the recently installed kernels, preventing them from booting. FIxed.
Tried booting to 5.19.4-200.fc36 and 5.17.15-300.fc36, though the system still insists on using llvmpipe instead of the Intel driver.
Added the “radeon.si_support=0 amdgpu.si_support=1” options back in. Now the amdgpu is seen vulkan info… but it won’t use it. sigh
vulkaninfo --summary
WARNING: radv is not a conformant Vulkan implementation, testing use only.
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
vulkan: No DRI3 support detected - required for presentation
Note: you can probably enable DRI3 in your Xorg config
WARNING: lavapipe is not a conformant vulkan implementation, testing use only.
==========
VULKANINFO
==========
Vulkan Instance Version: 1.3.204
Instance Extensions: count = 19
-------------------------------
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_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_surface : extension revision 25
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
Instance Layers: count = 1
--------------------------
VK_LAYER_MESA_device_select Linux device selection layer 1.3.211 version 1
Devices:
========
GPU0:
apiVersion = 4206803 (1.3.211)
driverVersion = 92278791 (0x5801007)
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 22.1.7
conformanceVersion = 1.3.0.0
deviceUUID = 7450d249-b957-0fa9-6c7b-d2e31620dbf5
driverUUID = 4bb42d09-c7a1-618d-f1d1-05403a44aa75
GPU1:
apiVersion = 4206803 (1.3.211)
driverVersion = 92278791 (0x5801007)
vendorID = 0x1002
deviceID = 0x6600
deviceType = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName = AMD RADV OLAND
driverID = DRIVER_ID_MESA_RADV
driverName = radv
driverInfo = Mesa 22.1.7
conformanceVersion = 0.0.0.0
deviceUUID = 00000000-0100-0000-0000-000000000000
driverUUID = 414d442d-4d45-5341-2d44-525600000000
GPU2:
apiVersion = 4206803 (1.3.211)
driverVersion = 1 (0x0001)
vendorID = 0x10005
deviceID = 0x0000
deviceType = PHYSICAL_DEVICE_TYPE_CPU
deviceName = llvmpipe (LLVM 14.0.0, 256 bits)
driverID = DRIVER_ID_MESA_LLVMPIPE
driverName = llvmpipe
driverInfo = Mesa 22.1.7 (LLVM 14.0.0)
conformanceVersion = 1.3.1.1
deviceUUID = 6d657361-3232-2e31-2e37-000000000000
driverUUID = 6c6c766d-7069-7065-5555-494400000000
I’m not sure where to look next, so don’t wait for my answer with reinstallation. Maybe env will show you some environment variable forcing software rendering or you’ll find something in journalctl -b.
You’d have to use same kernel parameters as before while booting live iso to enable amdgpu and with it RADV - open source Vulkan driver - for AMD to show up as another Vulkan capable GPU.
RadeonSI (AMD OpenGL driver) uses LLVM to compile shaders, so it’s not the same as LLVMpipe used for software rendering on CPU. So both GPUs work correctly on the live systems.