Xe – Platforms
Currently, Xe is already functional and has experimental support for multiple platforms starting from Tiger Lake, with initial support in userspace implemented in Mesa (for Iris and Anv, our OpenGL and Vulkan drivers), as well as in NEO (for OpenCL and Level0).
During a transition period, platforms will be supported by both Xe and i915. However, the force_probe mechanism existent in both drivers will allow only one official and by-default probe at a given time.
For instance, in order to probe a DG2 which PCI ID is 0x5690 by Xe instead of i915, the following set of parameters need to be used:
i915.force_probe=!5690 xe.force_probe=5690
In both drivers, the ‘.require_force_probe’ protection forces the user to use the force_probe parameter while the driver is under development. This protection is only removed when the support for the platform and the uAPI are stable. Stability which needs to be demonstrated by CI results.
In order to avoid user space regressions, i915 will continue to support all the current platforms that are already out of this protection. Xe support will be forever experimental and dependent on the usage of force_probe for these platforms.
When the time comes for Xe, the protection will be lifted on Xe and kept in i915.
It shouldn’t be necessary, but maybe try using the force_probe parameter with your card’s PCI ID?
Addendum:
I think the following command would show something if they had:
$ diff <(modinfo -k 6.12.7-200.fc41.x86_64 -F alias i915) <(modinfo -k 6.12.8-200.fc41.x86_64 -F alias i915)
$
I guess after upgrade I not made straight a reboot. With the install of the dkms-r8168 something went wrong I believed first it is because of it. Removed dkms again while parts of the 6.12.8 has been removed and so … with the modules reinstalled everything is fine again.