Werner

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

looks like you are not using Armbian. Therefore support cannot be provided.

There should be. I suggest to start investigation here: https://github.com/armbian/build/blob/main/config/boards/nanopi-r4s.conf

Maybe because there is no HDMI output this has been stripped from the config? Did not investigate, just guessing

You have less uncompressed memory available then if this is a strain for you

topic split since it is off-topic

Each and every board (not board family) needs a dedicated maintainer attached to gain "maintained" status. If there is none or maintainer lacking their duties (loosing interest, missing deadlines...) boards loose "maintained" status and become unmaintained or community maintained. Both unmaintained and community maintained are more or less the same because boards can be unmaintained while still from time to time code gets pushed that improves it. So the line between these is blurred. It is not only not being maintained by Armbian. There is literally no piece of code in our build framework that relates to it. Therefore it does not exist. The tag in forums is goodwill only because it may or may not become introduced in the build framework at some point. Somebody seem to have done that already but (as we all know from certain people) GPL is violated by not sharing the source code. Maybe latter is available in the mean time, did not bother checking.

Non-LTS Ubuntu userspaces are mostly added for fun for the developers to get an idea where upstream development is going. These images were never supported and only meant to be used by enthusiasts who know what they are doing. You can try to upgrade userspace: https://docs.armbian.com/User-Guide_Getting-Started/#how-to-upgrade-distribution-like-focal-to-jammy-or-bullseye-to-bookworm

The noise is probably picked up from the current that passes through the board from the power input to the pins. Also keep in mind powering peripherials from the board rather than a dedicated PSU is vulnerable to voltage drop and therefore may not work correctly. A slight overvoltage of something like .2 volts above 5V might be needed to compensate for latter but this won't fix the ripple voltage.

Kinetic is EOL

There is no need to add sub-forums. Threads are properly tagged, can be found easily: https://forum.armbian.com/tags/orangepizero3/ Also why wasting our resources when there aren't even official Armbian images for a board?

The link you followed is just fine. As stated you could try to use an older kernel (like 5.15.y) or try edge branch which follows 6.x.y, not sure if 6.5 already but 6.4.y I think And check if this makes a difference. It is easier to investigate if known that it works properly on other firmware.

I see. Something is fishy. No instant solution. You can try to revert to an older kernel using code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } armbian-config for now. Btw. you are sure you have the OPi3 without LTS? Because the LTS variants differs hardware-wise and that is why there are separate images for it.

The interface name is code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } end0 code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } code { font-family: Consolas,"courier new"; color: crimson; background-color: rgba(0, 0, 0, 0.2); padding: 2px; font-size: 105%; } Use udev rules to rename to eth0 if you want.

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

Armbian does not provide images for this board nor does it support it (yet). The OS you are using comes from a 3rd party. So I suggest to ask for support where you got the image from.

You must be either poor or selfish (or both) to abuse open source projects that are living from donations themselves to beg for money. I have never seen such a behaviour before...

Because they aren't. Only way to get hw acceleration at this time is using an Ubuntu Jammy based image and install 3rd party ppa + packages like stated on the download page.

Flagship I'd say anything that is based on RK3588(S). However mainline support is still in development, legacy got most of the stuff working. If you want something older that is well matured and should handle 4k with ease I'd say something with RK3399. For latter LibreELEC provides images for various boards. It sounds like you are mostly interested in streaming so go for LibreELEC. If you want generic Linux desktop with Debian/Ubuntu userspace functionality go for Armbian. As a generic hint I recommend avoiding so called "TV Boxes" altogether. These devices are like cancer on the market. Undocumented, no source codes, no BSP, removed/inaccessible debug console, mutating uncontrolled (vendors tend to change hw components without notice and simply keeping the product name while breaking software support). Better get a proper board. Here is some inspiration:https://www.armbian.com/download/

Try importing updated keys from Debian, similar to this: https://talk.plesk.com/threads/no_pubkey-bd11a6aa914bdf7e.368962/post-924677

I don't know what you were booting but certainly not Armbian...

There are no pre-made Armbian images yet. However you can make your own using the build framework: https://github.com/armbian/build

Mainline support for RK3588(S) is in early stage so issues are kind of expected. Did you try legacy (5.10.y) in comparison?

Fairly new users to the forums are only allowed to edit their posts for a short period of time. With time and created postings this time span will increase. Until then it is perfectly fine to create a fresh posting for adding information.

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