mitu

Try the 'minimal-iot' flavor, I think that's the only one that boots from the current images. You can then add the desired packages and even switch to the 'edge' kernel from armbian-config.

@Fredrik thank you for testing.

@Fredrik thank you for the reply. I wonder what's Gnome doing to initialize the audio that's different from a regular (non-graphical) boot. FWIW I installed also Pipewire/Wireplumber and tried to test the audio through the PW ALSA emulation, but that didn't work either. Just out of curiosity, does speaker-test work from the CLI once booted into Gnome or is it just the sound test in Gnome settings that's working ?

OK, so I installed the latest Debian/Trixie + Cinnamon + vendor kernel available and audio is working. The name of the cards and mixers are different though: speaker-test worked both by specifying the mixer (... -D plughw:CARD=rockchiphdmi0,DEV=0) or through PulseAudio's ALSA emulation after setting the default sink to the rockchiphdmi0 card. The list of audio cards is different in the vendor kernel than what's available OOB with the edge kernel, so I'm not sure if the configuration is comparable. But the audio port/cable combo seems to be fine so there's that..

I can try it, just to check that the cable/port combo is ok. I'm not sure how would that help - the reason I'm using the edge kernel is to use the upstream/Linux kernel implementation and the implementation may not be the same as the one provided in the outdated vendor image.

I haven't tried the vendor image, but I have another SBC (RasPi4) that can succesfully output audio through the monitor speakers, so the monitor is ok. I could re-test the HDMI cable I guess, but since the video signal is ok I don't expect the audio to have issues.

It doesn't seem to make a difference:

Sorry I mean Which kind of output device: TV, Monitor with build in speakers? I have a HDMI monitor with speakers included. Yes.

Here's the output, shows PCMs for both the HDMI and analog audio outputs: > How do you test the HDMI sound ? speaker-test or aplay (with a .wav file).

The kernel version reported by armbianmonitor (see my first post) is 6.16.4-edge-rockchip64.

amixer doesn't show any controls on the first card (and so does alsamixer) - amixer -c 0 shows nothing, while amixer -c 1 has a lot of output, but I think it's just showing the controls for the rockchipes8388 audio card (the analog output, not the HDMI).

I have an Orange Pi 5 board, installed with the 25.8 Debian Bookworm + Cinnamon desktop system. I have switched (using armbian-config) to the edge kernel in order to test the HDMI audio support in the new Linux kernel, but I'm not getting any audio out. The ALSA HDMI card seems to be present (see below), but there's no sound using speaker-test or aplay. I have enabled the hdmirx overlay through armbian-config also, but the result is the same. Is there anything extra that should be configured in order to get audio output ? Output from armbianmonitor - https://paste.armbian.com/gegorimako

Hello @Igor, thank you for the update. I understand the predicament for lacking enough resources given the scope of the project and I don't expect things to work OOB without testing. I've updated the package list via apt and now I can see the headers package now for the current-rockchip-rk3588 Linux kernel (along with a the new linux-image .deb package). I have installed it and can confirm that dkms works fine to complile the WiFi dongle's driver - though it's not fully working yet, though this is purely a driver issue, not related to Armbian/Debian. Thanks for the updated kernel packages.

@Werner thank you for the reply. I'm familiar with the Wiki page, I'm aware some functionality will be missing using the 'edge/current' kernels. In fact, my intention when using the current/upstream kernel was to test how HDMI output was working, since it wasn't working a few months back. However, the functionality I'm missing is not related to the specific SBC/Vendor - as you said also, I was expecting the driver for the 8812au to be included/work. I haven't found a related 'kernel headers' package through apt also, hence my question/topic is mostly about the package. Having the headers package would help with any external kernel module that would be installed through dkms.

I have installed the recently released `Desktop images with Armbian Linux v6.10` image (24.8.1, Debian Bookworm, with the Cinnamon desktop) on an OrangePi5 and I'm happy the HDMI support included has finaly enabled the video to my 1080p display. However, my previously supported WiFi adapter is not recognized in this version - it worked with the vendor (5.10) kernel which I used with last year's OrangePi5 image, but how it seems the driver is not installed with 6.10. The WiFi adapter is connected via USB and it's listed as Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter. Now, there are a few DKMS/out-of-tree drivers that I could install, but the problem is that there are no kernel headers for the current Linux image kernel - trying to install them via armbian-config returns me to the previous screen almost immediately. Is the kernel headers package missing or is maybe named differently ? FWIW, the Linux image package is linux-image-current-rockchip-rk3588.

There are various methods to check the current resolution. compile modetest from Mesa (not sure if there's any package including it) and use it to inspect the current resolution. https://gitlab.freedesktop.org/mesa/drm/tree/master/tests/modetest there's a similar utility (kmsprint) in the kmsxx project - https://github.com/tomba/kmsxx Both utilities also allow you to test various resolutions to see if they're supported by your monitor/display. SDL2 has specific support for mode change in their KMS/DRM video driver. You can see how it's done by looking up in their test folder for various testing utilities, most of them support the --fullscreen parameter (when they set a fixed resolution, usually 640x480) and --fullscreen-desktop (where they use the current 'desktop' resolution and scale the main window to that). Note that none of this is specific to Armbian, the behavior and capabilities are dictated by Linux's DRM/KMS APIs. xrandr works only withing Xorg, so it's normal it's not working outside of it. There is no equivalent to it when you're using a pure KMS/DRM environment, the resolution change/switch has to be done at the application level. If you want to set a specific start-up resolution for your system, instead of Linux choosing the best resolution from the ones reported by your display, then you can use the video Linux kernel parameter to set it up - see https://wiki.archlinux.org/title/kernel_mode_setting#Forcing_modes.

Probably because mainline Linux kernel doesn't have HDMI support yet - see https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/blob/main/mainline-status.md. I think that if you need GPU/Video support it's better to use the version based on the legacy (5.10 ?) Linux kernel.

This is a domoticz issue, if you're unable to install from source then ask for support in their forums (or whatever they use for support). The issue is not specific to Armbian.

You'll need to install it from source the binary releases don't seem to support the newer OpenSSL3 libraries, see https://github.com/domoticz/domoticz/issues/5233,

I think there's more than one place where ifconfig is used. Debian 12 bookworm seems to not include it by default, so perhaps it's time to be replaced with the "newer" alternative. I have a hunch that the Armbian is aware of this issue.

Looks like ifconfig is not found and armbian-firstrun-config errors out because of it. Which image are you using ?

Check the contents of /etc/default/locale - put there your desired language (en_US.UTF-8 should get you American English) and then reboot. Also, check out the Debian Local entry from https://wiki.debian.org/Locale, your question is not specific to Armbian.

Run: sudo dpkg-reconfigure locales and choose your preferred language. Your current locale seems a variant of Yiddish

Does this work for a 23.02 system ? I just gave it a try and - although I didn't get any errors from apt - the system didn't boot afterwards. EDIT: forgot to mention this was done on a OrangePi 5 system (installed with Ubuntu Jammy 23.02 release/image).

Using hostnamectl