Wine / Gallium

System:    Kernel: 5.10.81-1-lts x86_64 bits: 64 compiler: gcc v: 11.1.0
           parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts root=UUID=b0e4d9bb-6152-4407-bf73-0dbf7d629019 rw
           [email protected] quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
           systemd.unified_cgroup_hierarchy=1 loglevel=3
           Desktop: Xfce 4.13.3 tk: Gtk 3.24.5 info: xfce4-panel wm: xfwm 4.12.5 vt: 7 dm: LightDM 1.30.0 Distro: Garuda Linux
           base: Arch Linux
Machine:   Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK (MS-7C02) v: 1.0 serial: <filter>
           UEFI: American Megatrends LLC. v: 1.H5 date: 04/22/2021
CPU:       Info: 8-Core model: AMD Ryzen 7 2700X bits: 64 type: MT MCP arch: Zen+ family: 17 (23) model-id: 8 stepping: 2
           microcode: 800820D cache: L2: 4 MiB
           flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 118399
           Speed: 2084 MHz min/max: 2200/3700 MHz boost: enabled Core speeds (MHz): 1: 2084 2: 2330 3: 1941 4: 2027 5: 2134
           6: 2191 7: 2091 8: 2195 9: 1904 10: 2177 11: 2038 12: 2122 13: 1951 14: 2199 15: 1910 16: 2253
           Vulnerabilities: Type: itlb_multihit status: Not affected
           Type: l1tf status: Not affected
           Type: mds status: Not affected
           Type: meltdown status: Not affected
           Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
           Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
           Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional, STIBP: disabled, RSB filling
           Type: srbds status: Not affected
           Type: tsx_async_abort status: Not affected
Graphics:  Device-1: NVIDIA GP106 [GeForce GTX 1060 6GB] vendor: ZOTAC driver: nvidia v: 495.44 alternate: nouveau,nvidia_drm
           bus-ID: 25:00.0 chip-ID: 10de:1c03 class-ID: 0300
           Device-2: NVIDIA TU116 [GeForce GTX 1660] vendor: ZOTAC driver: nvidia v: 495.44 alternate: nouveau,nvidia_drm
           bus-ID: 26:00.0 chip-ID: 10de:2184 class-ID: 0300
           Display: x11 server: X.Org 1.21.1.1 compositor: xfwm4 v: 4.12.5 driver: loaded: nvidia display-ID: :0.0 screens: 2
           default screen: 0
           Screen-1: 0 s-res: 5760x1080 s-dpi: 96 s-size: 1524x286mm (60.0x11.3") s-diag: 1551mm (61")
           Monitor-1: DP-0 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") diag: 604mm (23.8")
           Monitor-2: DP-2 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") diag: 604mm (23.8")
           Monitor-3: DP-4 res: 1920x1080 hz: 60 dpi: 93 size: 527x296mm (20.7x11.7") diag: 604mm (23.8")
           Screen-2: 1 s-res: 5760x1080 s-dpi: 95 s-size: 1540x292mm (60.6x11.5") s-diag: 1567mm (61.7")
           OpenGL: renderer: NVIDIA GeForce GTX 1660/PCIe/SSE2 v: 4.6.0 NVIDIA 495.44 direct render: Yes
Audio:     Device-1: NVIDIA GP106 High Definition Audio vendor: ZOTAC driver: N/A alternate: snd_hda_intel bus-ID: 25:00.1
           chip-ID: 10de:10f1 class-ID: 0403
           Device-2: NVIDIA TU116 High Definition Audio vendor: ZOTAC driver: N/A alternate: snd_hda_intel bus-ID: 26:00.1
           chip-ID: 10de:1aeb class-ID: 0403
           Device-3: Focusrite-Novation Scarlett 6i6 type: USB driver: snd-usb-audio bus-ID: 1-8:3 chip-ID: 1235:8012
           class-ID: fe01 serial: <filter>
           Sound Server-1: ALSA v: k5.10.81-1-lts running: yes
           Sound Server-2: JACK v: 1.9.19 running: yes
           Sound Server-3: PulseAudio v: 15.0 running: no
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel
           port: e000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
           IF: enp34s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
