Jump to content

Armbian for Amlogic S912


chocho

Recommended Posts

19 minutes ago, jeanrhum said:

I haven't opened my gt1 ultimate.

 

Thank you for testing! I would keep the box closed since it shows excellent heat dissipation (25"C less than VIM2 with same load -- that's really impressive). Out of curiousity: what material is the enclosure made of and does it feel warm(er)?

 

@balbes150: Do you have a pillow at home to throw on the VIM2? ;) I can't understand that no one is able to get the S912 throttling! :) 

Link to comment
Share on other sites

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).

Link to comment
Share on other sites

18 minutes ago, jeanrhum said:

I will also try to take more time to run this test

 

Usually 15 minutes should be sufficient (at least that's my experience). Wrt Beelink B1 heat dissipation forget my question please. Jean-Luc already provided insights over a year ago: https://www.cnx-software.com/2016/09/09/beelink-gt1-4k-tv-box-review-part-1-unboxing-and-teardown/

 

So the heat gets spread to this large metal plate at the enclosure bottom which seems to be rather efficient. :) 

Link to comment
Share on other sites

Wrapped in a warm hat is one of my TV boxes (Tronsmart Vega S96) :) .

Run test for a couple of hours. Here is the result at the end of the second hour. Such a conclusion in the console, no change for end hours, so stopped the test.

 

Spoiler

1512 @ 79:     execution time (avg/stddev):   4.1436/0.01
1200 @ 79:     execution time (avg/stddev):   4.0925/0.01
1512 @ 79:     execution time (avg/stddev):   4.1210/0.00
1200 @ 79:     execution time (avg/stddev):   4.1082/0.01
1512 @ 79:     execution time (avg/stddev):   4.0899/0.01
1200 @ 79:     execution time (avg/stddev):   4.1200/0.01
1200 @ 79:     execution time (avg/stddev):   4.0957/0.01
1200 @ 79:     execution time (avg/stddev):   4.1305/0.01
1512 @ 79:     execution time (avg/stddev):   4.1274/0.01
1200 @ 79:     execution time (avg/stddev):   4.0736/0.01
1200 @ 79:     execution time (avg/stddev):   4.1054/0.01
1200 @ 79:     execution time (avg/stddev):   4.1650/0.01
1512 @ 79:     execution time (avg/stddev):   4.0857/0.01
1512 @ 79:     execution time (avg/stddev):   4.0908/0.01
1512 @ 79:     execution time (avg/stddev):   4.1230/0.01
1512 @ 79:     execution time (avg/stddev):   4.1660/0.00
1200 @ 79:     execution time (avg/stddev):   4.0707/0.00
1200 @ 79:     execution time (avg/stddev):   4.1134/0.01
1512 @ 79:     execution time (avg/stddev):   4.1198/0.01
1200 @ 79:     execution time (avg/stddev):   4.0714/0.01
1200 @ 79:     execution time (avg/stddev):   4.1465/0.01
1512 @ 80:     execution time (avg/stddev):   4.0923/0.01
1200 @ 79:     execution time (avg/stddev):   4.0756/0.01
1200 @ 79:     execution time (avg/stddev):   4.2131/0.01
1200 @ 79:     execution time (avg/stddev):   4.1439/0.00
1512 @ 79:     execution time (avg/stddev):   4.0813/0.01
1512 @ 79:     execution time (avg/stddev):   4.1081/0.01
1512 @ 79:     execution time (avg/stddev):   4.1305/0.01
1512 @ 79:     execution time (avg/stddev):   4.0961/0.00
1200 @ 79:     execution time (avg/stddev):   4.1359/0.01
1512 @ 79:     execution time (avg/stddev):   4.1054/0.01
1512 @ 79:     execution time (avg/stddev):   4.0900/0.01
1512 @ 79:     execution time (avg/stddev):   4.0790/0.01
1512 @ 79:     execution time (avg/stddev):   4.0888/0.01
1200 @ 79:     execution time (avg/stddev):   4.0865/0.01
1200 @ 79:     execution time (avg/stddev):   4.1416/0.01
1512 @ 79:     execution time (avg/stddev):   4.1541/0.01
1512 @ 79:     execution time (avg/stddev):   4.0418/0.01
1512 @ 80:     execution time (avg/stddev):   4.1571/0.01
1512 @ 79:     execution time (avg/stddev):   4.1074/0.01
1512 @ 80:     execution time (avg/stddev):   4.1449/0.01
1200 @ 79:     execution time (avg/stddev):   4.1127/0.01
1200 @ 79:     execution time (avg/stddev):   4.1390/0.01
1200 @ 79:     execution time (avg/stddev):   4.1569/0.01
1512 @ 79:     execution time (avg/stddev):   4.1365/0.01
1200 @ 79:     execution time (avg/stddev):   4.0810/0.01
1512 @ 79:     execution time (avg/stddev):   4.1297/0.01
1200 @ 79:     execution time (avg/stddev):   4.0858/0.01
1512 @ 79:     execution time (avg/stddev):   4.0995/0.01
1200 @ 79:     execution time (avg/stddev):   4.1034/0.01
1512 @ 79:     execution time (avg/stddev):   4.0843/0.01
1512 @ 79:     execution time (avg/stddev):   4.1451/0.01
1200 @ 79:     execution time (avg/stddev):   4.1349/0.01
1512 @ 79:     execution time (avg/stddev):   4.1799/0.01
1512 @ 79:     execution time (avg/stddev):   4.1290/0.01
1200 @ 79:     execution time (avg/stddev):   4.2215/0.01
1200 @ 79:     execution time (avg/stddev):   4.1333/0.01
1512 @ 79:     execution time (avg/stddev):   4.1494/0.01
1200 @ 79:     execution time (avg/stddev):   4.1901/0.01
1512 @ 79:     execution time (avg/stddev):   4.1292/0.01
1512 @ 79:     execution time (avg/stddev):   4.1551/0.01
1200 @ 79:     execution time (avg/stddev):   4.2086/0.01
1512 @ 79:     execution time (avg/stddev):   4.1498/0.01

 

Link to comment
Share on other sites

14 hours ago, balbes150 said:

1200 @ 79:     execution time (avg/stddev):   4.2215/0.01

 

Thank you for the test. So this box starts to throttle around 80°C and reported cpufreq also decreases (when 1512 is shown in reality it's 1200 MHz, the above execution duration indicates ~1080MHz in reality). So numbers still bogus as expected but at least there is an indication that throttling happens through sysfs (Raspberry Pi for example fakes this also: when throttling happens there and the real cpufreq goes below 1200 MHz -- eg. 800 MHz -- sysfs still reports 1200 MHz until 600.1 MHz. Only if throttled down to 600.0 MHz sysfs shows correct values again).

Link to comment
Share on other sites

8 minutes ago, Shimon said:

Does anyone know if this feature could be ported to the Armbian kernel? I'm sure it would solve those weird ramspeed results reported earlier.

 

Ramspeed? Kernel?

 

The issue is that the firmware blob is lying to the kernel wrt cpufreq (not RAM -- testing with sysbench is excluding RAM 100%). How should something in the kernel fix firmware behaviour? What's the proof of 'All cores now work at 1.5ghz'? The fantasy values returned by /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq?

Link to comment
Share on other sites

27 minutes ago, tkaiser said:

 

Ramspeed? Kernel?

Please, read the thread before spouting question marks. I know what the issue is, I originally benchmarked it. The kernel is almost certainly involved in that observed performance drop due to big.little scheduling. 

 

Superceleron's mod is definitely worth investigating.

Link to comment
Share on other sites

How do i get my H96Pro+ to work with a DVI monitor (it works fine with our Samsung TV, HDMI input)? I've tried to with HDMI-to-DVI adapter (this could be opposite adapter not sure), no signals on the monitor. 

Do i need active HDMI-to-DVI adapter?

 

Will any Orange Pi H3 or H5 boards have the same issues too? I'm planning to buy an Orange Pi board that has accelerated X11/GUI so that i can use it as a simple desktop, mainly to access my KVM VM over SPICE protocol.

 

Link to comment
Share on other sites

Data for the Odroid-C2 for 2 threads to fill out the table @tkaiser.

100:     execution time (avg/stddev):   196.7230/0.01
250:     execution time (avg/stddev):   76.9758/0.01
500:     execution time (avg/stddev):   37.5997/0.00
1000:     execution time (avg/stddev):   18.3120/0.00
1296:     execution time (avg/stddev):   14.3056/0.00
1536:     execution time (avg/stddev):   12.0588/0.00
1656:     execution time (avg/stddev):   11.1768/0.00
1680:     execution time (avg/stddev):   11.0148/0.00
1752:     execution time (avg/stddev):   10.5501/0.00

 

Link to comment
Share on other sites

Hi, i'm mauro i'm try to enter in this world.....I have a T95K PRO box but i have some problem can anyone help me. I'm succefull boot up Arm bian with many image with q2012g.dtb file but after all startup process i can't utilize internet. I connect ehthet cable i try to set manual but nothid do. How can i solve?

 

I see that ethert was see because i see MAC address...

 

i have a question the dtb.img have driver?? so i need to try all boot up my box?

 

sorry if i bother all of you

 

Thankyou Mauro

Link to comment
Share on other sites

Hello, guys!

I am still trying to start Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_icewm_20171212.img.xz on Beelink GT1 Ultimate.

Without any dtb.img files it started, asked me for root login/password, asked to create linux user, rebooted and after that it don't want to start:

IMG_20171220_215905.jpg

 

After that I've rebooted TV box with CTLR+ALT+DEL and got another view:

IMG_20171220_220728.jpg

 

I've tried all files from dtb directory and, as result, TV box booted only with kvim****.dtb files, but the similar boot error.

With other files from dtb directory TV box didn't booted at all - it hangs on Beelink boot logo.

 

Here is my /var/log/ directory from TV box, booted with kvim multiboot dtb - https://goo.gl/tJwQSa .

Can you advise me, how to fix such error?

 

Thank you!

Link to comment
Share on other sites

I found warnings in the file /var/log/lightdm/seat0-greeter.log :

** (process:4593): WARNING **: Error reading existing Xauthority: Failed to open file '/var/lib/lightdm/.Xauthority': Permission denied
Error writing X authority: Failed to open X authority /var/lib/lightdm/.Xauthority: Permission denied

 

but there is no .Xauthority file in the /var/lib/lightdm/ directory.

Link to comment
Share on other sites

I have some progress - I've downloaded boot.img from my Android 7.1.1 Beelink GT1 Ultimate TV box.

I followed an instruction from lvmc - 

 

but I got only

 

./split_bootimg.pl boot.img
Page size: 2048 (0x00000800)
Kernel size: 7944273 (0x00793851)
Ramdisk size: 1482583 (0x00169f57)
Second size: 0 (0x00000000)
Board name:
Command line: buildvariant=user
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.

 

and there is no boot.img-second.gz .

 

How can I extract DTB/DTS from Android 7.1.1 TV box? 

 

Thank you! 

Link to comment
Share on other sites

I got same issue like @ArtUrlWWW on H96 Pro+ 3GB/32GB S12. On LE I use gxm_q200_3g.dtb and works with no problem at all but on "Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img" boot well without any dtb but it stuck on similar ss posted above.

 

I can enter to gui with command "strartx" from  a tty shell but it send me to a different gui I think because it doesn't have the option  of lightdm in the upper right corner of the screen where I can choose one of the three option there and at the same time I can't use sudo from mate terminal.

 

For some strange reason that I don't understand when I was try to run Armbian for the 2nd or 3rd time I could enter to Armbian login with no problem but wifi didn't work so I hadn't read enough then try to fix it running Armbian from zero again with no luck (noob mistake, now I know that I just need to load the wifi_dummy module :)) after that I flashed my tvbox to its stock firmware, reburned my media a few times with no luck.

 

Link to comment
Share on other sites

Hi all!

 

I wanted to thank @balbes150 for his work, I tested ubuntu xenial with icewm on a H96 pro+ 3G/32G, and it works very well.

However, as I tried to download the regular (mate) distribution on https://yadi.sk/d/5_32km_EsCV2A/ARMBIAN , I had a lot of trouble because download througput is too slow, and stops before download is finished.

 

Do you have another option for downloading this file ? Thank you in advance for your help !

Link to comment
Share on other sites

Excuse my lazyness, but I see this topic is huge... I see it's possible to run Linux on Amlogic S912 packed in Beeling GT1 Ultimate, but I'm not sure if hardware graphic acceleration (it's that ARM Mali-T820MP3, right?) can be used. Some say it's possible but I have yet to see someone says it works flawlessly on this type of sweet little box. Also, does wireless keyboard/mouse work?

 

Android 7 on this box is kind of usable, yet there are many problems like low picture quality when rendering movies (it's ok on desktop), hardware acceleration not working in Kodi (you can't play 4K videos), and generally it's really painful to use Android as desktop operating system.

 

Can somebody throw few useful links?

 

Thanks!

Link to comment
Share on other sites

Hello,

Ive got an
H96 pro plus 3/32 
I would like to put linux on but it doesn't work.

Does anyone can tell me exactly which DTB file i have to use for this model?


ive got the same issue than Marcopolo

I run initially UPDATE&BACKUP App and choose the zip file, It says "shutting down" and there is no sign of activity of any reboot, no screen output nothing.
waited much longer than 10mins several times.

Tried to press the reset button when power on with paper clip. no screen output anytime when booting with sd card inserted.

In a second time i would like to install direcly Linux if it work well on eMMC...

If anyone can help me it will be great!

thx

Rémi

Link to comment
Share on other sites

46 minutes ago, pulesky said:

I run initially UPDATE&BACKUP App and choose the zip file, It says "shutting down" and there is no sign of activity of any reboot, no screen output nothing.
waited much longer than 10mins several times.


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.

Link to comment
Share on other sites

13 hours ago, jeanrhum said:


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 ve got GT1 ultimate also

 

Do you use stock ROM or superceleron ROM on GT1?

 

On superceleron rom no android tv for me i don't have the backup apk...

 

 

Could you help to trying to install on ultimate GT1?

 

what is the step and your initial firmware please?

 

 

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines