20:46 <Armbian-Discord> <j​azza> klipper@pine64:~$ client_loop: send disconnect: Broken pipe

20:47 <Armbian-Discord> <j​azza> it was ssh

21:07 <Manouchehri> oh dang, so the R4SE needs a completely different image than the R4S?

21:09 <Manouchehri> The LAN port isn't showing up

21:13 <Manouchehri> wait wut it's working now after a reboot

21:14 <Manouchehri> rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!

21:14 <Manouchehri> that's what I had on a previous boot

21:23 <Armbian-Discord> <c​0rnelius> basically the u-boot dts needs to be edited to support eMMC along with the kernel patched to add the dts.

21:24 <Manouchehri> if I don't want to use the eMMC, is it fine to just use the same image as the R4S?

21:24 <Manouchehri> *same dts

21:26 <Armbian-Discord> <c​0rnelius> from what I was told its just the eMMC that didn't work. well that and the board doesn't have a unique mac addr.

21:27 <Manouchehri> on both LAN and WAN?

21:27 <Armbian-Discord> <c​0rnelius> yes.

21:28 <Armbian-Discord> <c​0rnelius> need to either force one with scripting or patch u-boot. honestly not sure if the u-boot method works though. I don't actually have the board.

21:29 <Manouchehri> Any idea on how I can tell WAN and LAN apart in a script?

21:29 <Manouchehri> like when I had that PCIe timeout issue, I had only eth0. Next boot, I had enp1s0 and eth1 (so no eth0).

21:31 <Armbian-Discord> <c​0rnelius> adding net.ifnames=0 to the boot command line should force eth0, eth1, eth2, etc.

21:33 <Manouchehri> hmm, is that the best way?

21:34 <Manouchehri> is there a way of naming them based on if it's the RTL8211E or RTL8111H?

21:36 <Armbian-Discord> <c​0rnelius> create a udev rule and you can name them that way.

21:36 <Manouchehri> thank you!! I totally overlooked udev.

21:38 <Manouchehri> Is it u-boot or the Linux kernel that sets the MAC address?

21:38 <Manouchehri> *sets the random MAC address

21:39 <Armbian-Discord> <c​0rnelius> I doubt this exact thing would work, but something like it. echo 'SUBSYSTEM=="net", ACTION=="add", DRIVERS=="rk_gmac-dwmac", KERNEL=="eth0", NAME="WAN"' > /etc/udev/rules.d/10-nanopi-r4se-eth.rules echo 'SUBSYSTEM=="net", ACTION=="add", DRIVERS=="r8169", KERNEL=="eth1", NAME="eth0"' >> /etc/udev/rules.d/10-nanopi-r4se-eth.rules

21:41 <Manouchehri> are addresses like e2:06:b3:xx:xx:xx random or unique?

21:43 <Armbian-Discord> <c​0rnelius> if the board doesn't have a unique one it will just spit out random ones during each reboot. friendlyarm did this to cut costs and they only offer units with one if you buy a large amount of them.

21:44 <Manouchehri> c0rnelius: perfect, thanks! I didn't realize they used two different drivers; I can actually use netplan here I think, with `driver: r8169` and `driver: st_gmac` :D

21:44 <Manouchehri> hmm, I don't think I get a random one on each reboot

21:44 <Armbian-Discord> <c​0rnelius> well thats good. don't play with it then 🙂

21:45 <Armbian-Discord> <c​0rnelius> don't fix what isnt broken

21:46 <Manouchehri> ehhh, I'd like to figure out why it's not random, so it doesn't screw me over later :P

21:48 <Armbian-Discord> <c​0rnelius> armbian has a script that will set the mac addr. I'm not sure if its currently running on ur system, but I have looked over the script before.

21:53 <Manouchehri> I don't see it in /boot/boot.cmd or /boot/armbianEnv.txt

22:00 <Manouchehri> c0rnelius: `xxd /sys/bus/nvmem/devices/rockchip-efuse0/nvmem` < what does this return for you on any of your nanopi devices?

22:01 <Armbian-Discord> <c​0rnelius> cat /sys/bus/nvmem/devices/rockchip-efuse0/nvmem RK3���!TMS624.00��,)

22:02 <Manouchehri> https://github.com/armbian/build/blob/master/packages/bsp/common/usr/lib/armbian/armbian-firstrun#L72-L78

22:02 <ArmbianHelper> ^ build/armbian-firstrun at master · armbian/build · GitHub

22:03 <Manouchehri> c0rnelius: odd, do you have a unique MAC address?

22:04 <Armbian-Discord> <c​0rnelius> thats the NanoPC T4 so I hope so 🙂 damn board cost a fortune.

22:04 <Manouchehri> ahh

22:04 <Armbian-Discord> <c​0rnelius> same SoC though.

22:09 <Manouchehri> hmm, I really am confused as to where this MAC address is coming from on mine

22:09 <Manouchehri> /boot/armbianEnv.txt doesn't have any MAC addresses in it

22:30 <Manouchehri> c0rnelius: looking at rk3399-nanopi4.dtsi now, it doesn't seem to set the MAC addresses

22:35 <Armbian-Discord> <c​0rnelius> I don't believe it would be in the dts.

22:36 <Manouchehri> `dtc -I fs -O dts /sys/firmware/devicetree/base` # dumps the current device-tree

22:37 <Manouchehri> I see `local-mac-address` defined for the PCIe ethernet card

22:37 <Armbian-Discord> <c​0rnelius> which is interesting.

22:38 <Armbian-Discord> <c​0rnelius> maybe you lucked out and got one with a MAC ADDR?

22:39 <Manouchehri> so I have 40 of these

22:39 <Manouchehri> trying to avoid needing to check them all

22:43 <Armbian-Discord> <c​0rnelius> I'm fairly certain if you order in bulk they come with an mac addr.

22:45 <Armbian-Discord> <c​0rnelius> but this says: Purportedly, you can order a NanoPi R4SE with a unique MAC address, but only if you order over 100 units

22:46 <Armbian-Discord> <c​0rnelius> I really don't know.

22:53 <Manouchehri> I mean there's physically a chip there or not, surely there's gotta be a way to detect it

22:57 <c0rnelius> whats in `/etc/systemd/network` do you see something like 99-default.link or something like that linking to `/dev/null` ?

23:01 <Manouchehri> c0rnelius: it's an empty folder

23:02 <c0rnelius> k

23:09 <Manouchehri> so addresses starting with e2 *are* local

23:10 <Manouchehri> https://gchq.github.io/CyberChef/#recipe=From_Hex('Auto')To_Binary('Space',8)&input=ZTI

23:10 <ArmbianHelper> ^ CyberChef

23:10 <Manouchehri> see how the second last bit there is 1?