Nofan Tasi

February 27, 2017

Hello, same kind of issue for me with a GT1 2G/16G (A912) with AP6255 wifi/bluetooth device.

Wifi is working by loading cfg80211 and dhd with right firmware and nvram taken from Android, but bluetooth still not working due to brcmfmac not having the BCM43455.

(see https://forum.armbian.com/index.php/topic/2138-armbian-for-amlogic-s912/page-4#entry21842, I have done the same)

I tried to fork and compile the Balbes150 Amlogic Kernel directly on the beelink GT1, and add the drivers, but I have two issues : one with rtl8712 driver (not a real problem at first as the GT1 don't have this device) but also mpi does not ink

Here are the errors :

  LD [M]  lib/mpi/mpi.o
lib/mpi/generic_mpih-mul1.o: In function `mpihelp_add_1':
generic_mpih-mul1.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/generic_mpih-mul1.o: In function `mpihelp_add':
generic_mpih-mul1.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/generic_mpih-mul1.o: In function `mpihelp_sub_1':
generic_mpih-mul1.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/generic_mpih-mul1.o: In function `mpihelp_sub':
generic_mpih-mul1.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/generic_mpih-mul2.o: In function `mpihelp_add_1':
generic_mpih-mul2.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/generic_mpih-mul2.o: In function `mpihelp_add':
generic_mpih-mul2.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/generic_mpih-mul2.o: In function `mpihelp_sub_1':
generic_mpih-mul2.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/generic_mpih-mul2.o: In function `mpihelp_sub':
generic_mpih-mul2.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/generic_mpih-mul3.o: In function `mpihelp_add_1':
generic_mpih-mul3.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/generic_mpih-mul3.o: In function `mpihelp_add':
generic_mpih-mul3.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/generic_mpih-mul3.o: In function `mpihelp_sub_1':
generic_mpih-mul3.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/generic_mpih-mul3.o: In function `mpihelp_sub':
generic_mpih-mul3.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined  here
lib/mpi/generic_mpih-rshift.o: In function `mpihelp_add_1':
generic_mpih-rshift.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/generic_mpih-rshift.o: In function `mpihelp_add':
generic_mpih-rshift.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined   here
lib/mpi/generic_mpih-rshift.o: In function `mpihelp_sub_1':
generic_mpih-rshift.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/generic_mpih-rshift.o: In function `mpihelp_sub':
generic_mpih-rshift.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/generic_mpih-sub1.o: In function `mpihelp_add_1':
generic_mpih-sub1.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/generic_mpih-sub1.o: In function `mpihelp_add':
generic_mpih-sub1.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/generic_mpih-sub1.o: In function `mpihelp_sub_1':
generic_mpih-sub1.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/generic_mpih-sub1.o: In function `mpihelp_sub':
generic_mpih-sub1.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/generic_mpih-add1.o: In function `mpihelp_add_1':
generic_mpih-add1.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/generic_mpih-add1.o: In function `mpihelp_add':
generic_mpih-add1.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/generic_mpih-add1.o: In function `mpihelp_sub_1':
generic_mpih-add1.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/generic_mpih-add1.o: In function `mpihelp_sub':
generic_mpih-add1.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined  here
lib/mpi/mpicoder.o: In function `mpihelp_add_1':
mpicoder.c:(.text+0x580): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpicoder.o: In function `mpihelp_add':
mpicoder.c:(.text+0x5f0): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpicoder.o: In function `mpihelp_sub_1':
mpicoder.c:(.text+0x6e8): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpicoder.o: In function `mpihelp_sub':
mpicoder.c:(.text+0x758): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpi-bit.o: In function `mpihelp_add_1':
mpi-bit.c:(.text+0x60): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpi-bit.o: In function `mpihelp_add':
mpi-bit.c:(.text+0xd0): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpi-bit.o: In function `mpihelp_sub_1':
mpi-bit.c:(.text+0x1c8): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpi-bit.o: In function `mpihelp_sub':
mpi-bit.c:(.text+0x238): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpi-cmp.o: In function `mpihelp_add_1':
mpi-cmp.c:(.text+0x140): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpi-cmp.o: In function `mpihelp_add':
mpi-cmp.c:(.text+0x1b0): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpi-cmp.o: In function `mpihelp_sub_1':
mpi-cmp.c:(.text+0x2a8): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpi-cmp.o: In function `mpihelp_sub':
mpi-cmp.c:(.text+0x318): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpih-cmp.o: In function `mpihelp_add_1':
mpih-cmp.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpih-cmp.o: In function `mpihelp_add':
mpih-cmp.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpih-cmp.o: In function `mpihelp_sub_1':
mpih-cmp.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpih-cmp.o: In function `mpihelp_sub':
mpih-cmp.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpih-div.o: In function `mpihelp_add_1':
mpih-div.c:(.text+0x0): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpih-div.o: In function `mpihelp_add':
mpih-div.c:(.text+0x70): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpih-div.o: In function `mpihelp_sub_1':
mpih-div.c:(.text+0x168): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpih-div.o: In function `mpihelp_sub':
mpih-div.c:(.text+0x1d8): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpih-mul.o: In function `mpihelp_add_1':
mpih-mul.c:(.text+0x518): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpih-mul.o: In function `mpihelp_add':
mpih-mul.c:(.text+0x588): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpih-mul.o: In function `mpihelp_sub_1':
mpih-mul.c:(.text+0x680): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpih-mul.o: In function `mpihelp_sub':
mpih-mul.c:(.text+0x6f0): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpi-pow.o: In function `mpihelp_add_1':
mpi-pow.c:(.text+0x928): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpi-pow.o: In function `mpihelp_add':
mpi-pow.c:(.text+0x998): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpi-pow.o: In function `mpihelp_sub_1':
mpi-pow.c:(.text+0xa90): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpi-pow.o: In function `mpihelp_sub':
mpi-pow.c:(.text+0xb00): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
lib/mpi/mpiutil.o: In function `mpihelp_add_1':
mpiutil.c:(.text+0x60): multiple definition of `mpihelp_add_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x0): first defined here
lib/mpi/mpiutil.o: In function `mpihelp_add':
mpiutil.c:(.text+0xd0): multiple definition of `mpihelp_add'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x70): first defined  here
lib/mpi/mpiutil.o: In function `mpihelp_sub_1':
mpiutil.c:(.text+0x1c8): multiple definition of `mpihelp_sub_1'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x168): first defined here
lib/mpi/mpiutil.o: In function `mpihelp_sub':
mpiutil.c:(.text+0x238): multiple definition of `mpihelp_sub'
lib/mpi/generic_mpih-lshift.o:generic_mpih-lshift.c:(.text+0x1d8): first defined here
scripts/Makefile.build:444: recipe for target 'lib/mpi/mpi.o' failed
make[2]: *** [lib/mpi/mpi.o] Error 1
scripts/Makefile.build:455: recipe for target 'lib/mpi' failed
make[1]: *** [lib/mpi] Error 2
make[1]: *** Waiting for unfinished jobs....
Makefile:854: recipe for target 'lib' failed
make: *** [lib] Error 2
make: *** Waiting for unfinished jobs....

Are you compiling natively or do you cross compile?

Also which compiler suite on which linux distro?

February 13, 2017

Has anybody tried to build and run a mainline Linux kernel on a S912 device?

I do have a Beelink GT1 and would like to use a 4.9.x kernel, no graphics required for my headless server, just ethernet and maybe wifi for later. Currently I was able to boot the GT1 with an Armbian image from @balbes150, but this image has only a 3.14.29 kernel.

Any advice and pointers are really appreciated.

I have not tried any myself but

- http://linux-meson.com/ seems an effort to run latest kernel on amlogic

- https://forums.gentoo.org/viewtopic-t-1058530.html (raspberry pi 3) runs latest kernel

and

- I believe also ubuntu has a generic latest arm64 kernel

But, if any of those sufficiently support GT1 (e.g. network) is to be evaluated or enhanced.

February 13, 2017

Are you sure it's supposed to work? I was using the Armbian_5.24_Vegas95_Ubuntu_xenial_3.14.79_20160125 image for this test and it ends up with no console, as described. Moreover, you didn't include the dtb file for Mini MX III which was present in the github repo last year. I had to use a local copy.

I remember adding following to /boot/vegas95_init.sh before common_display_setup for 3.14.79

# 1920 1080 32 60 shows green
echo 1 > /sys/class/amhdmitx/amhdmitx0/output_rgb

note that this was specific to my 1920 1080 32 60 setup

The screen would now turn from green to black. And, in my case, I also eventually reach console.

Today I mostly run 3.14.29 again.

February 6, 2017

Update images. (20170205) TEST

Changes.

1. Added a lot of kernel modules for peripheral devices (DVB DTV Net Touchscreen etc)

2. Added script dd_backup_x to create a compressed copy of the internal memory (by xXx details about the script on the forum armbian in the subject s905\s905x)

3. Added a script to evaluate the performance of the CPU aml_cpu.sh in the /root directory

4. In the image MATE added a number of packages (screensaver, screenshot, multimedia, utility etc)

Thanks for new .config !

- DVB-T stick recognized

- webcam recognized (psychedelic colors though :-))

minimx-g ~ # lsmod
Module                  Size  Used by
bluetooth             243731  0
6lowpan_iphc            5767  1 bluetooth
nbd                     9769  1
snd_usb_audio         118514  0
snd_hwdep               6845  1 snd_usb_audio
snd_usbmidi_lib        20367  1 snd_usb_audio
snd_rawmidi            18862  1 snd_usbmidi_lib
uvcvideo               70360  0
videobuf2_vmalloc       3059  1 uvcvideo
dvb_usb_dtt200u        24406  1
dvb_usb                17207  1 dvb_usb_dtt200u
mali                  195629  0
hid_apple               5538  0

February 6, 2017

The results of running Your command sequence on s905x and s912 with a new look.

https://yadi.sk/d/K4UJK0UD3CzNbL

By the way, to simplify testing, I created a simple script aml_cpu.sh (of Your data), which can be downloaded here. I decided at the time to add it to the images that would be any non-trained user is able to run on any TV box that would have the information with different devices (the script is located in /root directory in the new images).

aml_cpu.sh

https://yadi.sk/d/jn_hH4GB3CzKtU

c-ray-mt v1.1
Rendering took: 7 seconds (7232 milliseconds)

on Mini MX-G (s905) running gentoo

January 27, 2017

The kernel sources for S905\S905X\S912 are in this GIT. The compliance branch in GIT the names of images and kernel versions.

