Armbian for Amlogic S9xxx kernel 5.x

[Linton]

On 3/18/2019 at 7:35 PM, guidol said:

dpkg -i armbian-config_5.77_all.deb dpkg -i linux-image-aml-s912_5.77_arm64.deb dpkg -i linux-headers-aml-s912_5.77_arm64.deb dpkg -i firmware-armbian-full_5.77_all.deb reboot

 

Thats a great tip! 

[Peyton]

1 hour ago, guidol said:

 

if you got a Box with S912 and armbian 5.76 - then you could "update" like I did.
Download the packages from  https://yadi.sk/d/pHxaRAs-tZiei/5.77/deb and

dpkg -i armbian-config_5.77_all.deb
dpkg -i linux-image-aml-s912_5.77_arm64.deb
dpkg -i linux-headers-aml-s912_5.77_arm64.deb
dpkg -i firmware-armbian-full_5.77_all.deb

reboot

(firmware and headers could be optional from your sight of view)

Before this firmware-package I only got a Broadcom (brcm) package installed for the WiFi Firmware

Headers are for compiling Sourcecode
 

This should leave you apps/config intact.

Worked like a charm. Thanks !

[Linton]

Outdated.

 

Edited March 26, 2019 by purplepumkin
Solved the issue myself

[Reddwarf]

Kernel 5.02 works fine except it doesen't see the built in BT on any of my boxes (905 and 905x), nor is there any sound with any dtb's

[dbsharpe]

36 minutes ago, Reddwarf said:

Kernel 5.02 works fine except it doesen't see the built in BT on any of my boxes (905 and 905x), nor is there any sound with any dtb's

I've had to use DTB's from other Armbian builds to get snd_soc_meson working.

[Reddwarf]

Just now, dbsharpe said:

I've had to use DTB's from other Armbian builds to get snd_soc_meson working.

Which box and which dtb did you use?

[dbsharpe]

13 minutes ago, Reddwarf said:

Which box and which dtb did you use?

 

14 minutes ago, Reddwarf said:

Which box and which dtb did you use?

I have two T95's - one is p201, the other is p212.
Armbian_5.73_Aml-s905_Ubuntu_bionic_default_4.20.2_desktop_20180129_img.xz (lima)  contains the working dtb's.

(see  forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-41x-ver-555/?do=findComment&comment=72165 )

[Reddwarf]

22 minutes ago, dbsharpe said:

 

I have two T95's - one is p201, the other is p212.
Armbian_5.73_Aml-s905_Ubuntu_bionic_default_4.20.2_desktop_20180129_img.xz (lima)  contains the working dtb's.

(see  forum.armbian.com/topic/7930-armbian-for-amlogic-s9xxx-kernel-41x-ver-555/?do=findComment&comment=72165 )

Thanks, I'll give it a go

[Reddwarf]

11 hours ago, Reddwarf said:

Thanks, I'll give it a go

