56 56
balbes150

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

Recommended Posts

My mx-plus (p200-board) does boot with the 2018-01-16 image.

network+wifi+ Bluetooth works.

Shutdown works only if called before logon (from lightdm). Shutdown from mate hangs. Filesystem seems OK when reboot after hang.

 

Image Form 2017-12-26 works fine.

 

Bitz

Edited by bitz

Share this post


Link to post
Share on other sites
1 hour ago, Inter95 said:

Is it possible to build a ddbr MultiOS_3in1 like the one for Khadas to boxes s905, s905x, s912?

You need to have a number of elements with reference to the model of the TV box, which is going the way 3in1.

1. The source code u-boot version which has the command you want (u-boot must be able to start the any system from partitions of internal drive).

2. Access to source code dtb data.

3. A working version of Android with a built-in mode reboot into the desired system.

4. Real hardware for testing.

Share this post


Link to post
Share on other sites

Hi

I have a problem, when i’m running nand-sata-install on my tv box i got:

 

root@amlogic:~# nand-sata-install
Start copy system for DATA partition.
Formatting DATA partition…
umount: /dev/data: mountpoint not found
The file /dev/data does not exist and no size was specified.
e2fsck 1.43.4 (31-Jan-2017)
e2fsck: No such file or directory while trying to open /dev/data
Possibly non-existent device?
done.
Copying ROOTFS.
mount: special device /dev/data does not exist
Copy BIN

Copy VAR
tar: var/log/syslog: file changed as we read it
tar: var/log/messages: file changed as we read it
tar: var/log/kern.log: file changed as we read it
Copy fstab
umount: /ddbr/install: not mounted

Done copy ROOTFS

Writing new kernel image…
dd: failed to open ‘/dev/boot’: No such file or directory
/dev/boot: No such file or directory
/dev/boot: No such file or directory
/dev/boot: No such file or directory
/dev/boot: No such file or directory
done.
Writing new dtb …
done.
Write env bootargs
Cannot parse config file ‘/etc/fw_env.config’: Invalid argument
Error: environment not initialized

Complete copy OS to eMMC parted DATA

 

 

After that nothing happend i still can boot android installed on eMMC.

Share this post


Link to post
Share on other sites
1 hour ago, bomber4 said:

I use "gxl_p212_2g.dtb" i tried different glx_p212 but u boot stops on "Starting Kernel".

Perhaps your model does not have eMMC memory used an old version of NAND. Need a connected console UART.

Share this post


Link to post
Share on other sites

You TV box not standard partition table, perhaps it uses encryption.

 

Partition table get from SPL is :                                              

        name                        offset              size              flag  

================================================================================

   0: bootloader                         0            400000                  0

   1: reserved                      400000            800000                  0

   2: cache                         c00000          10000000                  2

   3: env                         10c00000            400000                  0

   4: logo                        11000000            300000                  1

   5: encrypt                     11300000            100000                  1

   6: recovery                    11400000           2000000                  1

   7: tee                         13400000            800000                  1

   8: crypt                       13c00000           2000000                  1

   9: misc                        15c00000           2000000                  1

  10: boot                        17c00000           1400000                  1

  11: system                      19000000          60000000                  1

  12: persist                     79000000            800000                  4

  13: panic                       79800000            400000                  4

  14: data                        79c00000         158400000                  4

Share this post


Link to post
Share on other sites

@balbes150

Hello again, after a very long time of inactivity of me.

I'm writing to inform you about this small problem:

No matters what image i tried to use, and most of the dtb's that was used to work in the past for me,

i always had problems with wifi and system misbehavior. in general.

Right now i'm using the dtb from  https://kszaq.libreelec.tv/s905/8.2/device_trees/S905/gxbb_p200_2G_100M.dtb

and all the problems seem to have gone for ever.

My box is MiniM8S (not II or Pro) as always.

I'm writing this message from my MiniM8S with "Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_icewm_20171226.img.xz"

and using the previously mentioned dtb from kszaq and everything is fine.

Thanks for the IceWM images, as i am a great fan of this window manager, and also IceWM makes this boxes fly literally.

The problems with the dtb's coming with your images was:

1) No wifi at all (after "sudo modprobe wifi_dummy" [and before ofcourse])

2) Wifi disconnections or no internet at all, although i have had IP DNS and GATEWAY correctly.

3) Very slow and unresponsive system in general.

4) System hangs after sudo modprobe dhd (only mouse movement and nothing else alive in the system).

So... maybe something is wrong OR missing with the provided dtb's in your images?

Thanks again for all your efforts.

Share this post


Link to post
Share on other sites
2 hours ago, xXx said:

I'm writing this message from my MiniM8S with "Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_icewm_20171226.img.xz"

and using the previously mentioned dtb from kszaq and everything is fine.

Have you tried the latest test image Armbian Mate 20180116 ? I added a large number of new dtb (which are used in LE Kszaq). I have images with this kernel with IceWM\server and so on until they are uploaded to the site, I forward to feedback from users, something to learn how does a new set of dtb files on different machines. I received only one answer in a new way. Describing the problem with shutting down. By the way, I checked this message, the system shuts down, but sometimes it takes up to 10-15 minutes (I have not yet found a dependency, why it happens). I understand that you, like me, are a fan of IceWM ?

 

 

28 minutes ago, manuti said:

Same problem here with MXQ Pro and MXQ Pro +

Have you tried the latest test image Armbian Mate 20180116 ?

Share this post


Link to post
Share on other sites
17 minutes ago, balbes150 said:

I understand that you, like me, are a fan of IceWM ?

Yes, i am :D.

And i'm creating a livecd-only debian "distro" with only a minimal set of applications,

and IceWM as a window manager, for use as a thinclient.

The uploaded cd is x86_64 only at the link below, but fully functional (and good looking also),

and the script can also produce x86_32 images of lenny|squeeze|wheezy|stretch (and x86_64 ofcourse)

with some manual troubleshooting (like missing packages in ancient debian releases).

You can test it from here https://mega.nz/#F!rdFxwKKQ!_9aRWe2rfZaMt7LNQK_R1Q

I'm giving you this link, because i was thinking to do the same with armbian for my MiniM8S box,

but i don't know how to start. The livecd is generated by a script that i am developing lately.

The script needs debian as host system and deboostrap squashfs xorriso and some modifications.

If you try the livecd,  and you like the look and feel of it, i can give you the script (lh-icewm.sh)

to see if you can implement any of it to your images or help me to modify the script so it will be

able to produce an armbian image for flashing to our boxes.

This could become the ultimate IceWM armbian distro of all times :D:D:D.

About your images now:

1) YES... i had the same reboot/shutdown issue (that i forgot to mention) with non-testing images myself,

up to the point i changed the dtb with the kszaq one. After that all issues disappeared.

2) YES... i will try the latest testing images soon, and let you know.

Thanks again.

Share this post


Link to post
Share on other sites
1 hour ago, xXx said:

And i'm creating a livecd-only debian "distro" with only a minimal set of applications,

Oh, we think about the same .... :)

I downloaded your image with icewm, look at VirtualBox.

 

I have been working with Icewm. There is a part of the work.


 

 

 

By the way, for Khadas have a build system Fenix, which can be supplemented with Assembly of IceWM, look at her.

 

https://github.com/150balbes/fenix

 

 

 

Share this post


Link to post
Share on other sites
3 hours ago, balbes150 said:

Have you tried the latest test image Armbian Mate 20180116 ?

 

Yes, I download the zip, checked the hash and install the "Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20180116.img".

I need to open the box to check the Wi-Fi vendor inside these newx MXQ boxes.

Share this post


Link to post
Share on other sites
7 hours ago, balbes150 said:

You TV box not standard partition table, perhaps it uses encryption.

 

Partition table get from SPL is :                                              

        name                        offset              size              flag  

================================================================================

   0: bootloader                         0            400000                  0

   1: reserved                      400000            800000                  0

   2: cache                         c00000          10000000                  2

   3: env                         10c00000            400000                  0

   4: logo                        11000000            300000                  1

   5: encrypt                     11300000            100000                  1

   6: recovery                    11400000           2000000                  1

   7: tee                         13400000            800000                  1

   8: crypt                       13c00000           2000000                  1

   9: misc                        15c00000           2000000                  1

  10: boot                        17c00000           1400000                  1

  11: system                      19000000          60000000                  1

  12: persist                     79000000            800000                  4

  13: panic                       79800000            400000                  4

  14: data                        79c00000         158400000                  4

There isn't any way to bypass this encryption?

Share this post


Link to post
Share on other sites

@balbes150

INFO:

