grixm

Hi guys, I got a SPIdev overlay to work on the rock S0, figured I'd just share it here for the record, since I could have used this info myself (I spent days trying to figure it out since I had no experience with device trees or whatnot). Basically, download the attached .dts file, then run sudo armbian-add-overlay rk3308-spi2-spidev.dts I also edited /boot/armbianEnv.txt and added this line, but I'm unsure if that's actually necessary? param_spidev_spi_bus=2 This worked on Armbian 24.5.1 Noble, creating /dev/spidev2.0. You can verify that it works using this tool: https://github.com/rm-hull/spidev-test The dts file is based on this one from radxa, however changed to "fragment@" syntax like other armbian overlays: https://github.com/radxa-pkg/radxa-overlays/blob/main/arch/arm64/boot/dts/rockchip/overlays/rk3308-spi2-spidev.dts Maybe this will also work on Rock Pi S, but haven't tested. rk3308-spi2-spidev.dts

For the record, I finally found a solution. There is already a bash script in the rock pi s distribution that changes to a unique mac address. However for whatever reason this is not set up to run on the ethernet port, only on wifi. You can fix this by opening the file /etc/udev/rules.d/05-fixMACaddress.rules , adding this line: KERNEL=="end0", ACTION=="add" RUN+="fixEtherAddr %k 06" (Change end0 with eth0 on ubuntu version) PS: Even this didn't seem to work on older armbian versions like v22, but on v24 debian build it worked.

I have installed Armbian on my Rock Pi S, done some setup, and then taken an image of the disk to be duplicated to other devices. The problem is that each of these devices get the same permanent MAC address on the ethernet port as the first device. I don't know how Armbian gets the MAC address from the interface but it doesn't seem to depend on unique hardware, or if it does then the hardware ID isn't actually unique between boards. This leads to problems because my device is meant to be used several in the same network, causing collisions in DHCP assignment etc. I have tried multiple workarounds and none have worked well. I tried spoofing the MAC addr by changing the cloned-mac-address setting in NetworkManager. This worked at changing the MAC address, however it caused an entirely different problem, namely that a fallback connection with a link-local address never gets activated. It previously worked but after changing only this setting, it no longer works. I have no idea why but I have tried for days now to fix this issue and I'm out of new ideas. The other thing I tried was adding ethaddr=[some mac address] in the armbianEnv.txt file, as found in another forum thread. This didn't seem to do anything, the same duplicate MAC address was still used. I also tried using macchanger, but it was difficult to get to work nicely with NetworkManager, I don't think this is a good solution... What else can I try?

Hi, I'm trying to build an image on Windows. But when running compile.sh, I get the following error: [💲|💥] Problem detected [ WSL2 Terminal does not support UTF-8 ] Full log: https://paste.armbian.com/zopitumatu I don't know why this is happening, I've tried both cmd, powershell 5, powershell 7, all with the same result. The log mentions the Windows Terminal in the Microsoft Store should support it, but that already is installed and seems to just open the same Powershell 5, with the same error. Any idea on how to fix this?

Hi. For my application it would be very advantageous to speed up the boot time of the device as much as possible. The application depends on the network, and unfortunately it seems it takes a while for the interface to establish a connection. After plugging in the device, I count that it takes about 25-30 seconds until my application starts (which is set to start on reboot by cron). However, at that time, the network is still not up, so it matters little that the application has started. It takes another 20 seconds or so until the device is reachable by the network. So total 45-50 seconds from boot. Why is this? I see in systemd-analyze that NetworkManager.service starts at around 30 seconds, same as cron. So what is the holdup? The IP is static and it is plugged in with Ethernet, so I don't understand what takes time when it comes to connecting to the network, after the network manager has started. How can I troubleshoot this or make it connect faster? Bonus question. Another thing that takes a lot of time in the boot is armbian-ramlog.service, at nearly 8 seconds long. See attachment for full boot chart. Is there a way to shorten this too, without disabling ram logging entirely? bootanalyze.svg