No dice :(. Strange thou for sound worked for all images with kernel 3.x.....

[Linton]

Can someone please help me with a working dtb for a p281 a95 xr2 board? The generic p281 included with 4.x/5.x builds does not boot. There's a few revisions of the p281 board. I need p281 r2 (2g/16g). 

[Peyton]

You should try to downgrade your Android version like we have to do with mekool KM8P. Try kernel 3.14 armbian too just to check.

[Linton]

18 minutes ago, Peyton said:

You should try to downgrade your Android version like we have to do with mekool KM8P. Try kernel 3.14 armbian too just to check.

 

The only working dtb I have is from 3.x kernels yes. But I have no clue how to make that work for 4.x/5.x kernels or how to fix the non working p281 thats bundled with the new builds. I also don't know how to build 3.x kernels from source, by default the s905 build now builds a 5.x kernel. Not all modules I need are in 3.x kernels and also some wifi drivers don't build or work good for 3.x. They're usually for 4.x or newer kernels.

[balbes150]

On 3/19/2019 at 10:46 PM, Reddwarf said:

Kernel 5.02 works fine except it doesen't see the built in BT on any of my boxes (905 and 905x), nor is there any sound with any dtb's

 

I checked the launch on the Tronsmart Vega S95 Telos (s905). Everything works. BT, wired network and sound. After adding these files to the directory "/lib/firmware/brcm" , Wifi began to work.

 

https://yadi.sk/d/si381PghmHbRsQ

 

On Khadas VIM1 (s905x) with the correct dtb (use default to image)  also all works. BT Wi-Fi wired network audio.

 

 

Checked x96mini (s905w) 2\16. Used dtb p281 from the image. Everything starts normally and works with USB flash drives. Works wired network and sound. BT and WiFi chip ssw6051 will not work (the manufacturer has not provided the driver and disappeared).

[jeanrhum]

Tested last 5.77 aml-s912 on an Excelvan EX-T2 using q201 dtb:

~$ uname -a
Linux aml 5.0.2-aml-s912 #5.77 SMP PREEMPT Mon Mar 18 14:19:43 MSK 2019 aarch64 GNU/Linux

armbianmonitor -u output: http://ix.io/1E8H

 

There is no sd slot on this tv box, so I use an usb stick. Integrated wifi is working well. The desktop bit laggy, but it is expected since there is no HW acceleration.

 

Edit: Install-2018.sh works well too.

[balbes150]

48 minutes ago, jeanrhum said:

Tested last 5.77 aml-s912 on an Excelvan EX-T2 using q201 dtb: 

 

Are you sure you are using dtb q201 ? Judging by this infa, you use dtb from Khadas VIM2.

 

[ 11.798739] brcmfmac mmc2:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.khadas,vim2.txt failed with error -2

[jeanrhum]

You are right, I just wanted to report back that in fact old uboot (so uEnv.ini config file) may have been used when I started from usb, since now the cpu temp is not reported well when I look at htop.

I will update the extlinux.conf file to use the vim2 dtb.

 

Moreover I tried to use USBburning tool to check if I can restore an android image and the box is not visible. I also tried to boot again from my usb stick, but it doesn't work anymore, since I'm always booting to emmc.

[arcps]

To anyone who needs a Linux 4.20/5.0 8189es driver, I successfully compiled one from here https://github.com/jwrdegoede/rtl8189ES_linux/  

 

I installed the headers .deb but needed some files from source kernel,  so cloned the https://github.com/150balbes/Amlogic_s905-kernel/ and copied the scripts/mod folder to the /lib/modules/<kernel version>/build/

 

Then, on the rtl8189es_linux folder

 

make ARCH=arm64  KSRC=/lib/modules/<kernel version>/build/ CONFIG_POWER_SAVING=n

 

To install, for some reason sudo make install not worked, so I typed:

 

sudo install -p -m 644 8189es.ko  /lib/modules/<kernel version>/kernel/drivers/net/wireless/

sudo /sbin/depmod -a

sudo modprobe 8189es

 

And voilà, wifi working

Edited March 22, 2019 by arcps

[balbes150]

12 hours ago, jeanrhum said:

Moreover I tried to use USBburning tool to check if I can restore an android image and the box is not visible. I also tried to boot again from my usb stick, but it doesn't work anymore, since I'm always booting to emmc.

It should be. u-boot-2018 does not support USB Burn Tool (I warned all about this). Also, u-boot-2018 can not run external systems from USB media, you need to use only the SD card. You should only write u-boot-2018 to eMMC when you know exactly what you need it for. For other cases, you need to use the installation with the preservation of the standard u-boot-2015 (use the installation script install.sh).

 

To make USB Burn Tool work you need to erase u-boot-2018 in eMMC. For example to run the command "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=4M" (Replace X with the number of your eMMC).

 

[jeanrhum]

5 minutes ago, balbes150 said:

To make USB Burn Tool work you need to erase u-boot-2018 in eMMC. For example to run the command "dd if=/dev/zero of=/dev/mmcblkX bs=1M count=4M" (Replace X with the number of your eMMC).

Thanks, I will try this. It is sometime difficult to find the posts where the information is given. The topic becomes long and even if search utility helps, it sometimes difficult to find the relevant post.

 

Can I also use the install.sh from my usb key to install uboot 2015?

[balbes150]

2 hours ago, jeanrhum said:

Thanks, I will try this. It is sometime difficult to find the posts where the information is given. The topic becomes long and even if search utility helps, it sometimes difficult to find the relevant post.

 

Can I also use the install.sh from my usb key to install uboot 2015?

The script works with any media.

[Linton]

--snip--

Edited March 26, 2019 by purplepumkin
Problem solved

[amirul]

My temperature values are screwed up

amirul@aml:~$ armbianmonitor -m
Running unprivileged. CPU frequency will not be displayed.
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU

10:27:38:   ---      0.09   3%   1%   1%   0%   0%   0% 4294967295.0°C
10:27:43:   ---      0.08   0%   0%   0%   0%   0%   0% 4294967295.0°C

Running Armbian_5.77_Aml-s905_Ubuntu_bionic_default_5.0.2_20190318 with meson-gxbb-p201.dtb

Anyone have any pointers to fix this?

[balbes150]

On 3/23/2019 at 3:30 AM, purplepumkin said:

Put CoreElec on internal

Did I understand correctly that you are trying to run Armbian with Сoreelec installed in eMMC ?

[Linton]

Removed long winded post...

[balbes150]

16 hours ago, purplepumkin said:

3.x and 4.x are so much more stable I feel bit sad you removed those options from the ./compile.sh menu. All options lead to a 5.x kernel now. It's fun for those who want to run cutting edge versions but for server usage its far from ideal. The first option always gave me rock solid images. I think said something like 3.x/4.x kernels that manufacture uses in the description.

CE can not work with universal multi-boot, so it breaks down the work of all other systems. To build a system with kernel 4, you can roll back to the previous commits in Build-Armbian and get a system with kernel 4 when you run the build.

[Linton]

Ok, thanks.

[AndrewDB]

1 hour ago, purplepumkin said:

 

I'm using the last commit with 4.x to compile and it works good yes. I dunno how CE is relevant though, I only run Armbian on these boards and just tried CE out to see if the reboot issue was hardware or software, seemed like a good test. I could reboot many times in CE without a problem just like Armbian on 3.x and 4.x kernels, only with 5.x after some reboots it doesn't come back, it seems to hang right before the led normally changed colour when rebooting. I only posted in here to see if the problem could be solved or maybe others ran into it and also share my findings/testing to help with development. Thought this was the right place to do so...

In my experience 5.x on Amlogic S9XXX has a few regressions compared to 4.XX, I have posted about one of them in the Linux Amlogic mailing list. I suggest you stick to either 4.19 since it's an LTS (Long Term Support) kernel, or the last 4.XX stable (4.20.17). 3.14.29 is terribly outdated and has various unpatched security issues so it's NOT recommended. 

 

I am personally using kernel 4.19 or 4.20 on all my Amlogic TV boxes, after trying 5.XX on them and experiencing a number of problems.

 

You don't have to rebuild Armbian if you want to use any of Oleg's releases with an older kernel, just keep a copy of a reliable 4.19 or 4.20 kernel around and copy it over any new Armbian image. Or compile your own 4.XX kernel, I have posted about how to do it previously here in this forum. We can all be grateful that Oleg is keeping his S9XXX kernel repository in great shape so it's an excellent source if you want to compile your own Linux kernel. 

 

andrew@m9cmax4k:~/Benchmarking/Linpack/hpl-2.1/bin/Aarch64$ uname -a
Linux m9cmax4k 4.19.7-aml-s9xxx #5.67 SMP PREEMPT Fri Dec 28 10:16:25 MSK 2018 aarch64 aarch64 aarch64 GNU/Linux
andrew@m9cmax4k:~/Benchmarking/Linpack/hpl-2.1/bin/Aarch64$ uptime
09:29:21 up 46 days, 10:07,  1 user,  load average: 0.00, 0.00, 0.00
andrew@m9cmax4k:~/Benchmarking/Linpack/hpl-2.1/bin/Aarch64$
 

[AndrewDB]

22 hours ago, amirul said:

My temperature values are screwed up

amirul@aml:~$ armbianmonitor -m
Running unprivileged. CPU frequency will not be displayed.
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU

10:27:38:   ---      0.09   3%   1%   1%   0%   0%   0% 4294967295.0°C
10:27:43:   ---      0.08   0%   0%   0%   0%   0%   0% 4294967295.0°C

Running Armbian_5.77_Aml-s905_Ubuntu_bionic_default_5.0.2_20190318 with meson-gxbb-p201.dtb

Anyone have any pointers to fix this?

As usual, read the code. Check where armbianmonitor is reading the CPU temperature from. On my TV box below, I checked /etc/armbianmonitor/datasources, there is a link to the kernel sensor reading in /sys

 

andrew@m9cmax4k:~/Benchmarking/Linpack/hpl-2.1/bin/Aarch64$ uname -a
Linux m9cmax4k 4.19.7-aml-s9xxx #5.67 SMP PREEMPT Fri Dec 28 10:16:25 MSK 2018 aarch64 aarch64 aarch64 GNU/Linux
andrew@m9cmax4k:~/Benchmarking/Linpack/hpl-2.1/bin/Aarch64$ uptime
09:29:21 up 46 days, 10:07,  1 user,  load average: 0.00, 0.00, 0.00
andrew@m9cmax4k:~/Benchmarking/Linpack/hpl-2.1/bin/Aarch64$ armbianmonitor -m
Running unprivileged. CPU frequency will not be displayed.
Stop monitoring using [ctrl]-[c]
Time        CPU    load %cpu %sys %usr %nice %io %irq   CPU

09:31:34:   ---      0.05   0%   0%   0%   0%   0%   0% 45.0°C
09:31:39:   ---      0.05   0%   0%   0%   0%   0%   0% 45.0°C
09:31:44:   ---      0.04   0%   0%   0%   0%   0%   0% 45.0°C
09:31:49:   ---      0.04   1%   0%   0%   0%   0%   0% 45.0°C
09:31:54:   ---      0.12   0%   0%   0%   0%   0%   0% 45.0°C

 

[andybuks]

Hello!

I have a t95zMax 3/32 tv box.

5.77 works from SD card, but does not see internal EMMC

5.73 works from internal memory, but usually hangs after rebooting

 

Need help, thanks

[amirul]

root@aml:~# uname -a
Linux aml 5.0.2-aml-s905 #5.77 SMP PREEMPT Mon Mar 18 12:59:10 MSK 2019 aarch64 aarch64 aarch64 GNU/Linux
root@aml:~# cpufreq-info
...
analyzing CPU 3:
  driver: scpi-cpufreq
  CPUs which run at the same hardware frequency: 0 1 2 3
  CPUs which need to have their frequency coordinated by software: 0 1 2 3
  maximum transition latency: 200 us.
  hardware limits: 100.0 MHz - 2.02 GHz
  available frequency steps: 100.0 MHz, 250 MHz, 500 MHz, 1000 MHz, 1.30 GHz, 1.54 GHz, 1.75 GHz, 2.02 GHz
  available cpufreq governors: conservative, userspace, powersave, ondemand, performance, schedutil
  current policy: frequency should be within 500 MHz and 2.01 GHz.
                  The governor "ondemand" may decide which speed to use
                  within this range.
  current CPU frequency is 1.75 GHz (asserted by call to hardware).
  cpufreq stats: 100.0 MHz:0.04%, 250 MHz:0.06%, 500 MHz:72.89%, 1000 MHz:0.01%, 1.30 GHz:0.01%, 1.54 GHz:0.00%, 1.75 GHz:26.97%, 2.02 GHz:0.03%  (2062)

Is it my faulty memory or are we getting cpu speeds 1.75GHz and 2.02GHz now?

sysbench show no significant change between 1.5, 1.75 & 2.02GHz. Must be fake reporting then