piter75's post in [Invalid] - NanoPi M4V2: SPI Not Working was marked as the answer
@TCB13 I am a bit late to the party but I figured it may still be needed ;-)
spi-spidev is a special / dynamic overlay. Besides enabling it you need to also configure it and armbian-config cannot currently do that.
For configuration options have a look here:
You can also consult the local README file located in: /boot/dtb/rockchip/overlay/README.rockchip-overlays
piter75's post in Randoms reboot NanoPi M4V2 was marked as the answer
@i5Js you can download these packages and install them with apt/dpkg: https://users.armbian.com/piter75/nanopim4v2-stability-fix/
You need both of them for the fix.
When they are correctly installed and the board is rebooted you should see this message in your dmesg:
piter@nanopim4v2-4:~$ dmesg | grep rk808-regulator.*buck [ 2.840331] rk808-regulator rk808-regulator: max buck steps per change: 4 The last "4" means you have the fix. No message or "8" means you don't have a fix.
piter75's post in NanopiM4V2 (Rockchip RK3399) RAID with mdadm appears to write wrong/ corrupt data was marked as the answer
Could you test this image with your procedure?
It should fix the issues with voltage scaling on little cores cluster that made my units unstable and fail in the first loop of "memtester 3280M".
With the fix it run 150 loops without failures.
piter75's post in limit SSD/NVME speed to save battery life? was marked as the answer
Hi, have your friend tried passing pcie_aspm.policy=powersave to the kernel's command line?
It can be done with "extraargs=" stanza in /etc/armbianEnv.txt
I use it with all (two ;p) my rk3399 nvme setups and also with my Armbian build server. I remember it lowering both SSD temps and overall power usage.
I don't have hard figures on both savings and performance loss and... YMMV depending on the drive but it's worth trying.
piter75's post in RockPi4 C USB 2.0 not working was marked as the answer
Did you use the w same image for ROCK Pi 4C and 4B?
4C needs different images for all usb ports to work properly.
You could also adjust the currently burnt image by editing fdtfile setting in /boot/armbianEnv.txt.
Make sure fdtfile contains 4c and not 4b and reboot.
All usb ports should be working after the reboot.