Search the Community

I have an Ubuntu 20.04.06 system where my /var/log zram mount ran out of space. I took a few steps to address this (see below), and after rebooting, /var/log is no longer a zram mount. I've tried to find mentions of zram or ramlog in log files, but can't find anything that looks like an error message. /etc/default/armbian-zram-config and /etc/default/armbian-ramlog both still show they're enabled. Any idea how I can fix ramlog to come back up? - mv auth.log ../log.hdd/auth.log.240912 - mv mail.log ../log.hdd/mail.log.240912 cd ../log.hdd gzip auth.log.240912 gzip mail.log.240912 df -h # df showed /var/log as still full # it seems the moved and deleted files were still open for writing by apps cd ../log touch auth.log touch mail.log shutdown -r now Now /var/log is 17M, and log.hdd is 940K. log.hdd used to be much bigger.

I tried to download the Opi plus 2 Image in armbian download page, but it linked In to Opi plus which is older hardware. There Are only plus 2e and plus Image. Here is the link : https://www.armbian.com/orange-pi-plus-2/ How can I get the image of Opi plus 2 ?? Plz let me know:(

Hello! I have [ Oprange Pi plus ]. I need Armbian_20.05.1_Orangepipc_buster_current_5.4.43_desktop.img Please help me! Yours sincerely Leonid

I have Orange Pi Plus 2 running Ubuntu Bionic with Armbian Linux 4.19.62-sunxi and I would like to upgrade it to recent Armbian build based on Ubuntu Linux Server and move OS to SSD connected to one of USB ports. I tried to use Armbian_22.08.2_Orangepiplus_jammy_current_5.15.69.img.xz but it does not connect to both HDMI and network. I tried unofficial command line interface images from product page and weekly released unsupported community builds. Behavior of all these builds is the same - no output to HDMI, no network connection. Finaly I found that recent image for Orange Pi Plus / Plus 2 which boots is Armbian_22.08.1_Orangepiplus_jammy_current_5.15.63.img.xz. I was able to boot from this image and transfer OS to SSD but running "apt update" and "apt upgrade" breaks something in operating system even if Kernel is "frozen" using armbian-config utility. After upgrade OS does not recognize usb-to-serial adapter CH341 connected to one of USB ports. Amout of loaded Kernel modules essentially decrease: orangepiplus:~:# lsmod Module Size Used by pwrseq_simple 16384 1 sy8106a_regulator 16384 0 gpio_keys 20480 0 uas 24576 1 realtek 24576 1 orangepiplus:~:# Attempt to load module using modprobe fails: orangepiplus:~:# modprobe usbserial vendor=1a86 product=7523 modprobe: FATAL: Module usbserial not found in directory /lib/modules/5.15.63-sunxi orangepiplus:~:# It looks like kernel modules were upgraded by running "apt update" and "apt upgrade" although Kernel was "frozen" using armbian-config utility. There is no 5.15.63-sunxi folder in /lib/modules: orangepiplus:~:# ls -la /lib/modules/ total 12 drwxr-xr-x 3 root root 4096 Nov 14 21:04 . drwxr-xr-x 76 root root 4096 Nov 14 20:31 .. drwxr-xr-x 3 root root 4096 Nov 14 20:31 5.15.74-sunxi orangepiplus:~:# Adding sym link to upgraded modules does not help. Load module fails due to exec format error: orangepiplus:~:# ln -s /lib/modules/5.15.74-sunxi /lib/modules/5.15.63-sunxi orangepiplus:~:# ls -la /lib/modules/ total 12 drwxr-xr-x 3 root root 4096 Nov 14 20:45 . drwxr-xr-x 76 root root 4096 Nov 14 20:31 .. lrwxrwxrwx 1 root root 26 Nov 14 20:45 5.15.63-sunxi -> /lib/modules/5.15.74-sunxi drwxr-xr-x 3 root root 4096 Nov 14 20:31 5.15.74-sunxi orangepiplus:~:# orangepiplus:~:# modprobe usbserial vendor=1a86 product=7523 modprobe: ERROR: could not insert 'usbserial': Exec format error orangepiplus:~:# All modules in /lib/modules before and after running "apt update" and "apt upgrade" are compressed and have extension ".xz". It looks like upgraded Kernel has no ability to load compressed modules. I understand that Orange Pi Plus / Plus 2 is not supported anymore but is it possible to check if Kernels newer then 5.15.63 were compiled with "CONFIG_MODULE_COMPRESS=y" and "CONFIG_MODULE_COMPRESS_XZ=y"? Thanks, Sergey

http://paste.armbian.com/icedujiguw.yaml Hello everyone, trying to give new life to this old Orange Pi+ 2. Here is described what hapens when i try to boot up latest image. Can anyone help. Thanks in advance. Armbian 23.8 Bookworm Kernel 6.2.y, Size: 421Mb, Release date: Jun 3, 2023 SBC gets stuck after the request Sense .. and doesnt booy up, if i plug a device in usb ports, it bootloops .. see below using same sd-card and a diffrent image file works with no issues . hardware : grounded out pin 9 of the SD card slot (checked with multimeter and works) U-Boot SPL 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface9 eth0: ethernet@1c30000 starting USB... Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1d000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... EHCI timed out on TD - token=0x80008c80 unable to get device descriptor (error=-1) 2 USB Device(s) found scanning bus usb@1c1d000 for devices... Device NOT ready Request Sense returned 02 3A 00 SBC gets stuck after the request Sense .. and doesnt booy up, if i plug a device in usb ports, it bootloops .. see below U-Boot SPL 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) DRAM: 2048 MiB Trying to boot from MMC1 U-Boot 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus / Plus 2 DRAM: 2 GiB Core: 65 devices, 18 uclasses, devicetree: separate WDT: Not starting watchdog@1c20ca0 MMC: mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@1c28000 Out: serial@1c28000 Err: serial@1c28000 Net: phy interface9 eth0: ethernet@1c30000 starting USB... Bus usb@1c1b000: USB EHCI 1.00 Bus usb@1c1d000: USB EHCI 1.00 scanning bus usb@1c1b000 for devices... Device NOT ready Request Sense returned 02 3A 00 undefined instruction pc : [<bbf93980>] lr : [<bffa3391>] reloc pc : [<4600b980>] lr : [<4a01b391>] sp : bbf5e848 ip : 0000001c fp : bffde94a r10: bffe5c00 r9 : bbf67ec0 r8 : 00000000 r7 : 00000000 r6 : bbf93b18 r5 : a0000000 r4 : bbf93b80 r3 : bbf93980 r2 : 00000000 r1 : 00000000 r0 : bbf93b80 Flags: NzCv IRQs off FIQs off Mode SVC_32 Code: bbf68cc8 00000000 00000000 00000000 (ffffffff) Resetting CPU ... resetting ... U-Boot SPL 2022.07-armbian (Jun 03 2023 - 19:37:25 +0000) DRAM: 2048 MiB Trying to boot from MMC1

Hi. I need the serial number of the CPU of the orange Pi boards. I see it is in the file /proc/cpuinfo I need another place that is not file based as the cpuinfo file can be spoofed. Is there a way to read it directly from a register?