RAID:      Supported mdraid levels: raid0
           Device-1: md127 maj-min: 9:127 type: mdraid level: raid-0 status: active size: 1.82 TiB
           Info: report: N/A blocks: 1953258496 chunk-size: 512k super-blocks: 1.2
           Components: Online:
           0: sda1 maj-min: 8:1 size: 931.51 GiB
           1: sdb1 maj-min: 8:17 size: 931.51 GiB
Drives:    Local Storage: total: 3.87 TiB used: 2.05 TiB (53.1%)
           SMART Message: Required tool smartctl not installed. Check --recommends
           ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WDS250G1B0C-00S6U0 size: 232.89 GiB block-size:
           physical: 512 B logical: 512 B speed: 15.8 Gb/s lanes: 2 type: SSD serial: <filter> rev: 201000WD temp: 37.9 C
           scheme: GPT
           ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB block-size:
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01 temp: 32 C
           scheme: MBR
           ID-3: /dev/sdb maj-min: 8:16 vendor: Western Digital model: WD1003FZEX-00K3CA0 size: 931.51 GiB block-size:
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter> rev: 1A01 temp: 32 C
           scheme: MBR
           ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD10EFRX-68PJCN0 size: 931.51 GiB block-size:
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 1A01 temp: 33 C
           scheme: MBR
           ID-5: /dev/sdd maj-min: 8:48 vendor: Western Digital model: WD10EFRX-68PJCN0 size: 931.51 GiB block-size:
           physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5400 serial: <filter> rev: 1A01 temp: 33 C
           scheme: MBR
Partition: ID-1: / raw-size: 232.38 GiB size: 232.38 GiB (100.00%) used: 13.77 GiB (5.9%) fs: btrfs dev: /dev/nvme0n1p2
           maj-min: 259:2
           ID-2: /boot/efi raw-size: 512 MiB size: 511 MiB (99.80%) used: 576 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1
           maj-min: 259:1
           ID-3: /home raw-size: 1.82 TiB size: 1.79 TiB (98.38%) used: 639.36 GiB (34.9%) fs: ext4 dev: /dev/md127p1
           maj-min: 259:3
Swap:      Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
           ID-1: swap-1 type: zram size: 62.79 GiB used: 512 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors:   System Temperatures: cpu: 45.4 C mobo: N/A
           Fan Speeds (RPM): N/A
           GPU: device: nvidia screen: :0.0 temp: 38 C fan: 38% device: nvidia screen: :0.1 temp: 38 C fan: 38%
Info:      Processes: 463 Uptime: 3m wakeups: 0 Memory: 62.79 GiB used: 4.29 GiB (6.8%) Init: systemd v: 249 tool: systemctl
           Compilers: gcc: 11.1.0 clang: 13.0.0 Packages: pacman: 1493 lib: 449 Shell: Bash v: 5.1.8 running-in: sakura
           inxi: 3.3.08

err:d3d9nine:present_has_d3dadapter No available backends.
Native Direct3D 9 will be unavailable.
err:d3d9nine:d3dadapter9_new Your display driver doesn't support native D3D9 adapters.

Anything in Wine that requires D3D fails with the above message. I've tried various wine changes (staging, not staging, git). None of the wine packages say they are built against/with Gallium but I always get that message. I've tried clean prefixes, and uninstalling anything/everything related to gallium.

I've done some reading on the Gallium page it says to check for more info but it's all rather off topic for the issue. Web searches turn up irrelevant results for me.

I've tried running the Gallium config as well but everything is grayed out.
galliumCFG

Gallium config says I need a MESA driver but what isn't already installed?!

lib32-libva-mesa-driver 21.2.5-1
lib32-mesa 21.2.5-1
lib32-mesa-demos 8.4.0-2
lib32-mesa-vdpau 21.2.5-1
lib32-vulkan-mesa-layers 21.2.5-1
libva-mesa-driver 21.2.5-1
mesa 21.2.5-1
mesa-demos 8.4.0-4
mesa-vdpau 21.2.5-1
opencl-mesa 21.2.5-1
vulkan-mesa-layers 21.2.5-1

