-
-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Driver issues on Vega 12 MBP 2019 i9 #127
Comments
Vega 12? Are you using an external GPU? |
Sorry meant radeon pro vega 20! Its a: I found that removing all kernel header pkgs, and installing tiny-dfr , then reinstalling the latest t2 kernel fixes the touchbar/display issues at least. Messed around a bit with mesa drivers too, which dident help much, but somehow down the line when cleaning up something i did managed to fix the suspend issues that i thought was just something i had to accept.. But now, when i went back to the macbook, the gpu/touchbar issues were back, and suspend/sleep was once again broken.. But atleast now i have a specific time where it crashed and went back to having issues, so il collect some logs and upload |
For touchbar do |
No, maybe i was unclear, the issue is on a driver level for the amdgpu.. Initially, the touchbar is seen as a sec screen, and tiny-dfr/touchbar works, same with --switch --restart and so on. Ive done 3 setups now, 2. Purgin all amd gpu drivers and firmware, and using a older mesa driver **3. Just a test case, testing different drivers ** Using amd proprietery drivers |
Did you try linux-t2-lts? |
You can also try X11 to rule out whether it's an issue with Wayland |
Sorry for the lack of exact names and outputs, im on my phone and will update later!
Short desc
After the 2nd reboot touchbar stops working due to the gpu not recotnizing it. And huge visual bugs.
The problem
On a fresh install, the gpu is working as intended, until the first reboot.
Note that the driver is not
changed or replaced.
Im not 100% sure its a driver issue, it could be a gnome, wayland etc issue from some change in noble..
Symptoms
Firstly, theres a discrepancy between how the gpu is showing up in gnome settinga gui, after install it shows up as "Amd vega 12 [modelnumber] [info]
While after the first reboot showing up as simply "Amd graphics". But this is only from the gui in gnome settings, but still its a differance.
If listing screens on first start, it lists 2 screens, the touchbar and the actual screen.
After the first reboot it only lists the actual screen.
The reason being that it panics due to not being able to access the amd gpu du to "device busy".
From what ive seen, its not an issue with the touchbar driver/tiny-dfr or config, but the gpu driver.
While working fine after install, after the first reboot it breaks.
For some reason it seems to specifically have to do with rendering svgs? Regardless if in browser on a website, in an application etc.
The worst is chromium based browsers, where every single use of a svg anywhere within the browser or websites is completly garbage, looking like the type of glitches you would see on a gpu with dying vram.
While svgs are broken, video playback, images, scaling, is fine.
But i have only chromium, g chrome, firefox and vscode om the machine.
The text was updated successfully, but these errors were encountered: