*** ERROR: `ethaddr' not set

I wanted to change the IP address of my GoFlexHome unit, so I ran:-

fw_setenv ipaddr 192.168.1.23

at a Debian command prompt. On reboot and stopping U-Boot and trying tftp xxxxxx yyyyy, I got an error msg saying "*** ERROR: `ethaddr' not set".
t
I did not change ethaddr so why is it not set and how do I go about setting it to its previous value?

balanga Wrote:
-------------------------------------------------------
> I wanted to change the IP address of my GoFlexHome
> unit, so I ran:-
>

> fw_setenv ipaddr 192.168.1.23
>

>
> at a Debian command prompt. On reboot and stopping
> U-Boot and trying tftp xxxxxx yyyyy, I got an
> error msg saying "*** ERROR: `ethaddr' not set".
> t
> I did not change ethaddr so why is it not set and
> how do I go about setting it to its previous
> value?

Going by your boot log in your other post

[    8.663773] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 52:3b:20:9c:11:51

in u-boot

setenv ethaddr  52:3b:20:9c:11:51

You will need to "saveenv" to keep it and your other values if they are correct.

> I did not change ethaddr so why is it not set
I can only guess as you did not save it

Something is well and truly screwed... I only set ipaddr and serverip but somehow the system wants to start using DHCP/BOOTP:-

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:21:31 -0700)
Seagate GoFlex Home

SoC:   Kirkwood 88F6281_A1
DRAM:  128 MiB
WARNING: Caches not enabled
NAND:  256 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot:  0 
BOOTP broadcast 1
*** Unhandled DHCP Option in OFFER/ACK: 125
*** Unhandled DHCP Option in OFFER/ACK: 125
DHCP client bound to address 192.168.1.54 (32 ms)
*** Warning: no boot file name; using 'C0A80136.img'
Using egiga0 device
TFTP from server 192.168.1.1; our IP address is 192.168.1.54
Filename 'C0A80136.img'.
Load address: 0x800000
Loading: T T T T T T T T T T

I have no idea how this came about or how to stop it. The serverip address I wanted to set was 192.168.1.43 and I didn't want to use DHCP. The system doesn't attempt to boot from usb 0:1 as it did previously if left uninterrupted.

I managed to boot by entering the following after stopping autoboot:-

GoFlexHome> load usb 0:1 0x800000 /boot/uImage
3821592 bytes read in 823 ms (4.4 MiB/s)
GoFlexHome> load usb 0:1 0x1100000 /boot/uInitrd
7245696 bytes read in 1019 ms (6.8 MiB/s)
GoFlexHome> load usb 0:1 0x1c00000 /boot/kirkwood-goflexhome.dtb
10603 bytes read in 739 ms (13.7 KiB/s)
GoFlexHome> bootm 0x800000  0x1100000  0x1c00000

but I'd prefer to boot directly from the USB stick by default if it is present.

I've just noticed after running fw_printenv from a Debian command prompt that I have this:

bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm

I didn't expect that and don't know where it comes from...