Rare project developers

[Alexander Gall <>]

On Wed, 8 Mar 2023 11:15:04 +0100, mc36 <> said:

> ONIE:/ #
> ONIE:/ # onie-self-update 
> http://files.mchome.nop.hu/inet/barefoot/onie-updater-x86_64-asterfusion_x312p-r0-20230307.bi
> n -f
> Notice:  Invalid TLV header found.  Using default contents.
> Notice:  Invalid TLV checksum found.  Using default contents.
> Info: Attempting 
> http://files.mchome.nop.hu/inet/barefoot/onie-updater-x86_64-asterfusion_x312p-r0-20230307.bin
>  ...
> Connecting to files.mchome.nop.hu (10.10.10.10:80)
> installer            100% 
> |**********************************************************************| 
> 12101k  0:00:00 ETA
> Verifying image checksum ... OK.
> Preparing image archive ... OK.
> ONIE: Version       : 2020.11-dirty
> ONIE: Architecture  : x86_64
> ONIE: Machine       : asterfusion_x312p
> ONIE: Machine Rev   : 0
> ONIE: Config Version: 1
> ONIE: Build Date    : 2023-03-06T12:48+00:00

At least the "-f" hack worked :)

> Installing ONIE on: /dev/sda
> ERROR: Problems accessing sys_eeprom
> Notice:  Invalid TLV header found.  Using default contents.
> Notice:  Invalid TLV checksum found.  Using default contents.
> ERROR: Cannot open I2C device

But now it's hopeless, since the unbranded ONIE doesn't know how to
access the I2C devices.

> Failure: Unable to install image: 
> http://files.mchome.nop.hu/inet/barefoot/onie-updater-x86_64-asterfusion_x312p-r0-20230307.bin
> ONIE:/ #
> ONIE:/ #
> ONIE:/ #

So let's forget about the self-update then (and I have learned that
one cannot change the "branding" of an installed ONIE via this
mechanism). The only way to proceed is via the recovery image and USB,
AFAICT. What exactly was the problem with booting from USB?

-- 
Alex