All Activity

Booting from internal eMMC also works. Regarding HDMI: I've made another build where I pulled the DTS definitions for the M1S from the Linux mainline repository directly during compilation (thanks ChatGPT!). But that also did not help. The system "works" as before, just no HDMI...

If it isn't the PSU or SD than I'm not sure. The only REV available in the STATES "which is where I am" is the 2GB. The u-boot patch set is identical to the BPI-M4-Zero "minus the dts and defconfig of course". All my testing has been done with the unit I have available to me. It works with the Armbian, KIckpi and my own personal builds. As an aside the Kickpi web site is down for me STATE side. Not sure what that means? Doesn't look good though. Anyway, I'm out of ideas. Sorry.

I dd the armbian.img > emmc. and remove my sd card still the same output

I learned today that the cpudriver is the default which caps all cores at 480000 and refuses to respond to govenor or maxes or mins. Currently digging through the armbian build system to get the rockchip kernel source info to manually compile the rockchip_cpufreq.ko and I did see that the patchfiles (irrelevant for cpufreq) contained this: - "MAINTAINERS" # constant churn, drop them. sorry. - "Documentation/devicetree/bindings/arm/rockchip.yaml" # constant churn, conflicts on every bump, drop it. sorry. Given the fact that the build system says it's dropped and the forums say it's dropped I only expect support for the 5b to worsen over time. For anyone reading this, It's best to start looking for replacements for armbian for this board. The 5b has been tossed overboard by armbian, and there will be more breaking changes for it like the emmc that noone from the armbian team will care to fix or investigate. For anyone else going down this rabbithole, allow me to save you some time vendor) BOOTDIR='u-boot-rockchip64' declare -g KERNEL_MAJOR_MINOR="6.1" # Major and minor versions of this kernel. declare -g -i KERNEL_GIT_CACHE_TTL=120 # 2 minutes; this is a high-traffic repo KERNELSOURCE='https://github.com/armbian/linux-rockchip.git' KERNELBRANCH='branch:rk-6.1-rkr5.1' KERNELPATCHDIR='rk35xx-vendor-6.1'

Yep enabled the module and it's working now, Just sent a PR. Thank you.

Using mainline, which this img does, I have only had issues when the PSU isn't up to snuff. A 5V 2A should be enough, I use a 5V 3A usually. My only other suggestion would be; dd off the u-boot and OS from the eMMC and see if that helps.

I dont think so. I can boot the official system “kickpi-k2b-ubuntu-jammy-desktop-xfce-linux-5.4.125-20250901.img” using this SD card

@chuanzz 345032 -rw-rw-r-- 1 patrick patrick 353310884 Oct 23 11:00 Armbian_community_25.11.0-trunk.334_Kickpik2b_trixie_current_6.12.47_minimal.img.xz U-Boot SPL 2025.07 (Sep 24 2025 - 18:40:04 -0400) DRAM: 2048 MiB Trying to boot from MMC2 NOTICE: BL31: v2.12.5(debug):lts-v2.12.5 NOTICE: BL31: Built : 11:56:13, Sep 10 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0cd800, model: KickPi K2B INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: Probing for PMIC on I2C: INFO: PMIC: found AXP313 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. U-Boot SPL 2025.07-armbian-2025.07-Se37d-Pe61e-H8869-Vbdbf-Bb703-R448a (Oct 16 2025 - 02:34:23 +0000) DRAM: 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.12.5(debug):armbian NOTICE: BL31: Built : 03:03:57, Oct 1 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b7550, model: KickPi K2B INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: Probing for PMIC on I2C: INFO: PMIC: found AXP313 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.07-armbian-2025.07-Se37d-Pe61e-H8869-Vbdbf-Bb703-R448a (Oct 16 2025 - 02:34:23 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: KickPi K2B DRAM: 2 GiB Core: 74 devices, 23 uclasses, devicetree: separate WDT: Not starting watchdog@30090a0 MMC: mmc@4020000: 0, mmc@4021000: 2, mmc@4022000: 1 Loading Environment from FAT... Unable to use mmc 0:1... In: serial@5000000 Out: serial@5000000 Err: serial@5000000 Allwinner mUSB OTG (Peripheral) Net: eth0: ethernet@5020000using musb-hdrc, OUT ep1out IN ep1in STATUS ep2in MAC de:ad:be:ef:00:01 HOST MAC de:ad:be:ef:00:00 RNDIS ready , eth1: usb_ether starting USB... sun4i_usb_phy phy@5100400: External vbus detected, not enabling our own vbus USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 USB EHCI 1.00 USB OHCI 1.0 Bus usb@5101000: 1 USB Device(s) found Bus usb@5101400: 1 USB Device(s) found Bus usb@5200000: 1 USB Device(s) found Bus usb@5200400: 1 USB Device(s) found Bus usb@5310000: 1 USB Device(s) found Bus usb@5310400: 1 USB Device(s) found scanning usb for storage devices... 0 Storage Device(s) found Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc0 is current device Scanning mmc 0:1... Found U-Boot script /boot/boot.scr 4641 bytes read in 2 ms (2.2 MiB/s) ## Executing script at 4fc00000 U-boot loaded from SD Boot script loaded from mmc 191 bytes read in 1 ms (186.5 KiB/s) Load fdt: /boot/dtb/allwinner/sun50i-h618-kickpi-k2b.dtb 43768 bytes read in 5 ms (8.3 MiB/s) Working FDT set to 4fa00000 4203 bytes read in 4 ms (1 MiB/s) Applying kernel provided DT fixup script (sun50i-h616-fixup.scr) ## Executing script at 45000000 17093884 bytes read in 707 ms (23.1 MiB/s) 37613576 bytes read in 1554 ms (23.1 MiB/s) Moving Image from 0x40080000 to 0x40200000, end=0x426d0000 ## Loading init Ramdisk from Legacy Image at 4ff00000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 17093820 Bytes = 16.3 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 4fa00000 Booting using the fdt blob at 0x4fa00000 Working FDT set to 4fa00000 Loading Ramdisk to 48fb2000, end 49fff4bc ... OK Loading Device Tree to 0000000048f3e000, end 0000000048fb1fff ... OK Working FDT set to 48f3e000 Starting kernel ... Does the PSU have enough juice and is the SD card one of quality?

@MeJune A523/T527 support still needs a lot of work. There is no HDMI support yet. So you will need to install a usb serial device to your uart to interact with your box. You can find details at the botton of the site you posted https://linux-sunxi.org/X96QPro%2B. You could try warpme minimyth2 or miniarch. He has the latest support for these boxes. I don't own a X96q pro+ so I can't help you.

@Unrealchex The base-files error is a known issue. You'll need to run the ./compile command a second time and it should continue where it left off. Here's a post that show's you how to create patches. https://forum.armbian.com/topic/29794-how-to-install-armbian-in-h618/#findComment-227058 You want to edit u-boot and kernel dts. Remove the x96q code and add the wifi code from x98h. The x96h U-boot and kernel code might be different double check it. remove (Existing x96q wifi code.) reg_vcc_wifi: reg_vcc_wifi { compatible = "regulator-fixed"; regulator-name = "vcc-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; gpio = <&pio 6 18 GPIO_ACTIVE_HIGH>; /* PG18 WL_REG_ON */ regulator-always-on; enable-active-high; status = "okay"; }; wifi_pwrseq: wifi_pwrseq { compatible = "mmc-pwrseq-simple"; clocks = <&rtc CLK_OSC32K_FANOUT>; clock-names = "ext_clock"; pinctrl-names = "default"; pinctrl-0 = <&x32clk_fanout_pin>; /* PG10 with MUX3 set */ }; &mmc1 { vmmc-supply = <&reg_dldo1>; vqmmc-supply = <&reg_vcc_wifi>; mmc-pwrseq = <&wifi_pwrseq>; bus-width = <4>; non-removable; status = "okay"; wlan: wifi@1 { reg = <1>; interrupt-parent = <&pio>; interrupts = <6 15 IRQ_TYPE_EDGE_RISING>; /* PG15 WL_HOSTWAKE*/ interrupt-names = "host-wake"; local-mac-address = [dc 44 6d c0 ff 02]; }; }; Add (code borrowed from x98h) reg_vcc3v3: vcc3v3 { /* discrete 3.3V regulator */ compatible = "regulator-fixed"; regulator-name = "vcc-3v3"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; reg_3v3_wifi: vcc3v3-wifi { compatible = "regulator-fixed"; regulator-name = "vcc-3v3-wifi"; regulator-min-microvolt = <3300000>; regulator-max-microvolt = <3300000>; regulator-always-on; }; }; &mmc1 { vmmc-supply = <&reg_vcc3v3>; bus-width = <4>; non-removable; max-frequency = <35000000>; status = "okay"; wlan: wifi@1 { reg = <1>; }; }; You don't need to create a patch for build/config/boards. Edit the file x96q-lpddr3.csc and add this to the bottom of display_alert "$BOARD" "Using ${BOOT_FDT_FILE} for ${BRANCH}" "info" display_alert "Applying wifi firmware" pushd "$SDCARD/lib/firmware" ln -s "aic8800/SDIO/aic8800D80" "aic8800_sdio" # use armbian-firmware cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/usr/lib/armbian cp -R $SRC/packages/blobs/sunxi/h618/armbian-audio-config $SDCARD/lib/armbian popd

Sorry, I didn't take my medicines. where did you find the link between SliTaz and armbian? Do you intend to be the maintainer of this link? you need help writing SliTaz documentation?

I am using this version "Armbian_community_25.11.0-trunk.334_Kickpik2b_trixie_current_6.12.47_minimal.img". It shows U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. resetting ... U-Boot SPL 2025.07 (Oct 20 2025 - 18:19:29 +0800) DRAM:This DRAM setup is currently not supported. The system just loops this message and never proceeds. Has anyone encountered this issue before? Any suggestions or solutions would be greatly appreciated. Thanks in advance!

The system doesn't even start loading. Can you please explain how to do this? I can't figure out what I'm doing wrong in the compilation process according to your instructions. I'm sorry, the log file was really incomplete. I'm attaching the full one. Log_full.txt

https://github.com/manjaro-arm/opi5-plus-images/issues/22#issuecomment-3340442272

I bought this box and opened it up to find a lot of interesting things. For example, the specs are good, the circuit board is more versatile than other boards. There are two USB 2.0 ports and one USB 3.0 port, and the heat sink looks great. spec I built a Debian 13 image as per @Nick A's instructions and burned it to a micro SD card, and booted it with this box. Unfortunately, the screen went black with no progress.

Kernel Edge now support npu, for reference: https://github.com/armbian/build/commit/2e139987e79e68a4e4c4d98cd9367a057626a673

The strange thing is that, as far as I can see, this issue doesn’t occur on the vendor kernel. Continuing from our earlier discussion, I’ve just noticed that my variant shows the same problems as well only when i write stuff. I’ll get in touch with FriendlyELEC to clarify this. If the only solution is to scale down the frequency, then it would actually make more sense to modify it directly in the DTS rather than through an overlay.

Seems missing in kernel config. Feel free to send a PR and enable the module.

@Fredrik I got like ~80fps at 720p. I sometimes get the gamepad not working. For me, just remove the wineprefix and it will work again!

I'm actually sporting dxvk-2.7.1-stripped now as I spotted you used that version! I get around 45-61 fps in Hades at 720p, Wayland desktop. Some other tips for anyone trying, if you have sound that intermittently blanks/disappears you could try running this before the wine command, PULSE_LATENCY_MSEC=60 people say its a buffering problem and I think for me its actually helped. But note it adds latency to the audio. You can try different values. I wanted to play with gamepad but it didn't work for me in Hades. You can test if your pad generally works in Wine by running wine control then check the different input types. For me it worked there but not in the game. If you search it there are all kinds of complicated ways people are supposedly getting it to work. All I had to do was run these registry add commands, wine reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\winebus" /v "DisableHidraw" /t REG_DWORD /d 1 wine reg add "HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\winebus" /v "Enable SDL" /t REG_DWORD /d 1 Actually I also added the gamecontrollerdb.txt to somewhere after spotting a message in the term output. Not sure if this is the official one but I think I used this one, https://github.com/mdqinc/SDL_GameControllerDB Also I'm not sure if it helped as I did that first and it didn't fix gamepad input, doing the registry entries did.

@Fredrik You should use the dxvk-2.7.1-stripped (I have re-uploaded recently) for the Hades game. It achieves a higher frame rate (~15%) than the stripped versions of dxvk-1.x.x-stripped.

@MartinB direct from the game's folder (no Steam) no special arguments

Hello, I just got a wifi 7 adapter (QCNCM865) and I was thinking the ath12k driver was available starting from kernel 6.13, I'm running the edge kernel 6.16.4 and the ath12k driver is failing to load and I can't find any wireless drivers in /usr/lib/modules/6.16.4-edge-rockchip64/kernel/net/wireless. Do I need to rebuild the kernel with the ath12k driver? or is there a kernel version available with that driver? Thanks for your help!

Hello as this seems really fun I was also trying to get this to work but running into problems so it would be amazing if you could clarify a bit more please? I have mainline Mesa but that comes with PanVK to level 1.4+ vulkaninfo --summary Devices: ======== GPU0: apiVersion = 1.4.328 driverVersion = 25.2.99 vendorID = 0x13b5 deviceID = 0xa8670000 deviceType = PHYSICAL_DEVICE_TYPE_INTEGRATED_GPU deviceName = Mali-G610 driverID = DRIVER_ID_MESA_PANVK driverName = panvk driverInfo = Mesa 25.3.0-devel (git-099ac5be1a) conformanceVersion = 1.4.1.2 deviceUUID = b5130000-0000-67a8-0000-000000000000 driverUUID = ac34a6fa-924e-d4b0-3a47-66ccf4729ee5 I then build your dxvk repo https://github.com/khanh-it And install like, export WINEPREFIX=/path/to/wineprefix cp x64/*.dll $WINEPREFIX/drive_c/windows/system32 cp x32/*.dll $WINEPREFIX/drive_c/windows/syswow64 (its weird that the x64 files go in the system32 folder and opposite too) I then did the 'Native' override to those libraries mentioned in winecfg. I downloaded https://github.com/pythonlover02/DXVK-Sarek/actions and stuck the dll's in the games x64 folder But I keep getting a black window and the error that the game can't find a graphics device, info: Game: Hades.exe info: DXVK-Sarek: v1.11.0 info: Built-in extension providers: info: Win32 WSI info: OpenVR info: OpenXR info: OpenVR: could not open registry key, status 2 info: OpenVR: Failed to locate module [BOX64] Using emulated /mnt/net_d/emu/PC/wine-10.15-staging-tkg-ntsync-amd64-wow64/lib/wine/x86_64-unix/winevulkan.so [BOX64] Using native(wrapped) libvulkan.so.1 info: Enabled instance extensions: info: VK_KHR_surface info: VK_KHR_win32_surface info: Mali-G610: info: Driver: 25.2.99 info: Vulkan: 1.4.328 info: Memory Heap[0]: info: Size: 5950 MiB info: Flags: 0x1 info: Memory Type[0]: Property Flags = 0x7 2025-10-22 15:35:50 [MainThread ] direct3d11.cpp:833 INFO| Created DXGI1.2 factory. info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_1 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_1 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_0 err: D3D11CoreCreateDevice: Requested feature level not supported info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_1 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_0 err: D3D11CoreCreateDevice: Requested feature level not supported info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_1 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_1 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_0 err: D3D11CoreCreateDevice: Requested feature level not supported info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_11_0 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_1 info: D3D11CoreCreateDevice: Probing D3D_FEATURE_LEVEL_10_0 err: D3D11CoreCreateDevice: Requested feature level not supported 2025-10-22 15:35:50 [MainThread ] direct3d11.cpp:1012 INFO| gpuCount = 0 2025-10-22 15:35:50 [MainThread ] program.cpp:2117 ERR| Failed to initialize ForgeRenderer. 2025-10-22 15:35:50 [MainThread ] program.cpp:2118 INFO| Showing MessageBox: No Graphics Device 2025-10-22 15:35:53 [MainThread ] luaext.cpp:445 INFO| Lua interface destroyed Would you please be able to elaborate a bit on the steps if you can see what I'm doing wrong? Cheers! UPDATE: Oh wait! I got it to work now, I copied the 'stripped' x32 dll's from (https://github.com/khanh-it/dxvk/releases Into the games x64 folder. (I had previously copied the x64 dll's into the x64 folder. Silly me obviously that's not how it works) Cool!

my tv box: MXQ pro 4K 5G, Q44_V5.1_20210118, PROCESSOR: ALLWINNER TECH H3 LC267BA 91F2. I recorded the image on a 32gb sd card, but it doesn't boot. Has anyone solved it?