• Content Count

  • Joined

  • Last visited

About linda

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hello, I want to monitor the temperature of my Pine64, because I run the pine in an relatively warm environment. Unfortunately, the usual ways do not lead to a reasonable result: I tried the armbianmonitor: "armbianmonitor -m" with this result: Time CPU n/a load %cpu %sys %usr %nice %io %irq CPU 17:08:20: --- 0.00 0% 0% 0% 0% 0% 0% -13552°C 17:08:25: --- 0.00 0% 0% 0% 0% 0% 0% -13673°C and read the file: /sys/devices/virtual/thermal/thermal_zone0/temp: contains the same wrong value -13552 Is there a way to activate the temperature measurement? I am using the following system: ARMBIAN 5.49.180626 nightly Ubuntu 16.04.4 LTS 4.14.52-sunxi64 Thanks a lot Linda
  2. linda

    emmc for Pine64LTS/Pine64so

    Hello Tom, did your found a solution? The problem still exists with the current SoPine image. (see Thanks
  3. linda

    Can't install PINE A64-LTS to eMMC

    Is it planned to update the image Sopine-Image to the current mainline kernel?
  4. linda

    Can't install PINE A64-LTS to eMMC

    Hello, unfortunately, I do not have a solution yet to install Arbmian on an eMMC and boot from eMMC. The problem is very important to me because I need the PineLTS in a project. Is it planned that the detection of the eMMC will be built into a current SoPine image. It would help me a lot. Thanks a lot you in advance!
  5. Thanks a lot for your help. So if I update the two devices to the current image (apt update/upgrade), then the error should not occur. I will try it.
  6. I did the upgrades form an older image with 4.13-kernel via apt-get install linux-image-next-sunxi64 linux-headers-next-sunxi64 linux-u-boot-pine64-next linux-xenial-root-next-pine64 linux-dtb-next-sunxi64 on the 13th of july (resulting kernel 4.17.5) and on the 17th of july (resulting kernel 4.17.6). When was the commit entered into the next-branch? Can I fix the error if I make an upgrade (apt update, upgrade) to the current image?
  7. Is there a way to boot the Pine-A64 LTS with Armbian via eMMC? I can use the SD card to boot the armian-Sopine image, but the eMMC memory is not recognized. With the Ayufan image (jessie-minimal) on SD card (, I can at least recognize the eMMC memory and using sudo dd bs = 30M if = Image / jessie-minimal-sopine-0.7.19-118.img of =/dev/ mmcblk1 copy to the eMMC memory. I removed the SD card and booted with eMMC. I did the same steps with the Armbian image and write the Armbian image on the eMMC (with the Ayufan image on SD card) sudo dd bs=30M if=Image/Armbian_5.38_Pine64so_Ubuntu_xenial_default_3.10.107.img of=/dev/mmcblk1 and nothings happens after the reboot. There are further steps that I have to carry out?
  8. I have some pine64 with kernel 4.14 and so far the time-problems did not occur with this kernel. Unfortunately, however the pine64 updated to kernel 4.17 again show the the problem! Time jumps to the year 2113 (and sometimes even to 2208). I use kernel 4.17.5 and 4.17.6. The flag 'CONFIG_FSL_ERRATUM_A008585' is set (CONFIG_FSL_ERRATUM_A008585=y). Thanks a lot for help.
  9. How can I keep the LTS-kernel (4.14) with a terminal command? The lastest update/upgrade installs the kernel 4.17. How can I avoid this kernel-update? For my long term-project I need the LTS-kernel 4.14. Some time ago I updated by mainline-system (Ubuntu server kernel 4.13 to 4.14-kernel with the following command apt-get -y -qq --no-install-recommends install linux-image-next-sunxi64 linux-headers-next-sunxi64 linux-u-boot-pine64-next linux-xenial-root-next-pine64 linux-dtb-next-sunxi64 Thanks a lot.
  10. Is it correct to install the kernel with the following command: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 --reinstall -o Dpkg::Options::=--force-confdef -o Dpkg::Options::=--force-confold -y -qq --no-install-recommends install linux-image-next-sunxi64 linux-headers-next-sunxi64 linux-u-boot-pine64-next linux-xenial-root-next-pine64 linux-dtb-next-sunxi64 (found in the history.log of the updated device) A test on a device with the kernel 4.13 shows no error and results in the new kernel 4.14.
  11. many, many thanks for the quick responses and please excuse my bedelayed answer. In my current version (with kernel 4.13) CONFIG_FSL_ERRATUM_A008585 is not set. The updated kernel (4.14) results with CONFIG_FSL_ERRATUM_A008585 = y Thus, I will upgrade my existing devices to the new kernel (and hope that the issues zador.blood.staine addresses will not occur to me). With my test device I realized this with the tool "armban-config". Is there a way to parameterize the "armban-config" tool to run the update via script or is it possible to do the adjustment to the next kernel via command line?
  12. Hello, I have a massive problem as the time/date on my Pine64 keep changing randomly to the year 2113. In my project, I use several Pine64s and the problem now occurs on many of these Pine64s. Unfortunately I need the correct time for my project. I am using the following system: ARMBIAN 5.32.170911 nightly Ubuntu 16.04.3 LTS 4.13.0-sun50iw1 (with additional overlays = uart3 and console = ttyS3) Could this be due to the error described in the post and is the bug fixed in kernel version 4.14? Could I install this kernel version 4.14 via armbian-config (next-kernel)? Thanks a lot for help.
  13. Thank you very much for the quick help. I changed my existing image with the armbian-config-tool to the 'next'-kernel and now I have the kernel 1.14 in operation. Great! In addition I also created a new image yesterday, I will test this image and the possible options in the next few days.
  14. Hi, thanks for your quick reply. apt update && apt upgrade didn't helped for 4.13 to 4.14. I didn't freeze the kernel (checked with the armbian-config-tool). Is there a way to force an update from 4.13 to 4.14?
  15. Hello, I'm using an pine64 with the old mainline Ubuntu server (version 5.32.170911, kernel 4.13) for my project. Thanks for the great work for the Pine64-Armbian! I would like to change to a new image LTS kernel 4.14, because the existing kernel version is no longer supported. Unfortunately I only find the Debian Stretch version on the mainline kernel download server. Is it possible to get a new image with Mainline kernel 4.14 and Ubuntu server? and if not: - If there is no image with 4.14 Ubuntu server, can I change from legacy ubuntu to kernel 4.14? By the way, why ist the mainline-version using debian stretch, but legacy uses Ubuntu? How is the development planned further? I would really appreciate an answer.