I may try and write a walkthrough on how to enable it “my way”, despite certain things not being yet implemented for practical usage - though might take a look and implement some, when having lots of free time.
The crashing thing may be related to the fact that the graphics drivers gets loaded by dom0, rather than sys-gui-gpu and it has to be denylisted first (module_blacklist=i915).
I’ll paste what I wrote some time ago on the public chat:
The upgrade to 4.2 went smoothly! Furthermore, sys-gui-gpu works on my trusty T480!
Though I’m kinda confused - how do I do anything from sys-gui-gpu in the context of dom0? I’m primarily thinking about simple things like shutting down my laptop, but simply using a poweroff command results in a black screen. Or tweaking anything in dom0 without having to use
qubes.skip_autostartand removingmodule_blacklist=i915?
and later, after some more experiments:
The bad news
- Audio doesn’t work out-of-the-box, may be related due to the fact I haven’t touched anything related to audiovm
- Tray icons do not show up by default, need to manually recreate the application entries in templates, disposable templates and AppVMs
- 4.2-exclusive administrative graphical tools crash before they are fully loaded
- Only dom0 and sys-gui-gpu are visible, other qubes are not - need to manually run
$ qubes-prefs --set default_guivm sys-gui-gpu- On the XFCE4 taskbar in the “Windows Buttons” widget only “cute qube” icons showed up, that is no incoming-sanitized-colorized X11 application icons
- Some anomalies related to power management:
- brightness options are not persistent, the default “very dim” level is used
- selecting the Power Manager Plugin setting “Show label: Percentage” does nothing
The good news
- When from dom0 the policy
qubes.InputMouse * sys-usb sys-gui-gpu askis written, then input proxying works- Mirroring and extending displays works with HDMI
- Emulated hardware acceleration with llvmpipe should work inside qubes