katoomba

I also have the same problem. The last image that worked for me was focal (buster also works). Bookworm boots but does not activate USB. Jammy does not boot at all. I'd like to help and have volunteered to help with maintaining the BPIm2zero. No word from the armbian crew if I will be accepted.

Thanks for that Igor, I don't suppose there is an example I2C buss overlay lying around somewhere? 🙂 If not, I will just have to skip on using armbian on RaspPi. Which is no big deal. I use bananaPi and OrangePi in my products anyway.

Hardware: RPi4B Image: Armbian_22.05.1_Rpi4b_jammy_current_5.15.36.img.xz armbian-config does not show "Hardware" option under "System". I used the best SDcard I have. The PSU works for everything I've plugged it into. I re-flashed the SDcard several times. And I tried some ways that I googled and some postings here. All to no avail. Any help would be much appreciated.

Incredible to myself, I didn't check for the latest version of armbian: https://www.armbian.com/bananapi-m2-zero/ When I used that image, my bananapi all run without a hitch.

I tried to use "userspace" and the bananapi stayed up for about four days. But then it crashed again. The red LED stops blinking (stays permanently on). And is no longer responsive on the network. Ping fails and checking ARP tables on the same network shows no MAC entry. So the bananapi seems to be locked up hard. Sometimes the HDMI shows a blank screen, sometimes it shows a crash debug. I tried to change the CPU parameters in /etc/default/cpufrequtils to "performance" but, after a reboot, I always got "ondemand" output from cpufreq-info. What I found was that there are other CPU management modules running. So I did this: sudo systemctl disable loadcpufreq.service sudo systemctl disable raspi-config.service sudo apt install cpufrequtils Then: sudo systemctl enable cpufrequtils.service sudo systemctl start cpufrequtils.service sudo systemctl status cpufrequtils.service Now I was able to set the parameters in /etc/default/cpufrequtils: #GOVERNOR="userspace" #MAX_SPEED="720000" #MIN_SPEED="720000" GOVERNOR="performance" MIN_SPEED="480000" MAX_SPEED="720000" Then: sudo systemctl daemon-reload sudo systemctl restart cpufrequtils.service sudo systemctl status cpufrequtils.service I tried "userspace" (commented out above) but bananapi crashed after four days. Now I am switched to "performance" (shown above) and I will see how it goes. I will also try "performance" without lower and upper freq limits. It would be great to hear from Igor why this change of cpu operating parameters is supposed to fix the hanging bananapi.