From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>,
60010@debbugs.gnu.org
Subject: bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails
Date: Mon, 12 Dec 2022 21:11:55 +0100 [thread overview]
Message-ID: <87mt7sfkl0.fsf@jpoiret.xyz> (raw)
In-Reply-To: <87y1rcegff.fsf@pelzflorian.de>
Hi Florian,
"pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de> writes:
> So I tried waiting until it exists before modprobe (in the attached
> patch). But modprobe still fails in the same way, according to dmesg,
> even though the file evidently already existed.
I don't think there's a race issue with the files being available:
shepherd should start after system activation (so /run/current-system
exists), and after /gnu/store was mounted in the early userspace.
> I will try tomorrow to get an strace. The installer worked fine in …
> August I believe.
You could also probably try logging the system* call in some temporary
log file, by using some bash redirection (or with-current-output-port
and friends).
By the way, why is the modprobe binary inside a #+? The target will want
to be able to run the binary itself, right? Shouldn't it be #$?
Best,
--
Josselin Poiret
next prev parent reply other threads:[~2022-12-12 20:12 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 [this message]
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
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=87mt7sfkl0.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=60010@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--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).