All Activity

Your board isn't supported by Armbian. It is Community Maintained. You are the community, PRs are welcome with fixes.

That isn't the full name of the build. Please provide the full name of the image file or the output of armbianmonitor -u

I connect DS18B20 to orange Pi Zero on Armbian 23.02.2 Bullseye with Linux 6.1.63 Via armbian-config in Hardware enabled w1_gpio and add to armbiaEnv.txt param_w1_pin=PA14 param_w1_pin_int_pullup=0 and in overlyas= was w1_gpio cat /sys/bus/w1/devices/28-03165129ecff/w1_slave 54 01 4b 46 7f ff 0c 10 fd : crc=fd YES 54 01 4b 46 7f ff 0c 10 fd t=21250 cat /sys/kernel/debug/gpio gpiochip0: GPIOs 0-223, parent: platform/1c20800.pinctrl, 1c20800.pinctrl: gpio-14 ( |onewire@0 ) out hi gpio-17 ( |orangepi:red:status ) out lo gpio-20 ( |reg_vcc_wifi ) out hi gpio-166 ( |cd ) in lo ACTIVE LOW gpio-204 ( |usb0_id_det ) in hi IRQ dmesg |grep wire* [ 9.398674] Driver for 1-wire Dallas network protocol. [ 9.410366] gpio-14 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file [ 9.463654] w1_master_driver w1_bus_master1: Attaching one wire slave 28.03165129ecff crc 24 so all working very well on OZPI v1 with kernel 6.163 on Armbian 23.02.2 So my DS18B20 is work but on OZPI v3 with 6.6.30 kernel and user overlay for w1-gpio not work for me. It maybe we need more add in overlay for w1-gpio.dts?

Hello everyone ! I'm facing a hard issue that I still cannot solve. On my Raspberry, on Raspberry Os, to be able to use Rustdesk (https://github.com/rustdesk/rustdesk, an open source Teamviewer ) I needed to add some tweaks to the /boot/config.txt file: hdmi_force_hotplug=1 (See doc) hdmi_group=2 (See doc) Now, I'm trying to replicate these behaviours on Armbian for Opi zero 3 (but it could probably work for all Allwinner cpus if a solution is found) When looking on the Armbian documentation for Sunxi, I've found this (See doc) : For example to always use the hdmi connector, even if no cable is inserted, using edid info when available and otherwise initalizing it at 1024x768@60Hz, use: setenv video-mode sunxi:1024x768-24@60,monitor=dvi,hpd=0,edid=0 That really looks like what I want to achieve, but when adding this line to the /boot/boot.cmd file, re-building it using: mkimage -C none -A arm -T script -d /boot/boot.cmd /boot/boot.scr and after rebooting, I still can't connect to my distant Opi. Am I missing something? Did someone has faced something similar? Thanks for any help !

Description Rewrite with: ./compile.sh rewrite-kernel-config BOARD=board BRANCH=branch How Has This Been Tested? [ ] CI Checklist: Please delete options that are not relevant. [ ] My changes generate no new warnings View the full article

Description Added a call to losetup -f which would make sure that there is a loop device that exists and available for use. See #6568 Added doas support to is_root_or_sudo_prefix function. I will understand if this change would be asked to be removed, added just because I use doas. Jira reference number AR-2132 How Has This Been Tested? Building using the command ./compile.sh BOARD=orangepi5 BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=no KERNEL_CONFIGURE=no KERNEL_GIT=shallow RELEASE=bookworm on my machine. For some reason fails on the first try, creating the device and not finding it, but the second run succeeds. Checklist: Please delete options that are not relevant. [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

