KaoDome

Hi @TonyB.ca, I have another NanoPi Neo3 and I'm experiencing the same you are, I wonder what could be happening. Right now, I have a stable build on Jammy, but I have another microSD with which I'm making tests to try to see how come the actual MAC from the device isn't picked up. Just now I finished building a current Bookworm based Armbian, but with u-boot being that of 2023.04 instead, same outcome. I know the board was released with u-boot 2017.sth, but I thought, what the hell, perhaps it's a bug in the 2022 versions. In any case, I'm at a loss, I'll try to find other boards that ship with real MACs and see if there's any difference on how they're defined in configuration files or kernel builds. For example, the NanoPi R4S used to ship with a unique MAC, but due to shortage of parts or something they can't guarantee that now unless you place a considerable order; that doesn't happen with the Neo3, even if ordered just one they do come with a unique address. If anyone comes across this thread and knows at least where we should look into, we'd appreciate it! I'm new to this kind of low level stuff.

Yes, I think it is better that way too, I read the announcement for 23.05 and for a fundamental change like that it doesn't hurt to be cautious. Thanks for the explanation! I can't like more than one post a day for now, but I appreciate it!

I see, I was also looking for this, wondering how come repos had 23.02 packages but there were 23.05 images for my board (NanoPi Neo3) up. In my case I will be looking at Bookworm based Armbian in another microSD to experiment, but keeping the one I have based on Jammy, there is no rush. By the way, if I build an image right now using the build environment, Linux would be 6.1.31 (just a tad newer than the one available in the official image, .30), if one were to use home-built images of Armbian, the system would still be updated when newer versions are in the repos, right? (current, unmodified kernel, not building edge)