GPU compatible display cards do not work in Linux (virtio-gpu-gl-pci/virtio-ramfb-gl) #4941
Comments
|
Can you please test these two things?
I believe there is a second bug that is somehow not happening on Debian-based systems involving the NIR-to-TGSI translation layer (not fully sure what that is, but the git bisect-ing I did found that to be the problem). I have some storage issues, but then I'll try building UTM's sysroot for debugging. |
Hi, I created that issue. After mesa 22.3.3 hit my system's repository, I upgraded to it and now Xorg launches, but I'm experiencing an issue that's similar to this ticket. Namely, I just have a black screen with a mouse cursor I can move around, but I don't see anything else. Apps can launch with my system's keyboard shortcuts and I know they're launching successfully because when I launch my terminal, I can blindly type in "sudo poweroff" and password and the VM turns off. Here's some logs: sdtout and stderr from xorgXorg.0.logglxinfoxorg does have errors in its stdout and stderr that might be relevant. I should say that I've never attempted to have any GPU options in UTM working with this VM and that this VM has never attempted to have hardware acceleration working with it. This is something I'm trying to add to the VM with the recent update from UTM. Maybe I'm missing drivers in my VM? |
|
@ktprograms Sorry for the delay, I've been bisecting mesa this whole day.
Yep, it does work. No issues.
Tried just recently and yeah, Xorg crashes without the patch. Besides, from my testing I got the commit that could be causing this issue: c5cc9ed2. In this commit, mesa stops using Bisect log, if useful: |
|
@daniel-torrecillas-dsg thanks, this confirms what I found. Somewhere close to mesa 22.3 the shader stages were reordered, which was causing the crash that osy found. However, between 22.1.7 and 22.2, there was a change to use @JezerM Thanks also for confirming, and thanks for bisecting. I should have been more clear that I'd already bisected. |
|
This issue is still persisting for me on Kali Linux. Config: So as per the above discussion the issue is related to https://gitlab.freedesktop.org/mesa/mesa/-/issues/8023, the fix suggested was to downgrade Mesa or patch it. I checked my Mesa version and it looks like the fix should already be implemented - https://gitlab.freedesktop.org/mesa/mesa/-/commit/56c1c201619fd30659c6e475c6790bc7bed6a5df
Also checked Kali pkg list and the latest Mesa package has been added after the date of the merge for the fix above. I was thinking maybe it's something to do with the DE, I went digging around for any issues on XFCE and found this - https://forum.endeavouros.com/t/tutorial-work-around-for-xfce-black-screen-in-virt-manager-with-virtio-3d/17298 I managed to work out that -
I'm stuck on next steps to try. I guess I could try with no DE and just use i3, but I would prefer to use XFCE. Hope there is a fix for this soon. |
Please report back your findings, @Syn-ops. I'm running Arch Linux + i3 with no desktop environment and no compositor and I get a black screen with a cursor I can move around, but nothing else on the screen. I'm also on the latest version of mesa (22.3.3). |
|
same issue here! |
|
Same issue on an M2 iPad Pro with Ubuntu Server 22.04 & Xfce DE |
|
Yeah I had the same thing with those *-gl devices. I tested on Kali with i3 with KDE plasma, on plasma I get to see some GUI elements. Mesa version 22.3.6. I tried disabling the compositor (kwin), and tried out both ANGLE (OpenGL) and ANGLE (Metal) as the renderer, I don't think there's any difference. I guess this is an issue with mesa? plasma.movAlso tried it out on ARM64 Ubuntu desktop jammy, same issue as OP.
Full `gxinfo` output on Ubuntu
I think this is the same issue as #4983 |
|
Yep, it is the same issue. According to the latest UTM release and recent comments in the related issue, this issue should have been addressed, though I haven't tested it yet. |
|
I'm on the latest UTM (updated today), not working it does load the lock screen, but once I get past it, I just see a blue screen with a curser, and like a minute later the whole app crashes |
Oh right, sorry, didn't finish reading the entire convo.
You're on 4.2.4? Works fine for me so far. |
|
Yea (normal UTM with JIT) |
|
I'm using the latest UTM with virtio-ramfb-gl and it's working great on Debian Testing. |
|
Last time I managed to enable GPU acceleration was on my iPhone XS about 2 years ago |
|
Well, I ran the latest Mesa version in VoidLinux with GPU acceleration and it works! Thanks for solving this Mesa issue~ |
@EvanCarroll , I am trying exactly that combination and it lands in a black screen with a cursor. Did you install any drivers in the guest? Any tweaks to configuration on the host? Using an Apple M2 Max as host, in my case. |
|
I was using an M1 and unmodified debian testing runnning Xorg. I no longer have access to the laptop though. |
|
I managed to get it to work on a clean Elementary OS 7 install on my M2 iPad Pro but it doesn’t seem any different than CPU rendering OS does recognize an ANGLE GPU |
Describe the issue
I've been using VoidLinux in UTM for a long time, but it wasn't until the UTM v4.1 release that GPU compatible display cards stopped working correctly:
virtio-gpu-gl-pciandvirtio-ramfb-gl. I thought it was something related to my VM, so I reinstalled it but the issue persists. Unlike #4930, Xorg does not crash, the server and common apps are running and are "functional", but they are not rendered (so they aren't functional at all).Current VoidLinux's mesa version is 22.2.4, so it shouldn't be a mesa issue? (idk) I also tried to compile and install the latest mesa version (23.3.3) which includes the patch you mentioned. Tried as well to update mesa using VoidLinux methods, but neither fixed the issue.
Also, I have to point out that the Gnome UI is actually rendered; GDM and Gnome Desktop are the only things that are rendered.
In the following video, LightDM does not render but it is interactive, while GDM is rendered as well as the Gnome desktop. However, common apps like the Terminal or Nautilus does not render, yet they are interactive.
VoidLinux.UTM.GPU.mp4
Also, Arch Linux has the same issue, but in this one Xorg crashes like #4930.
Configuration
Crash log
No crash log.
Debug log
Xorg log:
Debug log:
Upload VM
config.plist:
The text was updated successfully, but these errors were encountered: