Bug 240228 - sysutils/u-boot-rpi3: program name not passed to argument list anymore
Summary: sysutils/u-boot-rpi3: program name not passed to argument list anymore
Status: New
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Only Me
Assignee: freebsd-ports-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-08-31 09:28 UTC by Sylvain Garrigues
Modified: 2020-09-17 09:39 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sylvain Garrigues 2019-08-31 09:28:10 UTC
I used to add, in rpi3_fragment:
CONFIG_USE_BOOTARGS=y
CONFIG_BOOTARGS="rootdev=disk1p2"

in the u-boot rpi3 port I had, which was version 2018.09

Now with the latest u-boot port, the rootdev argument is not taken into account, and I found out that is because the program name is no longer added.

I have to use instead
CONFIG_USE_BOOTARGS=y
CONFIG_BOOTARGS="loader.efi rootdev=disk1p2"

to fix it.


2018.09 boot log:
 In:    serial
 Out:   vidconsole
 Err:   vidconsole
 Net:   No ethernet found.
 starting USB...
 USB0:   scanning bus 0 for devices... 4 USB Device(s) found
        scanning usb for storage devices... 1 Storage Device(s) found
 Hit any key to stop autoboot:  0
 MMC Device 0 not found
 no mmc device at slot 0
 switch to partitions #0, OK
 mmc1 is current device
 Scanning mmc 1:1...
 Found EFI removable media binary efi/boot/bootaa64.efi
 libfdt fdt_check_header(): FDT_ERR_BADMAGIC
 Scanning disk mmc@7e300000.blk...
 Scanning disk usb_mass_storage.lun0...
 Found 7 disks
 FDT memrsv map 0: Failed to add to map
 637000 bytes read in 59 ms (10.3 MiB/s)
 libfdt fdt_check_header(): FDT_ERR_BADMAGIC
 FDT memrsv map 0: Failed to add to map
 ## Starting EFI application at 00080000 ...
 Consoles: EFI console
 FreeBSD/arm64 EFI loader, Revision 1.1

    Command line arguments: loader.efi rootdev=disk1p2
    EFI version: 2.70
    EFI Firmware: Das U-Boot (rev 8216.2304)
    Console: efi (0)
    Load Path: /\efi\boot\bootaa64.efi
    Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8)
 Setting currdev to configured rootdev disk1p2


==============

2019.07 boot log (without fix):
---
 In:    serial
 Out:   vidconsole
 Err:   vidconsole
 Net:   No ethernet found.
 starting USB...
 Bus usb@7e980000: scanning bus usb@7e980000 for devices... 4 USB Device(s) found
        scanning usb for storage devices... 1 Storage Device(s) found
 Hit any key to stop autoboot:  0
 MMC Device 0 not found
 no mmc device at slot 0
 switch to partitions #0, OK
 mmc1 is current device
 Scanning mmc 1:1...
 Found EFI removable media binary efi/boot/bootaa64.efi
 libfdt fdt_check_header(): FDT_ERR_BADMAGIC
 Scanning disk mmc@7e300000.blk...
 Scanning disk usb_mass_storage.lun0...
 Found 7 disks
 FDT memrsv map 0: Failed to add to map
 BootOrder not defined
 EFI boot manager: Cannot load any image
 637000 bytes read in 63 ms (9.6 MiB/s)
 libfdt fdt_check_header(): FDT_ERR_BADMAGIC
 FDT memrsv map 0: Failed to add to map
 Consoles: EFI console
 FreeBSD/arm64 EFI loader, Revision 1.1

    Command line arguments: rootdev=disk1p2
    EFI version: 2.70
    EFI Firmware: Das U-Boot (rev 8217.1792)
    Console: efi (0)
    Load Path: /efi\boot\bootaa64.efi
    Load Device: /VenHw(e61d73b9-a384-4acc-aeab-82e828f3628b)/SD(1)/SD(0)/HD(1,0x01,0,0x81f,0x18fa8)
Comment 1 Bugzilla Automation freebsd_committer freebsd_triage 2019-08-31 09:28:10 UTC
Maintainer informed via mail
Comment 2 Emmanuel Vadot freebsd_committer freebsd_triage 2020-09-17 09:39:42 UTC
It this still relevant ?