Jump to content


  • Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by NicoD

  1. Hi guys. I'm the maintainer for the Khadas VIM3. There are 2 small issue's with the Armbian images for VIM3, and also for VIM2. armbianmonitor -u http://ix.io/46L9 First off, the VIM3 has all its cores clocked to 1.5Ghz by default. I created a Jira for that a while ago. https://armbian.atlassian.net/browse/AR-1094 My simple fix is in /etc/default/cpufrequtils MAX_SPEED=15xxxxxxx → MAX_SPEED=2400000 But I have no idea how/where to adjust this so it is correct for all VIM3 images. Then for VIM2 and VIM3 (maybe VIM3L and VIM1 too) the HDMI audio isn't working as it should. https://armbian.atlassian.net/browse/AR-1095 I once was able to make it work. But I can't remember how. So the device is enabled at boot, but not directed to be used by pulseaudio. Thank you.
  2. Here all other Armbian related videos. And lots of review videos on my channel. So subscribe if you're interested. Greetings, NicoD
  3. Yes. Panfrost GPU driver is enabled on all images for M4V2/RK3399.
  4. What image are you using? There are many ways to install this. I'd advice to start with a fresh, current jammy and build retroarch yourself. https://docs.libretro.com/development/retroarch/compilation/ubuntu/ The problem is that RetroArch doesn't provide arm64 cores. There are gaming images for arm64 boards that include these cores. Good luck.
  5. Hi all. Werner has made a video where he presents himself and talks about how he got into using Linux, SBCs and Armbian. A very interesting video. This is a serie of video's. Igor and Lanefu also have made a video like that. You can find the other video's here. https://www.armbian.com/authors/ If you're willing to make a video like this. I am willing to edit and help out. Greetings, NicoD
  6. 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, ...
  7. 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
  8. 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
  9. 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
  10. 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.
  11. 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.
  12. 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.
  13. https://imola.armbian.com/archive/rock64/ ???
  14. 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
  15. Take care of yourself and those around you. Best of luck. These things can wait. Cheers.
  16. 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.
  17. 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.
  18. 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.
  19. 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
  20. 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.
  21. And here the video I made about the new release.
  22. There is a small problem with Cinnamon. The menu (start) button is missing. Must be some package that's missing. I'll try to investigate. But I don't know much about cinnamon. xfce is ok.
  23. @TRS-80Of course you can ping me. @fikThat is indeed the best way to work. Either freeze kernel, or use 5.10 Been a while that I tested it, but I also remember edge being unusable. There is a problem with all meson64 boards and edge. Someone is working on it. But no idea when it will be fixed. Too much work for too little hands. VIM3 development is also still in early fase. More things will not work. Check the cpu frequency. Possible it's set to 1.5Ghz on all cores. This because the configuration of the Odroid C2 was used as a base for the VIM3. I think you can set it with "sudo nano /etc/default/cpufrequtils"
  • Create New...