hello , im a 0 in linux ,

i have orange 5 with mvme ,

i folowed how to for boot directly to mvme ,
the how to made me delete the spi flash.

all was good, o5 boot on mvme succesfully
but at each reboot , my hardware have new mac adress.

any one can show me what to do step by step ?

i used :
Joshua-Riek/ubuntu-orange-pi5: Ubuntu 22.04 LTS for the Orange Pi5  ( desktop & serveur )
Armbian_23.02.2_Orangepi5_jammy_legacy_5.10.110.img.xz

ubuntu serveur 23.04 ( 64 )

 

it's the same on all ,
boot one time i have mac adress , reboot = new mac adress
i cant fix ip localy ,
so i think when i deleted spi flash , may be deleted config to get fixed mac adress ?

any help / link ?  , thank's
 

Try to set ethaddr in /boot/armbianEnv.txt

random mac generator: https://www.browserling.com/tools/random-mac

yep ,i tryed mac changer and other way
but nothing fix.

i assigned all other hardware with a ip with my box
and set dhcp with only 1 adress.. only way to get always same ip ...
but at each reboot , mac adress change (but no probleme to let it work ... )

Edited April 24, 20233 yr by J. C.

In gnome settings -> network -> settings wired -> identity -> choose mac -> set on permanent

 

Or this config file might help:

https://github.com/Joshua-Riek/ubuntu-orange-pi5/blob/main/overlay/usr/lib/NetworkManager/conf.d/10-override-wifi-random-mac-disable.conf

On 4/23/2023 at 11:58 PM, Werner said:

Try to set ethaddr in /boot/armbianEnv.txt

that one is still broken in 23.8 - it doesn't do anything

On 4/23/2023 at 5:56 PM, J. C. said:

any help / link ?  , thank's

Here is what worked for me - this is from the armbian init scripts not sure why they did not work in the first place

 

#!/bin/sh
UUID=8bc44dd6-7880-36fd-93e8-09b4dccd0b2d #take this from nmcli
nmcli connection down $UUID
nmcli connection modify $UUID ethernet.cloned-mac-address "44:ee:bc:6c:76:ba" #put here your preferred MAC address
nmcli connection modify $UUID -ethernet.mac-address ""
nmcli connection up $UUID

Use

nmcli connection show

to get the interface's UUID

@OttawaHacker Thank you for sharing the solution. I just followed your guide and it worked after first reboot. 

By the way, later on, after several other reboot, the mac is reset again.

Do you have any other suggesstion to fix?

 

Thank you.

Edited September 10, 20233 yr by chinhhut

8 hours ago, chinhhut said:

Thank you for sharing the solution. I just followed your guide and it worked after first reboot. 

By the way, later on, after several other reboot, the mac is reset again.

Do you have any other suggestion to fi

My solution has been stable - wondering if you possibly have some other network settings that might interfere. You could just put this script into one of the network init scripts to apply it on every boot.

10 hours ago, OttawaHacker said:

My solution has been stable - wondering if you possibly have some other network settings that might interfere. You could just put this script into one of the network init scripts to apply it on every boot.

I used the latest build of Orange pi 5b.  The strange point is our ethernet inteface is "end1" while normally it should be "eth0".

 

By the way, I tried other solution by editting the file /etc/network/interfaces and it seems to work well up to now.

Quote

allow-hotplug eth0
no-auto-down eth0
iface eth0 inet dhcp
    hwaddress 12:34:56:78:90:ab

 

On 9/10/2023 at 10:47 PM, chinhhut said:

By the way, I tried other solution by editting the file /etc/network/interfaces and it seems to work well up to now.

Yes this is the solution if you don't have NetworkManager installed - which should be the case on Debian/non desktop Ubuntu.

I think this is due to the bootloader. Try to revert the below commit in u-boot.

https://github.com/orangepi-xunlong/u-boot-orangepi/commit/1f70ac3a968d121d86350092a7eff0dbd56114b7

 

This u-boot patch was accompanied by a kernel patch where boards set the mac address based on a serial number. This kernel patch is not in the legacy rockchp kernel, so try to revert the above commit in u-boot.

8 hours ago, Spooky said:

I think this is due to the bootloader. Try to revert the below commit in u-boot.

could you help me how to do the u-boot patch according to your source code? I guess it may require to build the u-boot file again manually?

I've posted a working solution here, until a better fix comes out or it's patched.