laibsch

Or simply add whatever packages you desire with apt.

"apt policy ffmpeg" FTW ;-) apt also has a command-line option to force the installation of a particular package version. To automate this, you can put a file under /etc/apt/preferences.d/

Thank you for your work, @dg4gg8cb9s

That sounds very interesting. Where can I read more about this? @m11k I hope you are still active in this forum.

Thank you for your answer. My board is not Rockchip-based, we have been generalizing the discussion for quite a while now. Well, and this is where it would get interesting but ...

What I like to do in such a case is link to archive.org. some spam got posted to this thread which I removed, so I felt like I might as well add an answer at the same time

dig through the github actions, how the images are compiled is public information ;-)

probably time for the serial console my suspicion tells me that it will be hard to get proper logs otherwise my suspicion is that some umounts does not come back. <- try to unmount everything you can before the reboot and see if that helps.

Oh, my bad. That does indeed look very custom-made. Just an idea, maybe get yourself a Molex 4-Pin IDE to SATA power cable (this one even has five power outlets) and then power the HDD separately? Maybe there is 12V on the board somewhere you can tap into. I am not an electrical engineer so better verify. You will likely have to come up with a unique solution at this point.

spendist is the maintainer of the Nanopi Neo. Maybe he has something to say. Did you try another kernel? Another OS?

Awesome! Please do elaborate. Please do elaborate. What is the cargo cult practiced here at Armbian? I'm old, but I'm still interested to learn, so please do teach me.

That is surprising. I don't think they are custom. Isn't this what you need? Or this one for just 1€. Search for "SATA power cable" and skip the 4-pin ones.

Providing logs with armbianmonitor -u helps with troubleshooting and significantly raises chances that issue gets addressed.

nice, thank you for your feedback

I will soon be in the situation of having an offsite Helios4 installation at my non-techie father's place on another continent. I want to prepare for being able to do remote updates and if possible even some Armbian image testing. For that, I need a robust, bullet-proof and fully remote mechanism. The most I should assume to be able to ask my father is to unplug and replug the machine to powercycle. I hope you guys don't mind me joining your conversation to discuss my options. In the past, I had a setup on X86 with grub that I would like to hopefully replicate now in function with the Helios 4. There was a very minimal (read-only?) OS in a partition (network with DHCP, sshd) that would be the default boot target. The machine would always boot into this after a power cycle. From there, I issued a grub-reboot command to reboot into my desired OS. If I screwed the main system up somehow, I was always able to go back into the minimal system. How would I go about doing that in the Armbian world? From your discussion, it seems to be about tweaking armbianEnv.txt. But how can I do that in a way that has a bullet-proof option the system falls back to after a power cycle but also allows me to tweak it in a way that survives a warm reboot? I do like btrfs a lot and believe it should play a role here. I read @eselarm mentioning btrfs support in u-boot. How can I verify which u-boot is installed on my machine and whether it supports btrfs or not? Edit: https://embear.ch/posts/sw-update-concepts/ https://rauc.io/ https://mender.io/ https://bootlin.com/pub/conferences/2022/elce/opdenacker-implementing-A-B-system-updates-with-u-boot/opdenacker-implementing-A-B-system-updates-with-u-boot.pdf