unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Philip McGrath <philip@philipmcgrath.com>
To: help-guix@gnu.org
Subject: Getting Guix System to use llvmpipe
Date: Tue, 12 Oct 2021 12:52:46 -0400	[thread overview]
Message-ID: <b0c24af4-c072-5ddd-9b54-2fdee36a7338@philipmcgrath.com> (raw)

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


             reply	other threads:[~2021-10-12 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 16:52 Philip McGrath [this message]
2021-10-12 20:09 ` Getting Guix System to use llvmpipe raingloom
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=b0c24af4-c072-5ddd-9b54-2fdee36a7338@philipmcgrath.com \
    --to=philip@philipmcgrath.com \
    --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).