From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 40538@debbugs.gnu.org
Subject: bug#40538: installer: Support uvesafb to install on machines without KMS.
Date: Fri, 10 Apr 2020 16:58:58 +0200 [thread overview]
Message-ID: <20200410145858.cekc55kjog3eblbu@pelzflorian.localdomain> (raw)
In-Reply-To: <87tv1rv21e.fsf@gnu.org>
On Fri, Apr 10, 2020 at 04:38:37PM +0200, Ludovic Courtès wrote:
> AIUI, uvesafb is needed for ksmcon (or presumably X11) to work, but it’s
> not necessary to get the standard Linux framebuffer/console running
> (indeed, you were able to ctrl-alt-f3 to get a terminal). Is this
> correct?
Yes, all correct.
> If that’s the case, then I think it’s acceptable for now to install a
> system that lacks uvesafb. Of course X11 won’t work (right?),
Yes, right.
> which is
> not great, but people can hopefully address it at the console until we
> have a better fix, possibly using ‘kernel-module-configuration-service’
> as you write.
>
> WDYT?
I agree.
I will try making a patch including your suggestions in a few hours.
>
> 2. Does "modprobe.d/uvesafb.conf" work? I thought there was nothing
> taking care of creating “modprobe.d” automatically.
I think I tested this version of the patch and it worked. One can
test on QEMU by passing nomodeset (without uvesafb the installer stays
black, I think). It also matches the description of
kernel-module-loader-service-type that was recently added to the
manual.
Regards,
Florian
next prev parent reply other threads:[~2020-04-10 15:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-10 12:54 bug#40538: installer: Support uvesafb to install on machines without KMS pelzflorian (Florian Pelz)
2020-04-10 14:38 ` Ludovic Courtès
2020-04-10 14:58 ` pelzflorian (Florian Pelz) [this message]
2020-04-12 6:37 ` Bengt Richter
2020-04-12 8:35 ` Bengt Richter
2020-04-12 8:56 ` pelzflorian (Florian Pelz)
2020-04-11 18:43 ` pelzflorian (Florian Pelz)
2020-04-11 19:03 ` pelzflorian (Florian Pelz)
2020-04-11 20:59 ` Ludovic Courtès
2020-04-11 21:11 ` Efraim Flashner
2020-04-12 9:23 ` pelzflorian (Florian Pelz)
2020-04-12 14:28 ` Ludovic Courtès
2020-04-12 18:33 ` pelzflorian (Florian Pelz)
2020-04-12 9:02 ` pelzflorian (Florian Pelz)
2020-04-12 11:24 ` pelzflorian (Florian Pelz)
2020-04-12 12:33 ` pelzflorian (Florian Pelz)
2020-04-12 14:48 ` Mathieu Othacehe
2020-04-12 15:30 ` pelzflorian (Florian Pelz)
2020-04-12 17:48 ` Bengt Richter
2020-04-12 18:11 ` pelzflorian (Florian Pelz)
2020-04-13 5:00 ` Bengt Richter
2020-04-13 5:37 ` pelzflorian (Florian Pelz)
2020-04-14 8:57 ` pelzflorian (Florian Pelz)
2020-04-14 7:24 ` Mathieu Othacehe
2020-04-14 8:16 ` pelzflorian (Florian Pelz)
2020-04-14 8:34 ` pelzflorian (Florian Pelz)
2020-04-14 10:09 ` Ludovic Courtès
2020-04-14 10:28 ` pelzflorian (Florian Pelz)
2020-04-14 13:14 ` pelzflorian (Florian Pelz)
2020-04-14 14:12 ` Ludovic Courtès
2020-04-14 17:09 ` Mathieu Othacehe
2020-04-14 21:31 ` pelzflorian (Florian Pelz)
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=20200410145858.cekc55kjog3eblbu@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=40538@debbugs.gnu.org \
--cc=ludo@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).