All Activity

@KhanhDTPHi. First off, great job with all these games. Would it be possible to test FarmingSimulator 17 please? I got the game working, but the image is offset a lot. Mouse also. I needed to set wine to win7 and use the x86 FarmingSimulator2017.exe in the x86 folder. I've got no clue how to fix this issue, maybe you have more tips and tricks. In windowed mode I can see everything, but mouse goes out of the window and stops working. Otherwise it looks playable if it was outputting correctly. Cheers, NicoD

@gabriel_altoe Try this: https://brandolamarck.substack.com/p/como-extrair-e-decompilar-a-device. I'll take some time to try and follow the tips. I'll post any updates here.

@sicxnull Yes, I can try to extract the DBT. How can I do that?

@Nick A Thank you very much, I'll try using it and get back to you if everything is okay.

Thank you, @sven-ola , your work is amazing About the GPU, I suppose that spacemit can do something like what this guy did to make work the BXM-4-64 on the TH1520 https://mwilczynski.dev/posts/riscv-gpu-zink/ Anyways, my hardware knowledge is way far away from this...

nvme drive is in the bottom slot, oculink adapter going to a powered external pci-e adapter in the top nvme slot. i was able to plug a non-gpu in it and get a device to detect. just both my intel arc gpus failed to detect. edit, new discovery, when the fpga device is active on the 2nd nvme slot i can no longer see my original nvme drive if booting off the sd card. very strange. almost like its a lane bifrucation issue. ignore that, misconfig on my end.

You mean the M.2 PCIe slot? My RV2 board has no oculink slot, only 2 PCIe slots, one for NVMe and one for SSD.

not sure if this is the right place to ask, but i was able to get it to recompile the kernel with the xe driver flag turned on, and got a working booting 6.18.9 image, which is amazing, i have never been able to get anything newer than the 6.6 kernel the manufacturer provided working. so thank you so much for all your hard work. theres only one problem, when i do the lspci command, i dont see anything attached to that slot. i tried two different intel arc gpus, an arc 350 and an arc 310 neither detects. so i pulled out an ibm fpga card and plugged it into the same powered oculink adapter, and lo and behold the fpga card detected, so my pcie adapter setup is good. is there any advice you could offer besides enabling the xe2 driver in kernel that i may have to persue? i know this is kind of off topic, id just like to get hardware accelerated graphics working on this device.

While reviewing the system logs, I noticed several ftrace warnings appearing in dmesg. After investigating the root cause, I have applied the necessary configuration updates to eliminate these logs. The driver is now running cleanly without any ftrace-related noise.

Hi, did you resolve this? I'm having trouble with the same thing and this seems to be the only forum where this is mentioned. It seems to be a watchdog issue?

@Kevin su I just bought a TV Box with SV6256P and planned to port the driver and in my first search I found your post. Excellent work!

Board: MKS-Klipad50 Images: * Armbian_26.2.1_Mksklipad50_noble_current_6.18.8_minimal.img.xz * Armbian_26.2.1_Mksklipad50_trixie_current_6.18.8_minimal.img.xz Passed tests: * gpg and sha checksum files * boot from emmc, leds, display, touch, usb, internal wifi * initial setup, uboot-console, full klipper/klipperscreen install, reboot Result: All expected images do exist, verify and work properly.

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 1aed7e028 (https://ryanfortner.github.io/box64-debs/) + ge-proton10-29 (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton10-29) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v2.1 40~60fps@1080p (max settings, no AA) box64 environment variables: Grand Theft Auto San Andreas

Armbian 25.11.2 Noble XFCE (BSP Kernel: 6.1.115) + PanVk - mesa 26.0 (https://launchpad.net/~ernstp/+archive/ubuntu/mesaaco) + Box64 arm64 v0.4.1 1aed7e028 (https://ryanfortner.github.io/box64-debs/) + ge-proton10-29 (https://github.com/GloriousEggroll/proton-ge-custom/releases/tag/GE-Proton10-29) + dgVoodoo2 (https://github.com/dege-diosg/dgVoodoo2/releases) + DXVK-stripped v1.10.3 ~30fps@720p (ultra settings) box64 environment variables: Spider-Man Shattered Dimensions

Any news or predictions on when HDMI and VAAPI will work? I want to use the board as a Jellyfin server!

Hi. There's progress, but I think I'm stuck. I created a bin file from efuse_burner.elf and it got written somewhere (?!). The UART showed a "board locked" message. Afterwards, I checked the SID, and it hadn't changed. When I try to boot from the SD card, the terminal is silent and immediately connects to the PC in fel mode. I dumped an emmc and my rotpk was in there. ##xxd emmc_dump.bin 00000000: 0000 8061 0000 0000 0000 0000 0000 0000 ...a............ 00000010: 7c07 8aaa 1bcc 6cdf 85fd 6e67 f6fc ad6d |.....l...ng...m 00000020: 5535 5f38 e071 e5a3 57d7 c8a8 c255 8950 U5_8.q..W....U.P 00000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................## The sid dump also only has two values, the rest are zeros. I don't understand what they represent. ##xxd sid_dump.bin 00000000: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000010: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000020: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000030: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000040: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000050: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000060: 9300 0000 0000 0000 0000 0000 0000 0000 ................ 00000070: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000080: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000090: 3100 0000 0000 0000 0000 0000 0000 0000 1............... 000000a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000000b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000000c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000000d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000000e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000000f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000100: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000110: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000120: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000130: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000140: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000150: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000160: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000170: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000180: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 00000190: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001a0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001b0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001c0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001d0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001e0: 0000 0000 0000 0000 0000 0000 0000 0000 ................ 000001f0: 0000 0000 0000 0000 0000 0000 0000 0000 ................## When I try to sign the SD card using toc0, the same thing happens with fel. Please help. Did the key get written to the correct location, and how do I boot now?

All are interesting. However, H3, H5 and H6 boards will receive additional fixing to DVFS during this week. After that, I will rebuild them, but those are all CSC, so there are additional tasks: We only generate and test boards with at least "standard support", where a known maintainer is around. If you (or someone else) step up as a maintainer: https://docs.armbian.com/User-Guide_Board-Support-Rules/ following by PR as such https://github.com/armbian/build/pull/8981 boards will automatically be added to automatically generated build lists https://github.armbian.com/release-targets/targets-release-standard-support.yaml and images can be (auto) generated: https://docs.armbian.com/Process_CI/#automation-for-developers-and-maintainers If you wanna cover those steps, report status at release periods, step up. In most cases, boards work but during those tests we usually always found something to fix. And boot loader compilation is checked this way - end user upgrades don't upgrade that by default so you could be running a board for years while freshly build images would have borked uboot ... Perfect - new use case: Armbian QA

Great! It's working now, sorry, I made it too complex previously.

Can you see this post? Please write at least a letter.

Collabora continues to be a key contributor to the Linux kernel, with 125 patches from 21 developers! Highlights include Arm Mali GPU improvements, expanded MediaTek and Rockchip SoC support, Rust integration progress, and new Rockchip video capture functionality. View the full article

Boards that've tested: NanoPC T6 LTS: Kernel: Vendor (6.1) - Current (6.18) Variant: Desktop - Gnome What was tested: GPU works as expected WI-FI Card works as expected NVME, eMMC, SPI and SD Card works as expected Ethernets: 2x 2.5GbE works as expected HDMI both works as expected AUDIO: HDMI & via jack works as expected HDMI-IN video works as expected NanoPi M5: Kernel: Vendor (6.1) Variant: Desktop - Gnome What was tested: Image not boot, i have to investigate more, The previous image works without any problems. I will check soon and maybe migrate it to mainline uboot @Igor Can you do a double check if your board have the same issue? What was tested with the new build: GPU works as expected WI-FI Card works as expected NVME, SPI and SD Card works as expected UFS: I have to working on it, maybe with new mainline patches that will add the support on it Ethernets: 2x 1GbE works as expected HDMI both works as expected AUDIO: HDMI & via jack works as expected NanoPi R76S: Kernel: Vendor (6.1) Variant: Desktop - Gnome What was tested: GPU works as expected WI-FI Card works as expected eMMC and SD Card works as expected Ethernets: 2x 2.5GbE works as expected HDMI both works as expected AUDIO: HDMI works as expected

I have an Orange Pi Zero 3, Opi z2w, Opi z LTS, and Banana Pi M2 Zero. If the OS image is not in your download page, does it mean you don't need help with these boards? I didn't have any problems with opiz3 Armbian.com or self built image ever (last time I tried was 2 months ago). The others: haven't used in 1 year.

@maxsub no, its hacked. At least from my side. For us, that GPU stuff is closed, patented, tighly licensed and so on. LG // Sven-Ola

@Nick A Yes, I used the MT7601U for a few days, but I wasn’t really satisfied with it. So, with the help of AI, I decided to port the SV6256P anyway—and to my surprise, it actually worked.

@jock The driver-related knowledge is vast and quite complicated, with many pitfalls, so porting really requires strong assistance from AI. I don’t have an SSV6051, so I can’t actually complete the porting myself. Btw, the "ssv6x5x-sw.bin" I’m using is the file you posted on the forum.