Crash/black screen: after Aquamarine update with AMD iGPU (Ryzen AI 9 370HX) #10248
Replies: 9 comments 34 replies
-
|
Try the following monitor specification: You might have to change the I am still having the problem I reported in #8308 btw. Still need to use |
Beta Was this translation helpful? Give feedback.
-
|
can you get a trace log? |
Beta Was this translation helpful? Give feedback.
-
|
mm, this looks like a driver issue to me tbh :/ |
Beta Was this translation helpful? Give feedback.
-
|
Based on the hardware specs and using kernel g14 I'm guessing this is a ASUS Zephyrus? I recently got a G16 with the AMD CPU and had the exact same problem when trying to use the AMD iGPU, namely this sort of error in the logs before crash: Also was observing that KDE Plasma and Cosmic work, and sway does not. I just tried @ottersome's suggestion and it looks like |
Beta Was this translation helpful? Give feedback.
-
|
My OS info |
Beta Was this translation helpful? Give feedback.
-
|
Any one noticed the behavior reappearing after the latest linux update ? I am on 6.15.5-arch1-1-g14. |
Beta Was this translation helpful? Give feedback.
-
|
While we wait for a proper patch for this, I've just been building aquamarine manually with the offending commit reverted to be able to keep using recent versions of hyprland without version="${1:-}"
git clone --recursive https://github.com/hyprwm/aquamarine ${version:+-b $version}
cd aquamarine
git revert --no-commit 8b22613953961cbea21a620d0559c7ea27dc7e15
cmake --no-warn-unused-cli \
-DCMAKE_BUILD_TYPE:STRING=Release \
-DCMAKE_INSTALL_PREFIX:PATH=/usr \
-S . -B ./build
cmake --build ./build --config Release --target all -j$(nproc) \
&& { sudo rm -v /usr/lib/libaquamarine.so* ; sudo cmake --install ./build ; } |
Beta Was this translation helpful? Give feedback.
-
|
Ooh different CPU and prob very new 👀👀👀 Likely kernel driver related tho. The kernel is trying to keep up uptodate. Maybe will be fixed normally in Kernel 6.17 or Mesa 26/27 |
Beta Was this translation helpful? Give feedback.
-
|
Any update? It's been mesa 25.2 and linux 6.17 and the issue still exists |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey, this is a followup discussion for this issue, as it still exists.
#8308
I have a laptop with dual gpu setup and a Ryzen AI 9 370hx. I have the nvidia gpu disabled so the only card visible to linux is iGPU from amd though.
When I try to start Hyperland via tty I get a crash with the error that looks resolution related. It can't figure out what resolution to use (I think). See attached crash report.
When I set a supported resolution via the config ([email protected]) I don't get a crash, gut I do get a black screen.
However, if I connect an external display I do get a hyprland session. I did this and attach the regular logs and the trace enabled logs.
I tried a few resolutions but all give me a black screen on the internal display.
If I do "AQ_NO_ATOMIC=1" I can a image on the internal display aswell. But I need to disable hardware cursor and it seems to get very slow overtime. But this way it works.
Hope this helps to get a lead on the issue.
Thank you very much in advance
hyprland.log
hyprlandCrashReport2239.txt
hyprland_trace.log
systeminfo.txt
Beta Was this translation helpful? Give feedback.
All reactions