1. images, the title of which stated "3.14.29" use - collected from branches S905X (universal - for the entire line of chips S9xxx).

2. Images - "3.14.79" - the branch odroid (this thread is only for chips S905)

3. Branch "armbian" - universal plan - for entire line S9xxx in an attempt to collect all positive elements branches (Amlogic + Hardkernel + LE).

Pay attention to Assembly and installation\kernel for TV boxes is specific and different from the usual. I hope Marc (user Nofan Tasi) to share its successful experience build the kernel from source for TV boxes (including their details).

Hi all

Here is recipe I use to natively build S905/ordroid kernel. Note this is on gentoo so initramfs details differ from ubuntu practice.

**** BACKUP /boot /lib/modules /lib/firmware ****


**** choose 4.9 gcc ****
gcc-config aarch64-unknown-linux-gnu-4.9.4
. /etc/profile


export ARCH=arm64
git clone https://github.com/150balbes/Amlogic_s905-kernel.git


cd Amlogic_s905-kernel
git checkout S905X
 or
git checkout odroid


make clean
make mrproper


# S905X
wget https://raw.githubusercontent.com/150balbes/lib/master/config/kernel/linux-amlogics905x-default.config
cp -p linux-amlogics905x-default.config .config


# odroid
cp -p ../config-3.14.79-vegas95 .config


make oldconfig


make -j3 Image
make -j3 modules
make -j3 dtbs


