From: Thorsten Wilms <t_w_@freenet.de>
To: help-guix <help-guix@gnu.org>
Subject: Re: Wayland setup
Date: Thu, 15 Mar 2018 11:29:04 +0100 [thread overview]
Message-ID: <fd6c3131-7142-45b3-5bdc-1107a76ddaff@freenet.de> (raw)
In-Reply-To: <87y3iudu20.fsf@fastmail.com>
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/
next prev parent reply other threads:[~2018-03-15 10:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-05 12:59 Wayland setup Thorsten Wilms
2018-03-05 13:47 ` Andreas Enge
2018-03-07 13:06 ` Oleg Pykhalov
2018-03-11 17:07 ` Thorsten Wilms
2018-03-12 17:19 ` Thorsten Wilms
2018-03-12 19:05 ` Gábor Boskovits
2018-03-12 20:54 ` Thorsten Wilms
2018-03-13 19:50 ` Thorsten Wilms
2018-03-13 21:22 ` Gábor Boskovits
2018-03-14 21:10 ` Thorsten Wilms
2018-03-15 1:08 ` Marius Bakke
2018-03-15 10:29 ` Thorsten Wilms [this message]
2018-03-15 10:06 ` Thorsten Wilms
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fd6c3131-7142-45b3-5bdc-1107a76ddaff@freenet.de \
--to=t_w_@freenet.de \
--cc=help-guix@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).