gounthar

With Buster server I got:

I also downloaded Armbian Buster desktop legacy kernel 4.4.y and I got With Buster minimal 5.4 I got

I rebuilt the image for my RK3399 two days ago, and it is stuck at boot with this message: I rebuilt it today, and have the same output:

I see. I will give it another try later on. Thanks.

I'm not sure I got what you meant. I know there are some troubles with the power units for this board, but as I use the power adapter that was supplied with my board, I thought I would be good to go. My board can boot Android on the SDCard and Linux on the eMMC with this power adapter. Would you mean that Armbian would take too much current when starting, so that the board shuts off by itself?

I build yesterday for this board, and tried it today with no luck. I have the standard PSU that was delivered with it. I can boot Android on a SDCard, and Firefly's Linux on eMMC, but not Armbian for the time being. I haven't plugged UART yet, so I don't know what's going on.

OrangePi told me on twitter that the camera for my OrangePi RK3399 would be this one... I should get it tomorrow, so that I'll soon know that. They told me the same thing for the 10.1 display, but I did not buy it (yet).

Hi there, I was wondering if there is a GPIO generic Python library somewhere for Armbian? I think I remember that the pins are not always announced the same way on Armbian and on OrangePi distros. I have seen this effort by @chwe, but is there anything else? Thanks.

Keep us posted, I restricted myself not to buy it.

Thanks, will do.

OrangePi said it would be a 64bits distro on a 4.4.179 kernel.

Thanks a lot @JMCC, that sounds good! I will try it asap.

I went up to step 19, but the board does not boot. I suppose I failed around the copy of the files. sudo cp linux-4.20.17/arch/arm/boot/zImage /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/boot/zImage-4.20.17 sudo cp linux-4.20.17/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dtb /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/boot/ sudo cp sunxi-cedar-mainline/boot.scr /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/boot/ sudo cp sunxi-cedar-mainline/sunxi_cedar.ko /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/lib/modules/ sudo cp -R modules/lib/modules/4.20.17 /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/lib/modules/ sudo cp linux-4.20.17/arch/arm/boot/zImage /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/boot/zImage-4.20.17 sudo cp linux-4.20.17/arch/arm/boot/dts/sun8i-h2-plus-orangepi-zero.dtb /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/boot/ sudo cp sunxi-cedar-mainline/boot.scr /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/boot/ sudo cp sunxi-cedar-mainline/sunxi_cedar.ko /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/lib/modules/ sudo cp -R modules/lib/modules/4.20.17 /media/techforum/1868e640-9660-423a-8dd3-de560bfb2298/lib/modules/

Hi there, thanks a lot for your script. Unfortunately, I started with a Buster version of Armbian for XU4, so that did not make it. I got some errors along the way, and ffmpeg has not been installed. Out of curiosity, I rebuilt the standard ffmpeg package on this very machine before trying to modify anything. Once built, your provided command line works, but all the cores are used pretty heavily, so I guess the hardware acceleration just does not work. If you ever have the configuration used to compile your version of ffmpeg, I'd be glad to test it on my machine.

That's seriously cool!

Thanks a bunch @ubobrov for taking the time to write a detailed howto, I will give it a try.

Thanks. I have several gigabytes of swap, but why not, I will try it this way.

Thanks a lot. I am currently testing on another machine with an earlier version of gcc (7.x). Here is the list of commands I used: sudo apt-get install -y build-essential libncurses-dev bison flex libssl-dev libelf-devx libmp3lame-dev libpulse-dev libv4l-dev libx264-dev libasound2-dev git clone https://github.com/uboborov/ffmpeg_h264_H3.git git clone https://github.com/stulluk/FFmpeg-Cedrus.git cp ffmpeg_h264_H3/cedrus264.c FFmpeg-Cedrus/libavcodec/cedrus264.c cp -vraxu ffmpeg_h264_H3/sunxi/ FFmpeg-Cedrus/libavcodec/arm/ cd FFmpeg-Cedrus/ ./configure --prefix=/usr --enable-nonfree --enable-gpl --enable-version3 --enable-vdpau --enable-libx264 --enable-libmp3lame --enable-libpulse --enable-libv4l2 make -j2 I got the same error with the older version of gcc:

Regarding the ffmpeg build, I must have missed something, because this is what I got with gcc 8.3.0.

So, I've built the kernel and you repo on the Zero, because I don't have an Armbian build machine anymore. Should I go the old x86 way of installing the kernel, like make modules_install && make install I guess it's way more subtle on an ARM SBC.

For the time being, the encoding part is not available on the OrangePi RK3399, but OrangePi have at last supplied a camera for the board. The one I had bought from FriendlyArm was freezing the board.

Top notch! Sorry in advance, but I may have more dumb questions regarding this build, so please bear with me, I'm way out of my comfort zone.

I answered to your post before reading the link you provided, so yes, it's written, my bad. I will try to follow that page, so that I can switch to H3 when the encoding part will be available. Regarding the XU4, I know it's plenty powerful, and love to see its eight core working at full speed when compiling... But I have yet to test its encoding abilities, because if it can encode only one 1080p at a time, the ratio power/price won't really interesting. Anyway, thanks a lot for your crystal clear answer, the definite links, and your patience answering my vague questions.

Sounds like a nice list. Thanks a lot for detailing, I will give it a try.

Thanks a lot for your input. I started this quest for AllWinner hardware encoding because of this post: https://forum.armbian.com/topic/11551-4kp30-video-on-orange-pi-lite-and-mainline-hardware-acceleration/?do=findComment&comment=88617. Hardware decoding seems to work for @ubobrov, and I want to try the encoding part. FFmpeg is my reference software, so working with it is a big plus for me instead of gstreamer. Maybe I fooled myself and read what I wanted to read regarding H3 hardware encoding. Maybe the hardware decoding is implemented, but not the encoding. For the time being, I have applied the patches to ffmpeg and the kernel. Last time I saw the board, it was busy with building the kernel. Regarding the Rockchips, I have several rk3399 (OrangePi 2 and 4GB, Renegade Elite) but no rk3288 nor rk3328. I've been able to use hardware decoding with ffmpeg which I compiled, and sometimes hardware encoding with gstreamer (because most of the times, it crashes the board). The RockChip ffmpeg fork was supposed to be able to hardware encode Q4 2019, but there haven't been any news for a few months. I also have a XU4, which I have not tested yet. What is used? Vdpau, vaapi, something else? I will have to give it a try. My goal is to have a farm of cheap boards running hardware accelerated h.264 encoding, so that they multicast the downsized content to server for final users. As much as I love XU4, it's not a cheap board, so if you ever have a suggestion of another board (or TVBox) that would be cheap, h.264 hardware able with Armbian and ffmpeg, please let me know.