unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Keyhenge <key@keyhenge.xyz>
Cc: 40590@debbugs.gnu.org
Subject: bug#40590:
Date: Sat, 18 Apr 2020 20:17:29 +0200	[thread overview]
Message-ID: <20200418181729.lnovxwpyko227wj7@pelzflorian.localdomain> (raw)
In-Reply-To: <87k12celeo.fsf@keyhenge.xyz>

On Sat, Apr 18, 2020 at 01:47:11PM -0400, Keyhenge wrote:
> The amd option didn't work, but nomodeset allowed me to get to a shell,
> at which point I could start experimenting with various settings to see
> if I could get a graphical environment. I finally did by switching over
> to the proprietary kernel (which points to a graphical driver issue with
> AMD Navi cards in the libre kernel), but that's obviously less than ideal.
> 

If you have no problems sacrificing all the acceleration by your AMD
GPU, you can try using libre uvesafb for Xorg graphics.  What I wrote
at <https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00320.html>
was not necessary there but maybe is in your case.  That said, this
situation is far from ideal, but I don’t think the AMD firmware will
be freed (if there is no other way).

Regards,
Florian

  reply	other threads:[~2020-04-18 18:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-13  2:46 bug#40590: Keyhenge
2020-04-13  8:15 ` bug#40590: Mathieu Othacehe
2020-04-13 23:59   ` bug#40590: Keyhenge
2020-04-14  0:54   ` bug#40590: Keyhenge
2020-04-14  6:59     ` bug#40590: Mathieu Othacehe
2020-04-14 23:08       ` bug#40590: Keyhenge
2020-04-15  6:44         ` bug#40590: Mathieu Othacehe
2020-04-18 17:47           ` bug#40590: Keyhenge
2020-04-18 18:17             ` pelzflorian (Florian Pelz) [this message]
2020-04-19 10:09             ` bug#40590: Mathieu Othacehe

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=20200418181729.lnovxwpyko227wj7@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=40590@debbugs.gnu.org \
    --cc=key@keyhenge.xyz \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).