I made a USB thumb with Armbian_5.37_S9xxx_Ubuntu_xenial_3.14.29_mate_20180116.img.

I copied and renamed /boot/dtb/gxbb_p200_2G_100M as /boot/dtb.img (looks the same as kszaq to me and worked ok).

I booted the USB (NOTE: Only the back USB port can boot in this BOX [MiniM8S] the one that is between DC/IN and HDMI).

Everything worked at first boot (changing pass etc).

I edited /etc/modules (i put wifi_dummy in there) and instructed a reboot from mate menu.

Reboot hanged for more than 3 minutes so i did a POWER CYCLE (forced reboot).

Next boot was OK, i did wifi connection, all OK.

Sound via HDMI OK.

Bluetooth NO ADAPTER (as always with this box).

Video playback windowed with mpv ACCEPTABLE.

Video playback fullscreen with mpv NOT GOOD but no HANGUPS or anything, just UNWATCHABLE.

I did:

sudo apt-get update (ALL OK)

sudo apt-get upgrade (i had to do apt-get -f install but after that OK)

sudo apt-get upgrade (ALL OK)

sudo apt-get dist-upgrade (NO HELD PACKAGES = ALL OK)

sudo apt-get install dmz-cursor-theme (ALL OK)

sudo apt-get clean (ALL OK)

logout and login again via mate menu (ALL OK)

sudo armbian-config (did some configurations as tzdata and keyboard-configuration OK -- but motd messages was NOT OK -- infinite LOOP and NO CHANGES SAVED ever)

logout and login again (ALL OK)

sudo armbian-config (change hosname) (ALL OK)

logout and login again (ALL OK)

shutdown via mate menus (took more than 4 minutes, i lost focus at some point but finally the box did shutdown) (NOT OK)

The messages that kept shutdown back was systemd messages about "SAVING AUDIO" and "C3 STATE"

Right now i have these RED MESSAGES in sudo dmesg --ctime | egrep -i '(error|fail|abort|timeout)':

Spoiler

[Mon Jan 22 20:54:32 2018] Error: Driver 'ICPlus IP175C' is already registered, aborting...
[Mon Jan 22 20:54:32 2018] libphy: ICPlus IP175C: Error -16 in registering driver
[Mon Jan 22 20:54:32 2018] Error: Driver 'AMLOGIC internal phy' is already registered, aborting...
[Mon Jan 22 20:54:32 2018] libphy: AMLOGIC internal phy: Error -16 in registering driver
[Mon Jan 22 20:54:32 2018] Error: Driver 'RTL8211F Gigabit Ethernet' is already registered, aborting...
[Mon Jan 22 20:54:32 2018] libphy: RTL8211F Gigabit Ethernet: Error -16 in registering driver
[Mon Jan 22 20:54:32 2018] mmc driver version: 1.07, 2015-01-21: fix a bug in tuning which caused eMMC data CRC error
[Mon Jan 22 20:54:33 2018] DI-di_probe: get flag_cma error.
[Mon Jan 22 20:54:35 2018] hdmitx: ddc rd8b error 0x54 0x01
[Mon Jan 22 20:54:35 2018] hdmitx: ddc rd8b error 0x54 0x01
[Mon Jan 22 20:54:35 2018] hdmitx: ddc w1b error 0x54 0x20 0x00
[Mon Jan 22 20:54:35 2018] hdmitx: ddc w1b error 0x54 0x20 0x00
[Mon Jan 22 20:54:35 2018] hdmitx: ddc rd8b error 0x54 0x21
[Mon Jan 22 20:55:01 2018] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa1ff2800,virqc:3fff
[Mon Jan 22 20:55:01 2018] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa1ff2800,virqc:3fff
[Mon Jan 22 20:55:01 2018] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa1ff2800,virqc:3fff
[Mon Jan 22 20:55:01 2018] systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
[Mon Jan 22 20:55:01 2018] systemd[1]: Failed to start Load Kernel Modules.
[Mon Jan 22 20:55:01 2018] systemd[1]: systemd-modules-load.service: Unit entered failed state.
[Mon Jan 22 20:55:01 2018] systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
[Mon Jan 22 20:55:03 2018] EXT4-fs (sda2): re-mounted. Opts: commit=600,errors=remount-ro
[Mon Jan 22 20:55:04 2018] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa1ff2800,virqc:3fff
[Mon Jan 22 20:55:04 2018] [aml_sd_emmc_irq] sdio: resp_timeout,vstat:0xa1ff2800,virqc:3fff
[Mon Jan 22 20:55:05 2018] hdmitx: ddc rd8b error 0x54 0x01
[Mon Jan 22 20:55:05 2018] hdmitx: ddc rd8b error 0x54 0x01
[Mon Jan 22 20:55:05 2018] hdmitx: ddc w1b error 0x54 0x20 0x00
[Mon Jan 22 20:55:05 2018] hdmitx: ddc w1b error 0x54 0x20 0x00
[Mon Jan 22 20:55:05 2018] hdmitx: ddc rd8b error 0x54 0x21
[Mon Jan 22 20:55:18 2018] Bluetooth: hci0 command 0x1003 tx timeout
[Mon Jan 22 20:55:20 2018] Bluetooth: hci0 command 0x1001 tx timeout
[Mon Jan 22 20:55:22 2018] Bluetooth: hci0 command 0x1009 tx timeout
[Mon Jan 22 20:55:28 2018] Bluetooth: hci0 command 0x1003 tx timeout
[Mon Jan 22 20:55:30 2018] Bluetooth: Frame Reassembly Failed
[Mon Jan 22 20:55:30 2018] Bluetooth: Frame Reassembly Failed
[Mon Jan 22 20:55:30 2018] Bluetooth: hci0 command 0x1001 tx timeout
[Mon Jan 22 20:55:32 2018] Bluetooth: hci0 command 0x1009 tx timeout

