Jump to content

Guy

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by Guy

  1. It looks like even though avahi daemon was running I was missing libnss-mdns so just installing it using sudo apt install libnss-mdns solved it. In my case /etc/nsswitch.conf already had similar content, maybe from my previous attempts to solve this hosts: files mymachines mdns4_minimal [NOTFOUND=return] dns myhostname Thanks for all the help
  2. I am trying to ping device on my network by device name, it works on my Linux computer and does not work on my NPi R1. Expecting pinging the device name will retrieve ping data including my device local IP. $ ping HPC0180319938E.local ping: HPC0180319938E.local: Name or service not known I preformed sudo apt update && sudo apt upgrade Not sure how to check ping command version. _ _ ____ _ ____ _ | \ | | _ \(_) | _ \/ | | \| | |_) | | | |_) | | | |\ | __/| | | _ <| | |_| \_|_| |_| |_| \_\_| Welcome to Armbian 22.08.8 Focal with Linux 5.15.74-sunxi
  3. It looks like multipass error https://forum.snapcraft.io/t/creating-a-snap-for-raspberry-pi-4/19294 So I will just used lxd as they mentioned there
  4. Installing it manually does not work sudo apt install qemu-system-aarch64 root@nanopik1plus:~/testSnap# multipass start launch failed: Internal error: qemu-system-x86_64 failed getting vmstate (Process returned exit code: 1) with output: qemu-system-aarch64: -nographic: No machine specified, and there is no default Use -machine help to list supported machines
  5. I am trying to start snap multipass on the device nanopi k1 plus, getting the following error: root@nanopik1plus:~/testSnap# multipass start launch failed: Internal error: qemu-system-x86_64 failed getting vmstate (Process returned exit code: 1) with output: qemu-system-aarch64: -nographic: No machine specified, and there is no default Use -machine help to list supported machines
  6. Tested the new image and it is working now. Thanks everyone for your help. Can be closed
  7. I am not sure if this is intended or bug, When building the image for Nanopi duo2 I cannot add kvm. This worked before so I guess that this is regression. I get this search result for kvm in the build process: ┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Search Results ────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┐ │ Symbol: KVM [=KVM] │ │ Type : unknown │ │ │ │ │ │ Symbol: DRM_I915_GVT_KVMGT [=n] │ │ Type : tristate │ │ Defined at drivers/gpu/drm/i915/Kconfig:122 │ │ Prompt: Enable KVM/VFIO support for Intel GVT-g │ │ Depends on: HAS_IOMEM [=y] && DRM_I915_GVT [=n] && KVM && VFIO_MDEV [=n] && VFIO_MDEV_DEVICE [=n] │ │ Location: │ │ -> Device Drivers │ │ (1) -> Graphics support │ │ -> Intel 8xx/9xx/G3x/G4x/HD Graphics (DRM_I915 [=n]) │ │ -> Enable Intel GVT-g graphics virtualization host support (DRM_I915_GVT [=n]) │ │ │ │ │ │ Symbol: KVM_GUEST [=KVM_GUEST] │ │ Type : unknown │ │ │ │ │ │ Symbol: PTP_1588_CLOCK_KVM [=n] │ │ Type : tristate │ │ Defined at drivers/ptp/Kconfig:106 │ │ Prompt: KVM virtual PTP clock │ │ Depends on: PTP_1588_CLOCK [=y] && KVM_GUEST && X86 │ │ Location: │ │ -> Device Drivers │ │ (2) -> PTP clock support
  8. Forgot to emphasize that the serial is working in the last versions too. So it is working before the one that I checked and in the last one available, it is not working only specifically in that one. So the serial does not hold me back from testing new staff, but I don't know the specific commit that the serial was fixed so I can't check if that commit was the first place that the snap bug was introduced.
  9. Before it is working, after cannot connect to serial U-Boot SPL 2020.04-armbian (Jul 11 2020 - 16:51:48 +0300) DRAM: 512 MiB Trying to boot from MMC1 U-Boot 2020.04-armbian (Jul 11 2020 - 16:51:48 +0300) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: FriendlyARM NanoPi DUO 2 DRAM: 512 MiB MMC: mmc@1c0f000: 0 Loading Environment from FAT... Unable to use mmc 0:1... In: serial Out: serial Err: serial Net: No ethernet found. starting USB... No working controllers found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 3789 bytes read in 3 ms (1.2 MiB/s) ## Executing script at 43100000 U-boot loaded from SD Boot script loaded from mmc 190 bytes read in 3 ms (61.5 KiB/s) 13628911 bytes read in 1035 ms (12.6 MiB/s) 6118624 bytes read in 467 ms (12.5 MiB/s) Found mainline kernel configuration 29102 bytes read in 9 ms (3.1 MiB/s) 504 bytes read in 9 ms (54.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost0.dtbo 504 bytes read in 9 ms (54.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost2.dtbo 504 bytes read in 9 ms (54.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-usbhost3.dtbo 4185 bytes read in 9 ms (454.1 KiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 ## Loading init Ramdisk from Legacy Image at 43300000 ... Image Name: uInitrd Image Type: ARM Linux RAMDisk Image (gzip compressed) Data Size: 13628847 Bytes = 13 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 43000000 Booting using the fdt blob at 0x43000000 Loading Ramdisk to 49300000, end 49fff5af ... OK Loading Device Tree to 49290000, end 492fffff ... OK Starting kernel ... Uncompressing Linux... done, booting the kernel. and it just stop after booting the kernel Thanks man
  10. Not sure, is there easy way to build image with kvm and squashfs with the code before the merge ? this way I will test it.
  11. When installing snaps I get the following error: error: system does not fully support snapd: cannot mount squashfs image using "squashfs": mount: /tmp/sanity-mountpoint-910419852: wrong fs type, bad option, bad superblock on /dev/loop0, missing codepage or helper program, or other error. It worked about a mouth ago but now whenever I build the images and try to install a snap I get that error. Steps to reproduce: 1. Build Nanopi Duo2 image with kvm and squashfs 2. Connect to device and install snapd 'sudo apt install snapd' 3. Install snap to test it 'sudo snap install hello-world' Expectation: Snaps work as this is the same process that I did before to use snaps on armbian image for this device Result: Getting the error I have tried multiple sd cards, multiple nanopi duo2 devices and both 18.04 and 20.04 images.
  12. I started compiling some project (snowboy ) on the nanopiDuo2 like I am doing on the FriendlyCore 16.04 and suddenly the board stop working/booting. The red led is blinking fast, the same sd card is working on different boards, FriendlyCore does not boot on this board. "provide a log from serial console" I don't have serial cable yet. This happened to me twice, on Armbian 18.04 and on 20.04. First it destroyed the "IoT-2G Application Carrier Board for NanoPi Duo2" that it was on without the board, and the carrier had burnt smell, internet cable and power were connected. For one of them the red led is blinking fast, for the other the led does not blink at all (I can upload video of the red led if it helps). Just the last time it was compiling snowboy, the others I don't remember. I am uploading the Armbianmonitor of the last sd card but using different board.
  13. Thanks @le51 it worked. @Igor I will try to learn more about Linux kernel will start adding patch one day. Thanks all
  14. Is there a way that I can help, testing information gathering. Is there estimation when it will work, like two three months?.
  15. WiringNP does not work on NanopiDuo2, both in 18.04 and Ubuntu 20.04 Error piBoardRev: Unable to determine board revision from /proc/cpuinfo -> Is not NanoPi based board. -> You may want to check: -> http://www.lemaker.org/ open /sys/class/su Armbian /proc/cpuinfo content: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 136.80 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : Allwinner sun8i Family Revision : 0000 Serial : 02c00181e49e909a vs friendlyarm OS /proc/cpuinfo content: processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 2 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 3 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 22.85 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae evtstrm CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : sun8i Revision : 0000 Serial : 02c00081af9196e6 Armbian /sys/class/sunxi_info/sys_info file does not exist. vs friendlyarm /sys/class/sunxi_info/sys_info file content: sunxi_platform : sun8iw7p1 sunxi_secure : normal sunxi_chipid : unsupported sunxi_chiptype : unsupported sunxi_batchno : unsupported sunxi_board_id : 8(0) board_manufacturer: FriendlyElec board_name : FriendlyElec NanoPi-Duo2
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines