Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 778959 - media-libs/mesa-21.0.1 cannot start X with amdgpu
Summary: media-libs/mesa-21.0.1 cannot start X with amdgpu
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-28 15:13 UTC by Harley Wiltzer
Modified: 2022-02-03 00:33 UTC (History)
3 users (show)

See Also:
Package list:
Runtime testing required: ---

Attachments
Xorg log (Xorg.0.log,18.58 KB, text/x-log)
2021-03-28 15:13 UTC, Harley Wiltzer 		Details
emerge --info (emergeinfo,6.21 KB, text/plain)
2021-03-28 15:13 UTC, Harley Wiltzer 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Harley Wiltzer 2021-03-28 15:13:23 UTC 
Created attachment 695535 [details]
Xorg log

After upgrading to mesa 21.01, I cannot start X. My GPU is a Radeon RX480, and I've been using it with amdgpu and gentoo for a few years with no issues. See that attached Xorg log for details.

Downgrading to mesa 21.0.0 solved the problem.
Comment 1 Harley Wiltzer 2021-03-28 15:13:56 UTC 
Created attachment 695538 [details]
emerge --info
Comment 2 Matt Turner gentoo-dev 2021-03-29 01:44:46 UTC 
Oh, nice. Could you please file an issue upstream at https://gitlab.freedesktop.org/mesa/mesa/-/issues ?
Comment 3 tt_1 2021-03-29 08:34:31 UTC 
I can't confirm with my Radeon RX550

however I diffed the two mesa tarballs, there is just one patch it seems related to the amd backend. Maybe you can revert these changes locally to find the regression very easily? 

ping me if you need any additional information
Comment 4 Harley Wiltzer 2021-04-04 15:05:54 UTC 
Sorry for the delay. I just built mesa-21.0.1 so I could try reverting those changes that #3 suggested, but oddly enough I cannot reproduce the issue (before reverting anything)... I'm not sure how this is possible, I checked the history of the ebuild and it doesn't look like any recent changes could have contributed to resolving this.