Originally posted by bridgman
View Post
The bug was reported like a year and a half ago, see https://bugs.freedesktop.org/show_bug.cgi?id=90320.
But to my utter surprise, fglrx knows how to enable eDP, due to some dark display initialization voodoo magic, likely due to a workaround in its code dedicated to handle some buggy eDP link training or i2c link issues that are known for some LCDdisplays. Naturally, being forced to use fglrx in (what's almost) year 2017 is next to going insane, no new distros would work, gnome refuses to cooperate, console switching would fail, just pure pain and misery.
Now, a question related to all this new and awesome AMD open driver efforts (which I deeply respect); now that we have almost fully featured OpenGL, with all the GPU and accel optimizations coming in, what is the plan with these display init workaround code support that is obviously present in fglrx, but somehow amdgpu is missing it (including amdgpu-pro).
If by any mean this workaround code in fglrx can be made available and back-ported to amdgpu (or even radeon) as a part of DAL or whatever, I'm sure many of us will have much smoother AMD experience, and Linux inclined people may actually want to start buying these APU laptops. To what use it all the fancy 3D when one can not even have a working display...
Comment