jeanrhum

I gave some bucks for this powerful server. Paypal was perfect for me. Long live to armbian! I hope the target will be attained soon.

One of the coming issue is also that Balbes stops supporting amlogic socs for his next builds, so don't expect new robust builds. If you have tv boxes, then it depends of the soc(s) you have. On my side, I was able to use the rockpi4 armbian image with a rk3399 board (edge-v) and changing after in armbianEnv.txt to the right dtb. I have a working up-to-date environment that I installed in emmc but I may have problems if the next kernel/uboot upgrades breaks things. I also tried to do that with another box I have with a s912 soc, but there is no official armbian build with this soc. I was able to start a lepotato (s905x) image, but usb and network devices were not detected correctly. The best place to discuss that is tv box sub-forum as said JMCC. I think that several amlogic users are frustrated of the current situation and may want to make something from Balbes work (his github repo is available). Edit: you can also have a look at the linux meson wiki: http://linux-meson.com/doku.php

Looking at the documentation of jellyfin, only the rpi3 or 4 seems to be the supported boards based on an arm architecture. Other than that, I think that JMCC have a script to install such stuff on most rk boards based on 4.4 kernel if I remember well, but I'm not sure transcoding is working: Myy is also working on porting vpu rk lib to mainline for rk3399; I'm not up to date about cedrus features for transcoding concerning Allwinner socs. I'm quite sure that my previous server sbc based on H3 was able to transcode using plex several years ago. My current server is based on an amlogic soc and I didn't investigate the vpu for now. A few years ago plex didn't see any transcoding engine.

I think you misunderstand balbes. I think he was talking about u-boot for instance or any other low level software that can make things difficult when it does not fit the hardware. You can use the new images if you want to test, but there will be no support from him and no warranty that it'll work on your hardware. It is a bit sad, but when you look at the tv box market, amlogic boxes quality are worst and worst (many variants of the same reference with cheap chips and mainline support is mainly done slowly by Baylibre - only for the aml soc and not for all additional chips that may never come to mainline).

You shouldn't you android recovery. Have you installed a custom firmware or any alternative system that may have modified the original u-boot? If so, just flash an original firmware and try again. If it doesn't boot directly try the toothpick method.

Is it normal on your armbian storage, that the arm32 images are named Armbian_20.09_Arm-64_* ? Exactly like the arm64 ones.

You have an error in your extlinux.conf: you should comment the rk3399 lines and uncomment 1 line of amlogic starting with fdt and the last one starting with append. Here is the one I use for s912 boxes (you may change the dtb if the generic q200 is not relevant): And you may also change the extlinux.conf-menu file:

Even if Balbes makes a great work, I agree with Igor about updates and the use of a supported board. I'm not a good example since I use a S912 box with a Balbes image for my home server. But I can say that I stay on an "old" 4.19 or 4.20 since recent ones have several issues like GbE and usb even if some patches or hand modifications can be used to solve them. Rk3399 is powerful but heat a lot, so a good cooling is preferable if you plan to have heavy loads. Odroid c4 with amlogic S905x3 could be a nice alternative, since it is a supported board, you can add emmc and the cpu can be powerful enough for small server tasks.

Excelvan T2 (s912) using q201 dtb started from a slow usb key: http://ix.io/2qzp The system seems usable. It is slow but I think it comes from my usb key. EDIT: same test with an H96pro+ using vim2 dtb using a uhs1 sd card : http://ix.io/2qzv. The system is faster than my previous test and desktop is reactive. On both config video playback was smooth.

Maybe the best way to use HA is to use docker: https://www.home-assistant.io/docs/installation/docker/ I tested that on several tv boxes and it works nice and no more worry about python errors. Docker is available through armbian-config.

This may come from the dtb you use. I don't know if any available dtb expose the tv tuner.

Ethernet works: http://ix.io/2pla

The procedure has changed and the first post of this topic has been updated.

