Jump to content

ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)


balbes150

Recommended Posts

13 hours ago, fatugazuhati said:

I have been able to boot Stretch with the kernel, the modules and the firmware from Jessie but amremote still doesn't work -.-"

I checked the remote on the latest version of Mate 3.14.29 (20180205). It works. Perhaps Debian changed\no used to do packages.

Link to comment
Share on other sites

1 hour ago, balbes150 said:

I checked the remote on the latest version of Mate 3.14.29 (20180205). It works. Perhaps Debian changed\no used to do packages.

I really don't like ubuntu and I'd like to continue using Debian, do you think that this problem can be solved in some way?

Link to comment
Share on other sites

36 minutes ago, fatugazuhati said:

I really don't like ubuntu and I'd like to continue using Debian, do you think that this problem can be solved in some way?

I think it's solved. Try to compare the packages with a working version of Jessi or Ubuntu, maybe you'll find what packages are missing in the new version.

Link to comment
Share on other sites

8 hours ago, balbes150 said:

I think it's solved. Try to compare the packages with a working version of Jessi or Ubuntu, maybe you'll find what packages are missing in the new version.

I'm comparing jessie with stretch from yesterday but without much success.

 

Anyway I have just tried with Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20180205.img and the remote still doesn't work, for example if I press the power-off button nothing happens and in the syslog I have this:

Feb  5 20:51:01 localhost kernel: [  563.265710@0] remote: press ircode = 0x18,
Feb  5 20:51:01 localhost kernel: [  563.265735@0] remote: scancode = 0x0074,maptable = 0,code:0xe718ff00
Feb  5 20:51:01 localhost kernel: [  563.265777@0]
Feb  5 20:51:01 localhost kernel: [  563.625406@0] remote: release ircode = 0x18,
Feb  5 20:51:01 localhost kernel: [  563.625430@0] remote: scancode = 0x0074, maptable = 0,code:0x00000000
Feb  5 20:51:01 localhost kernel: [  563.625445@0]

 

Solved :-) I had to write a new rule, thanks for your hard work.

 

Link to comment
Share on other sites

Hi balbes150, great work you doing , I just need to ask one thing .Can't we use these images on vga monitors , on t.v its working fine but on vga monitors it says "Input not supported", so is there any change which I need to do to make it work on those vga monitors ?

Link to comment
Share on other sites

On 06.02.2018 at 10:59 AM, Saurabh said:

great work you doing , I just need to ask one thing .Can't we use these images on vga monitors , on t.v its working fine but on vga monitors it says "Input not supported", so is there any change which I need to do to make it work on those vga monitors ?

Have you tried changing the default resolution from 1080 to 720 ?

Link to comment
Share on other sites

Hi Balbes,

Could you please compile and include kernel drivers for the Ralink/Mediatek MT7601U with the AP options in?

They compile on other armbians e.g  Orange PI , on this one seems like not...

It is the one described here: 

Thanks!

 

Link to comment
Share on other sites

Link to comment
Share on other sites

12 hours ago, Vasy said:

Could you please compile and include kernel drivers for the Ralink/Mediatek MT7601U with the AP options in?

They compile on other armbians e.g  Orange PI , on this one seems like not...

It is the one described here: 

I'll add this to the next version of the image, or I'll try to make an additional deb package for self-installation.

 

 

Link to comment
Share on other sites

3 hours ago, Vasy said:

The second one is easier since it may save some of us from a complete reinstall..

Try the version from the catalog on the website mali6\5.41. Try to run from external media and test the mt7601. If it works, you can try to build a separate deb package for legacy images.

Link to comment
Share on other sites

On 08.02.2018 at 9:36 AM, Saurabh said:

Yes I tried changing mode from 1080 to 720p60hz. It was showing same ,"Input not supported"

 

hi there in the file - hdmi.sh error for changing to 720 need to take my

 

#!/bin/sh

bpp=32
#bpp=24

#mode=1080p60hz
mode=720p60hz

case $mode in
    1080*)
    fbset -fb /dev/fb0 -g 1920 1080 1920 2160 $bpp
    fbset -fb /dev/fb1 -g 32 32 32 32 32
    echo $mode > /sys/class/display/mode
    echo 0 > /sys/class/graphics/fb0/free_scale
    echo 1 > /sys/class/graphics/fb0/freescale_mode
    echo 0 0 1919 1079 > /sys/class/graphics/fb0/free_scale_axis
    echo 0 0 1919 1079 > /sys/class/graphics/fb0/window_axis
    echo 0 > /sys/class/graphics/fb1/free_scale
    ;;
    720*)
    fbset -fb /dev/fb0 -g 1280 720 1280 1440 $bpp
    fbset -fb /dev/fb1 -g 32 32 32 32 32
    echo $mode > /sys/class/display/mode
    echo 0 > /sys/class/graphics/fb0/free_scale
    echo 1 > /sys/class/graphics/fb0/freescale_mode
    echo 0 0 1279 719 > /sys/class/graphics/fb0/free_scale_axis
    echo 0 0 1279 719 > /sys/class/graphics/fb0/window_axis
    echo 0 > /sys/class/graphics/fb1/free_scale
    ;;
esac

# Enable framebuffer device
echo 0 > /sys/class/graphics/fb0/blank

# Blank fb1 to prevent static noise
echo 1 > /sys/class/graphics/fb1/blank

echo 0 > /sys/devices/virtual/graphics/fbcon/cursor_blink

#/etc/webmin/start &

#su -c 'hciattach /dev/ttyS1 any'
 

Link to comment
Share on other sites

2 hours ago, balbes150 said:

Updated version 3.14.29 20180211. Added modules Wi-Fi mt7601 and qca9377 (tested on Vega S96 s912).

Thanks! I booted it up, loaded the module, and when connecting the device I get "rt2870 probe failed with error -1". I assume you may not have one at hand to test it :(

Link to comment
Share on other sites

No one noticed a strange load in stretch? Wit a clean install, the cpu at 0% and with almost all the ram free the load never goes under 1. In jessie in the same conditions I have a load of 0. I'm trying to understand why this happens.


Ok, the culprit is vdec-core that always waits for disk access and the problem is in the kernel, using the kernel from jessie everything works correctly. I would use an updated kernel, how can this problem been solved?

Link to comment
Share on other sites

Hi

 

I have Armbian_5.34_S9xxx_Ubuntu_xenial_3.14.29_server_20171104 installed on the TV box's NAND, I want to upgrade to Armbian_5.37_S905_Ubuntu_xenial_3.14.79_server_20180209

What is the process? The system is up to date using apt-get upgrade  / dist-upgrade command. I don't want a fresh install and config everything from zero. Should I manually flash boot.img, update dtb and overwrite firmware directory?

Link to comment
Share on other sites

10 hours ago, 8zabi said:

I have Armbian_5.34_S9xxx_Ubuntu_xenial_3.14.29_server_20171104 installed on the TV box's NAND, I want to upgrade to Armbian_5.37_S905_Ubuntu_xenial_3.14.79_server_20180209

What is the process? The system is up to date using apt-get upgrade  / dist-upgrade command. I don't want a fresh install and config everything from zero. Should I manually flash boot.img, update dtb and overwrite firmware directory?

Have you tested the new version of the 3.14.79 kernel when running it from external media on your TV box model ?

Link to comment
Share on other sites

19 hours ago, Vasy said:

I booted it up, loaded the module, and when connecting the device I get "rt2870 probe failed with error -1". I assume you may not have one at hand to test it

Try to install additional packages from the firmware.

https://yadi.sk/d/VrXItQ-k3SKEth

 

17 minutes ago, 8zabi said:

Not yet, but what is the process of upgrade, in theory?

Since the beginning of the test, if it works, then it will be "theory".

Link to comment
Share on other sites

Today I did try to boot armbian on my Sunvell T95K Pro (S912, 2GB Ram, 16GB "ROM")

 

I used the aml_autoscript from https://yadi.sk/d/bqV6MEL-sWKmv/v05

(dont know when it worked - did the update serveral times via SD-card or USB-Stick).

 

Then I did try to boot via SanDisk uSD-Card....but it didnt worked with the following images:

Armbian_5.37_S9xxx_Debian_stretch_4.9.40_server_20180202.img

(from https://yadi.sk/d/pHxaRAs-tZiei/4.9.40)

and

Armbian_5.41_S9xxx_Debian_stretch_3.14.29_server_20180212.img

(from https://yadi.sk/d/pHxaRAs-tZiei/mali-6/5.41)

 

But Armbian_5.41_S9xxx_Debian_stretch_3.14.29_server_20180212.img did boot via USB-Stick (32GB Spaceloop by CnMemory)

on USB-Port USB1 (at the back) 

 

Armbian_5.37_S9xxx_Debian_stretch_4.9.40_server_20180202.img wont boot at the same port with a Toshiba 32GB USB 3.0 Stick

(only the first "blinks" then no more light from the USB-Stick)

 

Armbian_5.41_S9xxx_Debian_stretch_3.14.29_server_20180212.img  did boot very fast (not 7-10 Minutes...only 1-2 minutes)

Or 7-10 minutes for the Desktop-Image?

 

@balbes150: Should'nt the image with the new kernel boot on my device or has to be done more (on u-boot) for the newer kernel?

Link to comment
Share on other sites

More or less same results here with supposed MXQ PRO and MXQ PRO Plus (different Wi-Fi as show on previous images). Last image working without issues are Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20171226.img. But I can't make run any kernel 4.9 or new Mali images. 

Link to comment
Share on other sites

On 2/11/2018 at 8:35 PM, jjekaa79 said:

 

hi there in the file - hdmi.sh error for changing to 720 need to take my

 

#!/bin/sh

bpp=32
#bpp=24

#mode=1080p60hz
mode=720p60hz

case $mode in
    1080*)
    fbset -fb /dev/fb0 -g 1920 1080 1920 2160 $bpp
    fbset -fb /dev/fb1 -g 32 32 32 32 32
    echo $mode > /sys/class/display/mode
    echo 0 > /sys/class/graphics/fb0/free_scale
    echo 1 > /sys/class/graphics/fb0/freescale_mode
    echo 0 0 1919 1079 > /sys/class/graphics/fb0/free_scale_axis
    echo 0 0 1919 1079 > /sys/class/graphics/fb0/window_axis
    echo 0 > /sys/class/graphics/fb1/free_scale
    ;;
    720*)
    fbset -fb /dev/fb0 -g 1280 720 1280 1440 $bpp
    fbset -fb /dev/fb1 -g 32 32 32 32 32
    echo $mode > /sys/class/display/mode
    echo 0 > /sys/class/graphics/fb0/free_scale
    echo 1 > /sys/class/graphics/fb0/freescale_mode
    echo 0 0 1279 719 > /sys/class/graphics/fb0/free_scale_axis
    echo 0 0 1279 719 > /sys/class/graphics/fb0/window_axis
    echo 0 > /sys/class/graphics/fb1/free_scale
    ;;
esac

# Enable framebuffer device
echo 0 > /sys/class/graphics/fb0/blank

# Blank fb1 to prevent static noise
echo 1 > /sys/class/graphics/fb1/blank

echo 0 > /sys/devices/virtual/graphics/fbcon/cursor_blink

#/etc/webmin/start &

#su -c 'hciattach /dev/ttyS1 any'
 

@jjekaa79 thank you for pointing it out , it worked.

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