Github messages for voidlinux
 help / color / mirror / Atom feed
From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] gummiboot broken with linux-mainline
Date: Sat, 22 Apr 2023 16:12:39 +0200	[thread overview]
Message-ID: <20230422141239.NddeNgErTCJVseZ9R-yTffNBhR6w4c4QrjfJc-SdtDM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-42566@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

Closed issue by junkmanner on void-packages repository

https://github.com/void-linux/void-packages/issues/42566

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.14_1 x86_64-musl AuthenticAMD uptodate rFF

### Package(s) Affected

gummiboot-48.1_8, linux6.2-6.2.0_1

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

The system is supposed to boot up normally.

### Actual behaviour

When trying to boot the system, my computer gets stuck in an infinite loop of the fans spinning up and down. I did a bit of reading around and testing, and if I build the kernel with EFI_HANDOVER_PROTOCOL=y, the computer boots without issue, which leads me to believe the the issue is that gummiboot uses the deprecated efi handover protocol, and therefore cannot boot on linux-mainline where EFI_HANDOVER_PROTOCOL is not set.

### Steps to reproduce

1. Install gummiboot as bootloader
2. Install linux-mainline
3. reboot

      parent reply	other threads:[~2023-04-22 14:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 12:28 [ISSUE] " junkmanner
2023-03-07 16:28 ` paper42
2023-03-07 16:29 ` classabbyamp
2023-03-07 16:31 ` classabbyamp
2023-03-07 16:39 ` zdykstra
2023-03-07 17:06 ` paper42
2023-03-08  7:33 ` sonnysighedup
2023-03-08 13:13 ` junkmanner
2023-04-22 14:12 ` Johnnynator [this message]

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=20230422141239.NddeNgErTCJVseZ9R-yTffNBhR6w4c4QrjfJc-SdtDM@z \
    --to=johnnynator@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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. 
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 NNTP newsgroup(s).