From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: soheilkhanalipur@tutanota.com
Cc: 44301 <44301@debbugs.gnu.org>
Subject: bug#44301: Black screen in Guix System installation
Date: Sat, 31 Oct 2020 20:05:39 +0100 [thread overview]
Message-ID: <20201031190539.j5mwmyum3qqactvk@pelzflorian.localdomain> (raw)
In-Reply-To: <MKyooWB--3-2@tutanota.com>
On Sat, Oct 31, 2020 at 02:22:58PM +0100, soheilkhanalipur--- via Bug reports for GNU Guix wrote:
> Guix has some incompatibilities like (issues.guix.gnu.org/43985) with my computer.
> What are these? what's the solution?
Your issues are post-install, I think, so the installer worked
properly, so Guix basically works. However:
Possibly you will not get a good experience because (if I understand
it correctly) Linux-libre might have various incompatibilities because
it is deliberately lacking non-free firmware.
You might work around the graphics issues by using nomodeset or
blacklisting nouveau and then using uvesafb like
<https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00320.html>.
I’m not sure if all that is really necessary.
Your 7.jpg shows this message:
[ 18.727379] usb 1-1.3: Fatal – failed to load firmware
This may be because Linux-libre
next prev parent reply other threads:[~2020-10-31 19:06 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) [this message]
[not found] ` <CAB3EbL5Y20dhXgXZPWE5XOqYCmfcterrxeuQP+exe9Hp0c5zGg@mail.gmail.com>
2020-11-01 6:47 ` pelzflorian (Florian Pelz)
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=20201031190539.j5mwmyum3qqactvk@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=44301@debbugs.gnu.org \
--cc=soheilkhanalipur@tutanota.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.
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).