From: raingloom <raingloom@riseup.net>
To: Philip McGrath <philip@philipmcgrath.com>
Cc: help-guix@gnu.org
Subject: Re: Getting Guix System to use llvmpipe
Date: Tue, 12 Oct 2021 22:09:10 +0200 [thread overview]
Message-ID: <20211012220910.6d8e482c@riseup.net> (raw)
In-Reply-To: <b0c24af4-c072-5ddd-9b54-2fdee36a7338@philipmcgrath.com>
On Tue, 12 Oct 2021 12:52:46 -0400
Philip McGrath <philip@philipmcgrath.com> wrote:
> Hi folks,
>
> I'm trying to install Guix System on real hardware for the first
> time, and I'm having some graphics trouble.
>
> The machine has an older Asus M5A78L-M/USB3 motherboard with an
> onboard Radeon HD 3000 GPU---the R600 family, IIUC, so covered by the
> `radeon` driver rather than `amdgpu`. I understand that functionality
> will be limited since I'm not using nonfree firmware, and I can live
> with that.
>
> I've tried Debian 11 on this board (without "nonfree"), and, after
> noting the missing firmware, it falls back to work acceptably with
> `llvmpipe`.
>
> Unfortunately, Guix System is working less well. When it starts the
> display manager (I've tried both GDM and SDDM, with both X11 and
> Wayland), the screen goes blank permanently, and the logs show that
> starting the X server fails: initially with an error about an
> undefined symbol `exaGetPixmapDriverPrivate`, though through various
> incantations on the kernel command line or in the X configuration I
> can produce other errors, like "X: ../include/privates.h:121:
> dixGetPrivateAddr: Assertion `key->initialized' failed."
>
> Can I configure Guix to give up on the missing firmware and just use
> `llvmpipe`, as Debian does?
>
> Or, of course, if there's something even better I should do, I'd be
> glad to hear about that!
>
> Thanks,
> Philip
>
Just a hunch but maybe you could blacklist the broken firmware on the
kernel command line arguments. I think it's something like
modprobe.blacklist=radeon,amdgpu? Sorry, I can't look into it more
right now, but that should give you some keywords to search for and
maybe find the proper docs.
next prev parent reply other threads:[~2021-10-12 20:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 16:52 Getting Guix System to use llvmpipe Philip McGrath
2021-10-12 20:09 ` raingloom [this message]
2021-10-13 5:38 ` Philip McGrath
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=20211012220910.6d8e482c@riseup.net \
--to=raingloom@riseup.net \
--cc=help-guix@gnu.org \
--cc=philip@philipmcgrath.com \
/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).