NicoD

Try using mpv instead. VLC is not accelerated with no images. And provide the needed info. I know nothing here with this question. What board, what kernel, what video file, ...

This might be a fix. I haven't had the time to test and implement. Steps used to fix audio on Armbian Clone @Spikerguy Repository From Manjaro Gitlab Ensure you have git installed with, pi@twisteros:~$ sudo apt install git Make a destination subdirectory under /home/pi for git pulls and builds, pi@twisteros:~$ mkdir ~/builds Change to your new ‘builds’ directory, pi@twisteros:~$ cd ~/builds Clone local copies of the Manjaro files: pi@twisteros:~$ git clone manjaro-arm / packages / community / khadas-utils · GitLab Copy Files to Their Correct Locations pi@twisteros:~$ sudo cp ~/builds/khadas-utils/g12_sound.sh /usr/bin pi@twisteros:~$ sudo cp ~/builds/khadas-utils/sound.service /usr/lib/systemd/system/ pi@twisteros:~$ sudo cp ~/builds/khadas-utils/G12B-KHADAS-VIM3.conf /usr/share/alsa/cards/ pi@twisteros:~$ sudo ln -s /usr/share/alsa/cards/G12B-KHADAS-VIM3.conf /usr/share/alsa/cards/G12BKHADASVIM3.conf pi@twisteros:~$ sudo cp ~/builds/khadas-utils/G12B-KHADAS-VIM3.conf /etc/asound.conf Make sure that /usr/bin/g12_sound.sh is executable. It should already be, and you can check with, pi@twisteros:~$ ls -l /usr/bin/g12_sound.sh Otherwise a quck chmod won’t hurt: pi@twisteros:~$ sudo chmod a+x /usr/bin/g12_sound.sh Initialize the Systemd Sound Service Unit pi@twisteros:~$ sudo systemctl enable sound.service

Hello everybody. Today the Khadas VIM4 is being released. The VIM4 uses the Amlogic A311D2 SoC. This is a new SoC with 8-cores of which 4 x A53 @ 2Ghz + 4 x A73 @ 2.2Ghz. The board comes with 8GB LPDDR4X and an eMMC of 32GB. If you want to learn more about this new board, then watch my review video about it here. Greetings, NicoD

Hi all. I made a new video where I explain all the basics of working with Armbian xfce4. This for the absolute beginners that come from Windows. But a more advanced user can maybe also learn a few things from it. Here is the video. Greetings, NicoD

Hi all. In my latest video I compare the Odroids HC4 and N2+, RPi400, NanoPi M4 and Radxa Zero with each other. I make a "NicoD opinion benchmark" where I give my thought on what each board is best for. And of course benchmarks... Greetings, NicoD For those interested, here are all my benchmarks of the last weeks.

For some people it is wanted/needed to change things. And for the devs it is a must. It's just expected of people who do change things, that they know what they are doing.

A lot. Just out of my head what I'm willing to part with. What I can miss. KM6 TVbox, OrangePi3, RPiZeroW, Tinker Board, Rock64, Atomic Pi. Only for a good price the Khadas VIM2 and Jetson Nano. RPi2B very maybe. I love that one too much, so only +50 euro for that one. I'll have to take a lok at what else I've got.

https://imola.armbian.com/archive/rock64/ ???

Me, me meeeeee

Hi all. In my latest video I make an Armbian Build server out of my old x86 PC. And I set up an extra Odroid HC4 as NAS with the old hard drives from my PC. I hope you'll like it, greetings. NicoD

Take care of yourself and those around you. Best of luck. These things can wait. Cheers.

Should be something like this. # max cpu frequency in MHz unit if test "${variant}" = "n2_plus"; then setenv fdtfile meson-g12b-odroid-n2-plus.dtb setenv max_freq_a73 "2208" setenv max_freq_a53 "1908" else setenv fdtfile meson-g12b-odroid-n2.dtb setenv max_freq_a73 "1800" setenv max_freq_a53 "1896" fi If you create an image, it only does the used disk space. Not the unused. So that's why I'm saying to decrease the partition size and then make the backup image. That is how Armbian images start. But there is a tool that expands the partition to full disk size at first boot. And check a new image to see how everything is done to see if it's n2 or n2+. I'm not sure where the "${variant}" is declared. I don't think that will be done on your image since older than that script.

I moved this to the correct place. I have not used Armbian on tv-box in a long time. My guess. 1. Write image to sd-card. 2. Mount sd-card in a Linux environment. 3. Change the armbianEnv.txt (or another Env file in the /boot directory) to point towards the correct dtb file for your device. (4) Might be needed that you press a boot button to boot it. That might be in the 2.5mm audio connector. Use a toothpick to press it and power the board. Read around in the TV-box club for more info.

Where did you find that image? Seems old. These days there's a script that checks if it's the N2 or N2+ and then loads the correct devicetree. But with old images (usually in config.txt) you had to manually select the correct device. My advice would be to use a more recent image. You need to decrease the size of your sd partition to do this correct. Safest way to do this is using another image on another sd/eMMC. Then use gparted to resize the partition so there's almost no free space. Then create the backup image. Then set the patition size again to original. The same when you burn the image to sd-card. Resize the partition with gparted.

Hi all. In my latest video I test the new Armbian 22.02 images on RK3399. I use the NanoPi M4. But it should be about the same for other RK3399 devices. Long story short. Jammy xfce 5.16 performs better. And has the better performing browser. Focal xfce 5.15 firefox is not HW-acc. Chromium is, but performs badly. Also bad blender result. Not all cores are used to the max. I've never seen this behaviour. So I would use the Jammy xfce 5.16 image. But I'm still using an older image that work. So I'm not upgrading. Greetings, NicoD

How is the state of this on the new release? Is VPU now possible on mainline? I had tried images from balbes150 for the station P1 where I could install his Kodi packages for this. I was wondering if this now is possible on the latest release or not? And what packages need to be used for this? Greetings.

And here the video I made about the new release.

Hi all. I've recently received the Odroid N2+. Since nobody else started a topic about it, I'll be the one. All works fine with Armbian since not much hardware changes have been made vs the N2. Except for the CPU frequency. With the Odroid Ubuntu you can set it to 2.4Ghz for the big cores A73 as overclock (2208 stock)., and 2016Mhz for the A53 cores (1908 stock). With Armbian the max clocks are 2Ghz for all cores. Using Armbian Focal 4.9 legacy. I tried setting the higher values in config.ini. Also tried with the "meson64_odroidn2_plus.dtb" file from the Odroid Ubuntu. Doesn't boot with that. (What do I know ) Other changes are the RTC battery that's now on the board. The heatsink has changed a little. But it's still more than sufficient to keep it cool even when overclocked. USB3 still rather s*cks on it. Slow and a lot of issues with 2.4Ghz dongles(wifi/keyboard...). Too bad they didn't do anything about that. But that probably could have complicated compatibility with N2 images. Also feels a bit more sluggish than RK3399 on NVMe vs 128GB eMMC on the N2+. That's what fast I/O does. I'll try on USB3-NVMe later. Here some pictures. 1st pic the N2+ with its case open. 2nd picture the N2 left and the N2+ on the right. Cheers all.