Now the box is back again and will remain UP for some more time.

The image in the USB will be kept for 1-2 days in case you want any more info from me and my MiniM8S box.

That's about all.

 

 

Share this post


Link to post
Share on other sites

I forgot to mention 3 things about my previous post with IceWM livecd:

1) The live cd has the following users:passwords

user:user

root:root

2) No drivers for virtualbox etc are included, so virtualbox etc will be sluggish with this livecd.

Booting in a real system via a fast USB thumb should be lightning fast.

3) The dpkg database is deleted before squashfs-ing (to save space) so...

in order to install any software via apt-get will need an apt-get update first.

################################ IDEA ####################################

i'll start scratching my head about the idea of making a pure/light/fast/goodlooking

image of armbian stretch with IceWM for my box (and maybe others if that goes well)

in the next days. The idea is to start using debootstrap, and then create an image

from the bootstrapped directory (only time will tell if this is even possible).

################################ IDEA ####################################

Share this post


Link to post
Share on other sites

Hi I have a nexbox a95x and i cannot get anything to boot, it comes up  with nexbox a95x and just hangs i've tried loads of dtb.img files fetching them from the dtb folder and renaming them to dtb.img  I've taken to running a kitchen timer so i know when its been stuck at that logo for 10 minutes.

 

can anyone advise me please.  

Share this post


Link to post
Share on other sites
16 hours ago, bomber4 said:

There isn't any way to bypass this encryption?

To replace the firmware or try to add encryption support to kernel and system (but not the fact that it will help to use an encrypted system).

 

13 hours ago, xXx said:

Now the box is back again and will remain UP for some more time.

The image in the USB will be kept for 1-2 days in case you want any more info from me and my MiniM8S box.

That's about all.

Thank you for the test, I got some info.

 

12 hours ago, xXx said:

I forgot to mention 3 things about my previous post with IceWM livecd:

1) The live cd has the following users:passwords

user:user

root:root

2) No drivers for virtualbox etc are included, so virtualbox etc will be sluggish with this livecd.

Booting in a real system via a fast USB thumb should be lightning fast.

3) The dpkg database is deleted before squashfs-ing (to save space) so...

in order to install any software via apt-get will need an apt-get update first.

################################ IDEA ####################################

i'll start scratching my head about the idea of making a pure/light/fast/goodlooking

image of armbian stretch with IceWM for my box (and maybe others if that goes well)

in the next days. The idea is to start using debootstrap, and then create an image

from the bootstrapped directory (only time will tell if this is even possible).

################################ IDEA ####################################

There are options on how to make a image for all tests.  Write system on SD card or USB flash drive 4-8 GB, perform all necessary settings and adding in a real system on your TV box. Remove from the system unnecessary files, and personal settings. Repack the rootfs and boot received in the archives. Zero media (dd if=/dev/zero of=/dev/sda). Create a clean file system\partitions (BOOT and ROOTFS) on the media. Unzip archives and copy files to the media. Copy the image from media using dd. This is the image that other users can easily record on media to use. To create an image with clean sections, instead of real media, you can use created on PC image file onto your mounted via loop. I would be interested to get your version of the image with IceWM for the test (even in a plain tar archive of a rootfs).

 

