chpasha

thank you, balbes150 . I was able to solve the problem by creating the image file (/boot/vmlinuz-5.5.0-rc6-arm-64) that installation was missing and renaming dtb folder which installation wanted to backup but could not. After that the kernel installed just fine and the box rebooted successfully with a new one

and with remove you mean "apt remove linux-image-current-arm-64" and then install the package again so it doesn't do "update"-routines but only fresh-install stuff, right?

Hi balbes150, I have your Ubuntu 18.04 build with 5.5.0-rc6-arm-64 kernel. I'm getting linux-image-current-arm-64 suggested for upgrade via apt which fails with following error Preparing to unpack .../linux-image-current-arm-64_20.05.0_arm64.deb ... Unpacking linux-image-current-arm-64 (20.05.0) over (19.11.5) ... dpkg: error processing archive /var/cache/apt/archives/linux-image-current-arm-64_20.05.0_arm64.deb (--unpack): unable to make backup link of './boot/dtb/allwinner/sun50i-a64-amarula-relic.dtb' before installing new version: Operation not permitted dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) mv: cannot stat '/boot/vmlinuz-5.5.0-rc6-arm-64': No such file or directory Errors were encountered while processing: /var/cache/apt/archives/linux-image-current-arm-64_20.05.0_arm64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) I do understand what the error says (/boot/vmlinuz-5.5.0-rc6-arm-64 is really absent in my /boot). The question is - is this some bug in proposed kernel version or is it just not compatible with my build and I should not try to install it at all)

what do you mean with "network repository"? your new builds on yandex disc or your Build-Armbian repo on github?

Hello Balbes, thank you very much for your beautiful builds I have one question: I have some older Ubuntu 18.04 build with 5.1.0-aml-s905 kernel and I want to compile media_build drivers to apply a patch for my dvb-card which works only partially (dvb-s works, dvb-s2 not, seems to be a common problem for dvb-adapters of this type). As far as I understand, I need a kernel source (or kernel headers) to be able to compile. Where I can get them for my kernel version (or do some other headers/source will do for compilation?). Unfortunately I don't know much about linux tinkering - I can follow instructions but I'm not able to overcome the unexpected problems and don't really understand what do I do mostly. What I did try - I have installed kernel-package and linux-source packages (which were 4.15.0 - but I have 5.1.0 kernel and need same source, right?) and run make oldconfig && make prepare. After that I run build inside media_build and of course the compilation failed, it can't find time.h, features.h etc. inspite of the fact that they are present in /usr/include and build_essentials (and all other prerequisites) are installed It would be great if you could give me a couple of tips how to compile media_build in your distros.

you can try . 3.14 with /root/install.sh command, 4.18 with 1. Execute script “/boot/create-mbr-linux.sh” 2. Execute script “/root/install.sh” and see if that works

according to balbes150 who creates those beautiful images, the installation to emmc on the kernel 4.xx looks like this: 1. Execute script “/boot/create-mbr-linux.sh” 2. install Armbian on eMMC execute script “/root/install.sh”. I did this and it worked just fine

install something like stress-ng and check if all 4 cores are working for instance with htop - or just run htop and wait, usually the load is distributed among all cores randomly even if system is idle - if they do work, who cares what system information is showing P. S. or just save your time - you do have 4 cores. I just looked at my s912 that has 8 cores and armbian shows the load for only 3 of them after login

how do you know, that you have only 3? what the command lscpu shows?

it is s905x, it should have gxl and/or p212 in name and 2gb as ram amount if there multiple dtb files for gxl_p212

Oh no pal, of course it is not ok. You should always rename it to dtb.img - that explains why 3.14 worked. It just took dtb from android on emmc and it did work because android on this box has same 3.14 kernel

connect via ethernet, find out the ip on your router - they usually have device list, connect from different machine via ssh and do what you want to do (first registration, wifi setup, etc)

100% because I could not find working dtb for 3.14 . But, now after googling a bit, I think we have different models - I have H96 Pro without + and in spite of same specs it looks slightly different than yours, so maybe that's why. Does yours have 1000M Ethernet or 100M? As far as I know all s912 with 1000M fall under gxm-q200 category, and all 100M should be gxm-q201

that is the hardest of them all - normally you don't need this, but congratulations anyway

many boxes get recognized only when you plug usb cable to specific usb port and some only as soon as you press reset button (it is often hidden in AV-output or just looks like a hole in the case). it is very hard (or almost impossible) to kill s905/s912 so just keep trying