-
Posts
28 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
I have installed Armbian 25.02 via an official Armbian image for Armbian 25.02 (Debian 12) Vendor Kernel 6.1.xx, is it possible (and sane) to upgrade to Armbian 25.05 (Debian 12) Vendor Kernel 6.1.xx? If so besides downloading the new image and installing fresh what are one's options?
-
I think I figured out the expert=yes switch a few days ago and built a test vendor kernel image. Works splendidly with the exception of an issue with screen not recovering from going to sleep or some such. Thanks for your assistance eselarm and Werner for the sharing of your expertise.
-
I would love to use Armbian Build to construct a Debian 12 Bookworm images with KDE Plasma as the windows manager. I note that KDE Plasma isn't an option in the armbian builder. I have no problem building with XFCE or Cinnamon.
-
I figured out the issue, after testing multiple EMMC modules. A pin on the connector on the SBC was bent and contacting a neighboring pin. A small needle tool was used to separate the overlapping pins of the connector followed by a clearing of MTD and reinstall of OS from 6.1.99 vendor image of Debian 12 was all that was needed to detect the 233GB emmc modules via lsblk command. I note that attaching the emmc module to connector is easier when the emmc has a heatsink added to assist in seating the module.
-
wget in WSL works with the links for me. I think the issue the within chrome may have something to do with http (not https), when I change http in the link to https it works, or if I browse to the .testing folder. Odd.
-
https link isn't functioning. I click and a new window opens and rapidly closes without automatic download. Using the latest Chrome (Version 135.0.7049.85 (Official Build) (64-bit)) within Windows 11 Pro, no pop-up blocker enabled.
-
Domain resolves, but ftp is not responding, hence links don't work.
-
I used the following image on a microsd card as the source of the bootloader. I note that most of the armbian website's Orange Pi 5 Plus images either fail to support EMMC for me, or lack I2C-2 support in the overlays. I thought perhaps this issue is due to me using a 32 gb ram variant of the SBC, but the missing EMMC is present on 16gb variants as well. I reinstalled a ubuntu environment and compiled the vendor 6.1.99 image for Orange Pi 5 Plus (Debian Bookworm, Full Desktop image), and it boots fine, but no EMMC. A boot from an orangepi5.org debian 12 image does include emmc support, and i2c2-m0 functionality, but does lack functional xrdp.
-
It was wiped, and U-Boot from the sdcard (from a armbian build image) so the unit can boot to NVME.
-
The wiping of SPI & SPNOR were themselves successful processes, the access to EMMC was not. I note this is the 32gb ram variant of the Orange Pi 5 Plus. I have also tried multiple 256 GB EMMC modules, each zeroed out via RKDevTool 3.19. Let me know if any other details would be handy in the diagnosis of this issue. https://paste.armbian.com/rakukijuju
-
Is there a list of Armbian Kernels that include EMMC support? I've tried the vendor kernel build 6.1.99, the LTS 6.12.21, and Bleeding Edge 6.14.0 to find they all lack the mmcblk0 under /dev/ , and lack overlays for it under /boot/dtb/rockchip/overlays/. I have wiped SPI and SPNOR without success.
-
Armbian Kernels with Functional I2C-2 Module
Robert Pace replied to Robert Pace's topic in Orange Pi 5 Plus
I note that edge (6.14.0-rc4) also lacks the i2c2-m0 overlay, so I believe the only function build for i2c2-m0 is found in the older Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img image. -
Armbian Kernels with Functional I2C-2 Module
Robert Pace replied to Robert Pace's topic in Orange Pi 5 Plus
After renaming it showed up in overlays in armbian-config, but takes a good minute to scan the i2c-2 bus, so not a solution for this issue. I note under that a bme280 sensor should show up under address 76 via i2cdetect -y 2. The sensor works fine with same hardware (after installing overlay for I2C2-M0 in armbian-config when using Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img. armbianmonitor -u report: https://paste.next.armbian.com/zanaqiwici Problematic Image: Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img SBC: Orange Pi 5 Plus (32gb) Kernel: Linux orangepi5-plus 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux List of overlays in /boot/dtb/rockchip/overlays/*i2c*.dtbo after copying rk3588-i2c2-m0.dtbo to rockchip-rk3588-i2c2-m0.dtbo -
Armbian Kernels with Functional I2C-2 Module
Robert Pace replied to Robert Pace's topic in Orange Pi 5 Plus
Yes, I meant overlays. Hopefully switching filenames will make them appear. I may need to revisit the previous images for good measure. Thanks Werner, you are always handy with your insight. -
I have built quite a few Debian12 Desktop images from github.com/armbian/build for a Debian Bookworm/XFCE/Vendor Kernel environment and noticed that recent vendor kernels do not have I2C-2.M0 as a kernel module listed within armbian-config. It appears that only two kernel modules are to be found, one being Panthos, the other involving a change in frequence of some item. This image does include I2C-2.mo: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img which includes kernel: Linux Atlas 6.1.99-vendor-rk35xx #1 SMP Fri Feb 21 18:11:03 UTC 2025 aarch64 GNU/Linux But these images do not contain the I2C-2.m0 kernel modules: Armbian-unofficial_25.02.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.84_xfce_desktop.img (same kernel build as Ambian 25.0.2.0-trunk listed above sans I2C-2-m0) Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_current_6.12.17_xfce_desktop.img Armbian-unofficial_25.05.0-trunk_Orangepi5-plus_bookworm_vendor_6.1.99_xfce_desktop.img Is it now necessary to customize the compile options for the kernel and choose that module for compilation when building newer vendor images? It would make sense (to me at least) to have each build option to have vendor kernels contain the same precompiled kernel modules for simplicity sake. I'm not even sure if the I2C-2.m0 is available or an option in the later vendor kernels to build.