Active threads

Ethernet is supposedly broken by design. While Xunlong is working on a hw revision of this board it is to be expected that it will be released under the same name which will then ultimately contribute to users confusion why on some boards eth works and on others not. Therefore get rid of this one altogether. https://github.com/armbian/build/issues/6587 View the full article

Unfortunately, my programming knowledge is low and knowledge of DTS Overlays + source code of w1-gpio linux kernel does not allow me to find the source of the problem [ 4.997793] sun50i-h616-pinctrl 300b000.pinctrl: pin PC10 already requested by onewire@0; cannot claim for 300b000.pinctrl:74

rk35xx: drop vendor-boogie-panthor BRANCH; it has been integrated into vendor rk35xx: drop vendor-boogie-panthor BRANCH; it has been integrated into vendor This reverts commit 5f59fe63f19391eea3f1d7f99e62db9bbc9c961f View the full article

multiple boards: fixes for board file syntax / missing vars (fixing JSON matrix prepare) multiple boards: fixes for board file syntax / missing vars (fixing JSON matrix prepare) BOARD_MAINTAINER must exist Every board file needs some variables defined, since they're parsed directly (and sources/includes are not resolved) View the full article

Description Same as #6588 for v24.05 branch View the full article

thanks for replying @Stephen Graf. I rather want to try using the older armbian-firmware package and keep the newer kernel, since the problem only shows up after I upgrade the firmware. currently it still hangs after 15-20 hours. can I extract the firmware from and image? the post from @ER Samson mention vnstat. I do not use it, and the package is not installed. i did use htop to check what's using the cpu. but nothing extensive. I haven't check the governor prior the deletion of firmware. currently is "on-demand"

I would not use ZFS with this kernel if I were you. This kernel is provided by hw vendor, by people / business that only cares about (selling) hardware features to work. Everything else is unmaintained and open source community (not just Armbian) developers are not even thinking to maintain this kernel outside that as its concorde fallacy. FYI - it is highly possible ZFS implementation is affected, but you are FREE to do whatever. 90% of solutions, not workarounds, Armbian team (a few people) is unable to integrate into OS with their private resources, public (thousands of you) are simply not there. I can estimate, we could integrate about 30% of resolved suggestions this community generate with few full time engineers. Which costs money. Until you are satisfied with reporting problems only, until you don't care that a lot of value is wasted, there is nothing we can do but keep trying to provide "best effort" support with what we have and explaining this situation. Users perspective will always be like we refuse to help ... but people that are working on / helping Armbian are already long maxed out in efforts of helping everyone, even our competitors. Also. Hardware vendors have exploit of open source community build into their business model. If it happens that you are using hardware with terrible vendors reputation, bugs can be written, but are last to be resolved, some bugs are never resolved ... If you really wanna help everyone, start here: https://github.com/armbian/os/wiki/Import-3rd-party-packages Study and implement a solution. We also have automated dependency testing, which should prevent this problem in first place, but ain't working well and it wouldn't help much in this case. ZFS package is imported from Trixie and yes I understand that upstream package dependency has been recently changed. Until a month ago, we didn't have this problem, everything was working right and now, there is little we can do except disabling importing (which will also delete packages from repository). We don't compile those packages on our own and I am aware that this is not the best way. There are more workarounds - like using Trixie or Noble user space ... Its sadly under-powered, too small. Math is simple - I would very much like to help, but costs are the one that are killing us. Imagine that fixing a problem costs 1000 USD. You are willing to pay 5 USD (or not even that), which is fair if there would be more people contributes their share that you cover all costs. This never happens. They come with another and another problem for 1000 USD (often a lot more, sometimes a lot less) instead. Then its expected that we pay the rest, 995 USD for costs of resolving community software problem, this is simply not sustainable way of cooperation. Even the bug was made by us. I am trying to keep ZFS available. Do you have any idea how much time loss this service already caused with no benefits whatsoever? There are thousands of bugs in open source software and most of people pin everything on us after they download "Armbian image" and images that are produced by copycats as they claim "its Armbian". This particular problem was introduced by us, yes, but alternatively would be not providing ZFS that is capable of working with recent kernels. Which touches to the core of embedded Linux experience and logic. Often we can't match user space and kernel like this is done on 1st class x86 desktop / server / hw Linux world. Even they, often breaks critical things too, even with thousands of full time employees (Redhat). We can't provide that level of services with close to nothing from your side.

Description Set correct video firmware based on the device being used. Fixes - https://forum.khadas.com/t/ffmpeg-and-hardware-h264-decode/19033/24 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Checked that the preload service starts correctly on vim4 and video_code.bin file points to correct firmware file. Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

hello luis , try this :https://drive.google.com/drive/folders/1ls4jTIl00CJ3UFQipGdOYmrN0XBnfJlS?usp=sharing

hi wulfy23, the problem is that you cannot use the console because the operating system no longer starts. If I extract the sd card and read it from the computer though, I can see all the OS files.

moved

moved

Wifi works flawlessly with recent image. Includes Link Quality and Signal Level

Attempting Armbian install onto an S905. Hardware specs at https://specdevice.com/showspec.php?id=6653-4ac9-1101-570d0033c587 Kernel begins to boot but gets errors and never completes dropping into initramfs shell. Was able to capture the dtb blob from the Android kernel and decompiled it. Enough differences to the dtb files in the Armbian distribution that I cannot figure out how to create a dtb file that will work. Have looked for other files on the internet but haven't come across something similar yet. Booting gets stuck in a loop of: meson-gx-mmc d0072000.mmc: no support for card's volts mmc0: error -22 whilst initialising SDIO card. mmc0: Card stuck being busy! __mmc_poll_for_busy Any feedback or guidance appreciated.

Description systemctl reload-or-restart ssh prevents botching job if sshd is started by socket How Has This Been Tested? Quite harmless change which broadens systemctl tolerance towards services, no negative impacts expected Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Description systemd-resolved is installed and enabled by default - unfortunately a static /etc/resolv.conf nameserver 1.0.0.1 set up during debootstrap phase is preventing systemd-resolved to do its job Removing the file after chroot has been finalized in post-tweaks.sh enables systemd-resolved to symlink /etc/resolv.conf to /run/systemd/resolved/stub-resolv.conf on first boot How Has This Been Tested? [x] Rebuilt an booted an Orangepi5-plus debian trixie image from trunk Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] My changes generate no new warnings View the full article

Which SoCs and on which branch can have extensions enabled? 4l2loopback-dkms mesa-oibaf here: https://github.com/armbian/os/blob/main/userpatches/targets-release-standard-support.yaml#L40-L95 Mapping config: https://github.com/armbian/os/blob/main/userpatches/targets-extensions.map

Nevermind, I just erased & installed the latest version and now sequencer works. Sorry for the trouble.

@sakesm Thank you for the update. I don't have a lot of experience with audio either. Usually it just works. With mpg123 you can adjust volume with the + and - keys, which I think do not cause any problems.

Description sid and unstable are synonyms of the same repository Credits: going --> https://forum.armbian.com/topic/37503-kali-linux-as-supported-distro/ [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code View the full article

Description /boot/armbianEnv.txt for rockchip64 doesn't preconfigure any console output by default - so "console=both" has been added to config/sources/families/rockchip64.txt to enable serial and display console at build time How Has This Been Tested? [x] Rebuilt orange5-plus trunk and booted correctly 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] My changes generate no new warnings View the full article

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 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

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