On Sun, Mar 26, 2017 at 05:49:12AM +1100, Jonathan Gray wrote: > On Sat, Mar 25, 2017 at 06:29:32PM +0000, Florian Obser wrote: > > > > ... it just sits here forever. > > > > Using hostserver's archive I bisected miniroots and found that > > this one works: > > > > https://ftp.hostserver.de/archive/2017-03-07-0105/snapshots/armv7/miniroot-panda-61.fs > > OpenBSD 6.1-beta (RAMDISK) #52: Sun Mar 5 15:11:37 MST 2017 > > > > U-Boot SPL 2016.11 (Dec 24 2016 - 09:08:50) > > OMAP4460-GP ES1.1 > > Trying to boot from MMC1 > > SPL: Please implement spl_start_uboot() for your board > > SPL: Direct Linux boot not active! > > reading u-boot.img > > reading u-boot.img > > > > > > U-Boot 2016.11 (Dec 24 2016 - 09:08:50 -0700) > > > > CPU : OMAP4460-GP ES1.1 > > Board: OMAP4 Panda > > I2C: ready > > DRAM: 1 GiB > > MMC: OMAP SD/MMC: 0 > > reading uboot.env > > > > ** Unable to read "uboot.env" from mmc0:1 ** > > Using default environment > > > > Net: No ethernet found. > > Hit any key to stop autoboot: 0 > > switch to partitions #0, OK > > mmc0 is current device > > SD/MMC found on device 0 > > reading boot.scr > > ** Unable to read file boot.scr ** > > reading uEnv.txt > > ** Unable to read file uEnv.txt ** > > switch to partitions #0, OK > > mmc0 is current device > > Scanning mmc 0:1... > > reading /omap4-panda-es.dtb > > 58423 bytes read in 8 ms (7 MiB/s) > > Found EFI removable media binary efi/boot/bootarm.efi > > reading efi/boot/bootarm.efi > > 64684 bytes read in 10 ms (6.2 MiB/s) > > ## Starting EFI application at 0x82000000 ... > > CACHE: Misaligned operation at range [bcf36000, bcf45cac] > > Scanning disks on usb... > > Scanning disks on mmc... > > MMC Device 1 not found > > MMC Device 2 not found > > MMC Device 3 not found > > Found 5 disks > > >> OpenBSD/armv7 BOOTARM 0.5 > > boot> > > cannot open sd0a:/etc/random.seed: No such file or directory > > booting sd0a:/bsd: 2168072+7992960+438796 [80+305024+146122]=0xa90cc4 > > > > OpenBSD/armv7 booting ... > > arg0 0xc0d90cc4 arg1 0xae7 arg2 0x88000000 > > Allocating page tables > > freestart = 0x80d91000, free_pages = 258671 (0x0003f26f) > > [...] > > > > and this one is busted: > > > > https://ftp.hostserver.de/archive/2017-03-09-0105/snapshots/armv7/miniroot-panda-61.fs > > OpenBSD 6.1-beta (RAMDISK) #54: Wed Mar 8 02:59:20 MST 2017 > > > > > > U-Boot SPL 2017.01 (Feb 04 2017 - 18:38:04) > > OMAP4460-GP ES1.1 > > Trying to boot from MMC1SPL: Please implement spl_start_uboot() for your > > board > > SPL: Direct Linux boot not active! > > reading u-boot.img > > reading u-boot.img > > > > [and then nothing] > > > > Using a working miniroot I can install the system and then use bsd.rd > > to upgrade the system past the breakage. > > The u-boot port has had newer versions for some time now. If you > install the u-boot-arm-2017.03 package from the amd64 packages > and copy > /usr/local/share/u-boot/omap4_panda/{MLO,u-boot.img} > to the msdos partition on the miniroot does that change anything?
yep, that works. No idea why the 2017.01 u-boot works for an installed system but not for the miniroot but I guess that's not really important? Thanks, Florian -- I'm not entirely sure you are real.
