jeanrhum

I'm not sure any of the proposed image has vpu software, which make plex less interesting (no transcoding). I currently use a 5.37 based image with kernel 3.14 and this functionality is not installed by default.

I test to upgrade a pine64 from 5.38 (xenial server 3.10.107) to nightly builds i got this output after the upgrade: http://ix.io/14cr I'm still on 3.10.107 kernel even after trying to swtiching to dev or next kernel (switch is very fast). Do you want me to test something particular? I don't know where to search since no error is reported.

Thanks, I forgot this point and will add this to my check list ;). If I have time, I will try again to upgrade my pine64 but this time starting from latest 5.37 instead of the old image I was using.

I agree with you and was a member of the project management platform that was used one year ago. Maybe this platform was too heavy and a bit rigid. IMO the forum is more dynamic and open to any people, but currently there is no clear rule/guide on how to conduct some tests. What I've done each time I test a build is (order is approximative): 1. burn an image to a sd card with etcher 2. check if it boots as expected (command line or desktop) 3. configure linux using armbian-config (timezone, keyboard, etc.) 4. check hardware support (ethernet, wireless, sound, gpu, vpu), 5. check some highlighted functionalities I'm able to test (eg: kernel switching, desktop install) 6. update and upgrade packages 7. report back to forum and post the result of send diagnostic item in armbian-config (I suppose it calls armbianmonitor -u). Is there something wrong/missing in this list to help you in a better way?

I think it would be interesting to list the preferred boards that should be used for testing (maybe in a specific thread). I look at armbian website, documentation and forum, but this kind of information is not defined in a clear and unique place. In the first post of this thread, we can identify a few of them but that's all. If we want to help in testing and for instance buy a new board for that purpose, it could guide us. It can also give everbody a clue about best supported boards and their probably long term support by armbian. For instance: - Officially supported boards for testing: orange pi plus 2E (H3), pine64+ (A64), tinker board (rk3288), odroid c2 (s905), odroid xu4 (Exynos5422)... - WIP boards for testing: espresso bin (Armada 3700), rock64 (rk3328), NanoPi Neo Core2 (h5)... In the previous list, I only chose 1 board for a given soc, but it is just an example and it is probably difficult to define this list with most people agreeing. For instance, nighlty builds are not generated for all boards, so it can be a criterion to select these boards. The WIP boards list can also be fed by the board bring up section when a board is validated for official support and software is mature enough. With this list, if a thread like this one is created before each new release, it think it will focus testing on these preferred boards.

Hi, I succesfully boot last image for pine64: Linux pine64 4.14.29-sunxi64 #57 SMP Fri Mar 23 12:09:14 CET 2018 aarch64 GNU/Linux I use debian stretch server image and after freezing kernel upgrade, I install desktop from armbian-config: http://ix.io/12BY Desktop does not feel so smooth than on my opi+2e. Before that, I upgraded without freezing kernel upgrades and than I was not able to boot again. I will try again and will look at uart, but I had no u-boot screen. After defreeze, these 4 packages can be upgraded: linux-dtb-next-sunxi64 linux-image-next-sunxi64 linux-stretch-root-next-pine64 linux-u-boot-pine64-next Edit: Here is the UART info: U-Boot SPL 2017.11-armbian (Mar 24 2018 - 11:04:27) DRAM: 0 MiB ### ERROR ### Please RESET the board ###

I successfully upgrade my opi one (debian 9 5.38 next) to nightly using armbian-config. I have 2 pine64 boards, but I suspect one to have hardware issues. With this one, I did not achieve the upgrade when starting from latest 5.38 (debian or xenial server 3.4 kernel), the screen stay blue after some downloads and I can't do anything even after more than 10 minutes. With the other one (running a 5.31 ubuntu desktop I think) I update&upgrade to 5.38, after that when I want to switch to nightly, it downloads package and propose to reboot, but after reboot I'm still on kernel 3.14. Armbian-config title says 5.42 but kernel stay at 3.14 even if I try to swith to dev or next.

