Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #83023 > unrolled thread
| Started by | Tj <tj.iam.tj@proton.me> |
|---|---|
| First post | 2024-07-16 12:40 +0200 |
| Last post | 2024-07-16 12:40 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#989229: grub-install: warning: Cannot read EFI Boot* variables. Tj <tj.iam.tj@proton.me> - 2024-07-16 12:40 +0200
Processed: Re: grub-install: warning: Cannot read EFI Boot* variables. "Debian Bug Tracking System" <owner@bugs.debian.org> - 2024-07-16 12:40 +0200
| From | Tj <tj.iam.tj@proton.me> |
|---|---|
| Date | 2024-07-16 12:40 +0200 |
| Subject | Bug#989229: grub-install: warning: Cannot read EFI Boot* variables. |
| Message-ID | <J0NLb-2vtT-5@gated-at.bofh.it> |
Source: linux Followup-For: Bug #989229 X-Debbugs-Cc: tj.iam.tj@proton.me Control: tag -1 moreinfo This is in all probability a system (manufacturer's) firmware bug. The kernel is doing what it is designed to do; that is, try to recover from the system's UEFI Runtime Services causing a Page Fault. There are new firmware releases available for that model - upgrading may fix the bug: https://www.acer.com/gb-en/support/product-support/SP111-31N/ Latest listed is v1.11 2018-12-25. Bug report shows: [Sun Jul 11 20:36:36 2021] Hardware name: Acer Spin SP111-31N/Ironhide_AP, BIOS V1.02 01/04/2017 There was a similar report back in 2019 via Ubuntu and Upstream and the response upstream is informative: "Note that this is *not* a kernel panic. The kernel does exactly what we intended, which is to contain the page fault caused by the buggy firmware, and proceed without EFI runtime services. Unfortunately, this means that the installer cannot update the boot path so that grub gets invoked at boot by default. The only way to achieve this is probably to use 'bcfg' from the UEFI shell. Since this is closed source firmware provided by the hardware vendor, there is really very little we can do about this except complaining to them that their firmware is buggy. " https://bugzilla.kernel.org/show_bug.cgi?id=204289#c7
[toc] | [next] | [standalone]
| From | "Debian Bug Tracking System" <owner@bugs.debian.org> |
|---|---|
| Date | 2024-07-16 12:40 +0200 |
| Subject | Processed: Re: grub-install: warning: Cannot read EFI Boot* variables. |
| Message-ID | <J0NLb-2vtT-21@gated-at.bofh.it> |
| In reply to | #83023 |
Processing control commands: > tag -1 moreinfo Bug #989229 [linux] grub-install: warning: Cannot read EFI Boot* variables. Added tag(s) moreinfo. -- 989229: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989229 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web