Search the Community

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! H96 MAX V56 RK3566 8gb Ram SD-Card unofficial images: Tutorial SD-Card Version v0.5 DEBIAN12 BETA unofficial Tutorial SD-Card Version v0.5 ARMBIAN23 BETA unofficial H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ unofficial images: Tutorial EMMC Version V0.7 ARMBIAN23 BETA unofficial H96 MAX V56 RK3566 8gb EMMC Mainline Boot Hzdm unofficial images: Tutorial EMMC Version v0.8 ARMBIAN unofficial Armbian 23.08.0 Jammy Kernek 6.2 Desktop v0.8 Beta unofficial H96 MAX V56 RK3566 8gb EMMC Mainline Boot Hzdm unofficial images: Tutorial EMMC Version v0.9 ARMBIAN BETA unofficial Debian 12 BookWorm Kernel 6.2 Server v0.9 unofficial Beta Armbian 23.11 Jammy Kernel 6.2 Server v0.9 unofficial Beta Debian 12 BookWorm Kernel 6.2 Desktop v0.9 unofficial Beta Armbian 23.11 Jammy Kernel 6.2 Desktop v0.9 unofficial Beta H96 MAX V56 RK3566 8gb EMMC Chainloader to mainline HotnikQ unofficial images: Tutorial EMMC Version v1.0 ARMBIAN unofficial Armbian 23.11.0 Server Kernel 6.2 Minimal V1.0 unofficial Armbian 23.11.0 Desktop Kernel 6.2 Gnome V1.0 unofficial Debian 12 BookWorm Kernel 6.2 Server Minimal v1.0 unofficial Debian 12 BookWorm Desktop Kernel 6.2 Gnome v1.0 unofficial H96 MAX V56 RK3566 8gb EMMC Hzdm Mainline Boot Custom unofficial images: Tutorial Build Your own Armbian EMMC unofficial image Armbian 23.11.0 Server Minimal Kernel 6.2 Custom unofficial Build Armbian 23.11.0 Desktop Cinnamon Kernel 6.2 Custom unofficial Build Armbian 23.11.0 Desktop XFCE Kernel 6.2 Custom unofficial Build Armbian 23.11.0 Server Standart Kernel 6.2 Custom unofficial Build H96 MAX V56 RK3566 EMMC Raspiblitz HotnikQ unofficial images: Tutorial Build Raspiblitz on EMMC Armbian Bullseye unofficial Armbian 23.11.0 Debian Bullseye Kernel 6.1.54 Custom unofficial Build Armbian_Raspiblitz Debian Bullseye kernel 6.1.54 Backup unofficial H96 MAX V56 RK3566 8gb EMMC Hzdm Mainline Boot unofficial images: Tutorial Build Your own V1.1 Armbian EMMC unofficial image Armbian 24.2.1 Server Minimal V1.1 Custom Kernel 6.2 unofficial Build Armbian 24.2.1 Desktop Gnome V1.1 Custom Kernel 6.2 unofficial Build Debian 12 BookWorm Server Minimal v1.1 Kernel 6.2 Custom unofficial Build Debian 12 BookWorm Desktop Gnome v1.1 Kernel 6.2 Custom unofficial Build H96 MAX V56 RK3566 8gb EMMC Ning Mainline Kernel: Tutorial Build Your own V1.2 & V1.3 Armbian EMMC official image Armbian Desktop Gnome kernel The Latest official Debian BookWorm Server Kernel Minimal The Latest official Software description: V0.5 = @armbian The Armbian SD card image "Compiled From Armbian Project" V0.8 = @hzdm Project with Mainline Bootloader "Boot the 64gb Emmc Armbian with Mainline Rockchip" V0.9 = @hzdm Release Mainline Bootloader "Boot the 32gb and 64gb Emmc Armbian with Mainline Rockchip" V1.0 = @hotnikq The Armbian SD card inside the Android Legacy Rockchip Image "Two Original Glued Images: Android boot for Linux" V1.2 = @ning Release Device Tree and Bootloader to longterm 6.6.27 Kernel "Boot with Mainline Rockchip" V1.3 = @Hqnicolas Github PR Enable h96 Rk3566 TV-Box device for Kernel 6.8 Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html Wifi Driver: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view?usp=sharing Or Just Live install Wifi Driver: cd /lib/firmware/brcm/ sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.h96-TVbox,rk3566.bin sudo reboot now nmcli dev wifi Topic description: This topic aims to demonstrate the path taken to the Armibian EMMC solution. In our path we create a lot of ready-to-use ROM files, some users burn an use this images without learning with the Linux compilation process. the name of the topic is efforts but that's no effort at all, you should try compile your own images. Device Capability Test: Using Rockchip SoCs NPU. Drivers: https://github.com/rockchip-linux/rknpu2 User Guide: https://github.com/rockchip-linux/rknpu2/blob/master/doc/Rockchip_RKNPU_User_Guide_RKNN_API_V1.4.0_EN.pdf OpenCV: https://opencv.org/blog/2022/11/29/working-with-neural-processing-units-npus-using-opencv/ A discussion on Reddit: https://www.reddit.com/r/OrangePI/comments/12b3jmj/accessing_the_npu_on_the_orange_pi/ Transformers models: https://github.com/usefulsensors/useful-transformers Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/ Usage: https://youtu.be/pN8mKZ5wpdQ

@snakekick Thanks, that seems to confirm my findings back a few months ago. Adding a 5ms delay in the test case did not prevent the crash. Though it could be the system load is at play. Maybe adding a delay at the kernel level would do. pcie is tagged on the big CPUs so the SATA disks seem to matter (as the ethernet port). One could try in emergency mode (passing emergency to the kernel (I do it by "setenv extraboardargs emergency" after halting u-boot with a key press then enter "boot"). You will have just the root partition mounted read-only (so no network connection, a serial console is required). Then run the test. Also note that the design of the GPU regulator has the same issue as the CPU b one ... (for my tests I blacklisted panfrost, ie the GPU driver). After looking at the rockchip64 board schematics the design around the CPU b regulator is not similar but exactly the same as the helios64 one (rockchip64 uses a tcs4545 regulator for cpu b and tcs4546 for GPU). I wonder if the easiest fix would not be to pay someone to desolder the syr837 regulator and solder a tcs4545 instead - same for the GPU regulator a tcs4546 instead of the syr838... except that these chips from Torch Chip seem nowhere to be found. Maybe rip them from a rockpro64 board. @aprayoga can you confirm the Helios64 design for the rk3399 big cpu and gpu regulators are the same as the RockPro64 ones? Would it make sense (and would it fix the unstable cpu_b) to desolder the syr837/syr838 to replace them with tcs4545/tcs4546? Ie the tcs4535 datasheet (I am still unable to find the tcs4545 datasheet) I found tells tcs425 has internal pulldown for VSEL and EN which syr837 does not, the syr837 datasheet requires a 22uF capacitor for VIN but the helios64 has a 10uF one like the rockpro64 for the tcs4545. The SW pin of the helios64 has 470uH inductor with 4 x 22uF capacitors like the rockpro64 for the tcs4545 (like the typical application in the tcs4535 datasheet with 470uH inductor with two 22uF capacitors)? Do you know a replacement for the TCS4545/TCS4546 that has closer specs than the syr837/syr838? I cannot seem to find TCS4545/TCS4546 for sale (maybe I could buy a rockproc64 to desolder them at least for a test... or could you check on your side with a helios64 board that the cpufreq-switching-2-b test above crash with syr837 but not with tcs4545 with vanilla rk3399 opp definitions in dts? Sadly the Helios64 filled a market that is left unfilled. People who do not have the know-how to go full low-wattage DIY NAS and who also cannot afford to pay 1K€ for a NAS (and who might need two NASs to make things worse). In the meantime, I spend a lot of time learning about DIY NAS, but it is still hard to get wattage at full load (they tend to give all idle power usage). I probably will end up gambling and buying one build and pray... but with Helios64 I had the metrics before buying. I found that the Rock960 has the same design for the cpu_b and gpu regulators except for the inductor which is 0.240uH on the rock960 and 0.470uH on the Helios64. But hard to tell if the Rock960 is stable with my cpufreq switching test for the big cpus of the rk3399, might be the use of the board does not stress it as much as a raid10 on the helios64 pcie sata which is tagged to the cpu_b ... (initially it was 4 3TB WD Red - the old CMR model WD30EFRX-68EUZN0), from Helios4 setup as advertised by Kobol wiki for the Helios4... the board crashes on first boot after assembly with this raid setup. Mind I found that the Pinebook Pro also has the same design as the Helios64 this time around the syr837/syr838 ... I begin to wonder if either they are all broken (could be the amount of stress of a NAS ethernet or raid10 pcie is not that common) or if this is not the issue at stake.

Hi guys, its the first time im gonna post here so bear with me, i am a recent user of orange pi zero 3, one with 4GB RAM and i have been able to run the latest community release on it, things work besides audio thru hdmi, but i have noticed that the video encoding and decoding is not working, albeit 3d acceleration works thru panfrost and Mesa. I have been digging this topic and i wanted to share what i found and maybe validate if im right or perhaps i am not getting this well. 1. Video encoding and decoding in G31-MP2 is something separated from what Mesa and panfrost would do, so even if those work i cant get video acceleration with h.264 etc. 2. It is possible because the android 12 TV version from the manufacturer can do it in a very easy way, but as far as i understood this is because it is using some kind of closed source driver, that the SoC manufacturer provided (that almost all the boards made with the allwinner H616/H618 would run, so it isnt like orange pi dedicated developers to create the android being offered but it is a stock stuff that Allwinner has available for whoever buys their chips) 3. There are efforts to reverse engineer this properly called CEDRUS but there is kind of a lack of information about them since 2019, it is supposedly present in the kernel, but as many others have said and tried for some reason is not working with H616//h618. Anyone knows if it is still being developed? In conclusion the state of things with hardware decoding and encoding of video in ARM is like a wasteland, at least for linux, these chips, ARM chips we get are mostly developed for android TV boxes or TVs or tablets, but they do not develop for linux, that maybe transferring the necessary code to make it work could be trivial, but with thin resources and doing the bare minimum and being closed source the SoC manufacturer has no interest in creating this support and it is left to open source volunteers to find a way. Which means that support for the H616/H618 might come several years into the future perhaps never. Am I interpreting reality right?, i had some hopes to create something like a jellyfin box with accelerated hardware coding and decoding but nothing might be possible, there is maybe some hope, i read somewhere in the LibreELEC forums that someone made it possible to run it with video decoding (if i am not mistaken) with no audio, so perhaps someone found a way?, thanks in advance.

🏆 help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. If you like what you see here and want to help: Donate Armbian, the like button only costs a few dollars. Armbian Needs you help! This Armbian adventure was summarized in my Public Github Repository. H96 MAX V56 RK3566 4gb Ram SD-Card unofficial images: Tutorial SD-Card Version v0.5 DEBIAN12 BETA unofficial Tutorial SD-Card Version v0.5 ARMBIAN23 BETA unofficial H96 MAX V56 RK3566 4gb EMMC unofficial images: Tutorial MMC Version V0.7 DEBIAN12 BETA unofficial Tutorial MMC Version V0.7 ARMBIAN23 BETA unofficial H96 MAX V56 RK3566 4gb EMMC HZDM unofficial images: Tutorial EMMC Version v0.9 ARMBIAN BETA unofficial Debian 12 BookWorm Kernel 6.2 Server v0.9 Beta unofficial Armbian 23.11 Jammy Kernel 6.2 Server v0.9 Beta unofficial Debian 12 BookWorm Kernel 6.2 Desktop v0.9 Beta unofficial Armbian 23.11 Jammy Kernel 6.2 Desktop v0.9 Beta unofficial H96 MAX V56 RK3566 4gb EMMC unofficial images: Tutorial EMMC Version v1.0 ARMBIAN unofficial Armbian 23.11.0 Server Kernel 6.2 Minimal V1.0 unofficial Armbian 23.11.0 Desktop Kernel 6.2 Gnome V1.0 unofficial Debian 12 BookWorm Server Kernel 6.2 Minimal v1.0 unofficial Debian 12 BookWorm Desktop Kernel 6.2 Gnome v1.0 unofficial H96 MAX V56 RK3566 4gb EMMC Hzdm Mainline Boot Custom unofficial images: Tutorial Build Your own Armbian EMMC image unofficial Armbian 23.11.0 Server Minimal Kernel 6.2 Custom Build unofficial Armbian 23.11.0 Desktop Cinnamon Kernel 6.2 Custom Build unofficial Armbian 23.11.0 Desktop XFCE Kernel 6.2 Custom Build unofficial Armbian 23.11.0 Server Standart Kernel 6.2 Custom Build unofficial H96 MAX V56 RK3566 EMMC Raspiblitz HotnikQ unofficial images: Tutorial Build Raspiblitz on EMMC Armbian Bullseye unofficial Armbian 23.11.0 Raspiblitz Custom Build H96 MAX V56 RK3566 4gb EMMC Hzdm Mainline Boot unofficial images: Tutorial Build Your own Armbian EMMC image unofficial Armbian 24.2.1 Server Kernel 6.2 Minimal V1.1 unofficial Armbian 24.2.1 Desktop Kernel 6.2 Gnome V1.1 unofficial Debian 12 BookWorm Server Kernel 6.2 Minimal v1.1 unofficial Debian 12 BookWorm Desktop Kernel 6.2 Gnome v1.1unofficial H96 MAX V56 RK3566 4gb EMMC Ning Mainline Boot Latest official images: Tutorial Build Your own v1.2 & V1.3 Armbian EMMC image official Armbian Desktop Gnome Latest official Debian BookWorm Server Minimal Latest official Software description: V0.5 = @armbian The Armbian SD card image "Compiled From Armbian Project" V0.8 = @hzdm Project with Mainline Bootloader "Boot the 64gb Emmc Armbian with Mainline Rockchip" V0.9 = @hzdm Release Mainline Bootloader "Boot the 32gb and 64gb Emmc Armbian with Mainline Rockchip" V1.0 = @hotnikq The Armbian SD card inside the Android Legacy Rockchip Image "Glued Image: Android boot for Linux" V1.2 = @ning Release Device Tree and Bootloader to longterm 6.6.27 Kernel "Boot with Mainline Rockchip" V1.3 = @Hqnicolas Github PR Enable h96 Rk3566 TV-Box device for Kernel 6.8 Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html Wifi Drivers: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view?usp=sharing Or Just Live install Wifi Driver: cd /lib/firmware/brcm/ sudo wget https://github.com/LibreELEC/brcmfmac_sdio-firmware/raw/master/BCM4335A0.hcd sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.h96-TVbox,rk3566.bin sudo reboot now nmcli dev wifi Topic description: This topic aims to demonstrate the path taken to the Armibian EMMC solution. In our path we create a lot of ready-to-use ROM files, some users burn an use this images without learning with the Linux compilation process. the name of the topic is efforts but that's no effort at all, you should try compile your own images. Device Capability Test: Using Rockchip SoCs NPU. Drivers: https://github.com/rockchip-linux/rknpu2 User Guide: https://github.com/rockchip-linux/rknpu2/blob/master/doc/Rockchip_RKNPU_User_Guide_RKNN_API_V1.4.0_EN.pdf OpenCV: https://opencv.org/blog/2022/11/29/working-with-neural-processing-units-npus-using-opencv/ A discussion on Reddit: https://www.reddit.com/r/OrangePI/comments/12b3jmj/accessing_the_npu_on_the_orange_pi/ Transformers models: https://github.com/usefulsensors/useful-transformers Usage: https://www.crowdsupply.com/useful-sensors/ai-in-a-box/ Usage: https://youtu.be/pN8mKZ5wpdQ

Hi @prahal I've just done a test with your cpufreq-switching-2 program. I'm running Helios64 on Armbian 23.08.0-trunk Bookworm with Linux 6.6.8-edge-rockchip64 I've started with LITTLE (CPUL = 1) The program ran the 100 loops without issue. Then I ran with big (CPUB = 1) So far it failed at the 6th loop Before a third run, I tried to change the interrupt allocation on xhci and ahci as you suggested Please note the interrupts may vary after reboot (e.g. ahci was 76-80, after reboot it is 75-79) # cat /proc/interrupts CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 18: 0 0 0 0 0 0 GICv3 25 Level vgic 20: 0 0 0 0 0 0 GICv3 27 Level kvm guest vtimer 23: 7947 8876 6014 7156 18916 24271 GICv3 30 Level arch_timer 25: 6601 5232 4476 4609 11249 4343 GICv3 113 Level rk_timer 31: 0 0 0 0 0 0 GICv3 37 Level ff6d0000.dma-controller 32: 0 0 0 0 0 0 GICv3 38 Level ff6d0000.dma-controller 33: 0 0 0 0 0 0 GICv3 39 Level ff6e0000.dma-controller 34: 0 0 0 0 0 0 GICv3 40 Level ff6e0000.dma-controller 36: 915 0 0 0 0 0 GICv3 132 Level ttyS2 37: 0 0 0 0 0 0 GICv3 147 Level ff650800.iommu 38: 0 0 0 0 0 0 GICv3 149 Level ff660480.iommu 39: 0 0 0 0 0 0 GICv3 151 Level ff8f3f00.iommu, ff8f0000.vop 40: 0 0 0 0 0 0 GICv3 150 Level ff903f00.iommu, ff900000.vop 41: 0 0 0 0 0 0 GICv3 75 Level ff914000.iommu 42: 0 0 0 0 0 0 GICv3 76 Level ff924000.iommu 43: 0 0 0 0 0 0 GICv3 85 Level ff1d0000.spi 44: 0 0 0 0 0 0 GICv3 84 Level ff1e0000.spi 45: 0 0 0 0 0 0 GICv3 164 Level ff200000.spi 46: 1399 0 0 0 1775 0 GICv3 142 Level xhci-hcd:usb1 47: 30 0 0 0 0 0 GICv3 67 Level ff120000.i2c 48: 0 0 0 0 0 0 GICv3 68 Level ff160000.i2c 49: 5031 0 0 0 0 0 GICv3 89 Level ff3c0000.i2c 50: 540 0 0 0 0 0 GICv3 88 Level ff3d0000.i2c 51: 0 0 0 0 0 0 GICv3 90 Level ff3e0000.i2c 52: 0 0 0 0 0 0 GICv3 129 Level rockchip_thermal 53: 0 0 0 0 0 0 GICv3 152 Edge ff848000.watchdog 54: 0 0 0 0 0 0 GICv3-23 0 Level arm-pmu 55: 0 0 0 0 0 0 GICv3-23 1 Level arm-pmu 56: 0 0 0 0 0 0 rockchip_gpio_irq 9 Edge 2-0020 57: 0 0 0 0 0 0 rockchip_gpio_irq 10 Level rk808 63: 0 0 0 0 0 0 rk808 5 Edge RTC alarm 67: 2 0 0 0 0 0 GICv3 94 Level ff100000.saradc 68: 0 0 0 0 0 0 GICv3 97 Level dw-mci 69: 0 0 0 0 0 0 rockchip_gpio_irq 7 Edge fe320000.mmc cd 70: 0 0 0 0 0 0 GICv3 81 Level pcie-sys 72: 0 0 0 0 0 0 GICv3 83 Level pcie-client 74: 0 0 0 0 0 0 ITS-MSI 0 Edge PCIe PME, aerdrv 75: 0 489 0 0 524 0 ITS-MSI 524288 Edge ahci0 76: 0 0 237 0 0 904 ITS-MSI 524289 Edge ahci1 77: 0 0 0 489 31578 0 ITS-MSI 524290 Edge ahci2 78: 0 0 0 0 249 0 ITS-MSI 524291 Edge ahci3 79: 0 0 0 0 0 248 ITS-MSI 524292 Edge ahci4 83: 14093 0 0 0 0 0 GICv3 43 Level mmc1 84: 0 0 0 0 0 0 rockchip_gpio_irq 5 Edge Power 85: 0 0 0 0 0 0 rockchip_gpio_irq 3 Edge User Button 1 86: 0 0 0 931 0 0 GICv3 44 Level end0 87: 5 0 0 0 0 0 rockchip_gpio_irq 2 Level fsc_interrupt_int_n 88: 0 0 0 0 0 0 GICv3 59 Level rockchip_usb2phy 89: 0 0 0 0 0 0 GICv3 135 Level rockchip_usb2phy_bvalid 90: 0 0 0 0 0 0 GICv3 136 Level rockchip_usb2phy_id 91: 0 0 0 0 0 0 GICv3 60 Level ohci_hcd:usb4 92: 0 0 0 0 0 0 GICv3 58 Level ehci_hcd:usb3 93: 0 0 0 0 0 0 GICv3 137 Level dwc3-otg, xhci-hcd:usb5 94: 0 0 0 0 0 0 GICv3 32 Level rk-crypto 95: 0 0 0 0 0 0 GICv3 146 Level ff650000.video-codec 96: 0 0 0 0 0 0 GICv3 87 Level ff680000.rga 97: 0 0 0 0 0 0 GICv3 145 Level ff650000.video-codec 98: 0 0 0 0 0 0 GICv3 148 Level ff660000.video-codec 99: 0 0 0 0 0 0 rockchip_gpio_irq 2 Edge gpio-charger 100: 0 0 0 0 0 0 rockchip_gpio_irq 27 Edge gpio-charger 101: 2 0 0 0 0 0 GICv3 51 Level panfrost-gpu 102: 0 0 0 0 0 0 GICv3 53 Level panfrost-mmu 103: 0 0 0 0 0 0 GICv3 52 Level panfrost-job IPI0: 1384 1517 1472 1311 4816 7551 Rescheduling interrupts IPI1: 12225 10971 9100 9240 10161 26978 Function call interrupts IPI2: 0 0 0 0 0 0 CPU stop interrupts IPI3: 0 0 0 0 0 0 CPU stop (for crash dump) interrupts IPI4: 2213 2003 2357 2402 2137 1671 Timer broadcast interrupts IPI5: 598 601 747 496 1106 784 IRQ work interrupts IPI6: 0 0 0 0 0 0 CPU wake-up interrupts Err: 0 I reallocated the interrupts over the little core. # echo 0 > /proc/irq/46/smp_affinity_list # echo 1 > /proc/irq/75/smp_affinity_list # echo 2 > /proc/irq/76/smp_affinity_list # echo 3 > /proc/irq/77/smp_affinity_list # echo 0 > /proc/irq/78/smp_affinity_list # echo 1 > /proc/irq/79/smp_affinity_list Then I ran the program on the big again (CPUB = 1) And I reach the 25th loop before it failed.

Hello all, As subtitler guy, I experienced many troubles making aegisub work. , I finally made the subtitle editor, working with hardware under armbian jammy but having still annoyances. I want to share my thought and my discoveries on it. First I would like to thanks all who post on this already, including alternative ways such as schroot and of course the armbian team for the improvements of the boot .. schroot allow to run an linux in a linux. According to what I experienced, meson driver development is leaded by oibaf and in advance in ubuntu but here aegisub does exists only on debian. The idea was thus to boot on debian jammy and chroot in debian buster armhf at least or better bookworm arm64. By doing so, I crashed many time aegisub 3.2.2 due to lua badly supported. schrooting and debian bookworm gives many warning messages (see the pict below, I washed the lua script directory too) but goes further if we dare to skip assert warnings. Moreover, at this point, we are no more dealing with Llvm (software accel using 100% of CPUs) but meson-drm and panfrost (harware accel, using 20% of CPUs). aegisub still remains very fragile but very responsive. So today I decided to switch and to boot into bookworm directly. After launching aegisub 3.20.3 on arm64 with panfrost enabled (you can check this with glxinfo -B, or inxi -Gs), I discovered it is very stable but suffered of responsivity due to a flood in the logs Hewitt has just given... a patch yesterday against "panfrost ffe40000.gpu: l2 power transition timeout" log flood here: https://lkml.org/lkml/2024/3/22/977 You will also be unable to set brightness by software (too bright for my eyes) at least on xfce4, trying my luck with all techniques https://askubuntu.com/questions/894465/changing-the-screen-brightness-of-the-external-screen that did not succeed except that ddcci-dkms gave me a clue during install : BACKLIGHT_CLASS_DEVICE disabled in this kernel I suggest enabling dkms and this for future kernel and taking Hewitt patch into account. With these findings, did someone has noticed the same and manage to make sound and videos responsive without unsync? PS/ For now, the armbian is on a sdcard, the log flood may be the cause of the unsync. I have to test further. Trying with latest jammy and schrooting under bookworm.

Hello everyone, I've recently started migrating a project for Banana Pi M5 from Debian 10 Buster to Armbian, because I've found that the latest versions of it now support the GPU, Mali G31, and come with Panfrost OpenGL driver, which is crucial for this project. Everything was perfect until I had to implement two features: operating with TV via CEC and showing boot logo. Quickly about the last one - as I've understood, we have to use Plymouth, but I didn't really get how to do it, I've tried to activate it but had no success (how exactly see under paragraph). However, it doesn't work on Server Images (even on those that were compiled with build tools and activated option BOOT_LOGO in kernel conf), but in GUI Images everything is fine with it. Also I've tried using uBoot logo (boot-logo.bmp.gz), but also no success. # Adding "splash quiet loglevel=0 logo.nologo" to extraargs in "/boot/armbianEnv.txt" # Activating bootlogo in "/boot/boot.cmd" (am I even supposed to edit this file?) sudo plymouth-set-default-theme -R customtheme # It contains our logo # sudo update-initramfs -c -u # In fact, it runs automatically sudo reboot # ... sudo plymouthd sudo plymouth --show-splash Now about CEC. I've made some observations: CEC Under Debian # Sorry, there is no support for Shell syntax highlighting apparently. pi@TEST:~$ uname -a Linux TEST 4.9.312-BPI-M5 #1 SMP PREEMPT Wed Mar 1 01:44:35 UTC 2023 aarch64 GNU/Linux pi@TEST:~$ cec-client -l libCEC version: 4.0.4, compiled on Linux-4.9.0-8-arm64 ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC Found devices: 1 device: 1 com port: AOCEC vendor id: 0000 product id: 0000 firmware version: 5 type: unknown pi@TEST:~$ ls -l /dev/*cec* crw-rw-rw- 1 root root 503, 0 Feb 14 2019 /dev/aocec pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1 opening a connection to the CEC adapter... pi@TEST:~$ # Works fine. pi@TEST:~$ echo 'on 0' | cec-client -s -d 1 opening a connection to the CEC adapter... pi@TEST:~$ # Works fine. pi@TEST:~$ sudo lsmod | grep cec pi@TEST:~$ sudo find /lib/modules/ -name "*cec*" pi@TEST:~$ # No CEC module in lsmod or modules overall, but works fine. pi@TEST:~$ It uses AOCEC on 4.9 Linux kernel. Works flawlessly. All the parts in "/boot/boot.ini" concerning CEC: ... ### voutmode : hdmi or dvi setenv voutmode "hdmi" # setenv voutmode "dvi" # HPD enable/disable option setenv disablehpd "false" # Enable/Disable CEC setenv cec "true" ... ### Normal HDMI Monitors if test "${display_autodetect}" = "true"; then hdmitx edid; fi if test "${hdmimode}" = "custombuilt"; then setenv cmode "modeline=${modeline}"; fi if test "${cec}" = "true"; then setenv cec_enable "hdmitx=cec3f"; fi ... # Boot Args setenv bootargs "...${cec_enable} sdrmode=${sdrmode}" ... If I set cec "false" this happens: pi@TEST:~$ cec-client -l libCEC version: 4.0.4, compiled on Linux-4.9.0-8-arm64 ... , features: P8_USB, DRM, P8_detect, randr, Exynos, AOCEC Found devices: 1 device: 1 com port: AOCEC vendor id: 0000 product id: 0000 firmware version: 5 type: unknown pi@TEST:~$ ls -l /dev/*cec* crw-rw-rw- 1 root root 503, 0 Feb 14 2019 /dev/aocec pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1 opening a connection to the CEC adapter... unable to open the device on port AOCEC ERROR: [ 2233] AllocateLogicalAddresses - failed to allocate device '0', type 'recording device' ERROR: [ 2233] failed to find a free logical address for the client ERROR: [ 2233] failed to register the new CEC client - cannot allocate the requested device types ERROR: [ 2233] failed to register a CEC client pi@TEST:~$ # Doesn't work pi@TEST:~$ Here, "/dev/aocec" doesn't sweep away when setting CEC to false. It just becomes unaccesible. CEC Under Armbian pi@TEST:~$ uname -a Linux TEST 6.6.8-edge-meson64 #1 SMP PREEMPT Wed Dec 20 16:02:07 UTC 2023 aarch64 GNU/Linux pi@TEST:~$ cec-client -l libCEC version: 6.0.2, compiled on Linux ... , features: P8_USB, DRM, P8_detect, randr, Exynos, Linux, AOCEC Found devices: NONE pi@TEST:~$ ls -l /dev/*cec* ls: cannot access '/dev/*cec*': No such file or directory pi@TEST:~$ echo 'standby 0' | cec-client -s -d 1 autodetect FAILED pi@TEST:~$ echo 'on 0' | cec-client -s -d 1 autodetect FAILED pi@TEST:~$ sudo lsmod | grep cec pi@TEST:~$ sudo find /lib/modules/ -name "*cec*" /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/usb/pulse8/pulse8-cec.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/usb/rainshadow/rainshadow-cec.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/cec-gpio /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/cec-gpio/cec-gpio.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/meson/ao-cec.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/media/cec/platform/meson/ao-cec-g12a.ko /lib/modules/6.6.8-edge-meson64/kernel/drivers/gpu/drm/bridge/synopsys/dw-hdmi-cec.ko pi@TEST:~$ sudo modprobe cec pi@TEST:~$ sudo modprobe cec-gpio pi@TEST:~$ sudo modprobe ao-cec pi@TEST:~$ sudo modprobe ao-cec-g12a pi@TEST:~$ sudo modprobe dw-hdmi-cec pi@TEST:~$ sudo modprobe pulse8-cec pi@TEST:~$ sudo modprobe rainshadow-cec pi@TEST:~$ sudo lsmod | grep cec rainshadow_cec 16384 0 pulse8_cec 24576 0 dw_hdmi_cec 12288 0 ao_cec_g12a 12288 0 ao_cec 16384 0 cec_gpio 12288 0 pi@TEST:~$ # cec.ko isn't in libs so in lsmod there is no such module, but why "modprobe cec" gives no error? pi@TEST:~$ ls -l /dev/*cec* ls: cannot access '/dev/*cec*': No such file or directory pi@TEST:~$ # And activating modules just doesn't help, there is still no any "/dev/*cec*" device pi@TEST:~$ It doesn't use any of CEC on 6.6.8 Bleeding Edge Linux kernel (I've tested it before on stable 6.1 kernel, but it didn't work as well, I've activated some modules concerning CEC in kernel config and built using the latest possible kernel, thinking it will change something). Just doesn't work. AOCEC module is compiled and launched though, but it doesn't use it at all since there is no "/dev/*cec*" device. All the parts in "/boot/boot.cmd" concerning CEC: ... setenv sdrmode "auto" setenv voutmode "hdmi" setenv disablehpd "false" setenv cec "false" ... if test -e ${devtype} ${devnum} ${prefix}zImage; then ... setenv bootargs "...${cec_enable} sdrmode=${sdrmode}" ... Somehow, it misses the part where we should set "cec_enable" variable. What if I restore it and set to true? But I don't really think it will change something, as "/dev/aocec" existed on Debian even when CEC was disabled. That didn't work, as well as adding "hdmitx=cec3f" to extraargs in "/boot/armbianEnv.txt". There is just no CEC device in "/dev/", I don't know which type of problem is that - module, overlay, kernel?? Yes, I've used v4l, and it also fails because it doesn't find any "/dev/*cec*". Anyway, I hope this problem can be resolved and thanks to everyone for attention, have a happy new 2024 year!

Can you be the first to run video drivers on this device? https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html I use it as a server without video render. But some users ask for video acceleration.

Hello! I'm able to reproducibly get a kernel oops whenever I start a docker container on my Helios64 The SD card I was running my Helios64 from died and so I reinstalled Armbian using the steps to install bookworm from this post. I did skip the steps related to hs400 and L2 cache as I'm currently running the system from an SD card. After the install seemed to be working well I installed zfs, imported my existing pool, and then installed docker. My previous setup was using docker's ZFS storage driver so I got that configured as well. Now, whenever I start up a docker container (ie by running "sudo docker run hello-world") I get the following oops from the kernel: [ 246.422387] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000038 [ 246.422400] Mem abort info: [ 246.422403] ESR = 0x0000000096000005 [ 246.422406] EC = 0x25: DABT (current EL), IL = 32 bits [ 246.422411] SET = 0, FnV = 0 [ 246.422414] EA = 0, S1PTW = 0 [ 246.422417] FSC = 0x05: level 1 translation fault [ 246.422421] Data abort info: [ 246.422423] ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 [ 246.422426] CM = 0, WnR = 0, TnD = 0, TagAccess = 0 [ 246.422430] GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [ 246.422434] user pgtable: 4k pages, 48-bit VAs, pgdp=000000000942d000 [ 246.422439] [0000000000000038] pgd=0800000016225003, p4d=0800000016225003, pud=0000000000000000 [ 246.422452] Internal error: Oops: 0000000096000005 [#1] PREEMPT SMP [ 246.423015] Modules linked in: veth xt_nat xt_tcpudp xt_conntrack nft_chain_nat xt_MASQUERADE nf_nat nf_conntrack_netlink nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 xfrm_user xfrm_algo xt_addrtype nft_compat nf_tables nfnetlink br_netfilter bridge rfkill sunrpc lz4hc lz4 zram binfmt_misc zfs(PO) crct10dif_ce leds_pwm panfrost spl(O) gpio_charger gpu_sched drm_shmem_helper pwm_fan snd_soc_hdmi_codec snd_soc_rockchip_i2s rockchip_vdec(C) hantro_vpu rk_crypto snd_soc_core rockchip_rga snd_compress v4l2_vp9 v4l2_h264 videobuf2_dma_sg videobuf2_dma_contig ac97_bus v4l2_mem2mem snd_pcm_dmaengine snd_pcm videobuf2_memops videobuf2_v4l2 snd_timer videodev nvmem_rockchip_efuse videobuf2_common mc snd soundcore gpio_beeper ledtrig_netdev lm75 ip_tables x_tables autofs4 efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear cdc_ncm cdc_ether usbnet r8152 realtek rockchipdrm dw_mipi_dsi fusb302 dw_hdmi tcpm analogix_dp dwmac_rk typec drm_display_helper stmmac_platform cec [ 246.423214] drm_dma_helper stmmac drm_kms_helper drm adc_keys pcs_xpcs [ 246.431612] CPU: 5 PID: 2686 Comm: dockerd Tainted: P C O 6.6.8-edge-rockchip64 #1 [ 246.432383] Hardware name: Helios64 (DT) [ 246.432731] pstate: 60000005 (nZCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 246.433344] pc : get_device_state+0x28/0x88 [ledtrig_netdev] [ 246.433854] lr : netdev_trig_notify+0x13c/0x1fc [ledtrig_netdev] [ 246.434387] sp : ffff80008b2ab3e0 [ 246.434680] x29: ffff80008b2ab3e0 x28: ffff0000154d3378 x27: ffff80007a36dc30 [ 246.435313] x26: ffff800081c89a40 x25: ffff800081907008 x24: ffff80008b2ab5b8 [ 246.435944] x23: 000000000000000b x22: ffff000005efb000 x21: ffff0000154d3300 [ 246.436575] x20: ffff0000154d3378 x19: ffff0000154d3300 x18: ffff80008d293c58 [ 246.437206] x17: 000000040044ffff x16: 00500074b5503510 x15: 0000000000000000 [ 246.437837] x14: ffffffffffffffff x13: 0000000000000020 x12: 0101010101010101 [ 246.438468] x11: 7f7f7f7f7f7f7f7f x10: 000000000f5d83a0 x9 : 0000000000000020 [ 246.439099] x8 : 0101010101010101 x7 : 0000000080000000 x6 : 0000000080303663 [ 246.439729] x5 : 6336300000000000 x4 : 0000000000000000 x3 : 0000000000000000 [ 246.440360] x2 : ffff000021bdbc00 x1 : ffff000021bdbc00 x0 : 0000000000000000 [ 246.440991] Call trace: [ 246.441210] get_device_state+0x28/0x88 [ledtrig_netdev] [ 246.441683] netdev_trig_notify+0x13c/0x1fc [ledtrig_netdev] [ 246.442185] notifier_call_chain+0x74/0x144 [ 246.442561] raw_notifier_call_chain+0x18/0x24 [ 246.442956] call_netdevice_notifiers_info+0x58/0xa4 [ 246.443399] dev_change_name+0x190/0x318 [ 246.443751] do_setlink+0xb7c/0xde4 [ 246.444064] rtnl_setlink+0xf8/0x194 [ 246.444383] rtnetlink_rcv_msg+0x12c/0x398 [ 246.444748] netlink_rcv_skb+0x5c/0x128 [ 246.445089] rtnetlink_rcv+0x18/0x24 [ 246.445408] netlink_unicast+0x2e8/0x350 [ 246.445755] netlink_sendmsg+0x1d4/0x444 [ 246.446102] __sock_sendmsg+0x5c/0xac [ 246.446432] __sys_sendto+0x124/0x150 [ 246.446760] __arm64_sys_sendto+0x28/0x38 [ 246.447117] invoke_syscall+0x48/0x114 [ 246.447453] el0_svc_common.constprop.0+0x40/0xe8 [ 246.447871] do_el0_svc+0x20/0x2c [ 246.448168] el0_svc+0x40/0xf4 [ 246.448442] el0t_64_sync_handler+0x13c/0x158 [ 246.448829] el0t_64_sync+0x190/0x194 [ 246.449158] Code: f9423c20 f90047e0 d2800000 f9404e60 (f9401c01) [ 246.449695] ---[ end trace 0000000000000000 ]--- TIA for the help and for keeping this unsupported hardware alive!

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. ########################### EMMC: V1.1 HZDM Release Version ########################### If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! # Tested on 4gb 32gb version (04/04/2024) Armbian 24.2.1 H96 Max v56 Kernel 6.2.16: The Ubuntu Jammy Server 8gb image unofficial The Ubuntu Jammy Desktop 8gb image unofficial The Debian BookWorm Server 8gb image unofficial The Debian BookWorm Desktop 8gb image unofficial If you given up of Armbian Linux on your H96MAX RK3566 TV box Think Again and again and again and again, because: @hzdm updated armbian Build configuration: V1.1 HZDM original Build Armbian Tutorial: #START# On Linux: 1 - Follow the Build Armbian instructions if it doesnt Build your image as espected rm -rf build git clone --depth 1 --branch v24.02 https://github.com/armbian/build try again and again and again and again 2 - Download H96MAX Armbian Build Config (Original Source) 3 - Copy the h96-max-v56 directory to build/packages/blobs/ directory 4 - Copy the h96-max-v56.conf file to the build/config/boards/ directory 5 - Run the image build ./compile.sh On Windows: 6 - Download the Armbian.cfg file to RKDevTool (Original Source) 7 - Drop it on RKDevTool 8 - Shutting down H96 MAX. 9 - Press the Reset button. 10 - Turn on the H96 MAX. 11 - Wait until The message "Found One MASKROM Device" or "Found One LOADER Device" should appear. (1) 12 - Mark all 2 sections with check marks (2) 13 - Open 2 files for each section (3) 14 - Check "Write by Address" (4). 15 - Press the "Run" button (5). The download will start. When the message "Download image OK" appears, the download is finished (6). 16 - H96 MAX will automatically reboot. Done. Alternative: On Linux OS rkdeveloptool db MiniLoaderAll.bin # If this is not your first time flashing with this firmware, an error may appear here\. It\'s not a big deal rkdeveloptool wl 0x0 Your_Armbian_Image-trunk_H96-max-v56_jammy_current_6.1.62.img rkdeveloptool rd And because a malware was discovered in the XZ library from Edge trixie and Edge sid I came here again to remove and ReBuild all afected images. Ubuntu: One of the most popular Linux distributions is not affected as its xz version is the older 5.4 version. No updates are required. Debian Linux: No stable versions of the distribution were affected. but compromised packages were part of test, unstable and experimental versions. Users must update xz-utils. Read more: CVE-2024-3094 Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html

🏆 Become a sponsor, help to add other boards in armbian standart, you don't need to be a programmer to help the community, just need a copy of the ARM BOARD and a x86 computer to compile new versions. ########################### EMMC: V1.1 HZDM Release Version ########################### If you like what you see here and want to help: Donate Armbian the like button only costs a few dollars. Armbian Needs you help! If you given up of Armbian Linux on your H96MAX RK3566 TV box Think Again and again and again and again, because: @hzdm updated armbian Build configuration: V1.1 HZDM original Build Armbian Tutorial: #START# On Linux: 1 - Follow the Build Armbian instructions if it doesnt Build your image as espected rm -rf build git clone --depth 1 --branch v24.02 https://github.com/armbian/build try again and again and again and again 2 - Download H96MAX Armbian Build Config (Original Source) 3 - Copy the h96-max-v56 directory to build/packages/blobs/ directory 4 - Copy the h96-max-v56.conf file to the build/config/boards/ directory 5 - Run the image build ./compile.sh On Windows: 6 - Download the Armbian.cfg file to RKDevTool (Original Source) 7 - Drop it on RKDevTool 8 - Shutting down H96 MAX. 9 - Press the Reset button. 10 - Turn on the H96 MAX. 11 - Wait until The message "Found One MASKROM Device" or "Found One LOADER Device" should appear. (1) 12 - Mark all 2 sections with check marks (2) 13 - Open 2 files for each section (3) 14 - Check "Write by Address" (4). 15 - Press the "Run" button (5). The download will start. When the message "Download image OK" appears, the download is finished (6). 16 - H96 MAX will automatically reboot. Done. Alternative: On Linux OS rkdeveloptool db MiniLoaderAll.bin # If this is not your first time flashing with this firmware, an error may appear here\. It\'s not a big deal rkdeveloptool wl 0x0 Your_Armbian_Image-trunk_H96-max-v56_jammy_current_6.1.62.img rkdeveloptool rd And because a malware was discovered in the XZ library from Edge trixie and Edge sid I came here again to remove and ReBuild all afected images. Ubuntu: One of the most popular Linux distributions is not affected as its xz version is the older 5.4 version. No updates are required. Debian Linux: No stable versions of the distribution were affected. but compromised packages were part of test, unstable and experimental versions. Users must update xz-utils. Read more: CVE-2024-3094 Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html

This Chinese box It's always a surprise. sometimes it works, sometimes it doesn't Kernel V6.6 was the new standart if you build any image let me know @Antonio Cahuana About the hardware acceleration, i think you can install Video drivers: https://developer.arm.com/downloads/-/mali-drivers/bifrost-kernel https://docs.mesa3d.org/download.html https://docs.mesa3d.org/drivers/panfrost.html

Version 20230401 with kernel 6.2 (pancsf-midstream). With HDMI USB support. https://disk.yandex.ru/d/W8pOOhizVjq91A To enable HW acceleration, install the mesa package with the forced overwrite option or an archive to enable acceleration for wayland. To enable wayland acceleration, you need to replace the files in the /usr/lib/aarch64-linux-gnu directory with the contents of the archive (with file replacement). After that, acceleration will work with wayland. X11 and wayland acceleration works the same way on Debian Sid (the images are the same as Ubuntu). After starting the system and initial configuration, replace the files from the archive in the same way and acceleration will work. The results of running in Debian Sid Gnome for x11 and wayland. dpkg -i --force-overwrite mesa_23.0.0-dev-2_arm64.deb After installation and reboot, HW acceleration will work in x11 and wayland. Please note, this is a test version of mesa for the initial evaluation of the work, some of the functions do not work in it and there may be bugs. With x11, the system works more stably, but the test results are lower than in gnome+wayland. deb\archive https://disk.yandex.ru/d/h8c-Y2FfAvx76g

I tried with recommanded lxc (linux container is more secure) but opengl Mai is not recognized ----> so instead of sudo mkdir -p /srv/chroot/armbian sudo debootstrap --arch arm64 --foreign bookworm /srv/chroot/debian-arm64 http://debian.xtdv.net/debian sudo schroot -c debian-arm64 (step to create user pi skipped) apt install aegisub inxi We notice EVERYTHING IS RECOGNIZED: (debian-arm64)root@bananapim5:/home/pi# inxi -Gs Graphics: Device-1: meson-g12a-vpu driver: meson_drm v: N/A Device-2: meson-g12a-mali driver: panfrost v: kernel Device-3: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: N/A Display: server: X.Org v: 1.21.1.4 driver: dri: meson gpu: meson_drm,panfrost,meson_dw_hdmi note: X driver n/a resolution: 1920x1080~60Hz API: OpenGL v: 3.1 Mesa 22.3.6 renderer: Mali-G31 (Panfrost) Sensors: System Temperatures: cpu: 44.3 C mobo: N/A Fan Speeds (RPM): N/A ++++++> I have done sudo lxc-create --name "arm64-bookworm" --template download -- --dist debian --release bookworm --arch arm64 sudo lxc-start -n "arm64-bookworm" sudo lxc-attach -n "arm64-bookworm" apt install aegisub inxi We notice GL is not FULLY DETECTED root@arm64-bookworm:/home/pi# inxi -Gs Graphics: Device-1: meson-g12a-vpu driver: meson_drm v: N/A Device-2: meson-g12a-mali driver: panfrost v: kernel Device-3: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: N/A Display: server: X.org v: 1.21.1.7 driver: X: loaded: fbdev,modesetting gpu: mroot@arm64-bookworm:/home/pi# inxi -Gs Graphics: Device-1: meson-g12a-vpu driver: meson_drm v: N/A Device-2: meson-g12a-mali driver: panfrost v: kernel Device-3: meson-g12a-dw-hdmi driver: meson_dw_hdmi v: N/A Display: server: X.org v: 1.21.1.7 driver: X: loaded: fbdev,modesetting gpu: meson_drm,panfrost,meson_dw_hdmi resolution: 1920x1080 API: OpenGL Message: GL data unavailable for root. eson_drm,panfrost,meson_dw_hdmi resolution: 1920x1080 API: OpenGL Message: GL data unavailable for root. root@arm64-bookworm:/home/pi# lshw -c video *-graphics product: mesondrmfb physical id: 5 logical name: /dev/fb0 capabilities: fb configuration: depth=32 resolution=720,480 root@arm64-bookworm:/home/pi# xrandr --listproviders Can't open display :0 The reason is OpenGL rely on Xorg and Xorg can't find my display event after doing export DISPLAY=:0 the device :dev/fb0 does not exist also.as we can seet it withe the Xorg log: root@arm64-bookworm:/home/pi# cat /var/log/Xorg.0.log [ 25980.096] X.Org X Server 1.21.1.7 X Protocol Version 11, Revision 0 [ 25980.096] Current Operating System: Linux arm64-bookworm 6.2.0-rc3-meson64 #23.02.2 SMP PREEMPT Fri Feb 17 23:06:22 UTC 2023 aarch64 [ 25980.096] Kernel command line: root=UUID=4cc9d1be-c592-4e80-8f1c-e73b8c044930 rootwait rootfstype=ext4 splash plymouth.ignore-serial-consoles console=ttyAML0,115200 console=tty1 consoleblank=0 coherent_pool=2M loglevel=1 ubootpart=7ac72bfa-01 libata.force=noncq usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u,0x1058:0x1001:u video=drm_kms_helper.edid_firmware=HDMI-A-1:edid/720x480.bin video=HDMI-A-1:720x480M@60 fbcon=rotate:0 module_blacklist=simpledrm cgroup_enable=memory swapaccount=1 [ 25980.096] xorg-server 2:21.1.7-3+deb12u5 (https://www.debian.org/support) [ 25980.096] Current version of pixman: 0.42.2 [ 25980.097] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 25980.097] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 25980.097] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 17 20:03:34 2024 [ 25980.098] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 25980.098] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 25980.100] (==) ServerLayout "dummy_layout" [ 25980.100] (**) |-->Screen "dummy_screen" (0) [ 25980.100] (**) | |-->Monitor "dummy_monitor" [ 25980.101] (**) | |-->Device "dummy_videocard" [ 25980.101] (**) |-->Input Device "dummy_mouse" [ 25980.101] (**) |-->Input Device "dummy_keyboard" [ 25980.101] (==) Automatically adding devices [ 25980.101] (==) Automatically enabling devices [ 25980.101] (==) Automatically adding GPU devices [ 25980.101] (==) Automatically binding GPU devices [ 25980.101] (==) Max clients allowed: 256, resource mask: 0x1fffff [ 25980.101] (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. [ 25980.101] Entry deleted from font path. [ 25980.101] (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, built-ins [ 25980.101] (==) ModulePath set to "/usr/lib/xorg/modules" [ 25980.101] (II) Loader magic: 0xaaaac1da0f00 [ 25980.101] (II) Module ABI versions: [ 25980.101] X.Org ANSI C Emulation: 0.4 [ 25980.101] X.Org Video Driver: 25.2 [ 25980.101] X.Org XInput driver : 24.4 [ 25980.101] X.Org Server Extension : 10.0 [ 25980.105] (EE) systemd-logind: failed to get session: PID 991 does not belong to any known session [ 25980.109] (II) xfree86: Adding drm device (/dev/dri/card0) [ 25980.109] (II) Platform probe for /sys/devices/platform/soc/ff900000.vpu/drm/card0 [ 25980.111] (II) xfree86: Adding drm device (/dev/dri/card1) [ 25980.111] (II) Platform probe for /sys/devices/platform/soc/ffe40000.gpu/drm/card1 [ 25980.111] (II) no primary bus or device found [ 25980.111] (II) LoadModule: "glx" [ 25980.112] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so [ 25980.115] (II) Module glx: vendor="X.Org Foundation" [ 25980.116] compiled for 1.21.1.7, module version = 1.0.0 [ 25980.116] ABI class: X.Org Server Extension, version 10.0 [ 25980.116] (==) Matched modesetting as autoconfigured driver 0 [ 25980.116] (==) Matched fbdev as autoconfigured driver 1 [ 25980.116] (==) Assigned the driver to the xf86ConfigLayout [ 25980.116] (II) LoadModule: "modesetting" [ 25980.116] (II) Loading /usr/lib/xorg/modules/drivers/modesetting_drv.so [ 25980.117] (II) Module modesetting: vendor="X.Org Foundation" [ 25980.117] compiled for 1.21.1.7, module version = 1.21.1 [ 25980.117] Module class: X.Org Video Driver [ 25980.117] ABI class: X.Org Video Driver, version 25.2 [ 25980.117] (II) LoadModule: "fbdev" [ 25980.117] (II) Loading /usr/lib/xorg/modules/drivers/fbdev_drv.so [ 25980.117] (II) Module fbdev: vendor="X.Org Foundation" [ 25980.118] compiled for 1.21.1.3, module version = 0.5.0 [ 25980.118] Module class: X.Org Video Driver [ 25980.118] ABI class: X.Org Video Driver, version 25.2 [ 25980.118] (II) LoadModule: "void" [ 25980.118] (WW) Warning, couldn't open module void [ 25980.118] (EE) Failed to load module "void" (module does not exist, 0) [ 25980.118] (II) modesetting: Driver for Modesetting Kernel Drivers: kms [ 25980.118] (II) FBDEV: driver for framebuffer: fbdev [ 25980.119] (WW) Falling back to old probe method for modesetting [ 25980.119] (EE) open /dev/dri/card0: No such file or directory [ 25980.119] (WW) Falling back to old probe method for fbdev [ 25980.119] (II) Loading sub module "fbdevhw" [ 25980.119] (II) LoadModule: "fbdevhw" [ 25980.119] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 25980.119] (II) Module fbdevhw: vendor="X.Org Foundation" [ 25980.119] compiled for 1.21.1.7, module version = 0.0.2 [ 25980.119] ABI class: X.Org Video Driver, version 25.2 [ 25980.120] (EE) open /dev/fb0: No such file or directory [ 25980.120] (WW) Falling back to old probe method for modesetting [ 25980.120] (EE) open /dev/dri/card0: No such file or directory [ 25980.120] (WW) Falling back to old probe method for fbdev [ 25980.120] (II) Loading sub module "fbdevhw" [ 25980.120] (II) LoadModule: "fbdevhw" [ 25980.120] (II) Loading /usr/lib/xorg/modules/libfbdevhw.so [ 25980.120] (II) Module fbdevhw: vendor="X.Org Foundation" [ 25980.120] compiled for 1.21.1.7, module version = 0.0.2 [ 25980.120] ABI class: X.Org Video Driver, version 25.2 [ 25980.120] (EE) open /dev/fb0: No such file or directory [ 25980.120] (EE) No devices detected. [ 25980.120] (EE) Fatal server error: [ 25980.120] (EE) no screens found(EE) [ 25980.120] (EE) Please consult the The X.Org Foundation support at http://wiki.x.org for help. [ 25980.121] (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. [ 25980.121] (EE) [ 25980.121] (EE) Server terminated with error (1). Closing log file. Thus starting aegisub in linux container is impossible. root@arm64-bookworm:/home/pi# su - pi pi@arm64-bookworm:~$ aegisub-3.2 12:56:43: Error: Unable to initialize GTK+, is DISPLAY set properly? So now the question is DOES SOMEONE KNOW HOW TO MAKE LINUX CONTAINER WORK GRAPHICALLY UNDER Ubuntu JAMMY?

Normally, I would have said: "With suitable firmware in SPI flash, a raw image on any storage device is sufficient". This is still true for FC38, but further development of the kernel has revealed a flaw in the support of the S922X SoC. This results in a kernel exception for operation with an ODROID N2/N2+. Of course, this means that it no longer works out-of-the-box for newer releases. As far as I know, no one has yet provided a mainline acceptable solution, it is just a revert of the advancement. Of course, this is not a long-term solution and is not accepted in mainline. Rusticl doesn't seem to be able to use the Mali GPU in your setup. I can't tell if the kernel doesn't make it available via the panfrost driver or if Mesa 22.3.6 doesn't even provide rusticl panfrost driver support yet. For a quick test, I started FC38 again: As you can see from the clinfo-02.log, Mesa 23.1.9 still lacks basic extensions for rusticl. So it's quite possible that mesa 22.3.6 isn't enough. But it may also be that it is messed up by your additionally installed CL platforms.

Hi, okay, your workflow regarding creating an own OS image is definitely beyond my knowledge 😅. Maybe I will give it a try to create an image for the N2 via the Armbian build system. That looks quite straight forward. Maybe I just screwed up something on my system when I can not get clinfo to detect my GPU, so there is a chance that it works OOTB after fresh install... Here is the output of the command you requested: $ sudo RUSTICL_ENABLE=panfrost clinfo Number of platforms 3 Platform Name ARM Platform Platform Vendor ARM Platform Version OpenCL 2.0 git.c8adbf9.122c9daed32dbba4b3056f41a2f23c58 Platform Profile FULL_PROFILE Platform Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp16 cl_khr_icd cl_khr_egl_image cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_subgroups cl_khr_create_command_queue cl_arm_core_id cl_arm_printf cl_arm_thread_limit_hint cl_arm_non_uniform_work_group_size cl_arm_import_memory cl_arm_shared_virtual_memory Platform Extensions function suffix ARM Platform Name rusticl Platform Vendor Mesa/X.org Platform Version OpenCL 3.0 Platform Profile FULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions with Version cl_khr_icd 0x400000 (1.0.0) Platform Numeric Version 0xc00000 (3.0.0) Platform Extensions function suffix MESA Platform Host timer resolution 0ns Platform Name Clover Platform Vendor Mesa Platform Version OpenCL 1.1 Mesa 22.3.6 Platform Profile FULL_PROFILE Platform Extensions cl_khr_icd Platform Extensions function suffix MESA Platform Name ARM Platform Number of devices 1 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Device Name <printDeviceInfo:0: get CL_DEVICE_NAME size : error -6> Device Vendor ARM Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Device Vendor ID <printDeviceInfo:2: get CL_DEVICE_VENDOR_ID : error -6> Device Version OpenCL 2.0 git.c8adbf9.122c9daed32dbba4b3056f41a2f23c58 Driver Version 2.0 Device OpenCL C Version OpenCL C 2.0 git.c8adbf9.122c9daed32dbba4b3056f41a2f23c58 Device Type GPU Device Profile FULL_PROFILE Device Available Yes Compiler Available Yes Linker Available Yes Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Max compute units <printDeviceInfo:32: get CL_DEVICE_MAX_COMPUTE_UNITS : error -6> Available core IDs (ARM) <printDeviceInfo:33: get CL_DEVICE_COMPUTE_UNITS_BITFIELD_ARM : error -30> Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Max clock frequency <printDeviceInfo:40: get CL_DEVICE_MAX_CLOCK_FREQUENCY : error -6> Device Partition (core) Max number of sub-devices 0 Supported partition types None Supported affinity domains (n/a) Max work item dimensions 3 Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Max work item sizes <printDeviceInfo:62: get number of CL_DEVICE_MAX_WORK_ITEM_SIZES : error -6> Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Max work group size <printDeviceInfo:63: get CL_DEVICE_MAX_WORK_GROUP_SIZE : error -6> Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Preferred work group size multiple (kernel) <getWGsizes:1950: create context : error -6> Preferred / native vector sizes char 16 / 4 short 8 / 2 int 4 / 1 long 2 / 1 half 8 / 2 (cl_khr_fp16) float 4 / 1 double 0 / 0 (n/a) Half-precision Floating-point support (cl_khr_fp16) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Single-precision Floating-point support (core) Denormals Yes Infinity and NANs Yes Round to nearest Yes Round to zero Yes Round to infinity Yes IEEE754-2008 fused multiply-add Yes Support is emulated in software No Correctly-rounded divide and sqrt operations No Double-precision Floating-point support (n/a) Address bits 64, Little-Endian Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Global memory size <printDeviceInfo:108: get CL_DEVICE_GLOBAL_MEM_SIZE : error -6> Error Correction support No Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Max memory allocation <printDeviceInfo:114: get CL_DEVICE_MAX_MEM_ALLOC_SIZE : error -6> Unified memory for Host and Device Yes Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Shared Virtual Memory (SVM) capabilities <printDeviceInfo:117: get CL_DEVICE_SVM_CAPABILITIES : error -6> Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Shared Virtual Memory (SVM) capabilities (ARM) <printDeviceInfo:118: get CL_DEVICE_SVM_CAPABILITIES_ARM : error -6> Minimum alignment for any data type 128 bytes Alignment of base address 1024 bits (128 bytes) Preferred alignment for atomics SVM 0 bytes Global 0 bytes Local 0 bytes Max size for global variable 65536 (64KiB) Preferred total size of global vars 0 Global Memory cache type Read/Write Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Global Memory cache size <printDeviceInfo:139: get CL_DEVICE_GLOBAL_MEM_CACHE_SIZE : error -6> Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Global Memory cache line size <printDeviceInfo:140: get CL_DEVICE_GLOBAL_MEM_CACHELINE_SIZE : error -6> Image support Yes Max number of samplers per kernel 16 Max size for 1D images from buffer 65536 pixels Max 1D or 2D image array size 2048 images Base address alignment for 2D image buffers 32 bytes Pitch alignment for 2D image buffers 64 pixels Max 2D image size 65536x65536 pixels Max 3D image size 65536x65536x65536 pixels Max number of read image args 128 Max number of write image args 64 Max number of read/write image args 64 Max number of pipe args 16 Max active pipe reservations 1 Max pipe packet size 1024 Local memory type Global Local memory size 32768 (32KiB) Max number of constant args 8 Max constant buffer size 65536 (64KiB) Max size of kernel argument 1024 Queue properties (on host) Out-of-order execution Yes Profiling Yes Queue properties (on device) Out-of-order execution Yes Profiling Yes Preferred size 2097152 (2MiB) Max size 16777216 (16MiB) Max queues on device 1 Max events on device 1024 Prefer user sync for interop No Failed creating base context during opening of kernel driver. Kernel module may not have been loaded Profiling timer resolution <printDeviceInfo:195: get CL_DEVICE_PROFILING_TIMER_RESOLUTION : error -6> Execution capabilities Run OpenCL kernels Yes Run native kernels No printf() buffer size 1048576 (1024KiB) Built-in kernels (n/a) Device Extensions cl_khr_global_int32_base_atomics cl_khr_global_int32_extended_atomics cl_khr_local_int32_base_atomics cl_khr_local_int32_extended_atomics cl_khr_byte_addressable_store cl_khr_3d_image_writes cl_khr_int64_base_atomics cl_khr_int64_extended_atomics cl_khr_fp16 cl_khr_icd cl_khr_egl_image cl_khr_image2d_from_buffer cl_khr_depth_images cl_khr_subgroups cl_khr_create_command_queue cl_arm_core_id cl_arm_printf cl_arm_thread_limit_hint cl_arm_non_uniform_work_group_size cl_arm_import_memory cl_arm_shared_virtual_memory Platform Name rusticl Number of devices 0 Platform Name Clover Number of devices 0 NULL platform behavior clGetPlatformInfo(NULL, CL_PLATFORM_NAME, ...) ARM Platform clGetDeviceIDs(NULL, CL_DEVICE_TYPE_ALL, ...) Success [ARM] Failed creating base context during opening of kernel driver. Kernel module may not have been loaded clCreateContext(NULL, ...) [default] <checkNullCtx:4108: create context with device from default platform : error -6> clCreateContext(NULL, ...) [other] <error: no devices in non-default plaforms> Failed creating base context during opening of kernel driver. Kernel module may not have been loaded clCreateContextFromType(NULL, CL_DEVICE_TYPE_DEFAULT) <checkNullCtxFromType:4160: create context from type CL_DEVICE_TYPE_DEFAULT : error -6> clCreateContextFromType(NULL, CL_DEVICE_TYPE_CPU) No devices found in platform Failed creating base context during opening of kernel driver. Kernel module may not have been loaded clCreateContextFromType(NULL, CL_DEVICE_TYPE_GPU) <checkNullCtxFromType:4160: create context from type CL_DEVICE_TYPE_GPU : error -6> clCreateContextFromType(NULL, CL_DEVICE_TYPE_ACCELERATOR) No devices found in platform clCreateContextFromType(NULL, CL_DEVICE_TYPE_CUSTOM) No devices found in platform Failed creating base context during opening of kernel driver. Kernel module may not have been loaded clCreateContextFromType(NULL, CL_DEVICE_TYPE_ALL) <checkNullCtxFromType:4160: create context from type CL_DEVICE_TYPE_ALL : error -6> ICD loader properties ICD loader Name OpenCL ICD Loader ICD loader Vendor OCL Icd free software ICD loader Version 2.2.14 ICD loader Profile OpenCL 3.0

I'm currently running this: since Debian based systems are for my taste way to stable - outdated. At times, I grab a nightly image, rearrange it to my liking, drop in my personal configuration preferences and use it till the cycle restarts. Nothing special, the key is current mainline releases. Panfrost has been very mature for a long time, so the kernel version may be a bit older. But of course, the latest version comes with the latest fixes and improvements. The same goes for Mesa, and that's where the current release is important, as the development of Rusticl is still quite vivid. To use a version that is more than a year old, and thus to forego any improvements that have taken place during this time, is quite courageous. But nevertheless, I would be interested in the output result of this command: RUSTICL_ENABLE=panfrost clinfo

@usual user Well, that doesn't look that bad, I would say. But I personally am stuck where clinfo tells me that the GPU has not been found and that the kernel driver module seems not to be loaded. I tried a lot of thing like the default panfrost driver, self-compiled ARM driver, ARM userspace driver... Sure, I might have screwed some things up by myself. But I wouldn't have started tinkering around with that if it had worked from the beginning on .

The mesa Panfrost over panthor kernel driver can be built according to my note：Panfrost-build-howto

I installed Armbian_23.5.4_Helios64_bookworm_current_6.1.36 and kernel helios64 6.6.8-edge-rockchip64. Generally it is ok. First from long time I do not need to limit my sata to 3gbit , and I using cpu governor : on demand with min: 408000 max: 1200000 . ,instead of performance 1416000 My configuration its little specific because Im using LUKS crypt on top of my ZFS mirror (2x 4TB) + 1 cache SSD + 2 hdd EXT4 encrypted with ZFS. I tested NFS yesterday , and I successfully downloaded ~ 700GB without any errors . only what is not working as expected, that running sbc-bench.sh , causing kernel panic . ( http://sprunge.us/3VLJNX ) I will still test it, but it good point to start. [ 3500.389590] Internal error: Oops: 0000000086000004 [#1] PREEMPT SMP [ 3500.390166] Modules linked in: governor_powersave governor_performance dm_crypt trusted asn1_encoder nfsv3 nfs fscache netfs rfkill lz4hc lz4 zram binfmt_misc zfs(PO) spl(O) snd_soc_hdmi_codec snd_soc_rockchip_i2s crct10dif_ce rockchip_vdec(C) hantro_vpu snd_soc_core rockchip_rga v4l2_vp9 leds_pwm snd_compress v4l2_h264 ac97_bus videobuf2_dma_contig v4l2_mem2mem snd_pcm_dmaengine videobuf2_dma_sg snd_pcm pwm_fan panfrost gpu_sched gpio_charger drm_shmem_helper videobuf2_memops videobuf2_v4l2 snd_timer rk_crypto videodev snd videobuf2_common nvmem_rockchip_efuse mc soundcore gpio_beeper ledtrig_netdev nfsd lm75 auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 efivarfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx raid1 raid0 multipath linear cdc_ncm cdc_ether usbnet r8152 rockchipdrm realtek dw_mipi_dsi dw_hdmi analogix_dp fusb302 drm_display_helper tcpm cec typec dwmac_rk stmmac_platform drm_dma_helper drm_kms_helper stmmac drm adc_keys pcs_xpcs [ 3500.398227] CPU: 4 PID: 0 Comm: swapper/4 Tainted: P C O 6.6.8-edge-rockchip64 #1 [ 3500.399007] Hardware name: Helios64 (DT) [ 3500.399362] pstate: 000000c5 (nzcv daIF -PAN -UAO -TCO -DIT -SSBS BTYPE=--) [ 3500.399988] pc : psi_group_change+0xc8/0x358 [ 3500.400388] lr : psi_task_change+0x8c/0xbc [ 3500.400767] sp : ffff80008203bd60 [ 3500.401069] x29: ffff80008203bd70 x28: ffff800075e65000 x27: ffff800081cac8e8 [ 3500.401720] x26: ffff800081909d40 x25: 0000000000000000 x24: ffff800081907008 [ 3500.402368] x23: 0000000000000001 x22: 0000000000000000 x21: 0000000000000000 [ 3500.403015] x20: ffff0000f776ed40 x19: 0000000000000004 x18: 0000000000000000 [ 3500.403662] x17: ffff800075e65000 x16: ffff800082038000 x15: 0000000000000001 [ 3500.404309] x14: 0000000000000000 x13: ffff800081581d50 x12: ffff800081c89b68 [ 3500.404957] x11: 0000000000000040 x10: 0000000000000004 x9 : 0000032eff793e13 [ 3500.405605] x8 : ffff800081c8dd28 x7 : 0000000000000000 x6 : 000000001c036006 [ 3500.406252] x5 : 0000000000000001 x4 : 0000000000000001 x3 : 0000000000000001 [ 3500.406898] x2 : 0000000000000001 x1 : 0000000000000004 x0 : ffff0000f776ed40 [ 3500.407545] Call trace: [ 3500.407771] psi_group_change+0xc8/0x358 [ 3500.408131] psi_task_change+0x8c/0xbc [ 3500.408479] activate_task+0xcc/0x128 [ 3500.408818] ttwu_do_activate+0x58/0x274 [ 3500.409180] sched_ttwu_pending+0xe4/0x1c0 [ 3500.409557] __flush_smp_call_function_queue+0x14c/0x458 [ 3500.410042] generic_smp_call_function_single_interrupt+0x14/0x20 [ 3500.410594] ipi_handler+0x84/0x250 [ 3500.410920] handle_percpu_devid_irq+0xa4/0x230 [ 3500.411337] generic_handle_domain_irq+0x2c/0x44 [ 3500.411756] gic_handle_irq+0x50/0x128 [ 3500.412097] call_on_irq_stack+0x24/0x4c [ 3500.412458] do_interrupt_handler+0xd4/0xd8 [ 3500.412842] el1_interrupt+0x34/0x68 [ 3500.413173] el1h_64_irq_handler+0x18/0x24 [ 3500.413548] el1h_64_irq+0x64/0x68 [ 3500.413860] cpuidle_enter_state+0xc0/0x4bc [ 3500.414246] cpuidle_enter+0x38/0x50 [ 3500.414577] do_idle+0x1fc/0x270 [ 3500.414878] cpu_startup_entry+0x38/0x3c [ 3500.415238] secondary_start_kernel+0x128/0x148 [ 3500.415653] __secondary_switched+0xb8/0xbc [ 3500.416043] Code: 54fffec1 52800002 52800024 34000173 (8b224a80) [ 3500.416592] ---[ end trace 0000000000000000 ]--- [ 3500.417009] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 3500.417621] SMP: stopping secondary CPUs [ 3500.418110] Kernel Offset: disabled [ 3500.418425] CPU features: 0x1,00000208,3c020000,1000421b [ 3500.418903] Memory Limit: none [ 3500.419192] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]---

Description This is a follow-up of: https://github.com/armbian/build/pull/5901 It resolves a conflict between the SimpleDRM and Panfrost graphic drivers by blacklisting simpledrm. Other boards of the same family are assumed to have the same issue and will probably benefit from this fix as well. However, the fix has been actually tested only on the Khadas VIM3. I cannot test this change for other boards, as I do not own them. The Banana Pi M5 was also included for this change, because the driver conflict has also been mentioned in another Jira ticket. Note that this board is of the meson-sm1 family! How Has This Been Tested? Perhaps someone else has these boards available for testing? 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 [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article

Description Some high-resolution monitors (QHD/4K) will not output the desktop, and will enter sleep mode, directly after booting up an Armbian 23.8.1 desktop image and completing the initial setup questions. When such a monitor is attached, the kernel will auto-detect the SimpleDRM graphics driver, which is then prioritized over the Panfrost graphics driver. However, SimpleDRM outputs to a virtual output, while Panfrost outputs to the actual HDMI port. This causes the monitor to not receive any data. By blacklisting the simpledrm kernel module, Panfrost will take care of accelerated graphics (for any monitor) by default. Advanced users can still access simpledrm if required. Jira reference number [AR-1908] How Has This Been Tested? An Armbian image with a Cinnamon desktop has been build using the default options. That image has been written to a SD-card and tested on both a QHD monitor (that had the initial problem) and an older Full HD monitor (that worked fine before as well). In both test cases, the simpledrm kernel module was not loaded. The desktop was visible on the HDMI output both on initial boot and after subsequent reboots. 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 [N/A] I have made corresponding changes to the documentation [X] My changes generate no new warnings [N/A] Any dependent changes have been merged and published in downstream modules View the full article

@amazingfate This is it!!! You solved my root problem Thank you! I modified the EGL code, and now with device #1 works well. root@ubuntu:~/egl_example# ./egl_example dev1 Explicit device selection: 1 Loaded EGL 1.4 after reload. GL_VENDOR=Panfrost GL_RENDERER=Mali-G610 (Panfrost) GL_VERSION=3.3 (Compatibility Profile) Mesa 23.0.0-devel GL_SHADING_LANGUAGE_VERSION=3.30 root@ubuntu:~/egl_example# ./egl_example dev1 es2 Explicit device selection: 1 Loaded EGL 1.4 after reload. GL_VENDOR=Panfrost GL_RENDERER=Mali-G610 (Panfrost) GL_VERSION=OpenGL ES 3.1 Mesa 23.0.0-devel GL_SHADING_LANGUAGE_VERSION=OpenGL ES GLSL ES 3.10

I can confirm, after installing Armbian for Orange Pi 3 zero on the Orange Pi zero 2w that WiFi, Bluetooth and HDMI is working! me@OPIZ2W:~$ DISPLAY=:0 glxinfo -B name of display: :0 display: :0 screen: 0 direct rendering: Yes Extended renderer info (GLX_MESA_query_renderer): Vendor: Panfrost (0xffffffff) Device: Mali-G31 (Panfrost) (0xffffffff) Version: 22.3.6 Accelerated: yes Video memory: 3932MB Unified memory: yes Preferred profile: core (0x1) Max core profile version: 3.1 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.1 OpenGL vendor string: Panfrost OpenGL renderer string: Mali-G31 (Panfrost) OpenGL core profile version string: 3.1 Mesa 22.3.6 OpenGL core profile shading language version string: 1.40 OpenGL core profile context flags: (none) OpenGL version string: 3.1 Mesa 22.3.6 OpenGL shading language version string: 1.40 OpenGL context flags: (none) OpenGL ES profile version string: OpenGL ES 3.1 Mesa 22.3.6 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.10

I have been trying to research this and have come up a bit blank. I am trying to figure out if I need to do anything special to enable panfrost. I have built a jammy and bookworm image using the stable kernel. Both boot fine, but are both using llvmpipe. It does look like its trying to use panfrost. Inside of dmesg: [ 20.098662] panfrost fde60000.gpu: clock rate = 594000000 [ 20.098685] panfrost fde60000.gpu: bus_clock rate = 500000000 [ 20.098820] panfrost fde60000.gpu: Looking up mali-supply from device tree [ 20.099041] panfrost fde60000.gpu: _of_add_opp_table_v2: no supported OPPs [ 20.099287] panfrost fde60000.gpu: devfreq init failed -2 [ 20.099301] panfrost fde60000.gpu: Fatal error during GPU init [ 20.099458] panfrost: probe of fde60000.gpu failed with error -2 I tried building with a newer kernel, but was having issues on boot. I haven't dug into that further yet. Anyone have any thoughts or advise? Thanks