I suppose there are two main questions for this. #1 do I need to build from source to rid wine of Gallium? or #2 What is this looking for in my drivers that it thinks I don't have?

I have 'wine-nine' installed (Gallium) and I use 'wine-tkg-staging-fsync-git'. Uninstall any other 'wine' version. Have you tried that combo?

No that I hadn't. Given all of the wine packages I've tried don't mention Gallium I was kinda hoping to get rid of it. I've never had it work heh cue same same 5 years later heh.

I suppose it might also be helpful to mention I'm not trying to get Gallium to work because I want to use it. Just that IF all the wine packages in the repos are built against it how do I make it work or get rid of it since as I said it never works and it's continuing this obnoxious trend.

Here is the Arch wiki on it....

https://wiki.archlinux.org/title/wine#Gallium_Nine

I just tried wine-nine and it does the same thing.

wineboot -e ; wineserver -k for good measure before run running a wine command but the exact same error.

...and you are using 'wine-tkg-staging-fsync-git' version?

Mesa and nVidia? Is that a thing now?
I've not had nVidia for YEARS, maybe I'm being dumb!

No I just tossed on the wine-nine standalone. I am back to the wine meta package now because it installs wineasio and such as well. Again I'm not trying to get Gallium to work. If it worked I'd be cool with that but it never works for me so I'd rather just "how do I get rid of this!?" I had originally just thought the wine packages were stock but they all seem to have some tie to gallium - which doesn't work.

Yea, no. You can't use Wine-nine, you have to stick with wine-staging.
Beyond that, you'll need someone else. I think the nVidia /nine bit was missed.

Not sure what you mean but staging and non still give me those gallium errors and everything d3d dies. Hence my original question, do I have to build from source i.e. are ALL the packages in the repos built against Gallium or is there some config or other package I need to make the gallium crap work.

No, I think you are being correct on this. I missed he was using Nvidia. If you are using the proprietary drivers for Nvidia, then you don't need Mesa for anything at all.

Mesa is just used for the open-source drivers: Intel, AMD, Qualcomm Adreno.

Tell that to the gallium config ;p Either way I'd be just as happy getting RID of gallium or finding out why it complains there is no backend etc.

It wants it because you're trying to run a version of Wine that needs it.
From what I can tell, you want vanilla Wine / Wine Staging.

This post/thread seems it'd be useful (primarily I'm talking about Edit 3 in the OP).
But as I say, I've not nVidia's in years (because :fu: nVidia) or Wine for quite a long time (for much of anything).
https://bbs.archlinux.org/viewtopic.php?id=268691

1 Like

Again my original question are ALL the packages in the repos built against Gallium thus I need to build from source to get a NORMAL wine? I'm using to toss on the winehq builds and no issue. If there is a vanilla wine in the repos I'd sure like to know which one it is because none of the ones I've tried (except wine-nine) say anything about gallium.

All I know is ...don't use gallium with nVidia's proprietary driver. Gallium is the
architecture used by mesa for all open source 3D drivers (intel, radeon,
nouveau, etc).

nVidia bypasses all of that and does their own thing.

To my knowledge, Gallium is not a dependency of wine, or at least not the version (posted above) that I use.

@Chrispynut Not sure what you see in that post Edit 3, I already have dkms installed and my mkinitcpio already has the modules.

@RodneyCK Like I said none of the packages I've installed say they are Gallium Nine based but they all toss out those errors and D3D doesn't work at all. I can play things in wine using OGL fine, but older games all give me the Gallium issues unless there is an -opengl switch/flag I can throw at the game.

Now Tarkov is borked...ug.

I am going to assume it is game related then. I usually use Lutris and select the native wine version, which is how I run some of my games, and I have never received a pop-up/error like that. Again, I think it might be game related.

It's D3D related :wink: Which means in theory some of my VSTi might also be gibbed. No real care or need for Lutris over the years.

I find Lutris handy. You can set up games to run native or even look for runners which might help with issues. To each his own.

I've tried Lutris but I found more often than not it didn't work. The one time it did was there was a period where stock Wine had issues with the Blizzard launcher for SC2/D3. SC2 worked, D3 just gave you a gray screen same as stock Wine.

Plus Lutris does not help with other things like VSTi.