Re: git: 1dec3639fd0c - main - sysutils/u-boot: Update to 2021.07

On 8/20/2021 03:42, Emmanuel Vadot wrote:
> On Thu, 19 Aug 2021 18:39:37 -0400
> Karl Denninger <[email protected]> wrote:
>
>> Ok, something else funny is going on now..... and I'm not at all sure
>> what, or how to diagnose further.
>>
>> I grabbed the last u-Boot, which 2021.04 (April 13th) and put that on
>> the disk, and restored the config.txt.
>>
>> Now I get this:
>>
>> U-Boot 2021.04 (Apr 13 2021 - 03:57:26 +0000)
>>
>> DRAM:  948 MiB
>> RPI 3 Model B (0xa22082)
>> MMC:   mmc@7e300000: 0
>> Loading Environment from FAT... In:    serial
>> Out:   vidconsole
>> Err:   vidconsole
>> Net:   No ethernet found.
>> starting USB...
>> Bus usb@7e980000: USB DWC2
>> scanning bus usb@7e980000 for devices... 3 USB Device(s) found
>>          scanning usb for storage devices... 0 Storage Device(s) found
>> Hit any key to stop autoboot:  0
>> switch to partitions #0, OK
>> mmc0 is current device
>> Scanning mmc 0:1...
>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>> Scanning disk [email protected]...
>> ** Unrecognized filesystem type **  <<<<----- Huh?
>> Found 3 disks
>> No EFI system partition
>> BootOrder not defined
>> EFI boot manager: Cannot load any image
>> Found EFI removable media binary efi/boot/bootaa64.efi
>> 97448 bytes read in 35 ms (2.7 MiB/s)
>> libfdt fdt_check_header(): FDT_ERR_BADMAGIC
>> Booting /efi\boot\bootaa64.efi
>>
>> Except that starts, and then..
>>
>>   >> FreeBSD EFI boot block
>>      Loader path: /boot/loader.efi
>>
>>      Initializing modules: ZFS UFS
>>      Load Path: /efi\boot\bootaa64.efi
>>      Load Device:
>> /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(2)/SD(0)/HD(1,MBR,0x76440bf1,0x3f,0x18fe7)
>>      Probing 3 block devices...not supported
>> not supported
>> not supported
>>    done
>>       ZFS found no pools
>>       UFS found no partitions
>> Failed to load '/boot/loader.efi'
>> panic: No bootable partitions found!
>> ## Application failed, r = 1
>> EFI LOAD FAILED: continuing...
>> MMC Device 1 not found
>> no mmc device at slot 1
>>
>> Which implies I got the bootaa64.efi code loaded and then the EFI code
>> blew up looking for a bootable filesystem.
>   It looks like you're using boot1.efi as /esp/efi/boot/bootaa64.efi, do
> not do that, use loader.efi directly.

Indeed that's what it was.  Will adjust Crochet accordingly; I should 
have remembered this as I got bit by it on my AMD64 system sometime 
around 12.1 as well (with the same fix.)

Now if we can get the upstream u-boot fixed so I don't have to screw 
with that..... (which should also stop the problem for pre-built images 
too.)

-- 
Karl Denninger
[email protected] <mailto:[email protected]>
/The Market Ticker/
/[S/MIME encrypted email preferred]/