I notice that Amlogic Linux-4.9 doesn’t comes to support MALI-GPU yet, did you build buildroot with MALI supporting?
No, not yet without mali. By the way, I’m not well versed in the peculiarities of the framebuffer on Amlogic, can you tell me why the image is cropped. I have a feeling that there is not enough memory to display the entire page. Because if you use the resolution in monitor settings, more (1080 instead of 720), the picture is cropped more.
By the way, I gathered another option with the latest kernel (4.10.8). System start, here the log run.
871 bytes read in 32 ms (26.4 KiB/s)
Executing script at 01020000
4121758 bytes read in 2161 ms (1.8 MiB/s)
14883328 bytes read in 7707 ms (1.8 MiB/s)
25872 bytes read in 43 ms (586.9 KiB/s)
Loading init Ramdisk from Legacy Image at 13000000 …
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 4121694 Bytes = 3.9 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum … OK
load dtb from 0x1000000 …
Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x1000000
Loading Ramdisk to 73acb000, end 73eb945e … OK
Loading Device Tree to 000000001fff6000, end 000000001ffff50f … OK
fdt_instaboot: no instaboot image
Starting kernel …
uboot time: 19287078 us
domain-0 init dvfs: 4
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.10.8-g3fdae70-dirty (root@user-VirtualBox) (gcc version 4.9.4 20151028 (prerelease) (Linaro GCC 4.9-2016.02) ) #3 SMP PREEMPT Sat Apr 1 08:46:29 MSK 2017
[ 0.000000] Boot CPU: AArch64 Processor [410fd034]
[ 0.000000] efi: Getting EFI parameters from FDT:
[ 0.000000] efi: UEFI not found.
System runs, but still gets these messages.
By the way, the console is a standard UART is working and you can see the whole process.
[ 2.594096] l2tp_ip6: L2TP IP encapsulation support for IPv6 (L2TPv3)
[ 2.600520] NET: Registered protocol family 35
[ 2.604929] Key type dns_resolver registered
[ 2.619582] ALSA device list:
[ 2.619622] No soundcards found.
[ 2.620881] Freeing unused kernel memory: 960K
[ 2.668783] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 2.670766] random: systemd-udevd: uninitialized urandom read (16 bytes read)
[ 2.672841] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.672999] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.674555] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.674831] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.675112] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.675433] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.675941] random: udevadm: uninitialized urandom read (16 bytes read)
[ 2.676267] random: udevadm: uninitialized urandom read (16 bytes read)
[ 4.490439] random: fast init done
[ 113.823831] random: crng init done
Test versions images (20170401) server and mate kernel 4.10.8. When run from SD card the system starts up and allows you to log in through the console UART. Network and USB does not work yet. Error with the eMMC. Note that these images are for experienced users only, if you would be willing to help with debugging and testing.
kernel 4.11.1 v 20170407
Update test images kernel 4.11.0 (20170412). They have added modules for WiFi networks and many other elements. An important feature of primary configuration is possible only through the SSH connection. Network support is based on modules, so it is important when building your kernel to assure that the name of the directory with the modules , the name of the kernel.
For initial setup through the console UART (for connectivity with root user), you need to add to the file /etc/securetty line description of the interface ttyAML0.
Did you compile 4.11 from official mainline linux?
I used the branch 4.12\integ
Does anyone using this image have a stable ethernet connection?
I’m experiencing strange network timeouts/hangs after a while without any further notification.
A corrected version of the images 20170413. The only difference is that you can perform the initial configuration via the console UART (fixed authorization root user through the console UART).
v 20170421 (default kernel 3.14.29)
To enable BT. You need to perform two steps.
- Add to /etc/modules to list the module
- Add to the end of the initialization script (/boot/amlogics905x_init.sh) string
su -c ‘hciattach /dev/ttyS1 any’
After a reboot should turn on BT.
Information taken from this instruction The remaining steps in this manual you do NOT need to, everything you need is already in all desktop images Armbian.
Added test images Armbian (TEST 20170519) kernel 4.9.26 which employs USB.
thank you for that. i tried to run it, but on one vim pro with the latest ubuntu mate of khadas on emmc i only can run the 3.14 kernel with this 4.9.26 kernel on the sd-card. on the other vim pro with the newest android it stucks on the vim-logo.
could you please give me any advice?
You need to use a dtb file gxl_p212_2g.dtb for 4.9.26 (copy it to the root of the FAT partition and rename to “dtb.img”). By the way, for the image in the 4.11 need to use a dtb file from nexbox (meson-gxl-s905x-nexbox-a95x.dtb better support for all elements S905X).
thank you, will try it soon as possible!
thank you balbes150, it works. strange, that on one vim it boots in the old kernel on the other vim in the 4.9.-kernel. seems it depends on the intern bootloader.
but there is no sound and no wifi and the moduls for my dvbsky s960ci are not built in. i am not very in touch with linux so i have to wait for the next builds but anyway thank you very much for your work!
I saw this topic today, don’t know if it works, someone with more knowledge can check this.
It looks a little complicated for me, i have never compiled anything, but i would like to learn.