Hello, I found a temporary solution to the problem: Here are the steps: aptitude remove zfs-dkms aptitude install zfs-zed=2.2.3-1~bpo12+1 zfsutils-linux=2.2.3-1~bpo12+1 zfs-dkms=2.2.3-1~bpo12+1 aptitude install libnvpair3linux=2.2.3-1~bpo12+1 libzfs4linux=2.2.3-1~bpo12+1 libuutil3linux=2.2.3-1~bpo12+1 libzfs4linux=2.2.3-1~bpo12+1 libzpool5linux=2.2. 3-1~bpo12+1 aptitude install zfs-zed=2.2.3-1~bpo12+1 zfsutils-linux=2.2.3-1~bpo12+1 aptitude hold libnvpair3linux libuutil3linux libzfs4linux libzpool5linux zfs-dkms zfs-zed zfsutils-linux After "locking" the packages, you should see this: root@msrv 48.07℃ :~# apt-mark showhold libnvpair3linux libuutil3linux libzfs4linux libzpool5linux zfs-dkms zfs-zed zfsutils-linux systemctl enable --now zfs-scrub-weekly@ZPOOL.timer systemctl enable --now zfs-trim-weekly@ZPOOL.timer - if the array is on SSD It would be nice from the armbian team to fix things Actually, the new versions of zfs-dkms and zfsutils-linux come from the armbian repo, and these packages look for the libssl3t64 package, which is not present in Debian Bookworm, but is present in Debian Sid. I assume the Debian packages are compiled on top of Ubuntu, which is based on the Debian Sid. Regards,

I checked new sensor DS18B20 but still the same error in dmesg info, so I will try with my RPI or OZPI v1 z kernel 6.1 check use w1-gpio overlay

Armbian-unofficial 24.2.0-trunk Jammy

Let's start with what build of Armbian do you have installed?

Hello. I also had such a problem some time ago. I don't know how much experience you have with linux. Probably missing the /boot stuff. You can try the following, but it's a bit risky. You make an mmc card with arbian and kernel 6.1.XX. and you start nanopc from it. After it loads. You put in a USB to SD card adapter. In the new memory card, after loading the OS, create an OMV folder, in it /OMV/boot and /OMV/os/ in it you create /OMV/boot and /OMV/os/ rsync -va /boot/ /OMV/boot/ mv /OMV/os/lib/modules/6.1.43-vendor-rk35xx /OMV/os/lib/modules/6.1.43-vendor-rk35xx_old rsync -va /lib/modules/6.1.43-vendor-rk35xx /OMV/os/lib/modules/ After that, umount /OMV/boot and /OMV/os/, put the OMV card in the nanopc and if you're lucky, it might start. I hope I was helpful and good luck

