From: "Ludovic Courtès" <ludo@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: 60010@debbugs.gnu.org
Subject: bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails
Date: Tue, 13 Dec 2022 17:37:01 +0100 [thread overview]
Message-ID: <871qp3w98y.fsf@gnu.org> (raw)
In-Reply-To: <87sfhjfm3z.fsf@pelzflorian.de> (pelzflorian@pelzflorian.de's message of "Tue, 13 Dec 2022 14:51:12 +0100")
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> skribis:
> (provision '(maybe-uvesafb))
> (requirement '(file-systems))
> (start #~(lambda ()
> - (or (file-exists? "/dev/fb0")
> - (invoke #+(file-append kmod "/bin/modprobe")
> - "uvesafb"
> - (string-append "v86d=" #$v86d "/sbin/v86d")
> - "mode_option=1024x768"))))
> + (unless (file-exists? "/dev/fb0")
> + (load-linux-modules-from-directory '("uvesafb") "\
> +/run/booted-system/kernel/lib/modules"))))
To make it work, you’d need to add a ‘modules’ field so that (gnu build
linux-modules) is in scope, plus throw in ‘with-imported-modules’.
I’d say let’s stick to the minimal change where we still invoke
‘modprobe’.
Ludo’.
prev parent reply other threads:[~2022-12-13 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 16:27 bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails pelzflorian (Florian Pelz)
2022-12-12 20:11 ` Josselin Poiret via Bug reports for GNU Guix
2022-12-13 12:29 ` pelzflorian (Florian Pelz)
2022-12-12 23:18 ` Ludovic Courtès
2022-12-13 10:00 ` Ludovic Courtès
2022-12-13 12:50 ` pelzflorian (Florian Pelz)
2022-12-13 13:03 ` Ludovic Courtès
2022-12-14 13:49 ` pelzflorian (Florian Pelz)
2022-12-14 23:29 ` Ludovic Courtès
2022-12-15 17:42 ` pelzflorian (Florian Pelz)
2022-12-15 23:37 ` Ludovic Courtès
2022-12-16 11:48 ` pelzflorian (Florian Pelz)
2022-12-13 13:51 ` pelzflorian (Florian Pelz)
2022-12-13 16:37 ` Ludovic Courtès [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
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=871qp3w98y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=60010@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).