Fredrik

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.

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!

Yes for sure, thank you. > lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 003: ID 2b89:8761 Realtek Bluetooth Radio Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 006 Device 004: ID 0583:2060 Padix Co., Ltd (Rockfire) 2-axis 8-button gamepad > sudo dmesg | grep -i bluetooth [ 1.706048] usb 6-1: Product: Bluetooth Radio [ 4.360426] Bluetooth: Core ver 2.22 [ 4.360457] NET: Registered PF_BLUETOOTH protocol family [ 4.360460] Bluetooth: HCI device and connection manager initialized [ 4.360466] Bluetooth: HCI socket layer initialized [ 4.360469] Bluetooth: L2CAP socket layer initialized [ 4.360480] Bluetooth: SCO socket layer initialized [ 4.415023] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 4.417020] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 4.417027] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 4.417442] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 6.328832] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.328847] Bluetooth: BNEP filters: protocol multicast [ 6.328859] Bluetooth: BNEP socket layer initialized [ 870.557589] usb 6-1: Product: Bluetooth Radio [ 870.569776] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 870.571601] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 870.571614] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 870.571686] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 1246.745679] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 1246.747602] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 1246.747629] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 1246.747756] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 3667.259558] Bluetooth: RFCOMM TTY layer initialized [ 3667.259580] Bluetooth: RFCOMM socket layer initialized [ 3667.259595] Bluetooth: RFCOMM ver 1.11 [65689.757539] usb 4-1: Product: Bluetooth Radio [65689.769644] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [65689.771604] Bluetooth: hci0: RTL: rom_version status=0 version=1 [65689.771649] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [65689.771913] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin And here's a pastebin of the full dmesg output. https://pastebin.com/wMuX0bVW I got the driver files from here, https://github.com/Elif-dot/RTL8761BU uname Linux opi5 6.16.4-edge-rockchip64 #1 SMP PREEMPT Thu Aug 28 14:34:51 UTC 2025 aarch64 aarch64 aarch64 GNU/Linux thanks

Yeah so just like the title says, has anyone got a tip for a USB Bluetooth dongle that works with the mainline kernel? I got a UGREEN Bluetooth 5.0 dongle a while ago and have just tried again, installing firmware for it. It does get detected as a USB device and the firmware loads. But bluetoothctl never finds it. Gnome doesn't let me 'enable' bluetooth. I'd like to avoid buying a string of these so was just wondering if any are working with mainline? Cheers!

Hi is there a way to enable the old USB port without re-installing Armbian? I have done to much setup work to start all over again.

@mitu I'm not sure how to use that program it only plays white noise but it comes through hdmi. I can also play wav files using aplay on command line.

Audio out of HDMI works for me out of the box. Kind of. I flashed a kernel 6.15 (that I had lying around) Cinnamon image, because all the recent Gnome images I have fail and just boot to initramfs. I then installed Gnome and enabled Wayland. I then used armbian-config to upgrade the kernel to 6.16 something. Sound test in Gnome settings work. I think this should just work with my kernel 6.15 too iirc. But also I seem to remember having problems when not using Gnome.

Yes you were right it found those sha files when I tried yesterday! I didn't even realize I was trying that close to the release. Build has worked! Thank you! And can confirm that HDMI audio out with Ubuntu+Gnome works!

Hello! I'm trying to look around in the Armbian build/config scripts to see how I can enable a mainline v6.15-rc3 kernel to be built. I did try to make a build/userpatches/lib.config file with the contents, KERNELBRANCH="tag:v6.15-rc3" But that's not working. Would anyone be able to tell me the file I need to edit for an OrangePi 5? Update: I actually seem to have it try by editing config/sources/families/rockchip-rk3588.conf changing the version tag. But I get a bunch of red errors complaining about SHA1. hmm...an 'rc3' is probably not to be found in a tree with 'stable' in it. Cheers! Fred

Ok thanks good to know! I was following primarily this one, https://jamesachambers.com/orange-pi-5-ssd-boot-guide/ i did actually then use armbian-install. So i f I use armbian-install, I can then wipe that boot partition and re-install again, or just over install on the boot partition?

Hello! Iv'e just done a test run installing Armbian for booting off my new m.2 nvme drive. As 'm planning to have the drives 2nd large partition as my basic home file server I'm wondering if I can as easily re-install the OS if/when I need to update it to a newer one? Because the instructions I followed and that I see around do a very basic cat /dev/mmcblk1 > /dev/nvme0n1 onto the raw un-partitioned nvme. My case will be that I have data on a partition on that drive that needs to stay. Is this going to be an issue or are there ways to re-install Armbian or even other distro on the boot partition? Cheers!

Just tried glmark with the performance governor and got 3411. Cool but last time I did that I think it didn't make any/much difference in Dolphin, just the benchmark. Read the comment box of the youtube video for how I ran this. Its easier now as you don't need to apply the special commits.

At last I got around to trying with kernel 6.10, panthor and new mesa! Glmark2 score of 3055! (it was 1730 last time I tried with panfork) https://youtu.be/TbVD-F9SqWU