Search the Community

I am running a old buster image and ran apt-get upgrade, now it won't boot. Armbian 21.02.3 Buster with Linux 5.15.93-sunxi64 Get:8 http://netcup.armbian.com/apt buster/main arm64 linux-u-boot-orangepipc2-current arm64 25.2.3 [336 kB] ... Unpacking armbian-firmware (25.2.3) over (23.08.0-trunk--1-SA1251-B226d) ... dpkg: error processing archive /tmp/apt-dpkg-install-RjldFI/034-armbian-firmware_25.2.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin', which is also in package firmware-atheros 20190114+really20220913-0+deb10u2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) ... Preparing to unpack .../089-linux-dtb-current-sunxi64_25.2.3_arm64.deb ... Armbian 'linux-dtb-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' starting. Armbian 'linux-dtb-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' finishing. Unpacking linux-dtb-current-sunxi64 (25.2.3) over (23.02.2) ... dpkg: warning: unable to delete old directory '/boot/dtb-5.15.93-sunxi64/allwinner': Directory not empty dpkg: warning: unable to delete old directory '/boot/dtb-5.15.93-sunxi64': Directory not empty Preparing to unpack .../090-linux-image-current-sunxi64_25.2.3_arm64.deb ... Armbian 'linux-image-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' starting. update-initramfs: Deleting /boot/initrd.img-5.15.93-sunxi64 Removing obsolete file uInitrd-5.15.93-sunxi64 Armbian 'linux-image-current-sunxi64' for '6.6.75-current-sunxi64': 'preinst' finishing. Unpacking linux-image-current-sunxi64 (25.2.3) over (23.02.2) ... Preparing to unpack .../091-linux-u-boot-orangepipc2-current_25.2.3_arm64.deb ... Unpacking linux-u-boot-orangepipc2-current (25.2.3) over (23.02.2) ... ... Errors were encountered while processing: /tmp/apt-dpkg-install-RjldFI/034-armbian-firmware_25.2.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) ... Preparing to unpack .../armbian-firmware_25.2.3_all.deb ... Unpacking armbian-firmware (25.2.3) over (23.08.0-trunk--1-SA1251-B226d) ... dpkg: error processing archive /var/cache/apt/archives/armbian-firmware_25.2.3_all.deb (--unpack): trying to overwrite '/lib/firmware/ath10k/QCA9377/hw1.0/board-2.bin', which is also in package firmware-atheros 20190114+really20220913-0+d eb10u2 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/armbian-firmware_25.2.3_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) after rebooting U-Boot SPL 2019.10-armbian (Feb 17 2020 - 08:45:21 +0100) DRAM: 1024 MiB Trying to boot from MMC1 NOTICE: BL31: v2.2(debug):572fcdd-dirty NOTICE: BL31: Built : 08:45:08, Feb 17 2020 NOTICE: BL31: Detected Allwinner H5 SoC (1718) NOTICE: BL31: Found U-Boot DTB at 0x40a1650, model: Xunlong Orange Pi PC 2 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller NOTICE: PMIC: Assuming H5 reference regulator design INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for 855873 was applied INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 U-Boot 2019.10-armbian (Feb 17 2020 - 08:45:21 +0100) Allwinner Technology CPU: Allwinner H5 (SUN50I) Model: Xunlong Orange Pi PC 2 DRAM: 1 GiB MMC: mmc@1c0f000: 0 Loading Environment from EXT4... ** File not found /boot/boot.env ** ** Unable to read "/boot/boot.env" from mmc0:1 ** In: serial Out: serial Err: serial Allwinner mUSB OTG (Peripheral) Net: phy interface7 eth0: ethernet@1c30000 Warning: usb_ether using MAC address from ROM , eth1: usb_ether 230454 bytes read in 18 ms (12.2 MiB/s) starting USB... Bus usb@1c1a000: USB EHCI 1.00 Bus usb@1c1a400: USB OHCI 1.0 Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1b400: USB OHCI 1.0 Bus usb@1c1c000: USB EHCI 1.00 Bus usb@1c1c400: USB OHCI 1.0 Bus usb@1c1d000: USB EHCI 1.00 Bus usb@1c1d400: USB OHCI 1.0 scanning bus usb@1c1a000 for devices... 1 USB Device(s) found scanning bus usb@1c1a400 for devices... 1 USB Device(s) found scanning bus usb@1c1b000 for devices... 1 USB Device(s) found scanning bus usb@1c1b400 for devices... 1 USB Device(s) found scanning bus usb@1c1c000 for devices... 2 USB Device(s) found scanning bus usb@1c1c400 for devices... 1 USB Device(s) found scanning bus usb@1c1d000 for devices... 2 USB Device(s) found scanning bus usb@1c1d400 for devices... 1 USB Device(s) found scanning usb for storage devices... 2 Storage Device(s) 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 3069 bytes read in 6 ms (499 KiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 165 bytes read in 2 ms (80.1 KiB/s) libfdt fdt_check_header(): FDT_ERR_BADMAGIC No FDT memory address configured. Please configure the FDT address via "fdt addr <address>" command. Aborting! Bad Linux ARM64 Image magic! SCRIPT FAILED: continuing... Device 0: Vendor: ACASIS Rev: 0508 Prod: Type: Hard Disk Capacity: 228936.5 MB = 223.5 GB (468862128 x 512) ... is now current device ** Unrecognized filesystem type ** ethernet@1c30000 Waiting for PHY auto negotiation to complete....... done BOOTP broadcast 1 DHCP client bound to address 10.0.0.126 (7 ms) *** Warning: no boot file name; using '0A00007E.img' Using ethernet@1c30000 device TFTP from server 10.0.0.136; our IP address is 10.0.0.126 Filename '0A00007E.img'. Load address: 0x42000000 Loading: T T T T T T T T T T Retry count exceeded; starting again missing environment variable: pxeuuid missing environment variable: bootfile Retrieving file: pxelinux.cfg/01-02-01-1a-9a-1c-cb Using ethernet@1c30000 device TFTP from server 10.0.0.136; our IP address is 10.0.0.126 Filename 'pxelinux.cfg/01-02-01-1a-9a-1c-cb'. Load address: 0x4fd00000 Loading: T T T T T T T T T T armbianEnv.txt verbosity=1 console=both overlay_prefix=sun50i-h5 rootdev=UUID=5d4a9712-49dd-4566-8f99-28aba89a7816 rootfstype=ext4 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u boot.cmd mw.l 0x01C20020 0x80101810 # DO NOT EDIT THIS FILE # # Please edit /boot/armbianEnv.txt to set supported parameters # # default values setenv load_addr "0x44000000" setenv rootdev "/dev/mmcblk0p1" setenv verbosity "1" setenv rootfstype "ext4" setenv console "both" setenv docker_optimizations "on" # Print boot source itest.b *0x10028 == 0x00 && echo "U-boot loaded from SD" itest.b *0x10028 == 0x02 && echo "U-boot loaded from eMMC or secondary SD" itest.b *0x10028 == 0x03 && echo "U-boot loaded from SPI" echo "Boot script loaded from ${devtype}" if test -e ${devtype} ${devnum} ${prefix}armbianEnv.txt; then load ${devtype} ${devnum} ${load_addr} ${prefix}armbianEnv.txt env import -t ${load_addr} ${filesize} fi if test "${console}" = "display" || test "${console}" = "both"; then setenv consoleargs "console=ttyS0,115200 console=tty1"; fi if test "${console}" = "serial"; then setenv consoleargs "console=ttyS0,115200"; fi # get PARTUUID of first partition on SD/eMMC it was loaded from # mmc 0 is always mapped to device u-boot (2016.09+) was loaded from if test "${devtype}" = "mmc"; then part uuid mmc 0:1 partuuid; fi setenv bootargs "root=${rootdev} rootwait rootfstype=${rootfstype} ${consoleargs} panic=10 consoleblank=0 loglevel=${verbosity} ubootpart=${partuuid} usb-storage.quirks=${usbstoragequirks} ${extraargs} ${extraboardargs}" if test "${docker_optimizations}" = "on"; then setenv bootargs "${bootargs} cgroup_enable=memory swapaccount=1"; fi load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} fdt addr ${fdt_addr_r} fdt resize 65536 for overlay_file in ${overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-${overlay_file}.dtbo; then echo "Applying kernel provided DT overlay ${overlay_prefix}-${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done for overlay_file in ${user_overlays}; do if load ${devtype} ${devnum} ${load_addr} ${prefix}overlay-user/${overlay_file}.dtbo; then echo "Applying user provided DT overlay ${overlay_file}.dtbo" fdt apply ${load_addr} || setenv overlay_error "true" fi done if test "${overlay_error}" = "true"; then echo "Error applying DT overlays, restoring original DT" load ${devtype} ${devnum} ${fdt_addr_r} ${prefix}dtb/${fdtfile} else if load ${devtype} ${devnum} ${load_addr} ${prefix}dtb/allwinner/overlay/${overlay_prefix}-fixup.scr; then echo "Applying kernel provided DT fixup script (${overlay_prefix}-fixup.scr)" source ${load_addr} fi if test -e ${devtype} ${devnum} ${prefix}fixup.scr; then load ${devtype} ${devnum} ${load_addr} ${prefix}fixup.scr echo "Applying user provided fixup script (fixup.scr)" source ${load_addr} fi fi load ${devtype} ${devnum} ${ramdisk_addr_r} ${prefix}uInitrd load ${devtype} ${devnum} ${kernel_addr_r} ${prefix}Image booti ${kernel_addr_r} ${ramdisk_addr_r} ${fdt_addr_r} # Recompile with: # mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr /boot dir -rw-r--r-- 1 root root 263 Mar 18 2019 armbianEnv.bad.bak -rw-r--r-- 1 root root 165 Mar 1 13:17 armbianEnv.txt -rw-r--r-- 1 root root 165 Mar 18 2019 armbianEnv.txt.fresh -rw-r--r-- 1 root root 165 Jul 6 2024 armbianEnv.txt.good -rw-r--r-- 1 root root 0 Jan 14 2019 armbianEnv.txt.out -rw-r--r-- 1 root root 1536 Jan 9 2019 armbian_first_run.txt.template -rw-r--r-- 1 root root 230454 Jan 9 2019 boot.bmp -rw-r--r-- 1 root root 2997 Jan 11 2019 boot.cmd -rw-r--r-- 1 root root 4882 Jan 9 2019 boot-desktop.png -rw-rw-r-- 1 root root 3069 Jan 11 2019 boot.scr -rw-r--r-- 1 root root 223045 Feb 26 15:06 config-6.6.75-current-sunxi64 drwxr-xr-x 3 root root 4096 Mar 9 2020 dtb-4.19.104-sunxi64 drwxr-xr-x 2 root root 4096 Feb 1 2019 dtb-4.19.13-sunxi64 drwxr-xr-x 3 root root 4096 Feb 12 2019 dtb-4.19.20-sunxi64 drwxr-xr-x 3 root root 4096 Apr 16 2019 dtb-4.19.25-sunxi64 drwxr-xr-x 3 root root 4096 May 14 2019 dtb-4.19.38-sunxi64 drwxr-xr-x 3 root root 4096 Jul 6 2019 dtb-4.19.57-sunxi64 drwxr-xr-x 3 root root 4096 Aug 3 2019 dtb-4.19.63-sunxi64 drwxr-xr-x 3 root root 4096 Feb 11 2021 dtb-5.10.12-sunxi64 drwxr-xr-x 3 root root 4096 Feb 18 2021 dtb-5.10.16-sunxi64 drwxr-xr-x 3 root root 4096 Mar 29 2021 dtb-5.10.21-sunxi64 drwxr-xr-x 3 root root 4096 May 14 2021 dtb-5.10.34-sunxi64 drwxr-xr-x 3 root root 4096 Jan 10 2021 dtb-5.10.4-sunxi64 drwxr-xr-x 3 root root 4096 Sep 25 2021 dtb-5.10.60-sunxi64 drwxr-xr-x 3 root root 4096 Mar 10 2022 dtb-5.15.25-sunxi64 drwxr-xr-x 3 root root 4096 Aug 3 2022 dtb-5.15.48-sunxi64 drwxr-xr-x 3 root root 4096 Nov 5 2022 dtb-5.15.74-sunxi64 drwxr-xr-x 3 root root 4096 Mar 1 2023 dtb-5.15.93-sunxi64 drwxr-xr-x 3 root root 4096 May 10 2020 dtb-5.4.28-sunxi64 drwxr-xr-x 3 root root 4096 Jun 6 2020 dtb-5.4.43-sunxi64 drwxr-xr-x 3 root root 4096 Aug 23 2020 dtb-5.7.15-sunxi64 drwxr-xr-x 3 root root 4096 Sep 24 2020 dtb-5.8.10-sunxi64 drwxr-xr-x 3 root root 4096 Sep 26 2020 dtb-5.8.11-sunxi64 drwxr-xr-x 3 root root 4096 Oct 9 2020 dtb-5.8.13-sunxi64 drwxr-xr-x 3 root root 4096 Oct 18 2020 dtb-5.8.14-sunxi64 drwxr-xr-x 3 root root 4096 Oct 27 2020 dtb-5.8.16-sunxi64 drwxr-xr-x 3 root root 4096 Sep 8 2020 dtb-5.8.6-sunxi64 drwxr-xr-x 3 root root 4096 Dec 17 2020 dtb-5.9.14-sunxi64 drwxr-xr-x 3 root root 4096 Mar 21 15:49 dtb-6.6.75-current-sunxi64 lrwxrwxrwx 1 root root 20 Mar 9 2020 dtb.old -> dtb-4.19.104-sunxi64 lrwxrwxrwx 1 root root 23 Mar 1 2023 Image -> vmlinuz-5.15.93-sunxi64 -rw-r--r-- 1 root root 3584829 Feb 26 15:06 System.map-6.6.75-current-sunxi64 lrwxrwxrwx 1 root root 23 Aug 2 2023 uInitrd -> uInitrd-5.15.93-sunxi64

Armbian 24.2 is broken on Orange PI PC2 (Debian Bookworm CLI) Latest stable community release: https://github.com/armbian/community/releases/download/24.5.0-trunk.123/Armbian_community_24.5.0-trunk.123_Orangepipc2_bookworm_current_6.6.20_minimal.img.xz With update 23.11 -> 24.2 the orange pi pc2 no longer starts. I tried a new sd installation and it too does not appear on the network. Right now I don't have a serial cable to check but it is possible that the network driver is missing or not working. SD, SBC and PSU are 100% working: a revert to 23.11.2 makes it work perfectly.

I will use a orangepi PC2 as openhab server. Arbian 25.2 kernel 6.6.62 minimal.img is installed. The orangepi is connected with an ethernet cable to the router, but is not visible in the list of connected devices. So I suppose he does not make connection. I want to access the orangepi by putty on my PC but as long he is not online, connection is not possible. Led's on the ethernet connector ar flashing. What do I wrong ?

Hi, I am a Grade 12 STEM Student, and right now I need someone's help on our Investigatory Project. Can someone help me on how to connect screen saver (turns off automatically when snoozing) and turns on when PIR Sensor detected something so that It saves power when not used. And I also need to know how do I connect it to the Smart TV because our project is basically an Interactive Board (The thing that you can find around malls which you can use to know specific locations around the mall.) What I have: 1. Orange Pi 2. PIR Sensor 3. Smart TV What I need: 1. A step-by-step procedure on how to do it. 2. What commands/codes to input (Right now, we are using Python language but you can suggest other languages that we can use.)

I am creating a script that can backup sd-cards running on the system, resizing it with desired value or via resize2fs calculated. I learn a lot but there are a few things I don't fully understand. When I create a backup I dd what I understand is the bootsector, ie I grab the "start" position of the partition I am backing up with fidisk and use that value and a blocksize of 512. I then add another 10mb (in bytes) just to be sure. Usually the bootsector is 8192 big, but not always (IIRC nanopi neo3;s is WAY bigger). dd bs=512 count=$DDBOOTSECTOR if=/dev/mmcblk0 of=$IMG_FILE conv=noerror,sync status=progress I then truncate the file, calculated either by resize2fs minimum calculation or via an input + file usage in df (depending of what flag I start the script with) + bootsector + yadayadayda. (if someone want me to post the script I will, but the script and calculations work, although I "force" some commands) I then loop the created img file and delete the partition on the /dev/loop0 and recreates it to cover 100%. Then format it with mkfs.ext4 copying the name and uuid from wherever I backup from. I mount the loop and rsync / rsync -ahvD --exclude={/lost+found,/proc/*,/sys/*,/dev/*,/tmp,/run/*,/mnt/*,/media/*,/var/log.hdd,/var/swap,/etc/udev/rules.d/70-persistent-net.rules,/var/lib/asterisk/astdb.sqlite3-journal} --info=progress2 --stats --delete --force --partial / $tmp_dir This seems to work, but there are probably some things that are just "accepted" not really "perfect". So questions: 1. Should I only dd the EXACT bootsector and not add the extra 10mb? The reason I ask is because if I try to delete the partition with parted, I have to do a hack in the scrip where I simulate button presses, it warns me that "the partition cant be outside of the disk" when I try to REMOVE it. Solution, I use sfdisk to remove the partition, but it prompts me to think there is something wrong going on here. If the size I create is ABOVE the resize2fs reported minimum i don't get this warning. sfdisk was the solution in this case, but still curious on this behavior. If I try to only dd the small part, it sometimes works, sometimes doesn't so I come here asking. (I might be able to do some further research but since I have other questions, why not ask) 2. Does armbian ever update the u-boot via apt? I do my next update with rscync by looping the file and mounting it. But that wont EVER cover the bootsector. 2b. If yes, do I solve this by again dd:ing ONLY the bootsector? 3. I have noticed that sudo apt update on armbian includes armhf even though running arm64. This makes the update process VERY long. dpkg --print-foreign-architectures shows armhf so i remove it with dpkg --remove-architecture armhf and then find /var/lib/apt/lists/ -type f -exec rm {} -v \; Seems to fix this but is this a bad idea? Why is the armhf even being fetched to begin with? To my memory I have not added arhmf architecture... Thanks in advance!

Hi I'm auto-login using nodm with orange pi. I run my udp.py file by creating a file named udp.desktop under the .etc/xdg/autostart folder at startup. but I need to play the wav file using pygame in the .py file, but I get a warning that the audio device could not be initialized. If I trigger my .py file manually, I can play the wav file without any problems. probably unable to load sound drivers during autostart. Can you help with this.