From: raingloom <raingloom@riseup.net>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 54945@debbugs.gnu.org
Subject: bug#54945: installer should have a no-graphics boot option
Date: Sat, 16 Apr 2022 19:48:52 +0200 [thread overview]
Message-ID: <20220416194852.5eb15b2d@riseup.net> (raw)
In-Reply-To: <20220416172818.76uijqgbeux7uan7@pelzflorian.localdomain>
On Sat, 16 Apr 2022 19:31:15 +0200
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> On Sat, Apr 16, 2022 at 05:32:38PM +0200, raingloom wrote:
> > On Fri, 15 Apr 2022 22:44:58 +0200
> > "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> wrote:
> > >[…]
> > > I believe uvesafb makes the graphics work on any
> > > x86_64 or x86 machine, so no save-graphics GRUB entry is needed.
> > > But maybe I’m wrong and uvesafb isn’t a panacea.
> > >[…]
> > Hmm, it did end up working, even without the amdgpu trick. Finally
> > had an excuse to try the TUI installer.
> > I guess we can close this for now, but I still think that a safe
> > graphics mode could be a good idea.
>
> Is there reason to believe installer’s graphics don’t work on some PC?
>
> Regards,
> Florian
I have laptops with fried GPUs that still somewhat work with nomodeset.
For rescue images, a no-graphics or nomodeset graphics mode is
definitely useful, because graphics is often the reason booting is
broken.
next prev parent reply other threads:[~2022-04-16 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 0:17 bug#54945: installer should have a no-graphics boot option raingloom
2022-04-15 6:55 ` pelzflorian (Florian Pelz)
2022-04-15 11:36 ` raingloom
2022-04-15 20:44 ` pelzflorian (Florian Pelz)
2022-04-16 15:32 ` raingloom
2022-04-16 17:31 ` pelzflorian (Florian Pelz)
2022-04-16 17:48 ` raingloom [this message]
2022-04-18 14:50 ` pelzflorian (Florian Pelz)
2022-04-18 23:53 ` bug#54945: installer should have a no-graphics^W nomodeset " raingloom
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=20220416194852.5eb15b2d@riseup.net \
--to=raingloom@riseup.net \
--cc=54945@debbugs.gnu.org \
--cc=pelzflorian@pelzflorian.de \
/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).