From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: 40538@debbugs.gnu.org
Subject: bug#40538: installer: Support uvesafb to install on machines without KMS.
Date: Tue, 14 Apr 2020 10:16:52 +0200 [thread overview]
Message-ID: <20200414081652.vjdu7d6w2u5piud4@pelzflorian.localdomain> (raw)
In-Reply-To: <871roqlebf.fsf@gmail.com>
On Tue, Apr 14, 2020 at 09:24:52AM +0200, Mathieu Othacehe wrote:
>
> Hello Florian,
>
> > Please try adding nomodeset to the kernel parameters. I hope this
> > makes the Intel machine work fine.
>
> Yes it works fine with nomodeset! Do you think we can do something about
> it, besides adding a few lines in the documentation to warn that old
> hardware may require this option?
>
> Thanks,
>
> Mathieu
That is good to hear! The options I know of are:
1) Make the loading of the uvesafb kernel module by the installer
conditional. For your GPU, don’t load uvesafb, if before it worked
without.
2) Add modprobe.blacklist=i915 to the default kernel parameters (or
whatever the kernel module for this GPU is), so this kind of GPU
always only uses uvesafb.
3) Add nomodeset to the default kernel parameters for the installer,
so all GPUs always use uvesafb.
I do not know if uvesafb works on all display technologies though.
uvesafb certainly is not supported on ARM (though maybe it works; the
README of uvesafb’s helper program v86d just says it is not supported).
Regards,
Florian
next prev parent reply other threads:[~2020-04-14 8:17 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)
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) [this message]
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=20200414081652.vjdu7d6w2u5piud4@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=40538@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 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).