I was thinking that I reported that on the Q8 topic, but no it didn't work with that change in the dtb. I will try to compare with firefly dtb and I will try to extract the dtb from an android image in case it has some relevant info to define a ut3s specific dtb, but I'm not sure to have enough skills with dts file reading.

First test with ugoos ut3s with default dtb (firefly-reload): http://ix.io/2o7o For information, I have jock uboot and an old Q8 image installed on emmc. Wifi works, but ethernet seems buggy like on recent arm64 images (kernel 5.X pb with current dtbs ?). I didn't test it, but the connection was activated whereas no cable... System halts instead of reboot. Bluetooth seems not working well (xfce applet disappear when I try to use it to activate) With Q8 dtb the experience seems similar from a user perspective: http://ix.io/2o7q With popmetal and tinker dtb, the system does not boot: waiting root file system... running /scripts/local-block With miqi dtb, it boots, but without wifi and I was not able to connect a cable to test the wired network, but eth0 still shows as connected. Edit: As I noticed on Jock images, the Q8 dtb is not able to detect emmc on contrary to firefly-reload.

Downloading bullseye desktop legacy... I will try to give it a try this evening or tomorrow. I agree with Balbes about the position of his images and a CSC ugoos board. His images fit several boards at the same time and the behavior of these images (in particular for kernel update) is a bit different from official armbian.

This not directly related to armbian. You can have a look it for instance: https://wiki.debian.org/DesktopEnvironment

No, since it's not arm64. Look at this topic:

I have an ut3s, so if you want a tester for a similar ugoos box, don't hesitate. Have you tried/compared the community image from jock for Q8? It work not too bad on ut3s, but it lacks some dtb tweeks (fan, led and emmc in latest kernel).

Thanks and success too! I just built a focal standard server image under a recent focal install on emmc with the following modifications: - copy /lib64 folder from usb stick to emmc install - install qemu and change line 80 in config/sources/families/arm-64.conf to use qemu-x86_64-static instead of qemu-x86_64 It finished in 263 minutes, but my h96proplus throttle a lot at 80°C. The eight cores were used but the big ones limited to 1ghz and the small ones to 500mhz. I will try to find a simple way to better cool the box compared to the small default heatsink and run it again.

Can you explain the few modifications you've done to compile successfully an image please? I face the same error using the latest focal image on an s912 box. First, I had an error with qemu so that I installed it and then modify the file config/sources/families/arm-64.conf because the qemu binary was qemu-x86_64 instead of qemu-x86_64-static (line 80). /full-path/config/sources/families/arm-64.conf: line 101: qemu-x86_64: command not found /full-path/config/sources/families/arm-64.conf: line 121: qemu-x86_64: command not found After those modifications, I got the same error as you. Where do you get the ld-linux-x86-64.so.2 file?

I tested it and I'm able to see internal emmc: :~ $ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT mmcblk0 179:0 0 29,5G 0 disk └─mmcblk0p1 179:1 0 29,2G 0 part / mmcblk2 179:16 0 14,6G 0 disk mmcblk2boot0 179:32 0 2M 1 disk mmcblk2boot1 179:48 0 2M 1 disk zram0 252:0 0 50M 0 disk /var/log zram1 252:1 0 1000,8M 0 disk [SWAP] However, there are error in dmesg and the install to emmc from armbian-config does not work: I also put the decompiled dtb of a 4.18 kernel installed on emmc: rk3288-xt-q8l-v10-4.18.dts

Hi again, I write from my ut3s running armbian just built from sources and q8 image: Linux ut3s 5.4.37-rockchip #trunk SMP PREEMPT Sat May 2 12:27:06 UTC 2020 armv7l GNU/Linux However, still the same problem about emmc initialization so that I'm not able to install to it.

Nice board to come with cortex A55 and G31. We can hope efficient fanless cooling with this soc. The 12V2A psu seem a bit too much in terms of max power, but 12V psu is nice and will definitely stop bad 5V psu problems. More details on the odroid forum: https://forum.odroid.com/viewtopic.php?f=29&t=38555

Have you tried this image? http://www.lakka.tv/get/linux/rock64/