Installation on Yellow can not get past HAOS

Installation
1

Recently received a HA Yellow Rev. 1.3 std kit. RPi CM4 Lite with 2GB (CM4102000). Using a 512 GB HP SSD EX900 Plus M.2 NVMe for storage.
I used rpi-imager to create the Yellow install on a USB drive. Booted of the USB and the HAOS installed in a few minutes. Now it just boots to HAOS with the red and green LEDs on solid. I can ping 8.8.8.8 from HAOS prompt.
Here is the console output after the HAOS install:

[  179.935287] reboot: Power down
Core:  213 devices, 17 uclasses, devicetree: board
MMC:   mmcnr@7e300000: 1, mmc@7e340000: 0
Loading Environment from nowhere... OK
In:    serial
Out:   serial
Err:   serial
Net:   eth0: ethernet@7d580000
PCIe BRCM: link down
starting USB...
No working controllers found
Card did not respond to voltage select! : -110
Card did not respond to voltage select! : -110
MMC Device 2 not found
no mmc device at slot 2
PCIe BRCM: link down

Device 0: unknown device
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
PCIe BRCM: link down
ethernet@7d580000 Waiting for PHY auto negotiation to complete....... done
BOOTP broadcast 1
BOOTP broadcast 2
DHCP client bound to address 192.168.xx.yy (251 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-d8-3a-aa-bb-cc-dd
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8131D
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8131
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A813
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A81
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A8
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0A
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C0
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/C
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-bcm283x-rpi
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm-bcm283x
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default-arm
*** ERROR: `serverip' not set
Retrieving file: pxelinux.cfg/default
*** ERROR: `serverip' not set
Config file not found
starting USB...
No working controllers found
PCIe BRCM: link down
BOOTP broadcast 1
DHCP client bound to address 192.168.xx.yy (0 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
HAOS>

Console output has this level of RPi CM firmware:
raspberrypi-firmware soc:firmware: Attached to firmware from 2022-03-24T13:19:26, variant start

I’m at a loss. Help!

2

I connected the HA Yellow more ‘directly’ to the internet and got farther. Where is it supposed to go to get these images?

Device 0: unknown device
starting USB...
No working controllers found
USB is stopped. Please issue 'usb start' first.
starting USB...
No working controllers found
PCIe BRCM: link down
ethernet@7d580000 Waiting for PHY auto negotiation to complete..... done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
BOOTP broadcast 5
BOOTP broadcast 6
DHCP client bound to address 192.168.xx.yy (5761 ms)
*** Warning: no boot file name; using 'C0A842F2.img'
Using ethernet@7d580000 device
TFTP from server 192.168.xx.y; our IP address is 192.168.xx.yy
Filename 'C0A842F2.img'.
Load address: 0x1000000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
Retrieving file: pxelinux.cfg/01-d8-3a-dd-ee-ff-gg
Using ethernet@7d580000 device
TFTP from server 192.168.xx.y; our IP address is 192.168.xx.yy
Filename 'pxelinux.cfg/01-d8-3a-dd-ee-ff-gg'.
Load address: 0x2500000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
Retrieving file: pxelinux.cfg/C0A842F2
Using ethernet@7d580000 device
TFTP from server 192.168.xx.y; our IP address is 192.168.xx.yyy
Filename 'pxelinux.cfg/C0A842F2'.
Load address: 0x2500000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
... and so on...
3

It turns out have the right brand of NVMe is critical. Installed a Samsung 970EVO Plus as others have done and it is working just fine.