Search the Community

Hi, I have a question about distro upgrde. This is the information on welcome screen: Packages: Ubuntu stable (jammy), possible distro upgrade (noble) Support: DIY (community maintained) I checked the release info on https://www.armbian.com/orange-pi-plus-2e/ and the noble is available. I used sudo apt dist-upgrade and it found no upgrade. Is there any wrong with that? And how I can do the dist-upgrade except writing a new image?

I rebooted from the 6.6.16-current-sunxi kernel to the 6.7.4-edge-sunxi on my Orange Pi +2E and it couldn't mount some partitions from a USB stick. These use LVM2, and each partition is encrypted using LUKS2 with a keyfile stored in /etc (yes, I know this is a fig leaf encryption, but it prevents someone from grabbing the USB stick and getting the contents of the drive). This works fine with the older kernel, but fails with the newer kernel. I use the exact same setup on a Rock 64 board, and it works fine, on the 6.7.4-edge-rockchip64 kernel.

as per title, armbian sucks. The last version is totally broken, unusable. Only one quarter of the screen is readable, the rest is black: why nobody has said that? Why nobody says that vlc and mpv crashes every 2 min making watching a movie impossible? The once half-decent armbian is ready for the bin now

Hello, I bought an orange pi plus 2 and connected it to the power supply, the android that is already installed recognized the mouse and keyboard without any problem. I tried to boot the ARMbian using the version I was given, the orange pi plus 2e version, because there is no direct support for the orange pi plus 2. The BOOt works without any problem, but when I create the user, the system doesn't recognize my keyboard or mouse and I get stuck on the creating user screen. I'm using a 5V/3A power supply and a bluetooth mouse. Can anyone tell me if this is a kernel bug or am I using the wrong version to BOOT?

Hi, i have installed the latest Armbian 23.5 Jammy on my opi+2e and since then, only the top left of the screen is showing text, like if the screen is divided in 4 and only the upper left is showing login screen and text. If I try to install a desktop environment, everything goes full screen, but I see the mouse cursor of login screen overlapped to desktop, so i have two mouse cursors: one fixed and the other that can be moved. WTF is going on? Why don't you test the images before you publish?

At Raspberry Pi (at least on R.Pi 4) it is possibility to set up more than one 1-wire bus. Can that be done on Orange Pi plus 2e with Armbian? uname -a Linux XXXXXXXXXXX 5.15.93-sunxi #23.02.2 SMP Fri Feb 17 23:49:46 UTC 2023 armv7l armv7l armv7l GNU/Linux /boot/armbianEnv.txt verbosity=1 bootlogo=false console=both disp_mode=1920x1080p60 overlay_prefix=sun8i-h3 rootdev=UUID=d908a8da-8d2e-4802-8a05-aaab4f3290bb rootfstype=ext4 overlays=w1-gpio param_w1_pin=PD14 param_w1_pin_int_pullup=0 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u If it is possible: Any tip on configuration will make me happy. And can it be internal pull up for all 1-wire interfaces?

The system displays two WLANs, but in reality, there is only one onboard wireless network card. The network connection is slow and disconnected. The official system of Orangepi is normal, this issue occur in the new version of the Armbian system. logs：https://paste.armbian.com/eborebaviq

In kernel 6.1.24 default configuration for orangepione and orangepiplus2e is not checked module wireguard, which was previously checked. Is it paraticular reason for this or it's jus mistake. Please can devs make it checked in furure, this saves time when building. Thanks in advance.

Hello! My problem is with paying for OrangePi Plus 2 (not E), but I haven't found a suitable section. Dear administrators, please fix the split if I made a big mistake. I was installed image orangepiplus/Bullseye_current (Nov 30, 2022) in eMMC. All works is normal. In armbian-config I was run Firmware (Update all packages and firmware). Afeter this the board are not loading from eMMC or external CD with current image Armbian. The Ubuntu from site orangepi.org the loading is normal. In debug-uart I see a cyclical reboot with: <0xdd>!␊ ␊ <0xea><0xfc>q<0xb9><0xf6>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 1: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... 2 USB Device(s) found␍␊ scanning bus usb@1c1d000 for devices... Device NOT ready␍␊ Request Sense returned 02 3A 00␍␊ prefetch abort␍␊ pc : [<fffffffa>]⇥ lr : [<bffaa4b3>]␍␊ reloc pc : [<8a077ffa>]⇥ lr : [<4a0224b3>]␍␊ sp : b8a99728 ip : bbf6c038⇥ fp : bffdec47␍␊ r10: ffffffff r9 : bbf67ec0⇥ r8 : b8a99780␍␊ r7 : 00000000 r6 : 00000001⇥ r5 : e59ff014 r4 : 00000000␍␊ r3 : b8a99780 r2 : 00000001⇥ r1 : 00000000 r0 : e59ff014␍␊ Flags: nzcv IRQs off FIQs off Mode SVC_32 (T)␍␊ Code: 0000 0000 0000 0000 (0000) 0000 ␍␊ Resetting CPU ...␍␊ ␍␊ resetting ...␍␊ The problem is that the board no longer wants to load with EXT4, and now it loads only with FAT32. Please tell me how to teach the board to boot from EXT4 again.

