OpenBSD Archive › openbsd port - arm

RPi 4 crash on install

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

Lee Nelson

RPi 4 crash on install

I get the following when trying to install arm64 on my RPi 4 (4GB RAM):

disks: sd0* sd1
>> OpenBSD/arm64 BOOTAA64 1.2
boot>
cannot open sd0a:/etc/random.seed: No such file or directory
booting sd0a:/bsd: 2357768+668612+8777672+715720
[195459+109+574488+215117]=0xff
e7b0
FACP CSRT DBG2 GTDT APIC PPTT BGRT

Clearly it's getting far enough to try to load the kernel, but then dies.

I am using the latest available miniroot
-rw-rw-r-- 1 lnelson lnelson 34603008 Oct 17 13:57 miniroot68.img
and the sha256 signature matches. It was written to the 2nd sd card (the
one on usb) with:
sudo dd if=miniroot68.img of=/dev/sda bs=1M status=progress

My SD card in the slot has UEFI Firmware v1.20. That much is working
since I get as far as trying to load the kernel.

The RPi eeprom is:
BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTLOADER: up-to-date
CURRENT: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
LATEST: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000138a1

What am I missing?

Mark Kettenis

Re: RPi 4 crash on install

> Date: Sun, 18 Oct 2020 14:02:23 -0700 (PDT)
> From: Lee Nelson <[hidden email]>
>
> I get the following when trying to install arm64 on my RPi 4 (4GB RAM):
>
> disks: sd0* sd1
> >> OpenBSD/arm64 BOOTAA64 1.2
> boot>
> cannot open sd0a:/etc/random.seed: No such file or directory
> booting sd0a:/bsd: 2357768+668612+8777672+715720
> [195459+109+574488+215117]=0xff
> e7b0
> FACP CSRT DBG2 GTDT APIC PPTT BGRT
>
>
> Clearly it's getting far enough to try to load the kernel, but then dies.
>
> I am using the latest available miniroot
> -rw-rw-r-- 1 lnelson lnelson 34603008 Oct 17 13:57 miniroot68.img
> and the sha256 signature matches. It was written to the 2nd sd card (the
> one on usb) with:
> sudo dd if=miniroot68.img of=/dev/sda bs=1M status=progress
>
> My SD card in the slot has UEFI Firmware v1.20. That much is working
> since I get as far as trying to load the kernel.
>
> The RPi eeprom is:
> BCM2711 detected
> Dedicated VL805 EEPROM detected
> BOOTLOADER: up-to-date
> CURRENT: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
> LATEST: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
> FW DIR: /lib/firmware/raspberrypi/bootloader/critical
> VL805: up-to-date
> CURRENT: 000138a1
> LATEST: 000138a1
>
> What am I missing?

Depending on how the firmware has been configured, kernel output will
appear on the serial console or on the display connected to the HDMI
port. Make sure you set it correctly. Make sure you adjust the
setting even if it already appears to set correctly as some UEFI
versions have bugs where it would only work correctly after setting a
new value.

Lee Nelson

Re: RPi 4 crash on install

I'm trying to find the firmware configuration that you are talking about.
I am following INSTALL.arm64 and:
https://www.sudopigeon.com/raspberry-pi/os-install-installing-openbsd-on-a-raspberry-pi-4/

I went back to version 1.16 of the UEFI firmware that was used in the
above tutorial. It didn't make any difference.

Is there some other source of information that I'm missing?

On Sun, 18 Oct 2020, Mark Kettenis wrote:

>> Date: Sun, 18 Oct 2020 14:02:23 -0700 (PDT)
>> From: Lee Nelson <[hidden email]>
>>
>> I get the following when trying to install arm64 on my RPi 4 (4GB RAM):
>>
>> disks: sd0* sd1
>>>> OpenBSD/arm64 BOOTAA64 1.2
>> boot>
>> cannot open sd0a:/etc/random.seed: No such file or directory
>> booting sd0a:/bsd: 2357768+668612+8777672+715720
>> [195459+109+574488+215117]=0xff
>> e7b0
>> FACP CSRT DBG2 GTDT APIC PPTT BGRT
>>
>>
>> Clearly it's getting far enough to try to load the kernel, but then dies.
>>
>> I am using the latest available miniroot
>> -rw-rw-r-- 1 lnelson lnelson 34603008 Oct 17 13:57 miniroot68.img
>> and the sha256 signature matches. It was written to the 2nd sd card (the
>> one on usb) with:
>> sudo dd if=miniroot68.img of=/dev/sda bs=1M status=progress
>>
>> My SD card in the slot has UEFI Firmware v1.20. That much is working
>> since I get as far as trying to load the kernel.
>>
>> The RPi eeprom is:
>> BCM2711 detected
>> Dedicated VL805 EEPROM detected
>> BOOTLOADER: up-to-date
>> CURRENT: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
>> LATEST: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
>> FW DIR: /lib/firmware/raspberrypi/bootloader/critical
>> VL805: up-to-date
>> CURRENT: 000138a1
>> LATEST: 000138a1
>>
>> What am I missing?
>
> Depending on how the firmware has been configured, kernel output will
> appear on the serial console or on the display connected to the HDMI
> port. Make sure you set it correctly. Make sure you adjust the
> setting even if it already appears to set correctly as some UEFI
> versions have bugs where it would only work correctly after setting a
> new value.
>

Lee Nelson

Re: RPi 4 crash on install

In reply to this post by Mark Kettenis

For the next person that finds this, the System Table Selection needs to
be set to ACPI + Devicetree. I found this in the UEFI menus at:
Device Managet -->
-Raspberry Pi Configuration -->
--Advanced Configuration

I also disabled the Limit RAM to 3GB.

On Sun, 18 Oct 2020, Mark Kettenis wrote:

Archimedes Gaviola

Re: RPi 4 crash on install

On Mon, Oct 19, 2020 at 6:47 AM Lee Nelson <[hidden email]> wrote:

> For the next person that finds this, the System Table Selection needs to
> be set to ACPI + Devicetree. I found this in the UEFI menus at:
> Device Managet -->
> -Raspberry Pi Configuration -->
> --Advanced Configuration
>

Hi Lee,

Some caution, with UEFI firmware version v1.19, switching the default ACPI
mode into Devicetree or ACPI+Devicetree modes will crash my Raspberry Pi
4B. In my case the model I have is with 2GB of RAM but I'm not sure if your
4GB model will behave the same. With UEFI v1.18, it's much more stable and
this is the current version I'm using at the moment. Devicetree mode is
working well.

Thanks and best regards,
Archimedes

> I also disabled the Limit RAM to 3GB.
>
> On Sun, 18 Oct 2020, Mark Kettenis wrote:
>
> >> Date: Sun, 18 Oct 2020 14:02:23 -0700 (PDT)
> >> From: Lee Nelson <[hidden email]>
> >>
> >> I get the following when trying to install arm64 on my RPi 4 (4GB RAM):
> >>
> >> disks: sd0* sd1
> >>>> OpenBSD/arm64 BOOTAA64 1.2
> >> boot>
> >> cannot open sd0a:/etc/random.seed: No such file or directory
> >> booting sd0a:/bsd: 2357768+668612+8777672+715720
> >> [195459+109+574488+215117]=0xff
> >> e7b0
> >> FACP CSRT DBG2 GTDT APIC PPTT BGRT
> >>
> >>
> >> Clearly it's getting far enough to try to load the kernel, but then
> dies.
> >>
> >> I am using the latest available miniroot
> >> -rw-rw-r-- 1 lnelson lnelson 34603008 Oct 17 13:57 miniroot68.img
> >> and the sha256 signature matches. It was written to the 2nd sd card
> (the
> >> one on usb) with:
> >> sudo dd if=miniroot68.img of=/dev/sda bs=1M status=progress
> >>
> >> My SD card in the slot has UEFI Firmware v1.20. That much is working
> >> since I get as far as trying to load the kernel.
> >>
> >> The RPi eeprom is:
> >> BCM2711 detected
> >> Dedicated VL805 EEPROM detected
> >> BOOTLOADER: up-to-date
> >> CURRENT: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
> >> LATEST: Thu 03 Sep 2020 12:11:43 PM UTC (1599135103)
> >> FW DIR: /lib/firmware/raspberrypi/bootloader/critical
> >> VL805: up-to-date
> >> CURRENT: 000138a1
> >> LATEST: 000138a1
> >>
> >> What am I missing?
> >
> > Depending on how the firmware has been configured, kernel output will
> > appear on the serial console or on the display connected to the HDMI
> > port. Make sure you set it correctly. Make sure you adjust the
> > setting even if it already appears to set correctly as some UEFI
> > versions have bugs where it would only work correctly after setting a
> > new value.
> >
>
>