hi, Writing from: Linux orangepiplus2e 4.14.27-sunxi #105 SMP Thu Mar 15 22:24:12 CET 2018 armv7l armv7l armv7l GNU/Linux I'm testing xubuntu server nightly image. I successfully installed desktop and I'm writing this post inside chromium. Navigation on several simple websites is smooth and I was able to play a video from youtube. I configure wifi using armbian-config (default dhcp), then I defined a fixed IP. I was able to play a video with mpv, but it only plays smoothly inside a small window (default size). Sound is working but I had to launch alsamixer to increase the volume (~40% by default) because I was not able to change this in pulse audio gui. Cpu-freq adjust cpu frequency between 480MHz and 1.3GHz as expected More details: http://ix.io/YdQ Major features seems to work, great job! I will try to take time to test another image on my opi one upgrade to nightly and/or on a pine64.

Concerning the testing phase of Armbian, I was participating in previous "effort" using https://desk.armbian.com/public/index.php. I can continue to make some end-user tests (installation, upgrade, functionality test) if a process or something else is defined. I owned a few "armbian" boards based on A20, H3 and A64 and maybe planned to buy a more recent one based on rk3399 if it is cheap enough. Currently, I have not enough knowledge and time to come to the dev side.

I don't remember exactly which initial version I got (maybe 313 or something like that since I bought it about one year ago) and I manually upgrade via usb to one of the latest official rom (I think 704). Currently I use latest armbian server image from Balbes on sdcard and it just work as expected. I use the backup and upgrade procedure as described on the 1rst post of s905 topic. I upgraded android because , by accident, I erased the emmc with a previous version of Balbes' armbian a few month ago.

I had exact same problem with mine (Alfawise H96 pro+). I didn't find any solution... In fact I suppose that it comes from u-boot, but I had also some powering issues. with default android, reboot didn't work (I use now superceleron ATV and it works). Powering through classical power barrel didn't work anymore and I power it through usb . I have the model with 2 hidden usb ports. I also have a GT1 Ultimate and armbian work well with kernel 3.4 with no specified dtb (no wifi but no use for me). Since it has better heat dissipation than h96, I gave up to put armbian on it.

I haven't tested it. You have 2 possibilities: - look at retrorangepi to customize balbes image since they based their work on armbian and support most xunluong h3 boards. - use some similar emulators running on android. I just quickly test some emulators on android, and the main problem is with controllers. Since your are on a classical android, the user interface is based on tactile interactions (ie smartphone). Some of them allow to use a bluetooth or wired gamepad, which is very well supported by android, but mine low-cost one is not well recognized by the emulator itself. I just made some quick tests with some MAME emulators and it is not in my priorities to invest more times in this direction.

Hi, I have similar needs and here is my current configuration at home with the following hardware: - OPi+2E as server (nas+plex+home-assistant+small other various things) - an Amlogic TV box for multimedia (hdmi to TV and spdif to an home cinema for tv audio and airplay server) Previously I used a RPI2 (with raspbmc or openelec) instead of my TV box, but I had to plug a dac to have a decent audio rendering. Depending on the tv box you choose, you can have spdif and optical audio outputs for less money than a RPI+dac and android offers much more possiblities for multimedia and other activities, but it is less customizable than a real linux. You can also use Balbes150 armbian images on such hardware (look at TV box section of this forum). There are also android community firmwares which will most often deliver a better experience than the default one (look at freaktab forum). I think that for less than 80 euros you can have a good config with a sbc as server with a H3/H5 or A64 soc and GBE (or tv box with armbian on it) and a tv box for multimedia on your tv. Moreover, this config may not consume much more power than a big sbc around 200 euros (like those with A72 cores).

Maybe it is only for Allwinner SoCs, but you can try (Pine64 doc): If you use a DVI display don’t forget to define disp_dvi_compat=1 in /boot/armbianEnv.txt (supported starting with 5.21).

