Failed to install onto Raspberry Pi4

Installation
,
1

As far as I can tell, the install process is broken since the 3.13 OS update. I have followed these instructions multiple times, and also tried reverting back to hassos_rpi4-3.12.img (I’m trying to install hassos_rpi4-3.13.img). I’m using ethernet cable and can see traffic flow flow from the Pi and can ping it. It seems that regardless of how long I wait (well over 20 minutes) the hassos fails to initialise itself.

Is there a way to:

  1. Enable ssh at boot up time?
    OR
  2. Avoid hassos trying to self update itself?
2

For what it is worth my experience above lead me to come to change the MTU, which I assume is broken on some combination of Hassos and Rpi hardware:

ip link set dev eth0 mtu 900

where eth0 is your main network interface. Might be something different.

This was based off this post

3

It seems that the usual way of adding a file named “ssh” does not work.

My current and first attempt at installing Home Assistant on a RPi 3 B is not working, but I cannot tell if we have the same issue. However, you might be interesting to know of how I managed to get a trace of what is happening:

  • I connected a USB2Serial adapter to the RPi UART and to my desktop PC, and opened a terminal to it, with loggin to a file enabled.
  • I added the .necessary parameter (console=serial0,115200) to the cmdline.txt file on the SD card (actually to the SSD but this is another story).

This allowed me to discovered that the RPi, on boot, is trying to load its OS using BOOTP from my DHCP server. What, of course, does not have the slightest chance of working.

U-Boot 2020.01 (Apr 16 2020 - 02:07:37 +0000)

DRAM: 948 MiB
RPI 3 Model B (0xa02082)
MMC: mmc@7e202000: 0, mmcnr@7e300000: 1
In: serial
Out: serial
Err: serial
Net: No ethernet found.
starting USB…
Bus usb@7e980000: scanning bus usb@7e980000 for devices… 3 USB Device(s) found
scanning usb for storage devices… 0 Storage Device(s) found
WARNING at drivers/mmc/bcm2835_sdhost.c:410/bcm2835_send_command()!
WARNING at drivers/mmc/bcm2835_sdhost.c:410/bcm2835_send_command()!
Card did not respond to voltage select!
Card did not respond to voltage select!

Device 0: unknown device
Waiting for Ethernet connection… done.
BOOTP broadcast 1
DHCP client bound to address 10.40.0.10 (3 ms)
*** Warning: no boot file name; using ‘0A28000A.img’
Using smsc95xx_eth device
TFTP from server 10.40.0.1; our IP address is 10.40.0.10
Filename ‘0A28000A.img’.
Load address: 0x200000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
missing environment variable: pxeuuid
missing environment variable: bootfile

…

Filename ‘boot.scr.uimg’.
Load address: 0x2400000
Loading: T T T T T T T T T T
Retry count exceeded; starting again
HassOS>

I’ll open my own thread about this issue. But well, you might want to try the same to display what happens on your side, and diagnose your own issue.