[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openbsd-bugs
Subject:    Re: sysupgrade boot.bin apply m1 boot failure
From:       Klemens Nanni <kn () openbsd ! org>
Date:       2024-04-29 20:14:58
Message-ID: vtstlhbn3lu67a6fmkpls3xywo6ugxd4az6lkdyit3cepgodoc () u7qtcd65u6ec
[Download RAW message or body]

On Mon, Apr 29, 2024 at 12:58:25PM GMT, bobby@plexuscomp.com wrote:
> > Synopsis:	sysupgrade to latest snap results in bootloop, had to replace boot.bin
> > Category:	system aarch64
> > Environment:
> 	System      : OpenBSD 7.5
> 	Details     : OpenBSD 7.5-current (GENERIC.MP) #19: Sun Apr 28 13:44:22 MDT 2024
> 			 deraadt@arm64.openbsd.org:/usr/src/sys/arch/arm64/compile/GENERIC.MP
> 
> 	Architecture: OpenBSD.arm64
> 	Machine     : arm64
> > Description:
> 	Upgraded my m1 macbook air to the latest snapshot.
> After the installation, reboot, I see the mac logo, asahi logo, no OpenBSD logo, \
> then it reboots and repeats. I copied /m1n1/boot.bin from another asahi efi \
> partition to the OpenBSD m1n1 partition and it boots again. 
> > How-To-Repeat:
> 	Install a snapshot on a mac?

For the archives:  Installing is not enough, apple-boot's m1n1/boot.bin is
put there by installboot(8) which is run before fw_update(8) fetched it.

So far, it takes an upgrade or manual installboot to boot our firmware
(and thus see the OpenBSD logo).

> > Fix:
 	Use a boot.bin from asahi


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic