MX10.AC2N

Hi all, I am continuing my Armbian feedback on the Beelink GT-King Pro .. I am now working with the linux-image-current-meson64 and it works fine, had no issues I am super satisfied with the results of the GT-King Pro, my YUNoHost server works very well, only small downside I use Jellyfin and all transcoding is currently done only by the processor so increased use during the file transcoding phases, I would like to succeed in using GPU but so far I have not found ... If anyone has an idea I am interested .. I leave you a copy of "armbianmonitor -u".. http://ix.io/3s0O I hope it can help some of you but above all I hope that this damn beelink gt-king pro could be officially supported by Armbian .. In any case, I take this opportunity to say a huge thank you to all those who work for Armbian from near and far...

Oh okay, but I didn't know anything about the theft stories .. Sorry again .. On my gt-king pro I tested Manjaro but I could not set up yunohost under this OS, I tested the Debians posted by Darkstar on the Beelink forum but in both cases there was a problem with "Iptables "therefore impossible to install Yunohost also .. This is where @jfl told me about your Armbian build, which I tested directly but there was a system "Freeze" problem, I am discussing it on the Beelink forum and thanks @jfl who already had not badly tested (and especially who has the same gtking-pro model as me, S/N: SA9H....) he suggested that I test with the solution with the * .dtb file (taken from manjaro) and the uboot.ext file (taken from debian-5.10) And it has been working without "freeze" for several days at home with a functional Yunohost installation (web server), so I share, hoping that this will allow to have a stable and more "official" Armbian version on Beelink GT-King Pro.. Thank you again @balbes150 for his work, I have 2 tvboxes which can start Armbian thanks to you ... Have a good day..

Sorry @balbes150 there must be misunderstanding ... I am using google translate ... Sorry if you think you were stolen, that was not my intention at all .. I use your great armbian construction and I thank you again very much .. Without you nothing would have been possible .. But for it to work correctly on my gtking-pro, without "freeze" of the system I had to recover the 2 files that I mentioned in my post, since the system seems to me to be very stable and that's why I am sharing my experience, other people owning the Beelink Gt-King pro may be interested in being able to test Armbian, it seems to me, but maybe I was wrong .. If you feel that I am a thief by posting this, well asked and I will delete the post. Have a good day.

Good morning all, I share my Armbian experience on the Beelink GT-King Pro, and therefore after several tests where the system often ended up frozen, I currently have a stable armbian system running. I was able to install my web-server at home (Yunohost) and everything seems to be working fine .. So I share : I used Armbian_20.10_Arm-64_buster_current_5.9.0.img from https://users.armbian.com/balbes150/arm-64/? which I flashed on a USB key I recovered the meson-g12b-gt-king-pro.dtb file from the last Manjaro Manjaro-ARM-xfce-vim3-21.03.img I recovered the uboot.ext file on the debian 5.10 build by @darkstar => http://forum.bee-link.com/forum.php?mod=viewthread&tid=71213&extra=page%3D1 So I was able to start Armbian from USB, however, it is necessary that there is only that connected to USB otherwise the start-up does not work (apparently with the system on SD card there are no problems with have multiple USBs used) And so with that, the system seems very stable, of course I only tested for the implementation of Yunohost but it seems that this is the way to have Armbian stable on the GT-King Pro .. That's all, because I'm not really an expert in armbian but you just have to experiment. I take this opportunity to thank @jfl from the Beelink forum who helped me a lot, thank you brother .. Have a good day.. P.S: I put the *.dtb files taken in Manjaro-ARM-xfce-vim3-21.03.img as well as the uboot.ext file taken in Darkstar's Debian-5.10 And a paste of "armbianmonitor -U" => https://pastebin.com/pxSRmqB4 u-boot.ext meson-g12b-gsking-x.dtb meson-g12b-gtking.dtb meson-g12b-gtking-pro.dtb

This is good news, it gives us the P2 8G Ram 128G Emmc Station at 188.88 € delivered in France. This is a good deal, thank you Firefly.

