robertoj

thank you!

Did you need to specify linux stable or edge, debian or ubuntu, in the armbian build script? Or does it work with all linux and debian/ubuntus?

Why does the LLM output speak of experiments, failure modes and solutions as if it has done the experiments itself? It should be telling you where it is quoting that information from.

Hello I see in the github, that ffmpeg 8.1 with patches by kwiboo were included. Which kernel and debian/ubuntu version does this work with? Trixie? Noble? I already saw this working well with some rare crashes in Bookworm, but I never saw it working in anything newer. Can you separate the group of patches that implement the H264,H265 hardware decoding, and ffmpeg?

disable ligthdm with "sudo systemctl disable lightdm" and reboot. Log in with text mode. Run "sudo startx". If you see a gray screen with cursor, then X11 is working fine. If not, then you will see a lot of debugging messages. Write down those that start with (EEE). Quit X11 by right-click and "Exit" If you want to abandon X11, try compiling pi-greeter: a "greeter" for lightdm which avoids X11 https://github.com/robertojguerra/opiz3-labwc-setup/blob/main/4-pi-greeter.md Related post: https://forum.armbian.com/topic/55882-critique-or-improve-my-method-to-get-a-lightweight-labwc-desktop/#comment-227469 Re-enable lightdm with "sudo systemctl disable lightdm"

Thank you for sharing your results Which other armbian boards would be compatible with the LeMaker LCD?

I also have an orange pi zero 3 which was fried due to 12V applied to the GPIO +5V pin (forgot to turn a potentiometer to lower the voltage). What is the ED1? Is it a fuse or similar? Is there an equivalent for the GPIO 5V?

Thank you Jacob I hope to get a orange pi zero 3w in the near future, for NPU tasks (face and pose detection)

I am glad that someone else is also using that LCD driver. In the Raspberry community, it is also the favorite driver for LCDs, since it is universal and works well with Wayland. There are several threads here, in the Raspberry forum and the notro repository: https://github.com/notro/panel-mipi-dbi/discussions The signal inversion seems to be a deliberate change from linux 5.x to linux 6.x. This panel-mipi-dbi can also be used with bigger SPI LCDs, but you need to upgrade to 6.x (cant remember which) to use the big and cheap ILI9486, ILI9488, and even accelerated video is possible. I have seen the Orange Pi 4 Pro being mentioned. Is it similar enough to the Radxa A7* to use the same DTS? Is the Oranpe Pi Zero 3w also similar enough? (it has the same form factor as the Radxa A7z and same A733). Jacob, you should understand everything that Claude produces for you. Keep track of what it's changing in the EDK code. Make a diff patch from the unchanged code, and the code you are compiling. All the differences need to be sanity-checked by regular users, and rationalized by experts. And share a link to the starting original EDK.

I think it has some similarity with Radxa Cubie

Which Linux version are you using? Did you use the CMA=256M kernel argument? There's a lot of information here.

More likely: friendlyelec is maintaining a separate patch (source code additions to the official ffmpeg), that allows it to do it. The code should be available in the friendlyelec github, to be shared with the public. "No v4l2request"... that means that they implemented another protocol and/or another kernel module to work with the video decoder.

Thank you for the information mmgen, One thing you missed is the ffmpeg compilation information. Run: $ ffmpeg It will print out the ffmpeg version and all the libraries that were enabled, and all the libav* libraries it has compiled along with ffmpeg (libav* are parts of the ffmpeg project). The interesting information is whether it uses the "v4l2-request" library, which lets ffmpeg control a part of the kernel that controls the hardware decoder. When you run mpv -v yourvideo.mp4 you could also see v4l2request, or some other message about the hardware acceleration (at this point I doubt that v4l2request is used, because it works better in newer kernels)

If you are using the friendlyelec image, can you really say "mpv is vanilla from Debian"? I am really asking, because I haven't used friendlyelec in a long time, and I don't remember if they have their own DEB repository. Can you identify the ffmpeg version and compilation options? Same with mpv. Run $ ffmpeg with no options, and it will print out the version and the libraries that were activated. $ apt list ffmpeg $ apt list mpv $ mpv --version $ cat /etc/issue $ uname -a I do remember that friendlyelec has some extra video abilities, because they maintain their own patches with bleeding edge code, while the official ffmpeg and mpv maintainers are still checking whether to accept the pull requests. Is it even possible to run "armbianmonitor -u" in friendlyelec? Do you see "v4l2-request" or "va-api" (or "vaapi") anywhere in the mpv log? is your gnome desktop running under X11 or Wayland? (last time I used friendlyelec with Kodi, the graphic server was gbm, and there was no desktop, only Kodi). If you run $ mpv --vo=gpu -v my.mp4 , mpv will print a more verbose log, with more details of how its running.

Can you give more details about the limitations of this NPU? I thought that they would be using shared system RAM. because all models are multiple megabytes, Can you comment about the ability to convert any model to your desired NPU target with "AI model conversion" https://tinycomputers.io/posts/rockchip-rk3588-npu-benchmarks.html (search for "Conversion Performance (x86_64)") Maybe its possible to run LCM-Lora in an armbian device, if it has 16GB. It is already running in a 16GB laptop without NPU or GPU. https://forums.raspberrypi.com/viewtopic.php?t=398225&sid=2b66e2cebe37506dd74215ead3dd264c I am thinking about buying an Orange PI zero 3W (allwinner NPU), but if you have troubles with a 6 TOPs NPU, I will have more troubles with a 2 TOPs NPU