Werner

try https://archive.armbian.com
If not there they are gone.

https://github.com/McMCCRU/rtl8188gu

We only provide a small quantity of image combinations that are possible because building and providing them all would be just insane.
 
Check here for building your own customized image: https://github.com/armbian/build

You cannot install amd64 binaries on arm hardware.

As always the solution pops up once I start complaining
 
Seems like my 64G microSD is cursed. It works well on common usage but it refuses to work properly on SBCs. Not wrote the same image to a 32G SD of same quality and brand and it works...

Posting the same question on multiple occasions is considered abusive behavior.

Is that arm'ish enough?

Thanks
 
https://github.com/armbian/build/pull/4466

Correct. That way of installation has been removed by HASS and therefore broke our installer which then got removed:https://github.com/home-assistant/supervised-installer/commit/ece9fcc9468be41c67d052e043a9e70bad16a67a
 
You have to figure some manual way of installation. No idea though what packages are available and so on.

Did you do apt update beforehand?

This sounds quite confusing.
 
PHY is set to DHCP by default so it tries to aquire a lease by a DHCP server available in the network. If you don't have one you have to find another way to make the board connectable via copper. Like using UART serial console or build your own script using custom configuration.
Cannot say about using Pi as DHCP since I dont know your full network setup and therefore no idea if that would work. A dhcp server is usually also some kind a router to NAT data to a different network or WAN.

With MS Windows you can also try https://gitlab.com/bztsrc/usbimager
With Linux I'd simply go for dd if to create an image from an sdcard.

Depending n Armbian flavor (Bullseye, Jammy....) various Python versions are available for install via apt.

https://github.com/armbian/build/blob/master/config/boards/tinkerboard-2.wip
Feel free to join development
 

Userspace upgrades (Buster->Bullseye or Focal->Jammy) are neither tested nor supported.
 
Try replacing rootfs package.

We have some issues with the redirector. You can work around this by setting a random mirror from the list in your apt for now.
https://github.com/armbian/mirror

Lots of boards have been removed from support and automated builds according to https://www.armbian.com/newsflash/armbian-needs-your-help/
If you need an image for this board either build by yourself or check archive.

There are no such plans due to lack of human resources and literally thousands of other tasks waiting for being worked on.

check your sshd_config if PubkeyAuthentication is enabled.

Moved to Common issues / peer to peer technical support
Use proper way to prepare sd card: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-prepare-a-sd-card

Here are a few hints how to tweak journal: https://askubuntu.com/questions/1238214/big-var-log-journal

Did you check /etc/default/armbian-ramlog ?

R1 != R1S
Both boards may have a different WiFi Chip and therefore the device tree may not fit.

I usually do the noob way finding the trigger files for LEDs
code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } du -a /sys | grep led | grep trigger
 
I don't know what trigger is needed for mmc but heartbeat is self-explaining. code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } echo heartbeat > trigger
 
 

https://www.arducam.com/nvidia-jetson-nano-b01-update-dual-camera/#jetson-nano-b01-vs-a02-changes
If this is true for Armbian no idea since it is CSC.