all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 60010@debbugs.gnu.org
Subject: bug#60010: [version 1.4.0] AMD screen stays black; modprobe fails
Date: Tue, 13 Dec 2022 13:50:57 +0100	[thread overview]
Message-ID: <87o7s7zcum.fsf@pelzflorian.de> (raw)
In-Reply-To: <875yefy665.fsf@gnu.org> ("Ludovic Courtès"'s message of "Tue, 13 Dec 2022 11:00:34 +0100")

Ludovic Courtès <ludo@gnu.org> writes:
> Specifically, here’s the minimal change we should test:[…]
> +                    (unless (file-exists? "/dev/fb0")
> +                      (setenv "LINUX_MODULE_DIRECTORY"
> +                              "/run/booted-system/kernel/lib/modules")

Thanks for the patch.

I found I can test in QEMU if I put nomodeset in the kernel arguments
in GRUB.

Without the patch, the screen stays black there too.
With the patch, it hrmm it also stays black.

I will next try using 'load-linux-modules-from-directory' and no
modprobe.

Regards,
Florian




  reply	other threads:[~2022-12-13 12:54 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) [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o7s7zcum.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=60010@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.