Hello all, I setup an orangepi plus2 with Armbian_22.08.2_Orangepiplus_bullseye_current_5.15.69.img I follow tuto and it worked with boot on SD card. I run nand-sata-install Then, I reboot. I was in safe mode and try format emmc Then I reboot again Since, I have only green light. I connect to COM port and see that : U-Boot 2022.07-armbian (Sep 21 2022 - 18:37:27 +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... ** No valid partitions found ** 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... 2 USB Device(s) found scanning bus usb@1c1d000 for devices... Device NOT ready Request Sense returned 02 3A 00 prefetch abort pc : [<fffffffa>] lr : [<bffaa3fb>] reloc pc : [<8a077ffa>] lr : [<4a0223fb>] sp : b8a99728 ip : bbf6b210 fp : bffdeb78 r10: ffffffff r9 : bbf67ec0 r8 : b8a99780 r7 : 00000000 r6 : 00000001 r5 : e59ff014 r4 : 00000000 r3 : b8a99780 r2 : 00000001 r1 : 00000000 r0 : e59ff014 Flags: nzcv IRQs off FIQs off Mode SVC_32 (T) Code: 0000 0000 0000 0000 (0000) 0000 Resetting CPU ... resetting ... After resetting, it loops and again reset without any stop ! I don't understand "Loading Environment from FAT... ** No valid partitions found **" My SD card is Armbian_22.08.2_Orangepiplus_bullseye_current_5.15.69.img flashed with etcher Please, help found how to escape that caveat ! Many thanks

Hello, I have an orange pi plus 2 device. but Armbian 5.69 (5.75 or latest version) above Orangepiplus Ubuntu xenial default can be the url for desktop version. Can you please give me the working url? (By the way, I couldn't find a section for orange pi plus 2 in the forum. )

Hello, I have just updated the latest kernel available on my sbc orangepi+2e with the armbian-config tool and after that it no longer boots. After plugging in the serial port it complains "## Executing script at 44000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid". How can I fix it without having to reinstall everything? I run home-assistant and all the data is on emmc. U-Boot 2019.04-armbian (Jul 15 2019 - 18:03:30 +0200) Allwinner Technology CPU: Allwinner H3 (SUN8I 1680) Model: Xunlong Orange Pi Plus 2E DRAM: 2 GiB MMC: Device 'mmc@1c11000': seq 1 is in use by 'mmc@1c10000' mmc@1c0f000: 0, mmc@1c10000: 2, mmc@1c11000: 1 Loading Environment from EXT4... MMC: no card present In: serial Out: serial Err: serial Net: phy interface7 eth0: ethernet@1c30000 MMC: no card present MMC: no card present starting USB... USB0: USB EHCI 1.00 USB1: USB OHCI 1.0 USB2: USB EHCI 1.00 USB3: USB OHCI 1.0 USB4: USB EHCI 1.00 USB5: USB OHCI 1.0 USB6: USB EHCI 1.00 USB7: USB OHCI 1.0 scanning bus 0 for devices... 1 USB Device(s) found scanning bus 1 for devices... 1 USB Device(s) found scanning bus 2 for devices... 1 USB Device(s) found scanning bus 3 for devices... 1 USB Device(s) found scanning bus 4 for devices... 1 USB Device(s) found scanning bus 5 for devices... 1 USB Device(s) found scanning bus 6 for devices... 1 USB Device(s) found scanning bus 7 for devices... 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Autoboot in 1 seconds, press <Space> to stop switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3798 bytes read in 2 ms (1.8 MiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD MMC: no card present Boot script loaded from mmc 283 bytes read in 0 ms 8378512 bytes read in 403 ms (19.8 MiB/s) Found mainline kernel configuration 33059 bytes read in 7 ms (4.5 MiB/s) 804 bytes read in 3 ms (261.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo 4185 bytes read in 2 ms (2 MiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing... switch to partitions #0, OK mmc1(part 0) is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3798 bytes read in 1 ms (3.6 MiB/s) ## Executing script at 43100000 U-boot loaded from eMMC or secondary SD MMC: no card present Boot script loaded from mmc 283 bytes read in 1 ms (276.4 KiB/s) 8378512 bytes read in 403 ms (19.8 MiB/s) Found mainline kernel configuration 33059 bytes read in 7 ms (4.5 MiB/s) 804 bytes read in 3 ms (261.7 KiB/s) Applying kernel provided DT overlay sun8i-h3-spi-spidev.dtbo 4185 bytes read in 2 ms (2 MiB/s) Applying kernel provided DT fixup script (sun8i-h3-fixup.scr) ## Executing script at 44000000 Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid SCRIPT FAILED: continuing...

Hello! I run Armbian (just updated to version 21) from an 128GByte heavy duty SD card. I am just trying to setup searx (https://github.com/searx/searx) which is using Docker containers. One of the Docker containers won't start, throwing an error message: I searched for long, trying to find some possible solution for this issue. The most fitting seemd to be, where someone said: Yes, it's for another OS and hardware, but I found no other possible solution. So disabling apparmor through a kernel parameter, is what I am trying to achieve. I addded 'apparmor=0' to the bootenv, using armbian-config. I also updated the bootloader using armbian-config (is this necessary after updating env at all?). But: it does not work. dmesg shows the command line as: No 'apparmor=0' in there. And the initial problem with Docker remains. Can you help me please, I don't know how to go on from here .. Thanks! Edit: Btw, there was another issue which seemed to have resolved by itself, but maybe it's important: I did a dist-upgrade from 20 to 21 before. Then I rebooted and installed docker.io and docker-compose - but the docker-compose installation broke with an error, because zram/var/log was full at 49MByte used to 100%. I then uninstalled both, rebooted again, and then installed both packages again, which for some reason worked on the 2nd try ... but now I have noticed that zram/var/log is full most of the time (with no further errors so far..) Is this all right?