Active threads

Thanks for the initiative with the PR. (Usually we are only asked for money if little help is needed) Here is what happens: The cpufreqpolicy sets a generic value for the sampling_rate of 200000 (this is how often the governor’s worker routine should run, in microseconds). The sampling_rate should be set to a nominal value close to the cpuinfo_transition_latency (49000 nanoseconds for rk3399) such that it is effectively about 1000 times as large. For rk3399 boards the sampling_rate of 50000 is very responsive and not too demanding for the cpu. In that case no problems occur if io_is_busy is set to 1 ! So you could modify the PR and request that the sampling_rate should be a parameter (per cpu) and be set to the value of the cpuinfo_transition_latency of that cpu. The fine tuned values for Helios64 are those: for cpufreqpolicy in 0 4 ; do echo 1 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/io_is_busy echo 25 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/up_threshold echo 10 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/sampling_down_factor echo 50000 > /sys/devices/system/cpu/cpufreq/policy${cpufreqpolicy}/ondemand/sampling_rate done Edit: Helios64 is one of the best arm based NAS systems I have seen so far. I am not going to replace it anytime soon.

I follow the documentation tutorial step by step, the compilation will sometimes download the kernel and uboot source code, sometimes not download, is there any directive to download all the source code

Hi @ag123 Thank you for the replay but in case the DS18B20 uses a 1-wire bus, libgpiod is used to use the deprecated sysfs interface to GPIO, so it does not apply in this case, but I may be wrong

Any chances you guys could share your images? Been struggling getting a recent image to boot with my 1.5Gb one. only the old official Debian images work. One of the github links from Orange PI provides a bin uboot for the 1.5Gb but I had no luck with that. leeboby/opizero3-uboot-dtb: 保存opizero3 1.5gb和4gb版本的开发板linux6.x系统需要替换的u-boot和dtb文件 (github.com)

Attempting to build this image gives me the following error: [🐳|🔨] Image 'itb' is missing external blobs and is non-functional: opensbi [🐳|🔨] [🐳|🔨] /binman/itb/fit/images/opensbi/opensbi (fw_dynamic.bin): [🐳|🔨] See the documentation for your board. The OpenSBI git repo is at [🐳|🔨] https://github.com/riscv/opensbi.git [🐳|🔨] You may need to build fw_dynamic.bin first and re-build u-boot with [🐳|🔨] OPENSBI=/path/to/fw_dynamic.bin [🐳|🔨] [🐳|🔨] Some images are invalid [🐳|🔨] make: *** [Makefile:1124: .binman_stamp] Error 103 Any help would be appreciated.

does Armbian image use same DDR blobs as Joshua's?

