jeanrhum

Hi, I downloaded latest image (5.75) for s912 and give it a try with my beelink gt1 ultimate and it sucessfully boots with meson-gxm-q201.dtb. Compared to my previous try, usb and ethernet are working well. I'm re-installing my server with this build (OMV, home-assistant, zigbee2mqtt, etc.). Great work again! In case it is useful, here is the result of armbianmonitor -u: http://ix.io/1Be0

Yes I will try to clone your repo and build it by myself. They are not too expensive on gearbest now. That's where I bought mine.

I just ordered the box, so no I'm not there . I should receive the box in a few weeks.

Hi, Nice work! I just bought this box and I'd be happy to test your image if you can provide a link. Otherwise I will try to follow your instructions to build one.

Yes please, can you post it? I was able to boot jock image with my ut3s, but not all features working. Look at this topic:

A new test using a beelink minimx amlogic s905 with 1GB ram. I used one of the latest balbes img based on armbian 5.71 and kernel 4.20: http://ix.io/1z8U

I can also confirm that a Beelink MiniMX (s905 1/8GB) is working well with 5.71 debian stretch 4.20.2. I just had to modify the uEnv.ini to set the gxbb-p200.dtb and even wifi works. I use the desktop version to test all features, but with only 1GB of ram, it seems better to use it as a server. The video test file plays well in windowed mode and it seems viewable in fullscreen but there are some frame dropped. I'm not able to test sound since my lcd screen has no audio output and there is such output on that box.

Have you burnt uboot on the sdcard? My last post in this topic give one procedure.

Hi, I'm also using home-assistant since about 2 years I think on a tv-box with an armbian image from balbes (5.37 and legacy kernel). I used the virtualenv method and not hassio. The problem with hassio, is that I didn't manage to install it with docker on an arm64 system, but I didn't search too much. For mqtt and mosquitto, you just have to give the url of the server that can be local. There is also a mqtt server integrated in home-assistant.

Hi, Thanks Balbes, I am now able to boot my V88 mini III with your images (4.4 and 4.19). I summarize the procedure for those who have to burn uboot on the sd card: After getting an image from Balbes repo, download also the files for uboot (ibdloader.img, trust.img, uboot.img) also available on his yandex repo: Burn Balbes image with Etcher or any other reliable software Burn uboot on sdcard as follows: sudo dd if=path/to/idbloader.img of=/dev/sdb seek=64 conv=sync,fsync sudo dd if=path/to/uboot.img of=/dev/sdb seek=16384 conv=sync,fsync sudo dd if=path/to/trust.img of=/dev/sdb seek=24576 conv=sync,fsync My box boots with rk3328-rock64.dtb but there is no ethernet and no wifi, but with rk3328-evb-100m.dtb I have eth0 working.

An additional bench with a snapdragon 820 soc (Inforce 6640): http://ix.io/1uOW I used default small heatsink without any fan, so it throtles on some benchmarks which heavy cpu loads like cpuminer.

I didn't test if wif was working (I think it wasn't), because I only used ethernet.

With 3.14 kernel, I use the dtb of android img that is stored on emmc. So this is the Beelink dtb. In fact it is automatically used when you don't put a dtb file at the root of the sd card. I'll try to install it again, since a recent upgrade broke my system (no ethernet anymore). New images (4.xx) of Balbes does not really work on my box (no ethernet and no usb even if it boots).

Yes, my box was connected to a hdmi monitor, so I can view the console login prompt, but no usb to use a keyboard and no ethernet nor wireless to connect via ssh.

I tested recently and had the same issues with an s912 tv box (gt1 ultimate) previously running a 3.14 img. I was able to boot with most dtbs cthat are compatible with the soc, but I never hab been able to use usb nor network devices.

Until the campaign ends and they send the boards, I should receive one (1GB). I'll be able to test if there is any armbian build for it. I'm impressed (if verified when testing the board) by the current support status of this board. It often requires several months (years) when we look at existing boards (even if open source communities are doing a really great job).

Since I upgrade frequently, I think there is not too much difference. Armbian tools and firmware are updated as other packages. Of course there should be some specific modifications of Balbes after each update he made. If 5.41 has mali, it is useless for me since I use my box as a server.

As mentionned by talraash, I use 5.37 which use kernel 3.14. I don't do anything special, but the dtb from android is used since and I don't put anyone at the root of the sd card. The dtb from android (generally based on a 3.xx kernel for amlogic. soc) is often not compatible with kernel 4.x.

I tested yesterday evening your last image with my V88 mini III. I burnt your u-boot related files using rockchip opensource documentation, otherwise it booted to emmc starting android instead of sd card. After that, I still was not able to boot even after testing all available dtbs (except android ones). I'll try too connect uart as soon as possible to give more insight of the problem.

I'm currently running a Beelink GT1 ultimate (S912, 3Go DDR4, 32Go) with your armbian 5.37 based on 3.14.29 debian stretch without specifying any dtb file. It is used as a server with openmediavault and homeassistant. I'm running armbian from sd card. I just made upgrades and got armbian-config 5.64 with an uptime of 70 days.

I found that bt chip should be supported by mainline kernel, but relevant info have to be defined in device tree: https://github.com/torvalds/linux/blob/master/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt I suppose that your chip is also concerned, but I'm a totally newbie concerning device tree. I tried to decompile your current dtb, but then I'm not able to make the relevant modifications to then compile and get a working dtb. The dtc command asks for uart2_pins in the best case and I don't know how to configure them. Is there somebody else who make such broadcom bluetooth chip working with mainline? As I understand, only allwinner chips support overlays, because armbian-add-overlay returns an error claiming that.

No bluetooth is not working. No device is defined. I looked at several ways to add it, but nothing work for now.

Surely a stupid question, but is your psu working well ? and do you use the right usb port when use connect to pc?

Thanks a lot, wifi works well now with fw_bcm4339a0_ag.bin from github! In fact those files where in /lib/firmware/brcm/ (as asked by martinayotte) and not in /lib/firmware/ap6335/brcm/. I use the ones you told me to download, but I suppose that those in /lib/firmware/brcm/ should also work. You did something special to use this path?

Yes with many other brcmfac variants.