From: FingerlessGloves via pve-user <pve-user@lists.proxmox.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Cc: FingerlessGloves <me@FingerlessGloves.me>
Subject: Re: [PVE-User] 8.2-1 ISO doesn't boot via UEFI on usb
Date: Wed, 21 Aug 2024 13:20:01 +0100 [thread overview]
Message-ID: <mailman.352.1724243316.302.pve-user@lists.proxmox.com> (raw)
In-Reply-To: <f271301a-2042-1c90-42b1-143df97a5539@bryanfields.net>
[-- Attachment #1: Type: message/rfc822, Size: 5532 bytes --]
From: FingerlessGloves <me@FingerlessGloves.me>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] 8.2-1 ISO doesn't boot via UEFI on usb
Date: Wed, 21 Aug 2024 13:20:01 +0100
Message-ID: <95c4644326685997e297963d1007b0b3@FingerlessGloves.me>
Hi,
I recently built some new Proxmox hosts, with Ryzen 7000 series CPUs. I
had issues with UEFI as well, one system was Asrock Rack B650D4U and the
other was Minisforum MS-A1. On both systems I had to disable Secureboot
as I just couldn't get it working. I even tried the process linked
before to no avail either. I would disable secureboot over using BIOS
boot. I also have had the issue with an older Intel based Lenovo M920Q
as well.
Would be nice if Proxmox could provide certificates that could be
imported to the firmware to fix the trust issue, as the certificates
linked in the post below from Microsoft are the only ones I could find,
don't work. Not sure how it worked for the original poster, but I've
tried it on different systems now with no luck.
https://forum.proxmox.com/threads/import-secure-boot-certificate-used-by-proxmox.146027/
---
FingerlessGloves
On 2024-08-21 01:10 PM, Bryan Fields wrote:
> On 8/21/24 7:52 AM, Bryan Fields wrote:
>> I've setup to boot UEFI in the bios and
>> when selecting the usb stick with partition 2 for UEFI boot, I get the
>> GRUB
>> LOADING output and then nothing else.
>
> Sorry was going from memory here. It says:
>
> READY TO BOOT...Welcome to GRUB!
>
> Then after about 60 seconds this is printed:
>
> error: no such device /.disk/info.
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
pve-user mailing list
pve-user@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2024-08-21 12:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 11:52 Bryan Fields
2024-08-21 12:10 ` Gilberto Ferreira
2024-08-21 12:10 ` Bryan Fields
2024-08-21 12:20 ` FingerlessGloves via pve-user [this message]
2024-08-21 12:39 ` Demian Romeijn via pve-user
2024-08-21 16:17 ` Bryan Fields
2024-09-06 17:28 ` Bryan Fields
2024-09-06 20:06 ` Stefan Radman via pve-user
2024-09-06 23:07 ` Bryan Fields
2024-09-07 0:04 ` [PVE-User] Proxmox 8.x UEFI boot issues on supermicro x10/x11 (was 8.2-1 ISO doesn't boot via UEFI on usb) Bryan Fields
2024-09-07 9:42 ` Gilberto Ferreira
2024-09-07 16:47 ` Bryan Fields
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=mailman.352.1724243316.302.pve-user@lists.proxmox.com \
--to=pve-user@lists.proxmox.com \
--cc=me@FingerlessGloves.me \
/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