All Activity

ok, thx

It's enabled by default. I believe that you have the wires swapped. There's a topic here about it where I also added a overlay to adjust what speed at which temperature. I'm not sure if the overlay is still compatible, but since you've already found the source you can change it accordingly.

There is usually only one or two images built per board. That's enough to make sure it compiles properly. All other combinations can be made DIY with the framework, check documentation. Continous Integration https://en.wikipedia.org/wiki/Continuous_integration

ok , so no special procedure exists. There is only minimal image is accessible for download for bpi pro. Does It mean all other failed or nobody tried to build them? Random images are accessible from archive too. What does "CI" stand for?

Our CI produces automated builds which are published here: https://github.com/armbian/community/releases If a build fails we will notice and fix if it doesn't much effort. Otherwise it's demoted to EOS and autobuilds disabled.

Hello everyone, I flashed the armbian into my tf cand and inserted it into my OrangePi 5 Plus, with my fans inserted to the specific socket on board (2pin, 1.25mm, 5V, PWM3_IR_M1). However, when I booted it, the fans was running constantly instead of controlled by temperature dynamically, like the official OS images that did only the fans running when the temperature over 50 celsius. I wanna know how to configure my OS to enable the temperature-controlled fans like the official images. The offical documents shows: Linux uses the default pwm-fan drivers to control thye fans and the device tree was defined in orange-pi-5.10-rk3588/arch/arm64/boot/dts/rockchip/rk3588-orangepi-5-plus.dts Here is the code: fan: pwm-fan { compatible = "pwm-fan"; #cooling-cells = <2>; pwms = <&pwm3 0 50000 0>; cooling-levels = <0 50 100 150 200 255>; rockchip,temp-trips = < 50000 1 55000 2 60000 3 65000 4 70000 5 >; status = "okay"; }; Here are some descriptions regarding some columns: pwms = <&pwm3 0 50000 0>：The fans use pwm3. cooling-levels = <0 50 100 150 200 > 255>：Used to configure the speed levels (duty cycle of PWM). The number and magnitude of the levels can be customized. 6 levels are configured, with the speed range from 0 to 255. rockchip,temp-trips：Used to configure the correspondence between CPU temperature and fan speed levels. This can be adjusted according to actual needs. In the above configuration, 50°C corresponds to level 1, and 70°C corresponds to level 5. Thank you very much.

mihanson@armbi400:~$ sudo poweroff Broadcast message from root@armbi400 on pts/0 (Thu 2025-09-04 07:29:16 PDT): The system will power off now! mihanson@armbi400:~$ [41893.451514] reboot: Power down [41893.454658] ------------[ cut here ]------------ [41893.459337] Voluntary context switch within RCU read-side critical section! [41893.459354] WARNING: CPU: 0 PID: 1 at kernel/rcu/tree_plugin.h:331 rcu_note_context_switch+0x4e0/0x530 [41893.475859] Modules linked in: sg rfcomm cmac aes_arm64 algif_hash algif_skcipher af_alg bnep zram zsmalloc binfmt_misc hci_uart btbcm bluetooth ecdh_generic ecc bcm2835_codec(C) bcm2835_v4l2(C) bcm2835_isp(C) bcm2835_mmal_vchiq(C) v4l2_mem2mem vc_sm_cma(C) videobuf2_dma_contig videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_bcm2835(C) videodev snd_pcm videobuf2_common snd_timer mc raspberrypi_hwmon snd raspberrypi_gpiomem i2c_dev drm drm_panel_orientation_quirks backlight fuse bonding ipv6 brcmfmac_wcc brcmfmac cfg80211 rfkill brcmutil uio_pdrv_genirq uio nvmem_rmem [41893.527454] CPU: 0 UID: 0 PID: 1 Comm: systemd-shutdow Tainted: G C 6.12.44-current-bcm2711 #1 [41893.537603] Tainted: [C]=CRAP [41893.540606] Hardware name: Raspberry Pi 400 Rev 1.0 (DT) [41893.545989] pstate: 600000c5 (nZCv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [41893.553048] pc : rcu_note_context_switch+0x4e0/0x530 [41893.558080] lr : rcu_note_context_switch+0x4e0/0x530 [41893.563112] sp : ffff80008002b770 [41893.566466] x29: ffff80008002b770 x28: ffff2262c6ffb3c0 x27: ffff2262c0c5f8c0 [41893.573707] x26: ffff2262c0260000 x25: ffffcc22d85831f4 x24: 0000000000000000 [41893.580947] x23: 0000000000000000 x22: ffff2262c0260000 x21: ffffcc22d98b3070 [41893.588187] x20: 0000000000000000 x19: ffff22637b779fc0 x18: 0000000000000006 [41893.595426] x17: ffffcc22d97fb000 x16: 00000000a53a0512 x15: ffff80008002b0d0 [41893.602666] x14: 0000000000000000 x13: 216e6f6974636573 x12: 206c616369746972 [41893.609905] x11: 6320656469732d64 x10: ffffcc22d96d7a28 x9 : ffffcc22d7724ed8 [41893.617145] x8 : 00000000ffffefff x7 : ffffcc22d96d3960 x6 : 00000000000002b3 [41893.624384] x5 : 00000000000002b4 x4 : 40000000fffff2b3 x3 : 0000000000000000 [41893.631623] x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff2262c0260000 [41893.638863] Call trace: [41893.641336] rcu_note_context_switch+0x4e0/0x530 [41893.646016] __schedule+0xb4/0xe70 [41893.649463] schedule+0x3c/0x148 [41893.652733] schedule_timeout+0x98/0x1a0 [41893.656709] wait_for_completion_timeout+0x80/0x160 [41893.661653] mbox_send_message+0xf8/0x140 [41893.665716] rpi_firmware_property_list+0x104/0x298 [41893.670662] rpi_firmware_property+0x78/0xc8 [41893.674988] rpi_exp_gpio_get_polarity+0x68/0x100 [41893.679760] rpi_exp_gpio_dir_out+0x6c/0x120 [41893.684089] gpiod_direction_output_raw_commit+0x6c/0x348 [41893.689562] gpiod_direction_output+0xa8/0x1b8 [41893.694065] gpio_poweroff_do_poweroff+0x2c/0xd0 [41893.698747] sys_off_notify+0x48/0x80 [41893.702458] notifier_call_chain+0x80/0x140 [41893.706699] atomic_notifier_call_chain+0x44/0x70 [41893.711468] do_kernel_power_off+0x5c/0x80 [41893.715618] machine_power_off+0x40/0x58 [41893.719594] kernel_power_off+0x88/0x98 [41893.723479] __do_sys_reboot+0x1e0/0x240 [41893.727452] __arm64_sys_reboot+0x2c/0x40 [41893.731514] invoke_syscall+0x50/0x120 [41893.735314] el0_svc_common.constprop.0+0x48/0xf0 [41893.740083] do_el0_svc+0x24/0x38 [41893.743441] el0_svc+0x38/0x120 [41893.746622] el0t_64_sync_handler+0x120/0x130 [41893.751037] el0t_64_sync+0x190/0x198 [41893.754745] ---[ end trace 0000000000000000 ]--- 25.8.1 Trixie Armbian image and EXT4 FS. Does not happen on reboot, just poweroff. The below also produce the same result. $ sudo shutdown -H now $ sudo systemctl poweroff mihanson@armbi400:~$ armbianmonitor -u Collecting info and sending to paste.armbian.com, wait... Failed grabbing info (pipe 3 result 22) and sending to server paste.armbian.com. Collecting info and sending to paste.next.armbian.com, wait... https://paste.next.armbian.com/oxawoposil Please post the URL in the forum where you've been asked for.

OK, how should i understand build test?

Yes, csc boards are not actively monitored. Build test only.

As I understood they are not tested, am I right?

moved

Hi! I'm building a custom board for the AM69 processor, which is similar to AM68. My question is if there is any Arabian support for AM69 with web browsing e.g Chromium with streaming ability such as Youtube/Netflix etc? Any pre-compiled builds?

When things are not actively monitored, features stopped working without knowing. This has to be find out. At least all Armbian distributions have the same kernel, regardless of its upstream origin - Debian X,Y,Z and Ubuntu A,B,C ... have same kernel. But of course kernels versions go up all the time. I am not managing this that deep / specific. Where to search? On this forum. I am sure that this was already brought up.

@LanMarc77, I think you meant to tag @laibsch there What you're saying sounds like it could be a good option.

Actually, the connections on the cable harness appear to be good as well as all the capacitors. They are not expanded and they are not leaking--and no, I am not certain. I did not consider that it might be a board issue because I sniffed the board, there were no unusual odors when the system is powered up. Visually nothing appeared burnt. The failure occurred randomly after functioning for 4+ years. It has always been connected to an Online UPS that supports AVR, and Pure Sinewave on my server rack. I am not proficient at soldering, nor do I have a microscope, soldering iron or any of the required accessories to attempt a repair. For testing purposes, yesterday, I supplied power using an external power source from a USB enclosure and it worked. SATA Ports 1 and 2 are both functional, it is definitely related to power. I am meeting with my CEO tomorrow to discuss purchasing a new NAS type system. Leaning towards an HPE MicroServer Gen11. Going from a fantasic little affordable unit to an actual server that is going to cost around CAD$4,000 (price includes HDDs). YIkes. Thank you to everyone that took the time to read and reply though. I appreciate you, your time, and your suggestions. I was hoping I could just buy a cable and move on lol.

Alright, let's give a real quick overview where the code for A20 comes from. Let's focus on current. First stop. Board config: https://github.com/armbian/build/blob/main/config/boards/bananapipro.csc -> BOARDFAMILY="sun7i" Next stop. Family config: https://github.com/armbian/build/blob/main/config/sources/families/sun7i.conf -> No sources defined. However there are includes. Next stop. Includes: https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> No kernel source URL defined. Therefore kernel comes from mainline (kernel.org to say). However a version is tagged: v6.12.43 So we know: Linux source comes from unmodified mainline and the version is 6.12.43 Next stop. Patches: https://github.com/armbian/build/tree/main/patch/kernel/archive/sunxi-6.12 -> vendor family = sunxi, kernel major.minor is 6.12 All these patches are applied on top of the kernel source from kernel.org. And yes, that's a lot. I think sunxi is the worst family regarding number of additional patches to make stuff work. Next component is u-boot. https://github.com/armbian/build/blob/main/config/sources/families/include/sunxi_common.inc -> BOOTBRANCH:-"tag:v2024.01" so uboot is tagged to this version. So we know: U-Boot source comes from unmodified mainline and the version is v2024.01. And BOOTPATCHDIR="${BOOTPATCHDIR:-"u-boot-sunxi"}" which means here we find the patchset put on top of that version. Let's check. https://github.com/armbian/build/tree/main/patch/u-boot/u-boot-sunxi -> folders starting with board_ are applied only if the target board is being built. All remaining paches are always applied. There are more definitions of stuff appling for multiple families, whole architectures or even all boards regardless of architecture but in this case they are not important. Just including for the sake of completion/information: https://github.com/armbian/build/blob/main/config/sources/armhf.conf https://github.com/armbian/build/blob/main/config/sources/common.conf Good luck.

@grendel Sure you're certain you need a new cable harness? A few years ago, I replaced the HDD power switches myself, they’re just small smd transistors. 1 and 2 (Channel A) power on simultaneously, followed by 3, 4, and 5 (Channel B). There’s a built-in delay between the two channels to help manage voltage spikes that occur during HDD initialization — Channel A starts first, then Channel B.

Well I tried everything to make it work, including switching from PoE to a proven USB power supply, nothing worked. The only thing that worked is flashing back the latest Radxa bullseye image with 5.10.110 kernel, and upgrading to bookworm. I have a lot of errors at boot, so I might consider updating the kernel at some point, but I have absolutely no idea how to do that without flashing a new image. Considering 5.10.110 is the last kernel available from Radxa, I think I'm stuck... I suppressed the radxa apt in the sources.list as there is no bookworm apt, only bullseye. Could I still use the bullseye radxa apt with a bookworm debian? [ 59.024477] ramoops ramoops: failed to locate DT /reserved-memory resource [ 59.084556] fiq_debugger fiq_debugger.0: IRQ fiq not found [ 59.084581] fiq_debugger fiq_debugger.0: IRQ wakeup not found [ 59.084597] fiq_debugger_probe: could not install nmi irq handler [ 60.711536] rockchip-usb2phy ff770000.syscon:usb2-phy@e450: IRQ index 0 not found [ 60.714528] rockchip-usb2phy ff770000.syscon:usb2-phy@e460: IRQ index 0 not found [ 60.723981] rkvdec_init:1230: failed on clk_get clk_hevc_cabac [ 60.724074] mpp_rkvdec ff660000.rkvdec: shared_video_hevc_cabac is not found! [ 60.724090] rkvdec_init:1261: No hevc cabac reset resource define [ 60.746975] rockchip-vop ff8f0000.vop: missing rockchip,grf property [ 60.747264] rockchip-vop ff900000.vop: missing rockchip,grf property [ 60.750685] no ATF memory for init [ 60.763340] no ATF memory for init [ 60.767736] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [ 61.067311] vcc_cam: failed to get the current voltage: -EPROBE_DEFER [ 61.067671] vcc_mipi: failed to get the current voltage: -EPROBE_DEFER [ 61.090893] vcc_sdio: unsupportable voltage range: 3300000-3000000uV [ 61.094146] rockchip-dmc dmc: Failed to get ddr_leakage [ 61.094884] rockchip-dmc dmc: could not find power_model node [ 61.099683] rksfc_base v1.1 2016-01-08 [ 61.695258] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 61.695324] rockchip-pcie f8000000.pcie: deferred probe failed [ 69.217783] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.309154] rk-multicodecs es8316-sound: ASoC: Property 'rockchip,audio-routing' does not exist or its length is not even [ 69.456788] debugfs: File 'Left Hp mixer' in directory 'dapm' already present! [ 69.456983] debugfs: File 'Right Hp mixer' in directory 'dapm' already present! [ 69.457046] debugfs: File 'HPCP L' in directory 'dapm' already present! [ 69.457078] debugfs: File 'HPCP R' in directory 'dapm' already present! [ 69.457127] debugfs: File 'HPVOL L' in directory 'dapm' already present! [ 69.457157] debugfs: File 'HPVOL R' in directory 'dapm' already present! [ 70.938277] udc fe800000.usb: failed to start radxa-otgutils: -19 [ 81.008640] ieee80211 phy0: brcmf_escan_timeout: timer expired [ 89.540144] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540187] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.540706] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.540728] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 89.541174] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 89.541195] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.589939] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.589981] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590499] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.590521] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 6419.590978] hdmi-audio-codec hdmi-audio-codec.5.auto: hdmi_codec_startup doesn't support capture [ 6419.591003] hdmi-audio-codec hdmi-audio-codec.5.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22

@dale looking at the openvfd_x98h.dtso file you shared, openvfd uses these pins: openvfd_gpio_clk = <&pio 2 7 0>; openvfd_gpio_dat = <&pio 2 2 0>; openvfd_gpio_stb = <&pio 2 12 0>; So you should try with their equivalent: mosi-gpios = <&pio 2 2 GPIO_ACTIVE_HIGH>; /* mosi is the same as openvfd_gpio_dat */ sck-gpios = <&pio 2 7 GPIO_ACTIVE_HIGH>; /* sck is the same as openvfd_gpio_clk */ cs-gpios = <&pio 2 12 GPIO_ACTIVE_LOW>; /* cs is the same as openvfd_gpio_stb */

Hi, thanks for checking. I check dmesg -T | grep spi_gpio and see the error spi_gpio spi: probe with driver spi_gpio failed with error -22. Also the /sys/class/leds is empty. Do you think the gpio pins are not correct? Below are current gpio pins I try this time mosi-gpios = <&pio 2 11 GPIO_ACTIVE_HIGH>; /* PC11 = data */ sck-gpios = <&pio 2 12 GPIO_ACTIVE_HIGH>; /* PC12 = clock */ cs-gpios = <&pio 7 5 GPIO_ACTIVE_LOW>; /* PH5 = strobe/latch */

That will definitely make you not get hardware accelerated video Make sure to follow the 3 commands to install the custom repo, its certificate and higher priority: sudo wget http://apt.undo.it:7242/apt.undo.it.asc -O /etc/apt/trusted.gpg.d/apt.undo.it.asc . /etc/os-release && echo "deb http://apt.undo.it:7242 $VERSION_CODENAME main" | sudo tee /etc/apt/sources.list.d/apt.undo.it.list $ echo -e "Package: *\nPin: release o=apt.undo.it\nPin-Priority: 600" | sudo tee /etc/apt/preferences.d/apt-undo-it sudo apt update Then check that the new custom dpkgs are available for install/upgrade apt list ffmpeg-whatever Here's how I force install a specific version: sudo apt install packagename=nn.nn.n

Thanks, all's clear I might be such random person lol. However it would need either a lot of time or information delivered when it has been broken; open code is nice but there are too many kernel versions and distributions. That matter would need some deeper conversation. I think you was the person managing this area so maybe you know where to search the issue to correct it or you know the person who might know. I'm affraid I found the reason of long image generation time: my laptop fans are to silent today and it might be the reason...

Thinking about a better automated option to revert (e.g. just power off like @The Tall Man suggested) while still not touching uboot or even lower level layers the initrd might be an option based on the current setup. I assume we have very little probability for kernel+initrd load problems. Most issues will probably occur after the rootfs was mounted and handover. Integrating additional scripts inside the initrd could be used to auto revert the symlink in case of failure. Before we are going to reboot we place a status file inside the boot partitions boot directory that we just updated. For this first reboot we call this testboot1. When the new system boots up initrd script checks for this file and renames it to testboot2. If the system boots up correctly or can be accessed remotely /boot/testboot2 is deleted. But if the initrd script sees a testboot2 file during its boot process it knows something went wrong. It then changes the /boot symlink to the other boot folder deletes testboot2 and reboots instead of handing over to the rootfs. If the new system got stuck after it handed over to the rootfs the initrd script should have renamed the file to testboot2 already and a hard restart should revert. This hard reset could probably also be fully automated if the SBC has a hardware watchdog. If the watchdog module is integrated in the initrd it could set it to a reasonable value. The watchdog is then only disabled or changed to normal operation once the system is reliable working or if disabled via remote access. This concept would build on top of what exist. Any community member could choose to test the idea and implement management scripts. I guess everything can be done in bash/sh. It could also lead to a new armbian package: simpleAB which is not perfect but might be enough for many. It would not need many uboot or architectural changes. I guess it also works for all armbian supported devices? But as @Igor already said. One needs to invest.

@ebin-dev@mtlmarko189 Not sure if this issue can be resolved. I've been running tests with different chip versions and discovered that the first batch of Helios64 devices includes an unreliable chip. Take a look at this: root@helios64:~# lsusb -v -d 0bda:8156 | grep bcdDevice bcdDevice 30.00 bcdDevice 31.04 According to cnx-software 30.00 corresponds to RTL8156 31.00 corresponds to RTL8156B 31.04 correspond to the third version, RTL8156BG So far, the RTL8156BG has been working better with Linux kernel 6.12.42. P.S. The workaround suggested by @ebin-dev helps reduce the symptoms, but the NIC is still sending corrupted packets.

"apt policy ffmpeg" FTW ;-) apt also has a command-line option to force the installation of a particular package version. To automate this, you can put a file under /etc/apt/preferences.d/