Hello, I have ZFS installed, today there was an update, in which I no longer have ZFS. root@msrv 49.00℃ :~# apt dist-upgrade Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: libnvpair3linux libuutil3linux libzfs4linux libzpool5linux Use 'apt autoremove' to remove them. The following packages will be REMOVED: zfs-zed zfsutils-linux The following packages have been kept back: libnvpair3linux libzfs4linux The following packages will be upgraded: libuutil3linux libzpool5linux zfs-dkms 3 upgraded, 0 newly installed, 2 to remove and 2 not upgraded. Need to get 0 B/3,598 kB of archives. After this operation, 2,533 kB disk space will be freed. Do you want to continue? [Y/n] Y Preconfiguring packages ... (Reading database ... 71907 files and directories currently installed.) Removing zfs-zed (2.1.11-1) ... Removing zfsutils-linux (2.2.3-1) ... (Reading database ... 71592 files and directories currently installed.) Preparing to unpack .../libuutil3linux_2.2.3-2_arm64.deb ... Unpacking libuutil3linux (2.2.3-2) over (2.2.3-1) ... Preparing to unpack .../libzpool5linux_2.2.3-2_arm64.deb ... Unpacking libzpool5linux (2.2.3-2) over (2.2.3-1) ... Preparing to unpack .../zfs-dkms_2.2.3-2_all.deb ... Module zfs-2.2.3 for kernel 6.1.43-vendor-rk35xx (aarch64). Before uninstall, this module version was ACTIVE on this kernel. zfs.ko: - Uninstallation - Deleting from: /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. spl.ko: - Uninstallation - Deleting from: /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ - Original module - No original module was found for this module on this kernel. - Use the dkms install command to reinstall any previous module version. depmod... Deleting module zfs-2.2.3 completely from the DKMS tree. Unpacking zfs-dkms (2.2.3-2) over (2.2.3-1) ... Setting up zfs-dkms (2.2.3-2) ... Loading new zfs-2.2.3 DKMS files... Building for 6.1.43-vendor-rk35xx Building initial module for 6.1.43-vendor-rk35xx Done. zfs.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ spl.ko: Running module version sanity check. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/6.1.43-vendor-rk35xx/updates/dkms/ depmod... Setting up libuutil3linux (2.2.3-2) ... Setting up libzpool5linux (2.2.3-2) ... Processing triggers for libc-bin (2.36-9+deb12u7) ... Processing triggers for man-db (2.11.2-2) ... Processing triggers for initramfs-tools (0.142) ... ln: failed to create hard link '/boot/initrd.img-6.1.43-vendor-rk35xx.dpkg-bak' => '/boot/initrd.img-6.1.43-vendor-rk35xx': Operation not permitted update-initramfs: Generating /boot/initrd.img-6.1.43-vendor-rk35xx W: Possible missing firmware /lib/firmware/rtl_nic/rtl8125a-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8107e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168fp-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168g-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8106e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8411-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8402-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168f-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8105e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-3.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168e-1.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-2.fw for module r8169 W: Possible missing firmware /lib/firmware/rtl_nic/rtl8168d-1.fw for module r8169 W: Possible missing firmware /lib/firmware/regulatory.db for built-in driver cfg80211 W: Possible missing firmware /lib/firmware/regulatory.db.p7s for built-in driver cfg80211 update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.1.43-vendor-rk35xx Image Name: uInitrd Created: Sat May 11 11:42:20 2024 Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 9305942 Bytes = 9087.83 KiB = 8.87 MiB Load Address: 00000000 Entry Point: 00000000 update-initramfs: Armbian: Symlinking /boot/uInitrd-6.1.43-vendor-rk35xx to /boot/uInitrd ln: failed to create symbolic link '/boot/uInitrd': Operation not permitted update-initramfs: Symlink failed, moving /boot/uInitrd-6.1.43-vendor-rk35xx to /boot/uInitrd renamed '/boot/uInitrd-6.1.43-vendor-rk35xx' -> '/boot/uInitrd' update-initramfs: Armbian: done. root@msrv 48.07℃ :~# Fortunately, the module is on and everything is working now. ZFS is from the armbian repo. When I try to install I get this: root@msrv 47.15℃ :~# aptitude install zfs-zed zfsutils-linux The following NEW packages will be installed: libuutil3linux{a} zfs-zed{b} zfsutils-linux{b} 0 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded. Need to get 541 kB/666 kB of archives. After unpacking 2,696 kB will be used. The following packages have unmet dependencies: zfs-zed : Depends: libnvpair3linux (>= 0.8.2) but it is not installable Depends: libzfs4linux (>= 2.1.11-1) but it is not installable zfsutils-linux : Depends: libnvpair3linux (= 2.2.3-2) but it is not installable Depends: libzfs4linux (= 2.2.3-2) but it is not installable Depends: libzpool5linux (= 2.2.3-2) but it is not installable Depends: libssl3t64 (>= 3.0.0) which is a virtual package and is not provided by any available package The following actions will resolve these dependencies: Keep the following packages at their current version: 1) zfs-zed [Not Installed] 2) zfsutils-linux [Not Installed] Accept this solution? [Y/n/q/?] Y No packages will be installed, upgraded, or removed. 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B of archives. After unpacking 0 B will be used. Any ideas on how to fix it and/or what to provide as additional information

-console connection would help ( bootlog ) -so would an earlier backup of that SD Card... ( make a backup of it now anyway ) personally i'd just stick with the new OS ( a year is pretty long in the tooth )... and new card... then just scp/rsync whatever is critical over to the new OS. other than that try running a fsck, / seeing what the console says (edit: sorry i messed the beginners bit...)

Hi - I installed the latest images but unfortunately the GPU is not accelerated. Somebody has an idea how to use the PANFROST drivers? name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Mesa/X.org (0xffffffff) Device: llvmpipe (LLVM 15.0.6, 128 bits) (0xffffffff) Version: 22.3.6 Accelerated: no Video memory: 3932MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 4.5 Max compat profile version: 4.5 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.2 OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 15.0.6, 128 bits) OpenGL core profile version string: 4.5 (Core Profile) Mesa 22.3.6 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL version string: 4.5 (Compatibility Profile) Mesa 22.3.6 OpenGL shading language version string: 4.50 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

In pavucontrol, which is the Configuration in Volume Control, set the second Audio to off and exit. After playing the audio and opening the Volume Control at the same time, this problem will not occur and can be adjusted normally My understanding is that two Audio may have output conflict?