Ah it still costs 208.68 € for the 8G of RAM with the shipping costs for France, it is still not giving the small box .. In comparison we also find this kind of little novelty https://www.zimaboard.com/ to see the price they will have once everything is finished but their passage by kickstarter was very interesting, this zimaboard seems really not bad especially with its very low power consumption, but hey it does not have ARM sorry it was just for comparison .. Anyway for me Station P2 even with the pre-order it's too expensive ..!

Great this is exactly what I need, I want one ..

thank @SteeMan Indeed I got a little lost in my post .. Thank you for having put it back in the right place in the forum .. regarding DTBs that's what I thought, and that's why I'm looking for the dtb rk3328-mx10 for kernel 4.4.213 (to use with the buster version of the station m1 image)

On my Emmc install with Armbian_20.07_Rk3328-tv_buster_current_5.7.8.img I use this dtbrk3328-box.dtb but don't work with Armbian_21.05.0-trunk_Station-m1_buster_legacy_4.4.213.img

And shit I still have problems, so I'm looking for the right .dtb for my mx10 for this buster image of the station M1, I'm a bit lost to tell the truth, but I found an old post If anyone still has .dtb files for the mx10 I'm very interested ... Otherwise I tested several dtb with different results Boot OK but no eth with rk3328-roc-pc.dtb and rk3328-rock64.dtb (I noticed that rk3328-rock6.dtb is the only version that uses the led of my box in the correct blue way in operation and red in standby) Boot OK and eth OK but problems with the usb using the 3 versions rk3328-evb.dtb No boot with rk3328-box-liantong.dtb, nor with the dtb taken in the latest version of libreelec (rk3328-box.dtb) What a misery to find this damn .dtb ... Thank again..

Hello, I encounter a problem again but I have trouble understanding I had succeeded in booting the .img bullseye desktop from the station M1 with the rk3328-box.dtb taken in the last libreelec .. I am trying this time to boot the buster version of station M1 without a desktop by also placing the libreelec rk3328-box.dtb, but this time I have no boot (nothing.. only black screen) .. Is it since the kernel used in the Buster is old I have to find another one .dtb adapted to this kernel ..? something else since I can start Armbian from my Emmc, isn't there a command line allowing to reboot directly to the SD card ..? I can boot station M1 on my MX10, first I boot directly after flashed sd-card but I don't have eth0, so I try rk3328-evb.dtb and I can boot with eth0, I start testing (installation of yunohost) Thanks again @balbes150

@balbes150 and i take this opportunity to ask you another question, i would like to test jellyfin but i am not sure which method used to install it with support for hardware decoding? Can you explain to me how you installed jellyfin on your M1 station (dockers, snap, others, ...) Thank you

I have this kind of messages but I'm not sure if this is really annoying .. systemd-sysv-generator[336]: SysV service '/etc/init.d/hostapd' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 6.661760] systemd-sysv-generator[336]: SysV service '/etc/init.d/sysfsutils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 6.664647] systemd-sysv-generator[336]: SysV service '/etc/init.d/cpufrequtils' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust. [ 6.680000] systemd-sysv-generator[336]: SysV service '/etc/init.d/loadcpufreq' lacks a native systemd unit file. Automatically generating a unit file for compatibility. Please update package to include a native systemd unit file, in order to make it more safe and robust.

Thank you again and again, I managed to boot my old MX10 with the image for Station M1 with the rk3328-box.dtb file taken in your last libreelec image .. It starts I did an apt update / upgrade and j I started a transfer of large files via sftp to see if my previous problem was present or not, and very good surprise I was able to make my transfers without problem .. I will test the transfers to my SSD (but it should be good. .) I still have some errors, here is a copy of my armbianmonitor -u http://ix.io/2ROk Maybe I need use rk3328-evb.dtb ?

And thank you again @balbes150 I am not sure I have mastered the method to do what you explained to me, especially with the last .img Station M1 that I found on your MEGA, once flashed I cannot access it my SD card, I only have an ext4 partition (as I am under win10 to flash with BalenaEtcher). When I flash the old Armbian_20.07_Rk3328-tv_buster_current_5.7.8.img after I can access the boot partition even under Win10 ..? Can you give me the link to your libreelec builds please. And thank you again ..