Jump to content


  • Posts

  • Joined

  • Last visited

 Content Type 


Member Map




Everything posted by linda

  1. I cannot boot into lvm encyprypted root partition: mount: mounting "/dev/mapper/vg-root on /root failed: No such file or directory␍␊ Failed to mount "/dev/mapper/vg-root as root file system.␍␊ The flollowing step i made (short version) - create the lvm partition - mount lvm partition and and copy file system auf lvm partition, bind /dev, sys, proc - chroot in the lvm root partition (vg-root) - change /etc/fstab : insert /dev/mapper/vg-root / ext4 errors=remount-ro 0 1 UUID=<UUID-Partiion> /mnt/mnt ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 2 #UUID=<UUID-Partiion> / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 - create the initramfs: update-initramfs -u -k $(uname -r) - change armbian.txt: rootdev="/dev/mapper/vg-root cryptdevice=/dev/mmcblk0p2:lvm" During boot, the device ask the PW: Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Please unlock disk lvm: ␍␊ After inserting the password, lvm seems alright ("cryptsetup: lvm: set up successfully␍␊done.␍␊") But the boot file system is not fount Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems␍␊ done.␍␊ Begin: Will now check root file system ... fsck from util-linux 2.33.1␍␊ Checking all file systems.␍␊ done.␍␊ mount: mounting "/dev/mapper/vg-root on /root failed: No such file or directory␍␊ Failed to mount "/dev/mapper/vg-root as root file system.␍␊ i am very grateful for any comments and tips. I have already done such LVM boot encryption 2 years ago on Pine 64 and Pine LTS. BUT NOW I HAVE NO IDEA HOW TO LOOK FURTHER.
  2. I managed to reconnect via DHCP again with the following steps: Insert these lines in /etc/network/interfaces auto eth0 iface eth0 inet dhcp pre-up ifconfig $IFACE up pre-up ethtool -s $IFACE speed 100 duplex full autoneg off and change the line in /etc/NetworkManager/NetworkManager.conf to [ifupdown] managed=false
  3. I'm using a Pine 64 LTS. For this I have downloaded the SoPine images Armbian_21.08.1_Pine64so_buster_current_5.10.60.img and Armbian_21.08.1_Pine64so_focal_current_5.10.60.img Both images boot normally (including network connection), but after the update (apt update, apt upgrade) no IP4 network connection is established for eth0. For help I am very grateful for any help.
  4. I am using an old Sopine image (Armbian 21.02.3 Bionic with Linux 5.4.88-sunxi64). It works very well with the Pine LTS hardware. However, there is a new Pine LTS hardware (LTS-V2) that seems to have changed the network chip, so with the old Sopine image it is no longer possible to connect to the network. Is there any way to reinstall the current network drivers in my image? How can I use the kernel configs to do this? Thanks a lot in advance
  5. Hello, I'm using a Pine 64 LTS with the SoPine image Armbian 21.02.3 Bionic with Linux 5.4.88-sunxi64 I have made various changes and installations to this image, so I want/need to continue using this image. Unfortunately, with the new hardware of the Pine 64 LTS (Pine64 LTS-V2) network connection is no longer possible. (Note: With the current SoPine image there is a network connection). Is there any way to reinstall the current network drivers in my image? I would be very grateful for any help.
  6. Thank you very much for your help.
  7. It's an Orangepi Plus H3 V.1.1.
  8. Thanks for the quick answer. Your link points to bananapi-images. I'm a bit confused, can I use these images for my Orangepi? I can't find an orangepi-directory on the server https://mirrors.ustc.edu.cn/armbian-dl/ .
  9. Hallo, unfortunately i can't find the current orangepi image (https://www.armbian.com/orangepi/). The links to the images either go nowhere (404 file not found) or point to bananapi images. What is the correct link for the current Ubuntu image for the Orangepi? Thank you very much.
  10. I would also be very happy if I could integrate the patch into my current image!
  11. I have changed the DT file after the instructions and now I can use the ports again for my in-circuit programming! Many Thanks!
  12. How can I use / release the ports PC0-PC3 (GPIO 64 - 67) in kernel 4.19? In my project I am using the ports PC0-PC3 (GPIO 64 - 67) for in-circuit programming (with avrdude). Everything was fine until I switched from kernel 4.14 to kernel 4.19. Now the ports are already in use. (Although according to the pine64 schematics nothing is connected to those ports) sudo cat /sys/kernel/debug/pinctrl/1c20800.pinctrl/pinmux-pins ... pin 64 (PC0): device 1c68000.spi function spi0 group PC0 pin 65 (PC1): device 1c68000.spi function spi0 group PC1 pin 66 (PC2): device 1c68000.spi function spi0 group PC2 pin 67 (PC3): device 1c68000.spi function spi0 group PC3 ... In kernel 4.14 the ports were unclaimed: sudo cat /sys/kernel/debug/pinctrl/1c20800.pinctrl/pinmux-pins ... pin 64 (PC0): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 65 (PC1): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 66 (PC2): (MUX UNCLAIMED) (GPIO UNCLAIMED) pin 67 (PC3): (MUX UNCLAIMED) (GPIO UNCLAIMED) ... How can I free the ports so I can use kernel 4.19 in my project? Here is the related information from armbianmonitor -u: [ 5222.922107] sun50i-a64-pinctrl 1c20800.pinctrl: pin PC3 already requested by 1c68000.spi; cannot claim for 1c20800.pinctrl:67 [ 5222.922122] sun50i-a64-pinctrl 1c20800.pinctrl: pin-67 (1c20800.pinctrl:67) status -22 Thanks for any information in advance.
  13. Hi KemoNine, unfortunately, the problem still occurs sporadically for me (kernel 4.17). I have not found a solution and would also be very grateful for a practical work around. [my current work-around: "systemctl restart ntp"]
  14. 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
  15. Hello Tom, did your found a solution? The problem still exists with the current SoPine image. (see Thanks
  16. Is it planned to update the image Sopine-Image to the current mainline kernel?
  17. 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!
  18. 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.
  19. 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?
  20. 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 (https://github.com/ayufan-pine64/linux-build/releases), 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?
  21. 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.
  22. 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.
  23. 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.
  24. 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?
  25. 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.
  • Create New...