From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Brendan Tildesley <mail@brendan.scot>
Cc: guix-devel <guix-devel@gnu.org>, Mathieu Othacehe <othacehe@gnu.org>
Subject: Re: Call for 1.2 installer testing.
Date: Sun, 11 Oct 2020 22:32:08 +0200 [thread overview]
Message-ID: <20201011203208.lwhkrkwixxy5uxtj@pelzflorian.localdomain> (raw)
In-Reply-To: <10d0d175-3849-4b28-1136-2ce1e7bf45b2@brendan.scot>
On Sun, Oct 11, 2020 at 05:23:30PM +1100, Brendan Tildesley wrote:
> Hi, I went through the installer looking for anything negative I could say
> about it :) hope there is something helpful here:
Thank you for testing!
> Unrelated driver bug: installer was just a black screen until I rebooted
> with nomodeset: https://paste.debian.net/1166581/
> Even with nomodeset, I get an error about no UMS supported in radeon, but it
> doesn't stop anything.
This black screen regression should be “fixed” now (commit
34d436a4082b5c5f23b00e13eb8e5a92d957d704) by passing a kernel argument
“modprobe.blacklist=radeon” which disables the radeon driver.
(This was also blacklisted in the last release 1.1.0 of Guix, see
<https://issues.guix.gnu.org/40599>. I had removed
“modprobe.blacklist=radeon” because it was for some time no longer
needed on one of my machines.)
Some users will have a black screen in the installed system as well
(if they use Linux-libre). I don’t think we can do much about that.
Niels <https://issues.guix.gnu.org/40599#8> only had trouble with the
installer but did not on the installed system. It seems not feasible
to predict which users would have a black screen in the installed
system, so we cannot add instructions only for them.
> Languages listed in the language selection are sometimes in English, Rarely
> in the native language. […]
> Random thought: could we adapt the installer to use the same sentences from
> an existing installer, like the ubuntu one, so that all the translations can
> be copied in for free? All the basic quesions like please choose a password
> are surely shared between these installers.
Yes, we could copy translations without understanding the language (at
least after our planned switch from the Translation Project to our own
hosted Weblate translation infrastructure).
Regards,
Florian
next prev parent reply other threads:[~2020-10-11 20:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-11 6:23 Call for 1.2 installer testing Brendan Tildesley
2020-10-11 9:48 ` Efraim Flashner
2020-10-11 20:32 ` pelzflorian (Florian Pelz) [this message]
2020-10-11 20:36 ` Marinus Savoritias
2020-10-11 23:40 ` Brendan Tildesley
2020-10-13 6:47 ` Brendan Tildesley
2020-10-13 6:50 ` Brendan Tildesley
2020-10-12 12:44 ` Localization of language names Ludovic Courtès
2020-10-17 11:46 ` Miguel Ángel Arruga Vivas
2020-10-21 13:26 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2020-10-09 12:44 Call for 1.2 installer testing Mathieu Othacehe
2020-10-13 16:40 ` Alex Sassmannshausen
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=20201011203208.lwhkrkwixxy5uxtj@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=guix-devel@gnu.org \
--cc=mail@brendan.scot \
--cc=othacehe@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).