I didn't try these libraries, but here is what I would write according to your code and the links you give: from pyA20.gpio import gpio from pyA20.gpio import port import dht11 import paho.mqtt.client as mqtt import time import datetime #initialize GPIO PIN2 = port.PA6 gpio.init() #read data using pin port.PA6 instance = dht11.DHT11(pin=PIN2) channelId = "myid" # Put your channel ID here,i.e.. the number from the URL, https://thingspeak.com/channels/285697 apiKey = "mykey" # Put the API key here (the Write API Key from the API Keys tab in ThingSpeak) client = mqtt.Client() client.connect("mqtt.thingspeak.com",1883,60) while True: result = instance.read() if result.is_valid(): print("Last valid input: " + str(datetime.datetime.now())) print("Temperature: %d C" %result.temperature) print("Humidity: %d %%" % result.humidity) client.publish("channels/%s/publish/%s" % (channelId,apiKey), "temp="+str(result.temperature)+"&humidity="+str(result.himidity)) client.loop(2) time.sleep(1) The last line is not well displayed, it should only be shifted by 1 tab and not 2.

Hi, I think your errors are only python (basic) errors. If you put fun1() between quotes, it is a text an not a function call. Do you know how to program in Python? Because, I don't understand fun1() definition. Maybe you should take time to look a short tutorial on Python, like: https://learnxinyminutes.com/docs/python/ If you want your funtion to return a value, you have to use the return keyword, and not print function that print values into the console. Moreover, what is fun1.var? If you want to declare a local variable, in python you just have to state var = result.temperature. Then, result is unknown in the context of fun1. You have to pass it as a parameter. I stop here, but you really need to look at some basic documentation about programming and about Python language if this is the langauge you want to use.

what material is the enclosure made of and does it feel warm(er)? The enclosure is in platic. I will look closer to the enclosure and its temperature next time. Initial temperatures were around 36°C. I will also try to take more time to run this test, because I think the temperature could have continue to slowly increase but it was too late and I didn't want to let it run like that during night. I also have a H96 pro+ and the gt1 ultimate is much more heavy. I suppose that there is a big heatsink over the soc whereas h96pro+ has nothing (but I didn't succeed in running armbian on it, I suppose due to reboot issues even if I manage to install latest superceleron's rom from freaktab).

@tkaiserAfter more than 45 minutes I got this kind of values: -e 1512 @ 53: execution time (avg/stddev): 3.7886/0.01 -e 1512 @ 54: execution time (avg/stddev): 3.7963/0.01 -e 1512 @ 53: execution time (avg/stddev): 3.7880/0.01 -e 1512 @ 53: execution time (avg/stddev): 3.7933/0.00 -e 1512 @ 54: execution time (avg/stddev): 3.7865/0.01 -e 1512 @ 54: execution time (avg/stddev): 3.7899/0.01 I haven't opened my gt1 ultimate.

I just made a new test with latest image (xenial_3.14_20171104). I give you a wrong answer, that's my results: - with gxm_q200_3g.dtb : no hdmi output after beelink logo and not visible on my local network - without any dtb.img (default one from android rom I think): it boots well, but no wifi - with khadas vim 2 dtb: it boots well, but no wifi Since I want to use this box headless with a wired connection, I didn't checked wireless configuration. This evening, I'll try to make tests for tkaiser.

Hi, Yes I ran successfully (about 2 weeks ago) the 3.4 jessie version of Balbes150. I'll try to test again as soon as I have time (maybe this week-end). If I remember well, I used the same dtb as you. Which version of gt1 utlimate do you have (serial starting with S, G or A912, mine is G912)? It was running very well. I even use armbianconfig default script to install it on the emmc and it worked. Just after accepting the installation, I remembered Balbes' install.sh script is recommended instead of default armbian script to avoid bricking the box. So take care of that if you plan to install it on emmc, maybe I was lucky with my version.

