From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Mathieu Othacehe <m.othacehe@gmail.com>
Cc: Brice Waegeneire <brice@waegenei.re>, 41082@debbugs.gnu.org
Subject: bug#41082: nomodeset
Date: Wed, 6 May 2020 10:19:05 +0200 [thread overview]
Message-ID: <20200506081905.5yfdk3j7y237fdj2@pelzflorian.localdomain> (raw)
In-Reply-To: <874kstd00f.fsf@gmail.com>
On Wed, May 06, 2020 at 08:56:48AM +0200, Mathieu Othacehe wrote:
> Should we propose the installation of uvesafb service in the
> installation? Or detect that it is currently used and force its install?
>
> Florian, WDYT?
Yes, IMHO there should be a uvesafb-service-type. Copying the uvesafb
service from the installer into the config.scm should work (but the
video resolution should be adjusted, probably something higher than
1024x768 is supported by the system).
We could add a uvesafb-service-type to its own gnu/services/….scm.
Autodetection of the best usable resolution via v86d:testvbe could be
added (however the best resolution usable with uvesafb may be less
than the screen’s resolution).
One way such a uvesafb-service-type could work is exactly like in the
installler. Would it be right to add a uvesafb service that runs
modprobe itself?
Another way is to extend etc-service-type for this the way I wrote at
<https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00320.html>.
Extending other services seems cleaner, but in the discussions by
Brice Waegeneire and Danny Milosavljevic (I put them in Cc) they were
not really satisfied with etc-service-type.
Back then I wrote <https://lists.gnu.org/archive/html/bug-guix/2020-04/msg00215.html>:
> When the dust has settled on the kernel-module-configuration-service
> discussed by Brice Waegeneire and Danny Milosavljevic
> <https://lists.gnu.org/archive/html/guix-patches/2020-04/msg00272.html>,
> a proper uvesafb service can be added. Then I can make and test one
> and it could also be used in the installer. That would be the clean
> solution. In particular, it could detect the resolution to use for
> uvesafb automatically by running the attached code testvbe.scm as
> root. But how to run that code depends on the
> kernel-module-configuration-service if/when it exists. (I did not
> know how to extend etc-service-type with a file created at runtime not
> build time, but maybe kernel-module-configuration-service works
> differently anyway.)
Regards,
Florian
next prev parent reply other threads:[~2020-05-06 8:20 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) [this message]
2020-05-06 20:53 ` Danny Milosavljevic
2020-05-10 19:44 ` Brice Waegeneire
2020-05-06 14:57 ` Danny Milosavljevic
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=20200506081905.5yfdk3j7y237fdj2@pelzflorian.localdomain \
--to=pelzflorian@pelzflorian.de \
--cc=41082@debbugs.gnu.org \
--cc=brice@waegenei.re \
--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).