Description remove kinetic, lunar, mantic fix armhf sid, noble, oracular How Has This Been Tested? [x] Manual tests on affected Checklist: [x] My changes generate no new warnings [x] Any dependent changes have been merged and published in downstream modules View the full article

Hello, excuse me, can you share the images you have about s812 s805?

I'm half way feeling that it may be possibly to use DS18B20 using gpiod / libgpiod https://git.kernel.org/pub/scm/libs/libgpiod/libgpiod.git/tree/ I tried googling around but thare are lots of offers for DS18B20 many of which use w1-gpio as you are doing the timing requires for DS18B20 fig 16 page 16 https://www.analog.com/media/en/technical-documentation/data-sheets/DS18B20.pdf from 15 uS to 60 uS per bit of data isn't after all that impossible to synchronize the hard part about libgpiod is the timing part as sending and receiving data is timing sensitive, if there is a way to do that to read and write data in sync with tight timing it is possibly feasible to do so even in python. i.e. no kernel drivers, the python (or c etc) codes simply use libgpiod and work the signals. I've thus far not (yet) found one based on libgpiod admist the 'noise' returned from the searches, maybe try searching around and you may find an existing implementation that's already done. ether way, you seemed to have *achieved* making w1-gpio work, perhaps try connecting a sensor to see if the dmesg changes. the hint is [ 4.997833] w1-gpio onewire@0: gpio_request (pin) failed [ 4.997841] w1-gpio: probe of onewire@0 failed with error -22 if w1-gpio does a 'probe' it is probably sending the 'reset' signal to the chip and waiting for a response

Thank you for your answer and suggestions. Hmm, the problem is that I have a DS18B20 sensor connected to OZPIv3, which I used in another project on another SBC. PIN DATA DS18B20 is connected to PC10 and through the 4k7 resistor to VCC 3.3V and the third pin DS18B20 to GND I will have to check this sensor again to see if RPI or OZPIv1 works on the 6.1.x kernel or I will take another unit for testing.

I'm trying to enable GPU support for watching youtube on orange pi 2 zero w model. But there is no Mali driver and even kernel package How can I enable this?

good morning everyone, I installed Armbian 23.02.2 on orangepizero about a year ago without ever having a problem . Today it suddenly stopped booting and I can't get it to start again and that's what I'm interested in, also possibly to recover internal docker configurations. The orangepizero is powered by a 3A power supply under UPS and properly cooled, if I use the latest release on a new SD it works perfectly, so I think it is not a hardware problem. The SD with Armbian 23.02.2 is not corrupted and I can read every part of it. Does anyone know any tricks to get it running again?

Hi all, I have some x905 boxes and I'd like to use one (an old TX95 -> x905w IIRC) as a midi sequencer with fluidsynth. I found the hard way that the default kernel has no midi sequencer support (in kernel or module) so there's no way to use aconnect and have it as a midi box. The only solution seems to be rebuild the kernel with the added module support but it's been decades since last time i rebuilt a kernel and S905 kernels (with added balbes150 mods and stuff to have it working on those cheap boxes) seems a bit too complex for me. So the question is: is there a way to get a working kernel with midi support, and how to put it in. If this wasn't really feasable: how could a mere mortal (with some knowledge) rebuild an x905w kernel, pack it and install without breaking the whole thing in the process ? ( I'm not interested in a GUI or similar, it would work as headless with the RCA out for audio )

Sorry, I don't have a device that supports hdmi audio I tried to use mpg123 to play audio, but as long as the Volume Control is turned on, the bug also appeared I'm still new to audio and video, so I don't know how to solve it

I have remove the armbian-firmware #apt remove armbian-firmware just need to restart it once today. I still trying to find the deb package for older version of armbian-firmware couldn't find it on https://mirror.yandex.ru/mirrors/armbian/archive/orangepione/archive/ for info, I run the board for Pi-Hole using the cloudflared. The second service is a smbd server for low throughput usage in LAN the symtomps after armbian-firmware update to 24.2.1 is a hot cpu, so it might be the system cannot cope with the temperature and just hangs (I do not put any cooling / heatsink for 2 years and its working fine because of the low usages) any suggestion to a armbian-firmware.deb file that i can dpkg is appreciated. thanks

@sakesm Yes i came across that also. Can you confirm that it only happens on analog audio and not on HDMI and when using pulseaudio. I also tested with mpg123 and did not have problems using the mpg123 built in volume controls.