Hi, thanks for all your work, but I have a problem when trying to using your images (xenial_server_3.14 or debian_server_4.14). I bought recently an Alfawise H96pro+ (3G DDR3/32G) and i can't boot with your images. I have a black screen without any lights from the box itself. Then I open the box and use a serial2usb key and got the following message after clicking update within android and after the box stopped: ... [ 121.784675@0] reboot reason 3 bl31 reboot reason: 0xd bl31 reboot reason: 0x3 system cmd 1. GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 50518 BL2 Built : 11:58:42, May 27 2017. gxl gc3c9a84 - xiaobo.gu@droid05 set vdd cpu_a to 1120 mv set vdd cpu_b to 1050 mv set vddee to 1000 mv Board ID = 3 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 720MHz - PASS Rank0: 2048MB-2T-11 Rank1: 1024MB-2T-11 DataBus test pass! AddrBus test pass! -s Load fip header from eMMC, src: 0x0000c200, des: 0x01400000, size: 0x00004000 New fip structure! Load bl30 from eMMC, src: 0x00010200, des: 0x01100000, size: 0x0000d600 Load bl31 from eMMC, src: 0x00020200, des: 0x05100000, size: 0x00018400 Load bl33 from eMMC, src: 0x0003c200, des: 0x01000000, size: 0x00064000 NOTICE: BL3-1: v1.0(release):3348978 NOTICE: BL3-1: Built : 15:44:01, May 12 2017 NOTICE: BL3-1: BL33 decompress pass mpu_config_enable:ok [Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07] OPS=0x82 wdt: reset registers! 30 fb 90 e1 cc a5 72 13 4d 1c d3 b [0.261510 Inits done] secure task start! high task start! low task start! ERROR: Error initializing runtime service opteed_fast U-Boot 2015.01-g6842d86-dirty (Jul 27 2017 - 22:09:32) DRAM: 3 GiB Relocation Offset is: b6eb9000 register us The stock android firmware is based on android 7.1.2 and the board is from 20170728. The problem seems to appear before linux start. I tried with and without a dtb file from librelec (only for kernel 4), since my previous X96 (s905x) works well with your images running desktop but I saw that recent images requires it. Am i wrong somewhere in the process, or is there a specific problem to my uboot or maybe something else I don't understand ?

I use mosquitto as a MQTT broker on my opi+2e and it works well. It can be installed from standard repo, just do: sudo apt-get update sudo apt-get install mosquitto Before you can publish or subscribe to any topic, you have to install some clients: apt-get install mosquitto-clients Then you can send data (publish) to the broker on a topic, and/or get them (subscribe): # publish 32.5 value to topic sensor/temperature on localhost mosquitto_pub -h localhost -t sensor/temperature -m 32.5 # subscribe to topic sensor/temperature on localhost: it waits until ctrl+c for any publish values mosquitto_sub -h localhost -t "sensor/temperature" To test your local broker, you have to write the subscribe command in a terminal and the publish one in another and you can repeat the publish one with different values. You should see the values appearing in the subscribe terminal. You can also use node-red to manipulate MQTT message with other protocols or sources or targets for your data. You'll find easily some tutorials on the internet.

Rock2 images are no more available on Radxa servers. I saw in the same thread that firefly images seems to be also compatible. There is an ubuntu 16.04 image from may 2017. Most of these images should be flashed to emmc instead of running directly from sd card. Is there a procedure to change such images and run them directly from a sd card? Or is it possible to burn (eg. with etcher) them and it just works?

I tested MiQi image without any success. Like you, I have no output on hdmi and my UT3S does not seem to boot since the power led shut down after a few seconds. I have no time to investigate more, but will try as soon as possible. I tried to look for a dts or dtb without any success.

I made only a few tests on my UT3S received some days ago. I successfully upgrade firmware using win10 and androidtool. I flashed last official firmware being v3.1 (Android 5). It removes the dual boot with xubuntu 15.04. However, the bootloader allow me to boot from an sdcard if one is inserted. So I burnt an official xubuntu 14.10 image on a card and it's booting successfully. This image from Ugoos can be found here: http://ugoos.net/blog/ubuntu1504-sdcard-arm7-rk3288-ugoos-ut3-ut3s-um3