8 hours ago, John Ewen-Jones said:

Hi I have a nexbox a95x and i cannot get anything to boot, it comes up  with nexbox a95x and just hangs i've tried loads of dtb.img files fetching them from the dtb folder and renaming them to dtb.img  I've taken to running a kitchen timer so i know when its been stuck at that logo for 10 minutes.

 

can anyone advise me please.  

You may not exactly define the type of processor s905 or s905x or s905w. Try all the options dtb.

Share this post


Link to post
Share on other sites
Quote

You know how  can add new version and idesk idesk-set in a network repository Debian ?

If you are talking about official repositories, the sources has to be send to package maintainers, audited and approved and if all goes well, it will be added to official repositories at some point.

If you are talking for you own repository,  there is a method: dpkg-scanpackages packagedir | gzip > packagedir/Packages.gz for local directory, but this can be a network directory too (apache,nginx,lighttpd etc).

and supplement your sources.list with the url (or file://packagedir in case of local offline repo).

By the way... the debootsrap method works fine, and the project will be much easier than i thought :D:D:D

I already have a minimal USB thumb with only a base debian stretch system that is 353MB (this cannot be the final projec, but i think will fit in 1GB USB/SD).

Spoiler

DSC_0000072.jpg.84fcc77c1a081ca3bb6a8244d972202f.jpg

Sorry for the BAD picture... my main phone got FRP locked (and has a bug that is not able to unlock itself although i have google accounts and passwords) and completely non-functional :( .

I will soon have something to show, and an automated script at a bit later point.

Share this post


Link to post
Share on other sites

@balbes150

Hi again.

I manage to have everything working in my bootstrapped USB ROOTFS except:

Video resolution shows only part of the image.

xorg log says 1920x1080 virtual size

glxgears gives ~250.000 FPS

glxinfo says "direct rendering yes"

Any tips on how to solve this, or what am i doing wrong?

All packages i have installed came from debian stretch arm64 official repositories (no backports though),

and some packages from your debs in yandex deb directory (kernel and firmwares).

No packages at all from armbian repos are installed (maybe i'm missing something from there?)

If this resolution problem gets solved i'll start tweaking IceWM to the last detail,

and then i'll start creating an auto-build script according to the notes i have taken so far.

Thanks.

Share this post


Link to post
Share on other sites
8 hours ago, xXx said:

I manage to have everything working in my bootstrapped USB ROOTFS except:

Video resolution shows only part of the image.

xorg log says 1920x1080 virtual size

glxgears gives ~250.000 FPS

glxinfo says "direct rendering yes"

Any tips on how to solve this, or what am i doing wrong?

All packages i have installed came from debian stretch arm64 official repositories (no backports though),

and some packages from your debs in yandex deb directory (kernel and firmwares).

No packages at all from armbian repos are installed (maybe i'm missing something from there?)

If this resolution problem gets solved i'll start tweaking IceWM to the last detail,

and then i'll start creating an auto-build script according to the notes i have taken so far.

Package fbset installed ? What program watch the video ? Activation of the monitor (script /boot/hdmi.sh) running ?

Share this post


Link to post
Share on other sites

@balbes150

Hello!

If i type in my terminal:

dpkg -l | grep aml

i get:

aml-amremote-905                     5.37                                       arm64        IR amremote S905
aml-kodi-905                         5.37                                       arm64        aml-kodi-905
aml-mali-905                         5.37                                       arm64        lib mali S905
firmware-aml                         5.37                                       arm64        Linux firmware-aml
linux-dtb-amlogics905x               5.37                                       arm64        Linux DTB, version 3.14.29
linux-image-amlogics905x             5.37                                       arm64        Linux kernel, version 3.14.29
linux-u-boot-amlogic-s905x-default   5.37                                       arm64        Uboot loader 2015.01
linux-xenial-root-amlogic-s905x      5.37                                       arm64        Armbian tweaks for xenial on amlogic-s905x (default branch)

but in yandex drive i find only 5.27 5.34 and next.

Is this a typo in yandex disk?

If not, where can i find these 5.37 versioned packages?

Thanks.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
56 56