Skip to content

YUMI ID: fall back to eth0 / any wired port when end0 is absent - #1

Open
xtrack33 wants to merge 1 commit into
masterfrom
fix/yumi-id-interface-fallback
Open

YUMI ID: fall back to eth0 / any wired port when end0 is absent#1
xtrack33 wants to merge 1 commit into
masterfrom
fix/yumi-id-interface-fallback

Conversation

@xtrack33

@xtrack33 xtrack33 commented Sep 5, 2026

Copy link
Copy Markdown

The title bar shows YUMI ID: UNKNOWN on a DietPi-based YumiOS pad: the ID is the MAC of the wired port, read from end0 only (Armbian's predictable name for the H3 EMAC). With net.ifnames=0, or on a stock Debian, the same port is eth0 / enp1s0 / enx….

get_mac_address() now tries end0, then eth0, then any other en*/eth* interface in a stable order. end0 stays first, so every existing pad keeps exactly the value it had — same NIC, same MAC, same identity whatever the naming scheme. Checked with a fake netifaces for the Armbian (end0), DietPi (eth0), stock Debian (enp1s0) and no-wired-port cases.

YumiOS-Klipper-V2 also stops DietPi from renaming the port (net.ifnames=0 removed), so on our images end0 is back regardless of this change.

The YUMI ID shown in the title bar is the MAC address of the wired port,
read from the interface named end0 — Armbian's predictable name for the H3
EMAC. On a DietPi base (net.ifnames=0) or a stock Debian the same port is
eth0, enp1s0 or enx…, and the pad shows "YUMI ID: UNKNOWN".

Try end0 first, so every existing pad keeps exactly the value it had, then
eth0, then any other en*/eth* interface in a stable order. Same NIC, same
MAC: the identity does not change with the naming scheme.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant