chpasha

  • Posts

    29
  • Joined

  • Last visited

Posts posted by chpasha

  1. On 3/5/2020 at 5:28 PM, balbes150 said:

    Remove the 19.11.5 kernel package ( for example, via Synaptic) and then run the 20.05 kernel installation

    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

  2. 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)

  3. Hello Balbes,

     

    thank you very much for your beautiful builds :thumbup:

    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.

  4. 15 hours ago, gnthibault said:

    In case someone see what is going wrong:

    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

  5. 1 hour ago, lizzacore said:

    Okay now i get this issue back.

    Any idea?

    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

  6. 1 hour ago, gnthibault said:

     I just copy the meson-q200.dtb from dtb directory (the one that starts with amlogic S9xx) to /boot without renaming and without changing acces rights. Is it ok ?

    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

  7. 20 hours ago, gnthibault said:

    Are you sure that you used the version with 4.18 kernel

    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

  8. 48 minutes ago, ramawatar said:

    I use usb burning tool but my box not recognise

    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

  9. I'm experiencing problem installing Armbian 5.59 / 4.18 based on Ubuntu Bionic on my H96 Pro (s912 3/16) using (presumably correct) gxm_q200 dtb from image  - amlogic logo goes away after some time and then appears again in endless loop. Strange thing is that the same 5.59 / 4.18 based on xenial with the same dtb boots just fine. Not a big deal since xenial is also ok for me too

     

     

  10. 13 hours ago, balbes150 said:

    Activate your universal multiboot (using the image of Arabian). Now you use the old multiboot (from the image LE), it can only run images LE.

    that did the job, besides that I noticed that my box seems to boot from usb only on usb-port 1 but I didn't investigate further.

     

    regarding installation to emmc I used older deb files from yandex disc to downgrade and used one of older dtbs - that did help

  11. 4 hours ago, balbes150 said:

    Activate your universal multiboot (using the image of Arabian). Now you use the old multiboot (from the image LE), it can only run images LE.

    thank you, I'll give it a try.

     

    I also have a problem installing the system to the emmc - /dev/boot and /dev/data do not exist (I did flash a fresh android rom to emmc before trying this)

    /usr/sbin/fw_setenv initargs "root=/dev/data rootflags=data=writeback rw console=ttyS0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.repair=yes net.ifnames=0 mac=\${mac}" fails as well with message Cannot parse config file '/etc/fw_env.config': Invalid argument

     

    Can this be a problem with dtb-s for the last 905 ubuntu build with kernel 3.14.79? Installation to the emmc DID work on the previous ubuntu and debian builds with kernel 3.14.29 - so it is not about my box having some exotic emmc structure (actually it is a full clone of vega s95 pro)

  12. Hi there,

    I'm having problems trying to boot ubuntu s905 image on my mxq pro plus 2gb/16Gb/s905 - the box won't boot neither from sd nor from usb, it skips them and boots into Android inspite of multiboot being already applied - Libreelec installation boots without problems from SD on this box. My MX Plus box (1gb/8Gb/S905) doesn't have problems with booting from any of those media sources. I tried this distro and dtb images from it (I tried mxqplus, tronsmart meta and dtb from libreelec) without success. Do I miss something?

  13. 5 hours ago, odoll said:

     

     

    I had another freeze though having downgraded my Cubietruck to v5.35 and I also had a suspicion about tvheadend and downgraded that to 4.3-1067~g68d0bc5~xenial and froze it as well.

    I had a stable 4.2.25. But I come to conclusion that it is a docker, that makes the problems. After downgrading to 5.27 things became better - in spite of huge cpu usage the box didn't freeze completely so I could see what is causing the stress - it was dockerd daemon itself (I tried both latest 18.02 as well as previous 17.12  with same result) - it starts to use cpu power without a reason. After getting rid of it I have no problems anymore - but I had to return to ubuntu 16.04 based image since without being able to use docker some software pieces were missing in debian

  14. Hello guys,

    I've tried to read the topic, but there are too many pages and the older instructions seem to be outdated (at least current s905_autoscript looks very different from those) - is it possible to free reserved memory for the true headless mode in current debian/ubuntu distros? what is suggested steps to achieve this and is the distribution stable if it is done?

  15. 17 hours ago, denox said:

    Thank you for the updated kernel/fix. Unfortunately, it still results in similar behavior for me as well.

    I can confirm this. I experience similar issues with custom build for amlogic 905 based on armbian 5.37 / debian 9 (kernel 3.14.29) - I have pretty clean installation with only few additional software pieces like docker 17.12 (+tvheadend image) , openvpn and transmission-daemon. I tried 5.41 now and got the next freeze after about 8hours of uptime when the box was idle (I stressed it before for about 4-5 hours and it was ok, but after an hour of doing nothing it stopped responding). I'm not sure if it could help - but the most freezes I've got when compiling this docker image - 1 of every 3rd or 4th attempted resulted in box not responding. And it happens on the same operation:

    pip install --no-cache-dir -U \
            gevent \
            psutil \
            requests \
            bencode \
            virtualenv

    I'm testing 5.27 now