Re: Attempting to install on RPi4B w/ UEFI, having some problems

Robert Clausecker <[email protected]>
Newsgroups gmane.os.freebsd.devel.arm
Message-ID <[email protected]>
On Fri, Sep 11, 2020 at 01:56:10PM +0000, [email protected] wrote:
> September 11, 2020 2:42 PM, "Robert Clausecker" <[email protected]> wrote:
> 
> >> On 2020-Sep-10, at 13:11, Robert Clausecker <fuz at fuz.su> wrote:
> >> FYI: I use GPT partitioning. (No claim that you need to.)
> > 
> > Ah, good to know that that works. I was afraid the UEFI code
> > required an MBR scheme as the documentation indicated such.
> 
> EDK2 UEFI not supporting GPT would be *very* weird.
> I'm pretty sure the documentation was referring to the RPi early firmware.

Possible.  I may check this later tonight.  The main thing is that the
RPi4 firmware must be able to load UEFI's start4.elf from the EFI partition
within a GPT partition table.  Not sure if it can do that.

> Maybe the update that added pure-USB boot added GPT support there as well!
> 
> > But it appears that loading the DTB from the UEFI boot loader is not
> > supported at all. In fact, when I configure UEFI to generate a DTB
> > only (ACPI off), the kernel hangs during boot.
> 
> Well that might be a FreeBSD side problem.

Possibly.  I'm not entirely sure if it's really a kernel hang; some other
users suggested it might just be the kernel switching from serial console to
video output for the system console (it does stay at the serial console when
using ACPI).  I can't really tell as I don't have a way to attach a screen
ATM.  Any idea about debugging this further?

Yours,
Robert Clausecker

-- 
()  ascii ribbon campaign - for an 8-bit clean world 
/\  - against html email  - against proprietary attachments
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-arm
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.