unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: 44301 <44301@debbugs.gnu.org>
Subject: bug#44301: Black screen in Guix System installation
Date: Sun, 1 Nov 2020 07:47:22 +0100	[thread overview]
Message-ID: <20201101064241.2nvrmd7lgyvdk5fa@pelzflorian.localdomain> (raw)
In-Reply-To: <CAB3EbL5Y20dhXgXZPWE5XOqYCmfcterrxeuQP+exe9Hp0c5zGg@mail.gmail.com>

I do not know if you deliberately did not reply to all.  I hope you do
not mind me quoting you.

On Sat, Oct 31, 2020 at 04:16:11PM -0400, Douglas Linford wrote:
> Is recompiling the kernel to include radeon an option?
> Meaning, can I recompile the kernel myself?
> 
> Douglas

Guix will not provide support for that, but there is a Guix channel
where others are doing that.  (I cannot link to it and of course it is
a trade-off because parts of Linux (instead of Linux-libre) are
nonfree.)  The uvesafb solution I linked to in my last mail is an
alternative that I use for one old laptop of mine that does not make
much use of your GPU and is therefore slower and may or may not be
more power-hungry, I don’t know.

soheilkhanalipur reported problems with an Nvidia GPU.  I had not seen
that before, maybe the above also helps.  I do not know if
soheilkhanalipur’s USB issues are still problematic.

(Sorry I accidently sent out a draft e-mail before, but it was mostly
complete.)

Regards,
Florian




  parent reply	other threads:[~2020-11-01  6:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-29  6:03 bug#44301: Black screen in Guix System installation soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-29  7:22 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-10-29 20:23   ` Douglas Linford
2020-10-29 15:52 ` bug#44301: Comment soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-29 16:13 ` bug#44301: Black screen in Guix System installation soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-30 18:18 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-31 13:22 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-10-31 19:05   ` pelzflorian (Florian Pelz)
     [not found]     ` <CAB3EbL5Y20dhXgXZPWE5XOqYCmfcterrxeuQP+exe9Hp0c5zGg@mail.gmail.com>
2020-11-01  6:47       ` pelzflorian (Florian Pelz) [this message]
2020-11-01 12:44 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-01 15:26   ` Malte Gerdes
2020-11-02 12:57 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-02 13:11 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-02 13:36 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-02 18:09 ` soheilkhanalipur--- via Bug reports for GNU Guix
2020-11-02 18:25 ` bug#44301: Done soheilkhanalipur--- via Bug reports for GNU Guix

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=20201101064241.2nvrmd7lgyvdk5fa@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=44301@debbugs.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.
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).