all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 41082@debbugs.gnu.org
Subject: bug#41082: nomodeset
Date: Wed, 6 May 2020 16:57:30 +0200	[thread overview]
Message-ID: <20200506165730.48292398@scratchpost.org> (raw)
In-Reply-To: <874kstd00f.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 857 bytes --]

Hi,

On Wed, 06 May 2020 08:56:48 +0200
Mathieu Othacehe <m.othacehe@gmail.com> wrote:

> Should we propose the installation of uvesafb service in the
> installation? Or detect that it is currently used and force its install?

Since we don't have a previous generation to go back to, I'd prefer the first
generation to be one that actually works.  So the latter.

If that's not what is wanted, one can always go into config and reconfigure
the system.  If *that* doesn't boot, one can just reboot and select the
previous generation in the bootloader.

So I'd be in favor of the installer creating a system as close as possible
to the installer's own boot configuration.

Compared to that, if one created a system with a configuration different
to the installer's own boot media, maybe the system won't boot at all.
What do you do then?

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2020-05-06 14:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 17:03 bug#41082: Guix sd startup fails to initialize AMD Radeon RX 560 Ryan Osborne
2020-05-05  1:58 ` Boris A. Dekshteyn
2020-05-05 12:39 ` bug#41082: nomodeset Ryan Osborne
2020-05-06  6:56   ` Mathieu Othacehe
2020-05-06  8:19     ` pelzflorian (Florian Pelz)
2020-05-06 20:53       ` Danny Milosavljevic
2020-05-10 19:44         ` Brice Waegeneire
2020-05-06 14:57     ` Danny Milosavljevic [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200506165730.48292398@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=41082@debbugs.gnu.org \
    --cc=m.othacehe@gmail.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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.