cp -p arch/arm64/boot/dts/*.dtb /boot/dtb/


make modules_install
make install
make firmware_install


# S905X
dracut --kernel-cmdline "root=LABEL=ROOTFS boot=LABEL=BOOT" initramfs-dracut-arm64-3.14.29 3.14.29
cp -p initramfs-dracut-arm64-3.14.29 initrd.img
mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n uinitrd -d initrd.img uInitrd


# odroid
dracut --kernel-cmdline "root=LABEL=ROOTFS boot=LABEL=BOOT" initramfs-dracut-arm64-3.14.79+ 3.14.79+
cp -p initramfs-dracut-arm64-3.14.79+ initrd.img
mkimage -A arm64 -O linux -T ramdisk -C none -a 0 -e 0 -n uinitrd -d initrd.img uInitrd


# install them in /boot


unset ARCH=arm64
**** restore previous gcc ****
gcc-config aarch64-unknown-linux-gnu-6.3.0
. /etc/profile

depends on S905x or odroid your boot could look like

S905x

aml_autoscript      amlogics905x_init.sh  config-3.14.29  dtb.img             s905_autoscript      s905.start          uInitrd
aml_autoscript.zip  boot.bmp              dtb             initrd.img-3.14.29  s905_autoscript.cmd  System.map-3.14.29  zImage

odroid

aml_autoscript        boot.bmp         dtb.img              s905_autoscript.cmd  uInitrd           zImage
aml_autoscript.zip    config-3.14.79+  initrd.img-3.14.79+  s905.start           uInitrd-3.14.79+
amlogics905x_init.sh  dtb              s905_autoscript      System.map-3.14.79+  vmlinuz-3.14.79+

The script files come from Balbes distributions.

January 13, 2017

I've download it, resized the boot partition (too small when installing another kernel), but I don't know how to tell the box to boot on another kernel....

In general one needs to adjust initramfs and remake uInitrd for new kernel and modules.

I managed to do so for kernel built from 150balbes kernel amlogic git (for gentoo). But trying so for kernels I built from other repositories failed. But sure those must also one day succeed.

January 12, 2017

Hi all

With kind help from OP I learned how to make uInitrd u-boot image.

It boots successfully with gentoo kernel I natively built.

I also tried to make one to boot with the LE kernel I cross built. But so far I did not succeed.

But at least I can now do so for natively buillt kernel+modules.

Have a nice day.

January 10, 2017

This post is gentoo centric...

Question near end.

As 'test' I had replaced the files

config-3.14.29

System.map-3.14.29

zImage

in /boot

with the corresponding ones from kszaq LE S905 aarch64 7.0.3.012

Same for /lib/modules and /lib/firmware directories

Note that I had done same, with success, previously to replace

balbes150 distributed kernel with my own natively built kernel+modules

from 150balbes Amlogic_s905-kernel git.

But the gentoo did not boot properly with kszaq kernel. Screen stays

eventually black and no ssh access. So I reverted back to previous

kernel+modules.

Note also that I had built kszaq kernel+modules myself from kszaq

LibreELEC.tv git because, for now, kszaq's own builds are 32bit. And

my own 64bit built LE works fine.

So I thought to compare the both kernel+modules ...

Question: perhaps, to properly boot different kernel+modules, I will

need to update to different uInitrd u-boot image in /boot as well? If

so, how would one make such corresponding uInitrd ?

January 9, 2017

This will probably sound pretty dumb question, but why can't we use the official kernel for arm64 ?

For exemple from here : http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.9.1/

And deb packages from here : https://launchpad.net/ubuntu/xenial/arm64

(Not for kodi, it seems that we need version 17 https://launchpad.net/~team-xbmc/+archive/ubuntu/xbmc-nightly?)

Actually, I don't mind trying ubuntu 4.9.1 kernel and modules, you could do same.

In fact I may also want to try aarch64 7.0.3.012 LE kernel and modules.

For me if I can ssh into the box it is fine, fine for my gentoo experiments ...

Keep you informed

January 1, 2017

boot resolution in s905_autoscript change txt file, then build binary... in my case this problem disappears after login...

How does one build binary s905_autoscript from s905_autoscript txt file ?

such as: I would like to change hardcoded mac address.

thanks!

December 12, 2016

1. you can use the dd command to create a copy and restore.

[...]

all right :-) yes, I typically backup all partitions with dd.

December 12, 2016

[...]

4. I no longer use the USB cable and windows software for firmware (for archiving and full recovery of the contents of the internal memory, including u-boot). I was completely satisfied with the ddBR (NOT TWRP).

[...]

Can you share some details about this ddBR procedure?

Thanks!

November 17, 2016

@jan.pal what does

ls -al /dev/block

output?

November 16, 2016

Interesting device, perhaps not so much RAM though. Is Android effectively 64bit?

If this is a s905 device (I believe it is) you can just try to toothpick/recovery boot from SD or USBstick without danger. Armbian might pick up your internal dtb, and, if not, you might provide yours.

Also, drivers and application support for specific DVB might be missing. You could also try booting 64bit kszaq LE externally in case you search for alternative player as opposed to desktop experience.

November 6, 2016

Last month, I have been Un Brick my TV Box, after i apply the sofware update notification, it make the TV Box only show Blank Black [...]

Thanks for letting us know by confirming software update can brick and hence be fatal.

November 5, 2016

1. With system update you need to be careful. Yet in the current version of the system is not debugged process secure updates. When you upgrade can be rewritten in a standard boot loader u-boot version which is on SD card. After that, the TV box will become a brick. You will need to restore the boot loader.

[...]

Thanks a lot for the serious warning about bricking. I certainly do not want to recommend to do system upgrade, but, myself, I was curious to know if it would work. Oh well, I must have been very lucky, since the box is not bricked. It still boots Android.

November 5, 2016

I could upgrade via console (do-release-upgrade) to yakkety

root@amlogic-s905x:~# cat /etc/armbian-release
# PLEASE DO NOT EDIT THIS FILE
BOARD=amlogic-s905x
BOARD_NAME="Amlogic S905X"
VERSION=5.24
LINUXFAMILY=amlogics905x
BRANCH=default
ARCH=arm64

root@amlogic-s905x:~# lsb_release --all
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.10
Release:        16.10
Codename:       yakkety

So consulted ubuntu arm repositories seem decent at first sight for application support ... I guess what is further needed is to focus on future kernel/modules and X support. I must admit: mvp on a particular h264 file blocked (and needed reboot), but, mp3 files play fine though. I may have broken something on the go :-) I think one can conclude that there is working arm support from ubuntu.

November 4, 2016

Updated desktop images. Removed from the composition package "nodm". The order of use without package nodm. After creating a new user, exit from the root user (exit command, or you can reboot with reboot command) and authorization on behalf of the new user. After login give startx.

Nice work!

To finish sshd setup and make it available, one can do (as root):

# dpkg --configure --pending

The 29 kernel from LE has some more modules, for example, to make some dvb-t sticks work.

October 31, 2016

FYI:

I believe I ran into the ubuntu 2nd boot xfce black screen colors issue. Starting X for root on other virtual terminal did not fix colors.

I have uninstalled xfce and nodm and installed lxqt and openbox. I start X manually for non root user now. Screen colors again are good. Ideally I would want lxqt to start from lightdm, but I cannot get it to work (yet). I think lxqt is a good DE for this box.

update:

I use my box mainly for watching/listening to live dvb-t TV/Rdio with LE, and I strongly consider buying another one for further experimenting. Any suggestions for a good s905 or s905x box? I am very happy with my s905 MiniMX-G, but, I do no longer spot it for sale, so: is the s905x MiniMX II a good box? It has roughly same specs (but only 100Mbps ethernet). I am willing to pay a bit more for a good box with good specs, and developer support.

October 31, 2016

Hi all, sorry for Armbian newbie question...

I am on Armbian_5.24_Amlogic-s905x_Debian_jessie_3.14.29_desktop_20161028 and I am impressed ! Now there is 20161030.

How does one upgrade? Will one automatically upgrade from CLI using appropriate apt-get commands or from GUI using Synaptic Package Manager? And/or does one need to add any additional apt sources lists in etc? Also, is there a command that will tell the armbian version in such detail? /etc/armbian-release mentions VERSION=5.24 but no date.

Thanks

October 31, 2016

guys, i am getting bit crazy.

1) the latest , armbian_debian works great but can not mount internal filesystem

2) armbian_debian with manually installed xfce can not mount internal filesystem

3) armbian_debian_desktop can mount internal file system but ethernet does not work, which is showstopper for me

armbian_debian_desktop has /dev/system and /dev/data which are devices for mounting internal storage

but those devices does not exists on armbian_debian without desktop...

Any hint how to make the /dev/system and /dev/data appear on armbian withou desktop?

Am i missing some drivers?

Thanks for your help...

I guess you can always mount manually, say:

# mkdir /mnt/data /mnt/system
# mount /dev/data /mnt/data
# mount /dev/system /mnt/system
 ...
# umount /mnt/system /mnt/data

Sign In

Forums

Store

Crowdfunding

Applications

Events

Raffles

Community Map

Posts posted by Nofan Tasi

Important Information