Active threads

I've just tested cpufreq-switching-2-delay5msec in emergency mode. My setup is Armbian 23.08.0-trunk Bookworm with Linux 6.6.8-edge-rockchip64 My first attempt ran for few minutes before freezing and rebooting. Before my second attempt, I blacklist panfrost (not sure there is an impact at all in emergency mode...) $ sudo nano /etc/modprobe.d/blacklist.conf blacklist panfrost I then rebooted and started linux in emergency mode. # lsmod | grep panfrost lsmod didn't catch any panfrost module. Still, cpufreq-switching-2-delay5msec ended with a kernel panic: 10/100 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 cpub_freq 1200000 cpub_freq 1416000 cpub_freq 1608000 cpub_freq 1800000 cpub_freq 1608000 cpub_freq 1416000 cpub_freq 1200000 cpub_freq 1008000 cpub_freq 816000 cpub_freq 600000 cpub_freq 408000 cpub_freq 600000 cpub_freq 816000 cpub_freq 1008000 [ 51.732314] Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP [ 51.732887] Modules linked in: ip_tables x_tables autofs4 efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid0 multipath linear cdc_ncm cdc_ether usbnet raid1 r8152 realtek rockchipdrm dw_mipi_dsi dw_hdmi analogix_dp fusb302 drm_display_helper cec tcpm drm_dma_helper typec drm_kms_helper dwmac_rk stmmac_platform stmmac drm pcs_xpcs adc_keys [ 51.735962] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 6.6.8-edge-rockchip64 #1 [ 51.736610] Hardware name: Helios64 (DT) [ 51.736965] pstate: 800000c5 (Nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 51.737589] pc : update_blocked_averages+0x278/0x758 [ 51.738051] lr : update_blocked_averages+0x264/0x758 [ 51.738504] sp : ffff800082043e80 [ 51.738806] x29: ffff800082043e80 x28: ffff000005cd9600 x27: 0000000c01b0a9aa [ 51.739456] x26: ffff000005cdbc80 x25: ffff000005cdbc00 x24: 0000000000000000 [ 51.740104] x23: ffff0000f77a0f18 x22: 0000000000000028 x21: 0000000000000000 [ 51.740750] x20: ffff000005cdbd40 x19: ffff0000f77a05c0 x18: 0000000000000000 [ 51.741396] x17: ffff800075e85000 x16: ffff800082040000 x15: 0000000000000000 [ 51.742043] x14: 0000000000000001 x13: 000000000000002a x12: 00000000000e7fe0 [ 51.742689] x11: 0000000000000000 x10: 000000000000002a x9 : ffff000005cdbc80 [ 51.743336] x8 : 0000000000000000 x7 : ffff000005cdbc00 x6 : 0000000000000014 [ 51.743982] x5 : 00000000000003af x4 : 000000000000b6a8 x3 : 0000000000000000 [ 51.744628] x2 : 0000000000000000 x1 : ffff000001d6c400 x0 : ffff0000019c6000 [ 51.745274] Call trace: [ 51.745501] update_blocked_averages+0x278/0x758 [ 51.745924] run_rebalance_domains+0x4c/0x80 [ 51.746313] __do_softirq+0x160/0x3fc [ 51.746649] ____do_softirq+0x10/0x1c [ 51.746985] call_on_irq_stack+0x24/0x4c [ 51.747344] do_softirq_own_stack+0x1c/0x2c [ 51.747727] irq_exit_rcu+0x94/0xd0 [ 51.748051] el1_interrupt+0x38/0x68 [ 51.748382] el1h_64_irq_handler+0x18/0x24 [ 51.748758] el1h_64_irq+0x64/0x68 [ 51.749070] cpuidle_enter_state+0xc0/0x4bc [ 51.749454] cpuidle_enter+0x38/0x50 [ 51.749783] do_idle+0x1fc/0x270 [ 51.750083] cpu_startup_entry+0x34/0x3c [ 51.750444] secondary_start_kernel+0x128/0x148 [ 51.750859] __secondary_switched+0xb8/0xbc [ 51.751249] Code: f940ab20 f9406400 f8766801 b4000101 (f9407020) [ 51.751797] ---[ end trace 0000000000000000 ]--- [ 51.752214] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 51.752826] SMP: stopping secondary CPUs [ 51.753358] Kernel Offset: disabled [ 51.753674] CPU features: 0x1,00000208,3c020000,1000421b [ 51.754152] Memory Limit: none [ 51.754439] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

This board is not a supported board. Moved post to Community Maintained section and added the correct tag for the board.

TLDR; yes upping 75mV helps drastically, but is not enough at least for all frequencies. Indeed, before upping by 75mV I could not boot most of the time (only "emergency" mode boot was reliable, ie no raid10 and services off). But it seems 75mV is not enough to compensate for the issue at stake all the time. The thing is I don't know what the root issue upping 75mV workaround is. Could be 100mV is enough, but this is a value based on testing, not a theory that requires 75mV (could be the proper value is upper or could be upping the voltage only helps to cope with voltage drops, making them less frequently drop below a certain value where cpub crashes). The datasheet for the cpub regulator requires a bigger capacitor on voltage input than the helios64 one. But the weird thing is most rk3399 boards also use the same weak below-spec capacitor value at this place. At my level (without understanding the hardware interactions or barely) the next step would be to test if my test case also crashes these other boxes with the same vin too low capacitor ... if they crash we could guess that the design is bad and without a bigger capacitor the regulator cannot deliver the voltage for cpub reliably. Could be we could workaround this in software, but I am not qualified to tell that, at least at this point (I read about how these components work, but I am not an expert. Mind also I tested the board way less for the time to come as now that it is quite reliable I started using it again (been down for months, then I extracted the motherboard to test with the less complex setup possible, in emergency mode). NB: upping the voltage makes the CPU hotter, you might want to check the temperature values (with "sensors"). Mine were fine, way below the throttling temp of 80°C for the rk3399. Even with all opp3 and above at 1.2V. The issue seems mostly of keeping the power consumption low. But I wonder if it has a noticeable effect on helios64 power consumption.

Also Runing android APK's on H96 Max with this waydroid image: https://forum.armbian.com/topic/38184-waydroid-for-rk3588-with-armbian-edge-panthor-kernel-68/#comment-188934 No Vaapi on android video players.... Next try: Wine + Vulkan https://www.cnx-software.com/2021/03/29/panvk-panfrost-vulkan-driver/ https://archlinuxarm.org/packages/aarch64/vulkan-panfrost https://linuxconfig.org/improve-your-wine-gaming-on-linux-with-dxvk https://linuxhint.com/enable-vulkan-rendering-in-wine-games/ https://www.cnx-software.com/2023/07/21/arm-panfrost-is-now-the-gpu-driver-for-the-linux-community/

Testing this lineage on RK3566 h96 max No VAAPI No youtube

If the image would have been made by us its download would be either from armbian.com or https://github.com/armbian/community/ or https://github.com/armbian/os and not from some random baidu/google drive.

Hello RuDy_74 I try to do same (armbian on Bqeel K12pro S912) and thank you for yours posts. Some directory or links are deads. Can you resume whitch img and dbt files you used for working fine and install home assistant ? Thank you. PS: sorry for my poor english. brant : Bqeel model : K12 Pro CPU : Amlogic S912 Octa core ARM, Cortex-A53 64 bits – Maximum 2 Ghz GPU : Mali T820MP3 mother board : q201_9377 RAM 2 Go DDR3 ROM : 32 Go eMMC Ethernet Gigabit 100/1000M Wifi : b/g/n/ac – 2,4 & 5 Ghz Bluetooth : 4.1 Micro-SD : maximum 32 Go 2x USB 2.0 ports Android 6.0 (Marshmallow) mother board recto verso (left is left, top is bottom, right is right, bottom is top)

in this case, i think rk3528.dtb was on boot partition. Can you share the: $ lsblk $ df -h $ blkid

I have install armbian version 10 on this box. Did watch video for some time, no issues except remote who do not only mine box but satelite receiver also, and this do then crash. I have a new remote who can be adjusted on mucho boxes and dvd, tv enc. but did not manage to let it work on this RT box (mxq pro). Oke I did watch video and encode some in H265, but get not such small files als with H264 in handbrake, I do use hardware encoding with videocard, I need stil to install new computer board with a intel I7 but has not yet the time so I can try the intel hardware encoder who seems to be better... The video has much artifacts, special color screens and darknes, clouds. The videobox I have for years now the Elvira Xtreamer has not this artifacts on that same encoded H264 video while armbian has, The RT29** box do have a lot artfacts in dark scenes, sound do loud bang in the amplifier when boot, need to watch out with this, but that is not because of armbian but hardware of these cheap boxes.. Short, the H265 decoder on chip does a bad job, or the version of armbian has issues, and then I think special with the videoplayer, I can also just have 1280 x 720 max in armbian setup, or there is a software active who recode video on the fly for adjust screen dimensions?. I do not now. someone has experience with this?. regards

you want to add a 2 pin fan to opi5, unfortunitly, PWM port is IO port, it doesn't have enough power to driver your fan, thus would break the GPIO bank, and make whole bank unfunction. thus suggest to directly use 5V power pin. if you have 3 pin fan, you can use a PWM pin to control it speed. in this case, you need write dts code to enable it.

Hi @SteeMan, is official support back for orange pi zero? Not long ago the releases page clearly indicated CSC support but now I read standard support. The kernel I had problems with was 6.6.16 and now I see 6.6.20 available, who knows if they have solved the temperature problem with the new kernel.

Thanks. Just to be clear, that's the rkvdec from staging drivers, right? It overrides hantro for H.264? Oh and I'm assuming the reason hantro H.264 is disabled is rkvdec offers better performance. Is that right?

Not support yet We also need some time to prepare and roll-over stuff to a new environment. Also check https://github.com/armbian/build/issues/6527

It's locked the bootloader ( i cant enter usb device mode ) FPT FX6 right?

Yes I have tried the Zunlong images for orangepizero3 and they work. Unfortunately those images are for a Linux 6.1 kernel and the zero3 and 2w were only officially implemented into linux with 6.6. The challenge is to get the Zunlong code into Armbian with the newer kernels.

Well, sorry, if necessary I will open a new thread. I send the results of the commands cat /proc/modules overlay 110592 3 - Live 0x00000000 tls 69632 0 - Live 0x00000000 snd_seq_dummy 16384 0 - Live 0x00000000 snd_hrtimer 16384 2 - Live 0x00000000 l2tp_ppp 24576 0 - Live 0x00000000 l2tp_netlink 24576 1 l2tp_ppp, Live 0x00000000 l2tp_core 36864 2 l2tp_ppp,l2tp_netlink, Live 0x00000000 pppox 16384 1 l2tp_ppp, Live 0x00000000 xfrm_user 40960 2 - Live 0x00000000 ppp_generic 36864 2 l2tp_ppp,pppox, Live 0x00000000 xfrm_algo 16384 1 xfrm_user, Live 0x00000000 slhc 16384 1 ppp_generic, Live 0x00000000 algif_hash 16384 1 - Live 0x00000000 aes_arm_bs 24576 2 - Live 0x00000000 crypto_simd 16384 1 aes_arm_bs, Live 0x00000000 cryptd 20480 2 crypto_simd, Live 0x00000000 algif_skcipher 16384 1 - Live 0x00000000 af_alg 24576 6 algif_hash,algif_skcipher, Live 0x00000000 lz4hc 16384 0 - Live 0x00000000 lz4 16384 0 - Live 0x00000000 zram 32768 3 - Live 0x00000000 binfmt_misc 20480 1 - Live 0x00000000 snd_usb_audio 225280 2 - Live 0x00000000 snd_soc_rockchip_i2s 24576 2 - Live 0x00000000 snd_hwdep 16384 1 snd_usb_audio, Live 0x00000000 snd_usbmidi_lib 28672 1 snd_usb_audio, Live 0x00000000 snd_soc_simple_card 20480 2 - Live 0x00000000 snd_seq_midi 16384 0 - Live 0x00000000 snd_seq_midi_event 16384 1 snd_seq_midi, Live 0x00000000 snd_soc_hdmi_codec 20480 1 - Live 0x00000000 snd_soc_simple_card_utils 20480 1 snd_soc_simple_card, Live 0x00000000 snd_rawmidi 28672 2 snd_usbmidi_lib,snd_seq_midi, Live 0x00000000 snd_soc_core 172032 4 snd_soc_rockchip_i2s,snd_soc_simple_card,snd_soc_hdmi_codec,snd_soc_simple_card_utils, Live 0x00000000 snd_seq 57344 15 snd_seq_dummy,snd_seq_midi,snd_seq_midi_event, Live 0x00000000 snd_pcm_dmaengine 16384 1 snd_soc_core, Live 0x00000000 hantro_vpu 122880 0 - Live 0x00000000 rockchip_vdec 69632 0 - Live 0x00000000 (C) snd_seq_device 16384 3 snd_seq_midi,snd_rawmidi,snd_seq, Live 0x00000000 snd_pcm 94208 5 snd_usb_audio,snd_soc_hdmi_codec,snd_soc_simple_card_utils,snd_soc_core,snd_pcm_dmaengine, Live 0x00000000 v4l2_vp9 24576 2 hantro_vpu,rockchip_vdec, Live 0x00000000 rockchip_rga 24576 0 - Live 0x00000000 rockchip_iep 20480 0 - Live 0x00000000 rk_crypto 24576 1 - Live 0x00000000 v4l2_h264 16384 2 hantro_vpu,rockchip_vdec, Live 0x00000000 videobuf2_dma_sg 20480 1 rockchip_rga, Live 0x00000000 syscon_reboot_mode 16384 0 - Live 0x00000000 videobuf2_dma_contig 20480 3 hantro_vpu,rockchip_vdec,rockchip_iep, Live 0x00000000 v4l2_mem2mem 24576 4 hantro_vpu,rockchip_vdec,rockchip_rga,rockchip_iep, Live 0x00000000 snd_timer 28672 3 snd_hrtimer,snd_seq,snd_pcm, Live 0x00000000 videobuf2_memops 16384 2 videobuf2_dma_sg,videobuf2_dma_contig, Live 0x00000000 videobuf2_v4l2 24576 5 hantro_vpu,rockchip_vdec,rockchip_rga,rockchip_iep,v4l2_mem2mem, Live 0x00000000 snd 57344 22 snd_usb_audio,snd_hwdep,snd_usbmidi_lib,snd_soc_hdmi_codec,snd_rawmidi,snd_soc_core,snd_seq,snd_seq_device,snd_pcm,snd_timer, Live 0x00000000 videobuf2_common 45056 9 hantro_vpu,rockchip_vdec,rockchip_rga,rockchip_iep,videobuf2_dma_sg,videobuf2_dma_contig,v4l2_mem2mem,videobuf2_memops,videobuf2_v4l2, Live 0x00000000 rk3288_gpiomem 16384 0 - Live 0x00000000 dw_wdt 16384 0 - Live 0x00000000 crypto_engine 16384 1 rk_crypto, Live 0x00000000 reboot_mode 16384 1 syscon_reboot_mode, Live 0x00000000 hci_uart 40960 0 - Live 0x00000000 soundcore 16384 1 snd, Live 0x00000000 r8723bs 417792 0 - Live 0x00000000 (C) rockchip_thermal 24576 0 - Live 0x00000000 cpufreq_dt 16384 0 - Live 0x00000000 squashfs 45056 24 - Live 0x00000000 fuse 110592 1 - Live 0x00000000 ip_tables 24576 0 - Live 0x00000000 realtek 24576 1 - Live 0x00000000 gpio_rockchip 20480 12 - Live 0x00000000 gpio_keys 20480 0 - Live 0x00000000 panfrost 57344 2 - Live 0x00000000 gpu_sched 28672 1 panfrost, Live 0x00000000 dw_hdmi_cec 16384 0 - Live 0x00000000 dw_hdmi_i2s_audio 16384 0 - Live 0x00000000 uas 24576 0 - Live 0x00000000 ls /dev/sd* /dev/sda /dev/sda1 Thanks.

Go and see the LibreElec project... find the image for Orange Pi PC. That's the OS that works with Orange Pi Zero. I think Cedrus for video codec is for the H2/H3 specifically... I dont know about H616/8. Wiki says that the codec hardware is not available in Linux http://www.orangepi.org/orangepiwiki/index.php/Orange_Pi_Zero_3

Is there something specially difficult about SPI versus I2C? Luckily, my servo controller I plan to use with my opiz3 is I2C, but I was hoping to use an SPI LCD too in the future. Is there an spi-overlay option in armbian-config? https://forum.armbian.com/topic/12571-opi-win-how-to-steering-rgb-led-apa106/

The link to the krescue image on Armbian's Khadas-VIM3 page does not work (anymore). It needs to be replaced with https://dl.khadas.com/firmware/Krescue/dump/ (note the lower-case f in "/firmware/"). Confusingly, other firmware images are still available below https://dl.khadas.com/Firmware with upper-case F. To prevent the image from getting lost again, I've asked the internet archive to archive the latest krescue sd card image for VIM3: https://web.archive.org/web/20240426161033/https://dl.khadas.com/firmware/Krescue/system/versions/VIM3.krescue.sd.220110_266.img.gz

You missed my point. You choose the edge kernel version of the trunk versions. There are also vendor kernel versions. The vendor kernel is going to be more stable than the edge kernel.

Good morning everyone. My problem is that I had armbian installed in emmc and using armbian config I changed it to usb but I did not update the boot to sd and when I restart it only shows what I put in the photo and it remains black. Is there any way to fix it. By pressing reset with the HDMI unplugged it tries to start but stays in initramfs. Thank you

Hello, I am a user of your version, my English is quite bad, I am using a TVbox T9 series and it uses rk3328 it's fine in the file version Armbian_22.05.0 wlan is fine but I use upgrade or use file version Armbian_23.08.0 no longer recognizes wlan, some unimportant things like LEDs are not recognized when I use rk3318-config, hope to be supported soon ^^ The picture I sent is quite similar to my device, sorry for not being able to take a photo of my device.

Hello, I am happy to report that after I commented the lines from the build/lib/functions/compilation/armbian-kernel.sh script and manually doing a "pip install pylibfdt" (because it was complaining that it cannot compile it due to a missing "ld" which was there, in /usr/bin/ld), I was able to compile the edge kernel for rpi5b. No other steps were required. Now I have /proc/schedstats which will make cilium happy, I hope. Probably there will be no problems with the rest of the boards. Thank you very much for the great work you are doing! Stefanita Vilcu

Ok Here is the response from VHD the company that built our devices It is based on Rockchip RK3588 Development Board EVB1

A while ago I debugged the ssh problem and added some comments in this thread here. I don't remember if I used bookworm or trixie. Seems to me a timing issue or in which order things start. For now, whenever I do some dev work, I just do either another reboot after the first setup or restart the sshd service.