unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Hugo Buddelmeijer <hugo@buddelmeijer.nl>
Cc: 66651@debbugs.gnu.org
Subject: bug#66651: How to pass i915.enable_guc=0 in config.scm to prevent a 'wedged' GPU?
Date: Fri, 20 Oct 2023 20:38:30 +0200	[thread overview]
Message-ID: <cuco7gtdtm9.fsf@riseup.net> (raw)
In-Reply-To: <CA+Jv8O2G0g_022ctO4+ncVxgwShPQgV6xiQHXrh1fFP8gXBcKg@mail.gmail.com>


Hugo Buddelmeijer <hugo@buddelmeijer.nl> writes:

> The i915 driver will try to load the GuC firmware, at least for Iris
> Xe chips. Loading the GuC firmware fails because it is non-free and
> deblobbed. As a result, some software, like sway, will not work.
>
> It is possible to manually pass the i915.enable_guc=0 kernel parameter
> at boot from grub. Then everything works as intended. However, it
> seems not possible to set this parameter from config.scm.
>
> So at the moment my system is not fully declarative, as I have to type
> in a kernel parameter at boot; does anyone perhaps have advice on how
> can this be done better?
> ...

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.

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




  reply	other threads:[~2023-10-20 18:42 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 [this message]
2023-10-20 19:39 ` bug#66651: Hugo Buddelmeijer
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=cuco7gtdtm9.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=66651@debbugs.gnu.org \
    --cc=hugo@buddelmeijer.nl \
    /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).