fresh load via OOWOW
trying to build a headless server with the newest Ubuntu server possible.
Edge-V max
Every single time I reboot, the MAC address is different and the unit has a different IP…
Something is wrong with the Ubuntu image!
I have reloaded several times, confirmed it repeatedly…
fresh from image, just ran sudo apt update and upgrade.
Reboot - new ip - reboot again - new ip
on and on, my DHCP server is full of wasted addresses with random MAC all from this one issue!
Hello @JustSumDad
Can you provide this information? the MAC address may not be burned successfully.
khadas@Khadas:~$ cat /proc/cmdline
kasan.stacktrace=off kvm-arm.mode=protected cgroup_disable=pressure root=UUID=b959fe5e-f037-4df8-b06f-5d940af335c7 rootflags=data=writeback rw rootfstype=ext4 loglevel=4 no_console_suspend earlycon=aml-uart,0xff803000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 scsi_mod.scan=async xhci_hcd.quirks=0x800000 gamma=0 otg_device=1 reboot_mode_android=normal logo=osd0,loaded,0x3d800000 fb_width=1920 fb_height=1080 display_bpp=24 outputmode=none vout=none,disable panel_type=mipi_0 lcd_ctrl=0x00000083 hdmitx=,444,8bit hdmimode=1080p60hz hdmichecksum=0x00000000 frac_rate_policy=1 hdmi_read_edid=1 cvbsmode=576cvbs video_reverse=0 irq_check_en=0 androidboot.selinux=enforcing androidboot.firstboot=1 jtag= androidboot.hardware=amlogic androidboot.bootloader=01.01.240618.213256 androidboot.build.expect.baseband=N/A boot_source=emmc ddr_size=2 reboot_mode=normal androidboot.serialno=1234567890 mac=c8:63:14:71:48:dd androidboot.mac=c8:63:14:71:48:dd hwver=VIM3.V12 wol_ena
Make sure this is not installed.
$sudo apt remove macchanger
If it was installed
$sudo apt purge macchanger
It seems really odd the mac is rolling by its self, I can see the IP address doing that and that would be due to the gateway/router external to the board.
post this:
$sudo ifconfig
good thought but nope…
root@Khadas:~# sudo apt remove macchanger
Reading package lists… Done
Building dependency tree
Reading state information… Done
Package ‘macchanger’ is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
here is the response I got from that cmd
root@Khadas:~# cat /proc/cmdline
earlyprintk console=ttyS2,1500000n8 loglevel=0 rw root=UUID=01545e9d-30cd-4913-87aa-e0b184f9b223 rootfstype=ext4 init=/sbin/init rootwait fbcon=rotate:0 ubootpart=ecb74f2c-01 board_type=2 board_type_name=Edge-V khadas_board=Edge-V fan=auto mac=c8:63:14:70:42:70 androidboot.mac=c8:63:14:70:42:70 coherent_pool=2M imagetype=EMMC_MBR splash quiet plymouth.ignore-serial-consoles vt.handoff=7
I am also adding the result of IP a cmd to show that the MAC address is not the same.
root@Khadas:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether f6:a4:4b:77:45:8c brd ff:ff:ff:ff:ff:ff
inet 192.168.11.161/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
valid_lft 690802sec preferred_lft 690802sec
inet6 fe80::89f3:a4ae:3116:9914/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 28:ed:e0:e6:9e:64 brd ff:ff:ff:ff:ff:ff
I then rebooted and ran both cmd again, with these results.
root@Khadas:~# cat /proc/cmdline
earlyprintk console=ttyS2,1500000n8 loglevel=0 rw root=UUID=01545e9d-30cd-4913-87aa-e0b184f9b223 rootfstype=ext4 init=/sbin/init rootwait fbcon=rotate:0 ubootpart=ecb74f2c-01 board_type=2 board_type_name=Edge-V khadas_board=Edge-V fan=auto mac=c8:63:14:70:42:70 androidboot.mac=c8:63:14:70:42:70 coherent_pool=2M imagetype=EMMC_MBR splash quiet plymouth.ignore-serial-consoles vt.handoff=7
root@Khadas:~#
root@Khadas:~# ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 2a:fc:f8:c7:34:2f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.193/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
valid_lft 690802sec preferred_lft 690802sec
inet6 fe80::89f3:a4ae:3116:9914/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
link/ether 28:ed:e0:e6:9e:64 brd ff:ff:ff:ff:ff:ff
Each interface will have its own mac, that is normal. I was under the impression the interface eth0 or wlan0 was rolling. What you are showing is normal.
Its also best to either run wifi or wire, don’t run both at the same time on the internet gateway.
If you look at the results of ‘ip a’ you will see the mac of eth0 is rolling.
first boot -
f6:a4:4b:77:45:8c
next boot-
2a:fc:f8:c7:34:2f
Also this is only wired, eth0 - there is no wifi used in the current setup.
Note- another new random MAC on eth0
root@Khadas:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.119 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::e07c:3758:7139:2d91 prefixlen 64 scopeid 0x20
ether aa:ab:d1:3f:30:7c txqueuelen 1000 (Ethernet)
RX packets 9536 bytes 14125698 (14.1 MB)
RX errors 0 dropped 22 overruns 0 frame 0
TX packets 1628 bytes 121680 (121.6 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 31
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether 28:ed:e0:e6:9e:64 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
If you don’t have any thing of value on the board’s OS, I would just re-install the entire os including uboot. It is very odd, what is happening is not something that can be tracked down easily. Sorry, I am out of suggestions on this.
Sometimes its best to just start over. If you do decide to start over keep a list of everything you installed because sometimes that will have clues.
That might also be a setting in uboot, from a fading memory it seems like an option exists to roll the mac, its a security feature for a specific type of network presence.
nothing on the system yet, this is a fresh load.
Reloaded three times, same result.
Literally I just did Oowow cleaned the onboard memory completely, then dropped in the Ubuntu 20.04 server O/S - boot - sudo apt update and upgrade.
thats it, nothing else, this is what it does.
Edit:
I just did it again, even going so far as to do a full wipe of the 128gb onboard emmc memory first, then also useing the Oowow wizard I installed Ubuntu 20.04 server.
This time I did not run updates, just rebooted and checked reported MAC address. It chaned on every boot with NOTHING loaded or changed from the Oowow image installed.
then ran updates, rebooted -changed again.
now just for giggles I am running `sudo apt install update-manager-core
and sudo do-release-upgrade
I dont expect it to actually work of cource, but meh this box is doing nothing like it is…
Now to go clean my DHCP database of the dozen or so ghost entries this has left behind…
Hello @JustSumDad
Which image you installed? Please provide the information to us.
$ cat /etc/fenix-release
$ uname -a
Ok, this is interesting…
I loaded the Ubuntu 20.04 Gnome desktop version…
same issue…
going to try an android load… maybe something hardware is going on somehow…
Android does not have the issue. Seems to be only ubuntu images
ok, further messing with this…
tried a newer version of OOWOW
found version edge-oowow-240619.165-sd.img.gz
set that onto my SD card and booted it up… This version cannot get a list of images to burn…
I think maybe I should look for another way to load images…
are there any up to date Ubuntu images I can get and an alternate way to write them onto my Edge-V Max?
When I look at dl.khadas.com - Index of /products/edge1/firmware/ubuntu/emmc/
I dont see any images of any current versions of Ubuntu, everything is EOL…
Hello @JustSumDad
You can try the image here which will have fixed mac address.
all of those images are EOL.
Is the Edge V no longer supported by Khadas?
