Open asahilina opened 1 year ago
I'm not really sure which category this issue belongs to, but I'm having problems running Wayland with the newly installed linux-asahi-edge
and mesa-asahi-edge
. I followed the guide precisely, but when I try to login to Wayland, it goes to a blank black screen for about 5 seconds, then puts me back into the login screen where I can choose X11 or Wayland to login with. The issue does not occur with X11. Here's the output of asahi-diagnose
. Let me know if you need anything else!
I don't get GUI at all after installing asahi-edge
and mesa-asahi-edge
. Split-second black screen with cursor, and back to text mode. MBP M1 Max, nothing at all connected but a USB ethernet dongle. asahi-diagnose
output attached.
asahi-diagnose-20221207-090233.txt
EDIT: solved by pacman -S asahi-desktop-meta
, thanks to jannau. Apparently I have an old install :)
The system monitor applets are glitchy when set to "Line Chart". I think all of them, but at least the Memory Usage widget. It doesn't draw the line chart, but instead it draws over other apps (about 1/3 the screen width). It also seems to happen with "Grid", but not with the other display styles.
This happens in both Xorg and Wayland. (Using Xorg still because I can't seem to get scaling to work well on Wayland).
asahi-diagnose-20221207-125011.txt
Update: unfortunately the recent mesa update didn't fix this (I hoped it would). Also, I can confirm the System Monitor program has the same issue, as reported by @TheBrinkOfTomorrow. I did find that LIBGL_ALWAYS_SOFTWARE=1 plasma-systemmonitor
works around this issue.
Update 2: the latest mesa update also fixed the issue with the system monitor applets in the Plasma panel!
The system monitor applets are glitchy when set to "Line Chart". I think all of them, but at least the Memory Usage widget. It doesn't draw the line chart, but instead it draws over other apps (about 1/3 the screen width). It also seems to happen with "Grid", but not with the other display styles.
Same issue for me (using Wayland). Graphics corruption is restricted to the internal boundaries of the System Monitor view. asahi-diagnose-20221207-080358.txt
Same issue with the system monitor like described in the two comments above here too. The applets in the taskbar don't work correctly and the history tab inside the app has the same/similar glitches like in the above screenshot. Using a Macbook Pro 14" 10‑Core CPU 16‑Core GPU, 16‑Core Neural Engine, 32 GB RAM. Asahi is up to date, containing yesterday's mesa fixes.
Followed the steps on the blog as described, I cannot get to Plasma session on Wayland. I see terminal cursor blinking fast, then back to SDDM. asahi-diagnose-20221208-204440.txt
Followed the steps on the blog as described, I cannot get to Plasma session on Wayland. I see terminal cursor blinking fast, then back to SDDM. asahi-diagnose-20221208-204440.txt
dec 08 20:30:24 eatasbkng kernel: asahi 206400000.gpu: Unsupported GPU/firmware combination (G13, [12, 4, 0])
You have used macOS 12.4 as stub/firmware version on a M1 device. This is not supported. The 12.4 GPU firmware is only supported on M2 devices since those were released with 12.4.
I've got an issue in firefox 107.0.1 when browsing Plex on wayland, together wih gpu timeouts.
This is what it should look like (linux-asahi
, X11):
https://github.com/fredlahde/asahi-gpu-bug-report/raw/main/plex/Screenshot%202022-12-08%20at%2020-51-14%20Eminem%20-%20Seduction.png
This is what it actually looks like (linux-asahi-edge
, Wayland):
https://github.com/fredlahde/asahi-gpu-bug-report/raw/main/plex/Screenshot%202022-12-08%20at%2020-47-30%20Eminem%20-%20Seduction.png
Diagnose File: https://raw.githubusercontent.com/fredlahde/asahi-gpu-bug-report/main/plex/asahi-diagnose-20221208-204618.txt
@jannau do you know how to work around the stub version caused issues? I'm also having an issue where wayland just refuses to work and the only thing I see is a blinking cursor, then the lockscreen again. You can also find my asahi-diagnose
log here
Please do not add "me too" comments, as they just clutter everything up. Once an issue is reported, it's enough, we don't need more reports (unless you're going to add useful info, like more detailed/reliable repro steps --Lina).
Please don't report issues with nonstandard unsupported firmware. If you picked expert mode in the installer and then chose the wrong non-default options, you're on your own. You'll have to reinstall to fix it. It's called expert mode for a reason - if you break it you get to keep the pieces.
The System Monitor issues should now be fixed! ✨
@fredlahde Can you update, reboot and test the Firefox/Plex thing again? I don't have a Plex server to test with...
I noticed that GitHub is showing comments we mark as resolved as simply "hidden". We're just hiding them to declutter the bug, don't worry! Please look for that wording (This comment has been hidden.) if you're looking for previous comments reporting issues that have since been fixed ^^
@fredlahde Can you update, reboot and test the Firefox/Plex thing again? I don't have a Plex server to test with...
I'm still getting this after updating and rebooting.
Diagnose file: asahi-diagnose-20221209-180737.txt
@fredlahde Can you update, reboot and test the Firefox/Plex thing again? I don't have a Plex server to test with...
I can confirm what @iaguis said. Plex is still pink.
@asahilina
For testing you can use https://app.plex.tv/desktop/#!/. This site is public and does not require a Plex server or account.
Writing to gl_FragDepth
is broken.
Reproduction: Install glfw, compile the following with gcc -o depthwrite src/*.c -lglfw -Iinclude
, and run it: depthwrite.tar.gz (it's glfw example code with a gl_FragDepth = 1.0;
added to the shader)
Expected result: A spinny rainbow triangle
Actual result: A black window (commenting out the gl_FragDepth = 1.0;
makes it work fine)
If you run it with a debug build of mesa, you hit this assertion. Looks like the compiler expected all fragment stores to be lowered to nir_intrinsic_store_local_pixel_agx
s but in reality only the color stores get lowered that way.
asahi-diagnose
output: asahi-diagnose-20221210-144501.txt
I reliably hit GPU timeouts and a subsequent application segfault on Firefox 107.0.1 (Wayland, KDE Plasma, ArchLinuxARM, essentially what I got out of the Asahi installer + the blog post about installing the GPU drivers) when visiting any website that has a Mapbox (app sample 1, app sample 2) or a Maptiler (landing page, Shodan host view) map.
Firefox stdout/stderr shows the following before it segfaults:
Some notes:
ASAHI_MESA_DEBUG=no16
does not seem to help.ASAHI_MESA_DEBUG=trace
the timeouts still happen and the application eventually crashes, everything just happens in slow motion.Kernel: edge Mesa: edge session: X11 DE: Gnome
When I filling info for WIFI IN Gnome setting panel, the screen start fast flashing (from nolmar light level to lower, but not completly blank). And I can hear some current sound from power adapter at same time.
After filling, the screen back to normal and the sound disapear.
I think it not just display issue but also envolve some power issue?
Screen flashing is a known issue (https://github.com/AsahiLinux/linux/issues/72#issue-1480830781). Not sure about your power adapter, but it's probably unrelated. Edit: it may not be, that looks like an issue in KWin that doesn't effect GNOME/Mutter.
@levihuayuzhang Please follow the instructions and attach an asahi-diagnose
log.
@levihuayuzhang Please follow the instructions and attach an
asahi-diagnose
log.
sorry, it seems I cannot reproduce the problem after update and reboot. Maybe it was solved.
File for asahi-diagnose
:
I have found a few somewhat minor rendering issues, all on KDE/Plasma:
There is a possibility some of these are just the Xorg black artifacts issue.
asahi-diagnose-20221214-024216.txt
Update: the Yakuake issue seems to be fixed with the Xorg black glitches fix. The only issue I'm still experiencing is the flickering pointer, but as @asahilina indicated this is not an issue with the GPU driver (mesa/kernel).
@aykevl The cursor thing is an Xorg modesetting driver bug I think (I see it on other platforms...). For the vertical/black lines, have you tried setting your display scale to 100%?
The Yakuake issue sounds like the KWin redraw problem on X11... I'm going to be looking at that today.
I've confirmed that the Firefox issues with QuakeJS and Plex are a Firefox bug, so I've moved that to the third-party app issues list.
The cursor thing is an Xorg modesetting driver bug I think (I see it on other platforms...).
Ugh, ok. Was hoping it was easy to fix :(
For the vertical/black lines, have you tried setting your display scale to 100%?
Oh I forgot about that! Will do. Unfortunately it doesn't reproduce anymore today so ¯\(ツ)/¯ will report back once I manage to reproduce it reliably again (at 100% display scale). I think I also installed a Firefox update so that might also have fixed it.
As for the X11 black glitches issue, that should now be resolved! It turned out to be a core Mesa bug (not specific to our driver)...
@TellowKrinkle gl_FragDepth should now be supported too, please give it a try!
Found a different Mesa segfault under Firefox: in the PubChem website, if you load any 3D molecule visualization, you get a SIGSEGV while agx_pool_upload_aligned_with_bo
attempts this memcpy
from a glDrawElements()
call. Unlike the issue found with QuakeJS, this one causes no GPU timeouts, and the segfault itself happens on both debug and release Firefox.
UPDATE 19/12/2022: can also be reproduced on the WebGL visualization at https://skyline.github.com.
The following data was collected under this URL: https://pubchem.ncbi.nlm.nih.gov/compound/Copper-acetate#section=Structures
This is a tracker bug for general GPU issues, like:
When making a comment on this bug, please run the
asahi-diagnose
command and attach the file it saves to your comment. Please tell us what you were doing when the problem happened, what desktop environment and window system you use, and any other details about the issue.The purpose of this bug is to collect reports of app issues in one place, so we have somewhere to look when figuring out what to work on. Since the driver is still a work-in-progress and lots of things are not expected to work, please don't expect a timely response to reports. We're working on it!
Before reporting something, please check that the issue has not been reported already. Duplicate reports just clutter up the bug and will be marked as duplicate. --marcan
If you are having shader errors with Chromium/Electron-based apps after an update, delete your shader cache:
rm -rf ~/.config/chromium/Default/GPUCache
(or similar paths for other apps). Upstream bug. This is not a driver bug.If you run into a GPU lockup or crash (all GPU apps stop working, but you can still SSH into the machine), please open a new bug in this repo, tell us what you were doing when the GPU locked up, and attach the
asahi-diagnose
log.If you get GPU fault or GPU timeout messages in dmesg (probably together with rendering issues), but the GPU keeps working in general, this tracker bug is the right place to report that.
If you have
linux-asahi-edge
issues unrelated to the GPU, please report them here. This includes display output/controller related issues, like screen resolution switching and backlight control, which are unrelated to the GPU driver.If you are seeing single-pixel-wide glitches, please set your screen scale to 100%, log out and back in, and try to reproduce it again. These kinds of glitches are likely to be compositor/desktop environment bugs related to fractional scaling, rather than driver issues.
If you see magenta
Magenta is the error color on Apple GPUs. It is what you get when you sample an uninitialized compressed texture. This often happens with driver bugs that break rendering, but there are also many apps that have bugs that transiently display uninitialized buffer contents. These will often show up as black or transparent on other GPUs or with software rendering, which stands out less but it indicates the same bug.
If you see magenta glitches, please try running the app with
ASAHI_MESA_DEBUG=nocompress
. If you see the same problems but they are now black, tryLIBGL_ALWAYS_SOFTWARE=true
to force software rendering. If you get the same results (still black regions where previously there was magenta), then it is likely an app bug or an upstream Mesa bug, not a driver issue.Another common issue is apps that have rendering feedback loops, which are undefined behavior in OpenGL. These often result in 4x2 pixel shaped corruption regions. You can work around this with
ASAHI_MESA_DEBUG=nocompress
, which should fix the issue (at least if it wouldn't normally break on all GPUs). This could also be caused by a driver bug, though, so please do report anything that is fixed withnocompress
so we can take a look and determine whether it's an app bug or a driver bug!Known issues
Resolved issues
Issues that aren't driver bugs
Google Sheets bugFirefox bug) (workaround:ASAHI_MESA_DEBUG=no16
)