Werner

If you follow that way you could rip kernel package as well. That way the first working images for OPi Zero 2 were made. However Armbian does not want or like to do that since then you could basically directly use vendor provided images.https://docs.armbian.com/User-Guide_FAQ/#why-does-hardware-feature-xy-work-in-old-kernel-but-not-in-more-recent-one At the bottom line it all depends on the development for the SoC or family which in this case is rk35xx. If that grows adding support for different boards that are built around that SoC is easy in comparison but that also depends on having a person that knows how to do that and want to donate their precious time doing so. Both aren't easy to find .

Most of us do since there are no big companies or sponsors that give us big amounts of cash https://docs.armbian.com/Board_Maintainers_Procedures_and_Guidelines/

If they work independently fine but crash if they are connected both then it seems the PSU is too weak and drops voltage and therefore unexpected behavior like crashes can happen. If you are in electronics and like to tinker rather than directly grabbing a new PSU you could try to add an additional capacitor to compensate for load spikes that cause voltage drops. On the other hand oddly enough since basically ANY ATX PSU should be able to handle dozens of SBCs since they usually draw close to no power at all thanks to ARM architecture...

Are they visible if you do an code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } apt-cache search for those?

Check syslog/kernel output why root fs seem to have remounted ro.

moved to tvboxes

Can you verify that the file code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } /usr/share/keyrings/githubcli.gpg is there?

You can try to build your own legacy image using the build framework. However you might end up without connectivity since the PHY chip has changed and driver may not be present in 4.4.y branch. Well there is only one way to find out. https://github.com/armbian/build

moved

Edge, as its name implies, are bleeding edge that or functions of it can break any time. Might get fixed fast, maybe slow, maybe never. To avoid the mentioned issue I suggest to revert to stable current branch for now and give it another shot, maybe once the major version has been bumped.

Hi, Talk to the owner of the repo to provide the necessary key. No idea who is that though, certainly not us. Never saw those addresses. Therefore most likely not an official Armbian image but some 3rd party work.

Hm odd. You can install the correct headers the causal way via apt Never mind. Headers seem to be missing in repo or stuck in beta. Need to investigate.

Pure binary into txt would be a very (VERY!) long file containing nothing but 0 and 1 characters. So without knowing anything further about that binary this task is impossible.

I assume to be make armbian run in R4SE an additional patch is needed that enables eMMC in the device tree. Then nand-sata-installer should be able to do the rest.

Never heard of that device? Is that a random TV box?

These forums automatically grabs RSS/Atom feed from various sources. If you have an idea about what could be added feel free to leave a link here.

tl;dr: irc://irc.libera.chat/armbian Feel free to join us: Server: irc.libera.chat Ports: 6697 / non-SSL: 6667 Channels: #armbian, #armbian-commits, #armbian-rss There are even more channels available. Information about those and our services can be found in our documentation: https://docs.armbian.com/Community_IRC/ Registration with Nickserv is mandatory to join primary #armbian channel. Don't hesitate to get in touch with us