unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Hugo Buddelmeijer <hugo@buddelmeijer.nl>
To: 66651@debbugs.gnu.org
Subject: bug#66651:
Date: Fri, 20 Oct 2023 19:39:27 +0000	[thread overview]
Message-ID: <CA+Jv8O0bpe=dpJKiCU2Znk3KXPFC8oJOzPXR-LJb87S1sO7m2A@mail.gmail.com> (raw)
In-Reply-To: <CA+Jv8O2G0g_022ctO4+ncVxgwShPQgV6xiQHXrh1fFP8gXBcKg@mail.gmail.com>

Csepp <raingloom <at> riseup.net> wrote:

> You can use the kernel-arguments option in the operating-system config.
> Untested:
> (kernel-arguments (cons "i915.enable_guc=0" %default-kernel-arguments))
> This should work, in theory.

Thanks, using kernel-arguments indeed works!

The idea to use i915.enable_guc came from the arch wiki [1], which states

> GuC functionality is controlled by the i915.enable_guc kernel parameter.

So I searched the Guix manual for "kernel parameter", and found the
sysctl section.

> I suspect that the sysctl thing doesn't work because it is done too late
> in the boot process.

That makes sense now I understand the difference between kernel
arguments and parameters in Guix. From the sysctl man page:

> sysctl  is  used to modify kernel parameters at runtime.

And that is indeed a bit late for deciding whether to load firmware.


About the default value: naively I would think that the default of
i915.enable_guc should be changed to 0 in the libre kernel, at least
for those chips that do not have free firmware.

At least now the term 'wedged' is part of the issue tracker, so other
affected people will hopefully find this.


This issue can be closed as far as I'm concerned, but I don't know how
to do that. Let's try this:

/close

Thanks again,

Hugo


[1] https://wiki.archlinux.org/title/Intel_graphics




  parent reply	other threads:[~2023-10-20 19:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-20 17:42 bug#66651: How to pass i915.enable_guc=0 in config.scm to prevent a 'wedged' GPU? Hugo Buddelmeijer
2023-10-20 18:38 ` Csepp
2023-10-20 19:39 ` Hugo Buddelmeijer [this message]
2023-10-20 20:56   ` bug#66651: Tobias Geerinckx-Rice via Bug reports for GNU Guix
2023-10-20 22:35   ` bug#66651: Maxim Cournoyer

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='CA+Jv8O0bpe=dpJKiCU2Znk3KXPFC8oJOzPXR-LJb87S1sO7m2A@mail.gmail.com' \
    --to=hugo@buddelmeijer.nl \
    --cc=66651@debbugs.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 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).