00:49 <Armbian-Discord> <M​anoftheSea> it seems like most boards expect to set the mac in the u-boot environment variables

00:52 <Manouchehri> ManoftheSea: How does u-boot set it?

00:52 <Armbian-Discord> <M​anoftheSea> ethaddr variable, and eth{1,2,3}addr variables

00:52 <Armbian-Discord> <M​anoftheSea> But I don't know how it's passed to the kernel

00:52 <Manouchehri> eth1addr=02:44:62:57:FC:7F

00:53 <Manouchehri> should that work in /boot/armbianEnv.txt?

00:53 <Armbian-Discord> <M​anoftheSea> if your boot script sources that file, yeah.

00:54 <Armbian-Discord> <M​anoftheSea> I expect u-boot's default script will pull in a boot.scr, which itself will pull in armbianEnv.txt

00:54 <Manouchehri> ManoftheSea: I just have a stock ish armbian build

00:54 <Manouchehri> I didn't write a boot script :p

00:54 <Armbian-Discord> <M​anoftheSea> it's stock

00:54 <Armbian-Discord> <M​anoftheSea> you should still see it in /boot/

00:54 <Manouchehri> alright so after adding that and rebooting, it doesn't seem to apply to either of my interfaces

00:55 <Armbian-Discord> <c​ats> The new redirector version is live, let me know if there are any issues :)

00:59 <Armbian-Discord> <M​anoftheSea> manouchehri, I'm not the most knowledgeable, but I would do: - interrupt u-boot from serial, printenv, inspect the default boot command. From that, see if it finds /boot/boot.scr, and check the contents of that file for including armbianEnv.txt. if all that happens: you're beyond what I know

01:06 <Manouchehri> root@nanopi-r4s:~# cat /boot/boot.cmd

01:06 <Manouchehri> # DO NOT EDIT THIS FILE

01:06 <Manouchehri> hmm, why can't I edit it? :P

01:20 <Armbian-Discord> <M​anoftheSea> I don't know on that one.

01:43 <Manouchehri> hang on, why do I have both eth* and enp*?

01:43 <Manouchehri> shouldn't I only have enp* _or_ eth*?

06:44 <CosmicDJ> Manouchehri: yes, having both should not be possible (unless you renamed your interfaces using udev rules for example)

10:39 <Armbian-Discord> <T​ony-SAN> Hello. What the difference between Jammy and Sid builds? I can't find info about this.

10:44 <c0rnelius> Jammy is the latest Ubuntu LTS and Sid is Debian unstable and shouldn't really be used by anyone except devs.

10:46 <Armbian-Discord> <T​ony-SAN> Ok. Thanks.

11:29 <p0g0> SID has it's virtues, but yes, it is the test bed for recent development. You might not need to be a developer so much as someone who can accept some bleeding edge and have an idea of how to handle (and maybe report) software flaws. The main virtue of SID for the "average" (but not innocent) user is that it's got the most recent releases of software anywhere in the Debian system. But, again, it has risks and you are likely not going to get much love when you

11:29 <p0g0> complain that something is broken.

14:02 <Manouchehri> CosmicDJ: I did a stock jammy build and had both.

14:04 <Armbian-Discord> <M​anoftheSea> sid will break.

14:24 <CosmicDJ> Manouchehri: I have armbian bullseye running on my r4s and see only eth* network interfaces

15:04 <Armbian-Discord> <T​enkawa> <CosmicDJ>: if you do a dmesg | grep firmware do you get any messages complaining about files?