Description Quick fix to hdmi patch due to mainlined hunks. How Has This Been Tested? [x] New fixed patch apply on 6.8.9 edge kernel [x] Compiled rockchip drm code on the fly to check it works Did not check the real functionality, but I hope I did not break anything, the patch is minimal... Checklist: [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

The USB power has been a growing issue with my C2 for years now. To have the board use the SSD through a USB/SATA adapter, I now have to power the adapter (which has a Y cable) from a neighbour board. It used to work long time ago without the other board "help". So there is probably a weakening component on my C2. Right now the voltage drops between the +5V barrel alim centre, and USB connectors' 5V. I see no rationale in this. My C2 is now decommissioned (I bought a OPi 3 LTS instead). So I will try to to solder a wire under the board to have the incoming 5V straight to the USB ports. It should not be worse than the Y USB cable bringing the 5V from the neighbour board.

Hi Igor, I understand, I agree, this forum is for the Armbian, not the board. Thank you again for your time, for what is working now, it is waaaayyy faster than my Pi3b !!! In any case, a big thank you for your time! Richard.

@z28z34man See Werner's post

@cad 435 No you aren't really missing anything. In the stable channel, kernel .debs generally only get pushed out every three months when a new stable release is put out (24.05 will be out the end of this month for example). If you want to get regular updates of kernels you need to switch to the nightly builds repository in armbian-config. Right now there is no in between.

Description Devicetree is already in https://github.com/armbian/linux-rockchip so just a board config is enough How Has This Been Tested? [x] ./compile.sh BOARD=rock-5-itx BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow, flashed to emmc and boot 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 [ ] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Its a bug. You need to make sure the wireless country code is set, even when its not being used.

Hi all, I decided today to give an Armbian build a whirl as a virtual machine (guest). In particular, Armbian_24.2.4_Uefi-x86_jammy_current_6.6.21_kde-neon_desktop.img. As is usual with installing a virtual machine, it comes up with a default video resolution of 1024x768; I can usually quickly get it full screen on my system as 1920x1080 by going to the System Settings : Hardware : Display and Monitor : etc. However, here there is no hardware subsection at all, and a search didn't turn up a setting to change the display. Any advice on where to find it? I installed the spice guest driver and related packages on the guest. Thanks!

That board is no longer a valid armbian board. It is EOS status (end of support). So there is no Armbian support and no community support for that board.

Hi all, Armbian is now working on Rock 3C. You can download a community build: https://github.com/armbian/community/

It happens also with the latest Linux 6.7.4-edge-meson64 kernel. This problem could be related to a power switch which could be optionally connected to the J4 pin?

@elysiuMAccording to a user from a russian forum, the published stock firmware (28.10.23) does not match the device and will brick it! We have to wait until the correct firmware is released or someone finds another solution... https://4pda.to/forum/index.php?showtopic=1088113#entry129825636

I'm looking for a flash for this box. 16/2 x88 pro-b-rk3318-d4-v1.2 16/2

Hello all I have broken my installation when I tried to install the kernel 6.1 my current kernel 5.10.160-legacy-rk35xx. My nanopc t6 do not start. My installation is on EMMC and start on it. Could you please help me to recover it ? I have a backup file from OMV but I don't know how to push the backup to the EMMC? other possibility I guess copy the boot folder backup to EMMC boot folder but I do not know if it is enough. I really appreciate an help furthermore a clear turial could help evryone to recover an installation on EMMC memory. Thanks in advance for your support.

Debian Buster is EOL. Remove Armbian related entries from apt sources and you are good to go. There won't be any further updates from Armbian for this userspace. https://docs.armbian.com/User-Guide_FAQ/#how-do-i-upgrade-from-armbian-buster-to-bullseye Debug boot issue: https://debug.armbian.de Put SD card into your Linux computer and mount it.

removed

so, I tried it again with the kernel 6.1.43 and with the instructions from the howto. That resulted in the scrambled picture when opening kodi. (see above post) Then I built mpp, rga, ffmpeg_rockchip and kodi new. After a restart I could not open kodi as it complained about the missing fbdev module. Then I build drm-package and the mesa driver again. Then kodi opened again only to give the following errors when opening a movie: 2024-05-06 09:43:53.882 T:6596 info <general>: Creating InputStream 2024-05-06 09:43:53.916 T:6596 info <general>: Creating Demuxer 2024-05-06 09:43:53.990 T:6596 info <general>: Opening stream: 0 source: 256 2024-05-06 09:43:53.990 T:6596 info <general>: Creating video codec with codec id: 173 2024-05-06 09:43:53.990 T:6596 info <general>: CDVDVideoCodecDRMPRIME::Open - using decoder Rockchip MPP (Media Process Platform) HEVC decoder 2024-05-06 09:43:53.991 T:6596 info <general>: Creating video thread 2024-05-06 09:43:53.991 T:6600 info <general>: running thread: video_thread 2024-05-06 09:43:53.992 T:6596 info <general>: Opening stream: 1 source: 256 2024-05-06 09:43:53.992 T:6596 info <general>: Finding audio codec for: 86060 2024-05-06 09:43:53.992 T:6596 info <general>: CDVDAudioCodecFFmpeg::Open() Successful opened audio decoder truehd 2024-05-06 09:43:53.992 T:6596 info <general>: OpenStream: Allowing max Out-Of-Sync Value of 10 ms 2024-05-06 09:43:53.992 T:6596 info <general>: Creating audio thread 2024-05-06 09:43:53.992 T:6601 info <general>: running thread: CVideoPlayerAudio::Process() 2024-05-06 09:43:53.992 T:6596 info <general>: Opening stream: 9 source: 256 2024-05-06 09:43:54.003 T:6601 info <general>: Creating audio stream (codec id: 86060, channels: 8, sample rate: 48000, no pass-through) 2024-05-06 09:43:54.032 T:1329 error <general>: CEGLImage::SupportsFormat - format not supported: YU10 2024-05-06 09:43:54.033 T:1329 info <general>: GLES: Selecting single pass rendering 2024-05-06 09:43:54.033 T:1329 info <general>: GLES: Selecting YUV 2 RGB shader 2024-05-06 09:43:54.033 T:1329 error <general>: CBaseRenderer::GetShaderFormat - unsupported format 179 2024-05-06 09:43:54.033 T:1329 error <general>: GLES: BaseYUV2RGBGLSLShader - unsupported format none 2024-05-06 09:43:54.034 T:1674 info <general>: Skipped 1 duplicate messages.. So this means, that the original howto's for Rock 5b do not work anymore. And I did not find any working or reproducible collection of steps needed to get kodi reliably working with hw acceleration. This is quite a nightmare. I have this thing for over a year now and i am not able to use it.

Hi, uptime more 5 days with my pattern test and ebin-dev's file for voltage change, not crash. now i use helios64 on normal condition to see if better than before for information my pattern test never pass before today on my helios64 with ondemand gov and 408-1800 freqs since i have it Keep in touch root@helios64:~# uptime 10:06:08 up 5 days, 40 min, 2 users, load average: 1.94, 2.49, 2.65 root@helios64:~# uname -a Linux helios64 6.6.29-current-rockchip64 #1 SMP PREEMPT Sat Apr 27 15:11:44 UTC 2024 aarch64 GNU/Linux helios64@helios64:~$ cat /etc/fancontrol # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu #INTERVAL=10 INTERVAL=30 FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 #MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110 MAXTEMP=/dev/fan-p6/pwm1=50 /dev/fan-p7/pwm1=50 #MINSTART=/dev/fan-p6/pwm1=60 /dev/fan-p7/pwm1=60 MINSTART=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 #MINSTOP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MINSTOP=/dev/fan-p6/pwm1=20 /dev/fan-p7/pwm1=20 MINPWM=20 root@helios64:~# cat /etc/default/cpufrequtils ENABLE=true MIN_SPEED=408000 MAX_SPEED=1800000 GOVERNOR=ondemand

Hello, I hope someone might help me on this. Is anyone here using the ENC28J60 Ethernet port on an Orange Pi Zero 2W or Orange Pi Zero 3? If so, can you please share the file .dts (or .dtbo) that is working for you? I've generated a .dtbo using the file in https://github.com/armbian/sunxi-DT-overlays/blob/master/examples/spi-enc28j60.dts, with: dtc -I dts -O dtb -o /boot/overlay-user/spi-enc28j60.dtbo spi-enc28j60.dts but still it doesn't work. It says "chip not found". I'm using the same cable pinout as in my Raspberry Pi Zero 2W and it works successfully, but not in the Orange Pi Zero 2W. Any idea?