Re: current for arm64 tries tftp first for some reason

Reply: void : "Re: current for arm64 tries tftp first for some reason"
Reply: void : "Re: current for arm64 tries tftp first for some reason"
In reply to: void : "current for arm64 tries tftp first for some reason"
Go to: [ bottom of page ] [ top of archives ] [ this month ]
From: Mark Millard <marklmi_at_yahoo.com>
Date: Wed, 10 Jan 2024 05:37:54 UTC
On Jan 7, 2024, at 05:02, void <void@f-m.fm> wrote:

> In FreeBSD-15.0-CURRENT-arm64-aarch64-RPI-20240104-8bf0882e186e-267378.img of
> 2024-01-04, when booting, the u-boot stage firstly looks for tftp. How can this be turned off? is it an issue that I need to raise
> directly with u-boot? I've only seen this behaviour before
> when there's been no bootable (microsd or usb3) media available.
> Now it seems tftp is tried first then usb3 and not the other
> way around.
> 
> If I'm not available at the console to ctrl-c multiple times, it would
> take ages to eventually(?) boot to usb3. Each line where it says
> 'Abort' is there I've had to manually ctrl-c

For the RPi4B context I'm dealing with I let the first
time boot go through all its TFTP failures. It produced
a:

-rwxr-xr-x  1 root wheel uarch      88 Dec 30 00:00:00 1979 /boot/efi/ubootefi.var

that was not there originally. I wonder if it gives a
means of control over such things that would be
remembered?

> ###########
> 
> U-Boot 2023.10 (Jan 04 2024 - 05:11:11 +0000)
> 
> DRAM:  998 MiB (effective 7.9 GiB)
> RPI 4 Model B (0xd03114)
> Core:  210 devices, 16 uclasses, devicetree: board
> MMC:   mmc@7e300000: 3, mmc@7e340000: 0
> Loading Environment from FAT... ** Bad device specification mmc 1 **
> In:    serial,usbkbd
> Out:   serial,vidconsole
> Err:   serial,vidconsole
> Net:   eth0: ethernet@7d580000
> PCIe BRCM: link up, 5.0 Gbps x1 (SSC)
> starting USB...
> Bus xhci_pci: Register 5000420 NbrPorts 5
> Starting the controller
> USB XHCI 1.00
> scanning bus xhci_pci for devices... 4 USB Device(s) found
>       scanning usb for storage devices... 1 Storage Device(s) found
>       Hit any key to stop autoboot:  0        sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_send_command: MMC: 3 busy timeout increasing to: 200 ms.
>       sdhci_send_command: MMC: 3 busy timeout increasing to: 400 ms.
>       sdhci_send_command: MMC: 3 busy timeout increasing to: 800 ms.
>       sdhci_send_command: MMC: 3 busy timeout increasing to: 1600 ms.
>       sdhci_send_command: MMC: 3 busy timeout increasing to: 3200 ms.
>       sdhci_send_command: MMC: 3 busy timeout.
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_send_command: MMC: 3 busy timeout.
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_send_command: MMC: 3 busy timeout.
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_send_command: MMC: 3 busy timeout.
>       Card did not respond to voltage select! : -110
>       BOOTP broadcast 1
>       DHCP client bound to address 192.168.1.81 (3 ms)
>       *** Warning: no boot file name; using 'C0A80151.img'
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'C0A80151.img'.
>       Load address: 0x80000
>       Loading: T        Abort
>       missing environment variable: pxeuuid
>       Retrieving file: pxelinux.cfg/01-dc-a6-32-e2-48-fc
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/01-dc-a6-32-e2-48-fc'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0A80151
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0A80151'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0A8015
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0A8015'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0A801
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0A801'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0A80
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0A80'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0A8
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0A8'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0A
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0A'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C0
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C0'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/C
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/C'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/default-arm-bcm283x-rpi'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/default-arm-bcm283x
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/default-arm-bcm283x'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/default-arm
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/default-arm'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       Retrieving file: pxelinux.cfg/default
>       Using ethernet@7d580000 device
>       TFTP from server 192.168.1.1; our IP address is 192.168.1.81
>       Filename 'pxelinux.cfg/default'.
>       Load address: 0x2500000
>       Loading: *
>       Abort
>       ** Booting bootflow 'usb_mass_storage.lun0.bootdev.part_1' with efi
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_set_clock: Timeout to wait cmd & data inhibit
>       sdhci_send_command: MMC: 3 busy timeout.
>       Card did not respond to voltage select! : -110
>       No EFI system partition
>       No EFI system partition
>       Failed to persist EFI variables
>       Booting /efi\boot\bootaa64.efi



===
Mark Millard
marklmi at yahoo.com