mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Aditya Garg <gargaditya08@live.com>
To: "matthew.garrett@nebula.com" <matthew.garrett@nebula.com>,
	"jk@ozlabs.org" <jk@ozlabs.org>,
	"ardb@kernel.org" <ardb@kernel.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Orlando Chamberlain <redecorating@protonmail.com>
Subject: [REGRESSION] Failure to write the NVRAM variables starting from kernel 6.0 on T2 Macs
Date: Wed, 19 Oct 2022 19:26:04 +0000	[thread overview]
Message-ID: <23DC077F-69DF-402C-A940-2E7EEABF2D97@live.com> (raw)

Starting from linux kernel 6.0, the ability to write to the NVRAM has been lost on T2 Macs.

This has been observed especially during installation of boot loaders like GRUB, causing errors as shown :-

Installing for x86_64-efi platform.
grub-install: warning: Cannot set EFI variable Boot0001.
grub-install: warning: efivarfs_set_variable: writing to fd 7 failed: Invalid argument.
grub-install: warning: _efi_set_variable_mode: ops->set_variable() failed: Invalid argument.
grub-install: error: failed to register the EFI boot entry: Invalid argument.

I couldn't find any relevant error in journalctl though, but I still am posting my journalctl just in case I missed any error.

https://gist.github.com/AdityaGarg8/da7a9a2c891f5b2f68f71dc0d0e77f9a

Regards
Aditya

             reply	other threads:[~2022-10-19 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 19:26 Aditya Garg [this message]
2022-10-19 21:23 ` Ard Biesheuvel
2022-10-20 10:54   ` Aditya Garg
2022-10-26 21:18   ` Aditya Garg
2022-10-26 21:20     ` Ard Biesheuvel
2022-10-27  4:33       ` Aditya Garg

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=23DC077F-69DF-402C-A940-2E7EEABF2D97@live.com \
    --to=gargaditya08@live.com \
    --cc=ardb@kernel.org \
    --cc=jk@ozlabs.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew.garrett@nebula.com \
    --cc=redecorating@protonmail.com \
    /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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®