Igor

Administrators
  • Content Count

    10233
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Calendar

Everything posted by Igor

  1. No need to provide anything. It is most likely a classical problem with SPI bootloader which workaround is written on the download pages. I highly suspect this note: “How to solve boot troubles with SPI enabled boards? 1 (variant 2)” was not noticed here https://www.armbian.com/rock-pi-4/
  2. All images are tested. Have you followed instructions on the download pages?
  3. Main reasons for shutting the bord down are two: - unstable power (mUSB is unstable by default) - reaching critical temperature This is my test Tinkerboard - its currently up for 3 days since last reboot and during this uptime it was exposed to many brutality Tinkerboard Linux 5.4.38-rockchip U-Boot 2018.11-armbian nightly [ 22:59:18 - 30.204 Uptime: 3 days 2:48 ]
  4. I assume that modules list above is with a connected camera and on most recent Armbian beta kernel? armbian-config -> system -> nightly builds Did you update packages after you started?
  5. In short: Ubuntu is a commercial distribution where BS is always in the package Kernel - the most expensive part of the (Linux) distribution and the reason you can use your board, Linux, is maintained by Armbian. You are using Armbian Linux with Debian (or Ubuntu if you prefer) package base. It could be Arch, Fedora or whatever ... but most authors Debian is closer.
  6. From software department perspective, we hit the wall. Broken hardware?
  7. ___ ____ _ ____ ____ / _ \| _ \(_) | _ \ / ___| _ | | | | |_) | | | |_) | | _| |_ | |_| | __/| | | __/| |___ |_ _| \___/|_| |_| |_| \____| |_| Welcome to Armbian buster with Linux 5.4.37-sunxi No end-user support: untested automated build System load: 0.00 0.00 0.00 Up time: 1 day 21:34 Memory usage: 9 % of 999MB IP: 10.0.30.118 CPU temp: 46°C Usage of /: 17% of 7.1 This is how idle should look like.
  8. Each kernel has its config packed inside deb file. Its location is /boot /config-* ... if you will do comparisons. Nightly kernels and images are regularly purged. We don't keep a lot of historical versions. Not at this moment.
  9. No. I am referring to your initial post. For idle, that's not normal. Even without heatsink it should not go that high. Can you measure the temp? Is CPU that hot that you can't hold your finger on?
  10. Well, you only need a larger heat sink. IMHO there is no need for a fan in that case. I am occasionally using 120x120 12V fan attached to 5V to cool down my sbc in testing. You can barely hear it. Chromium is using it.
  11. One test board from this topic will be installed at this location and another at my desk and elsewhere. We will try to join them. After test boards come, some more coding has to be done. Also to have better overview over the test process. Currenlty test results looks like this: https://dl.armbian.com/_test-reports/2020-05-03_15.57.22.html Its still more or less a data collection without any proper analysis ...
  12. Igor

    Odroid C4

    You should only power cycle it Reboot works properly on eMMC, while on SD card it simply doesn't come back. But ethernet issues are quite often for me https://armbian.atlassian.net/browse/AR-231 - I spent a day trying to fix them, but nothing. Can't really afford working more on this right now. We have a release coming up and C4 is will anyway not be ready by then.
  13. No, we don't have all older matched kernels and headers. We started to pay attention recently, after headers and DKMS process were improved ... and we are working on to improve CI processes. In case you have know-how and some time, you are welcome to help. We are drowning in work. https://armbian.atlassian.net/projects/AR/issues/AR-214
  14. Armbian is the hardware interface, "Buster" or "Bionic" are only userland which you choose upon your software need. You need drivers for this card (probably it just need to be enabled in the config). Try nightly images - we recently enable lots of drivers ... Storage mode works because that is very basic and generic feature. Perhaps it is just a power problem - with mUSB powered devices this is the first thing you check - put powered USB hub in between.
  15. Since people already explained you that memory upgrade is no go ... I can suggest you Orangepi 3 with 2Gb memory or better, some RK3399 with 4Gb. Or some Amlogic with 4Gb. You don't need to tweak the system in any way to squeeze out more. Armbian is not Debian in this sense, we did that for you. It was pushed to the limits of the hardware long time ago.
  16. https://linux-sunxi.org/Linux_mainlining_effort#Status_Matrix
  17. It is not your fault and don't need to worry about I am just trying to show you how things looks like from our perspective ... and if somebody else read this after and not waste our time by asking more and more. Forum will only have more unanswered topic.
  18. This is not Opi community. This is Armbian community, welcome. Find your board here https://www.armbian.com/download/, download and install Armbian. In case of troubles, read documentation, read forum ... and if nothing helps, ask a question.
  19. For debugging application you need to contact Raspotify authors and show them logs - we don't know how this software works. We can help you around Armbian. Does this SW needs active sound card? What is your sound hardware? Is it operational? We only look into those logs: armbianmonitor -u aplay -l
  20. With latest boot loader 2020.04 and current 5.4.y kernel works as expected. Reboot, reboots. Lime 2 with 16gb eMMC REV K
  21. Bug ... was fixed for the future https://github.com/armbian/build/commit/bbaddc8aaa2cc3d3ffa6324c4472eab812f84781
  22. apt update and apt upgrade will solve your problems.
  23. Updated images for Odroid C1 Bootlog: http://ix.io/2kqB Credits: https://github.com/armbian/build/pull/1932
  24. Absolutely. You can try to add a test for that, after 7z.