On 15.03.2018 02:08, Marius Bakke wrote:
This looks like a driver problem. Can you post the output of
"dmesg | grep -w 'drm|r600|radeon'" ?
I seem to recall that hardware acceleration on radeon/amdgpu requires
proprietary microcode, even when using the free driver. Maybe that is
related?
Right, thank you!
comparing `dmesg | grep -w 'drm\|r600\|radeo'` from both systems made
this stand out:
---
radeon 0000:01:00.0: Direct firmware load for /*(DEBLOBBED)*/ failed
with error -2
[drm:rv770_init [radeon]] *ERROR* Failed to load firmware!
---
Guess I have to research how to put that back in now, as my level of
idealism doesn't cover basic functionality falling flat. I understand
the issues with binary blobs, but from a right-here, right-now
perspective, what you do here is to cripple a driver (one among many, I
assume) and let it be a surprise for users if things go belly up.
--
Thorsten Wilms
thorwil's design for free software:
http://thorwil.wordpress.com/
