[Bug 46729] New: Wine directx not detecting Intel HD Graphics 620 (Rev 02) chipset
https://bugs.winehq.org/show_bug.cgi?id=46729 Bug ID: 46729 Summary: Wine directx not detecting Intel HD Graphics 620 (Rev 02) chipset Product: Wine Version: 4.2 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: directx-d3d Assignee: wine-bugs(a)winehq.org Reporter: winehq(a)darkhelm.org Distribution: --- Created attachment 63708 --> https://bugs.winehq.org/attachment.cgi?id=63708 GPU Caps Viewer screenshot (from within Wine) Wine is not identifying my card.
From lspci -nn | grep VGA:
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 620 [8086:5916] (rev 02) Yet when I run GPU Caps Viewer, it cannot determine my card. When I run WoW, it lists my card info as: 2/20 08:35:39.152 Vendor ID: 8086 2/20 08:35:39.916 Device ID: 162 Which is an Intel HD Graphics 4000, an older card -- apparently a "fallback" card used by Blizzard when it cannot determine the card information. This is preventing games from being able to use vkd3d. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #1 from Cliff Hill <winehq(a)darkhelm.org> --- Created attachment 63714 --> https://bugs.winehq.org/attachment.cgi?id=63714 WoW gx.log -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #2 from Cliff Hill <winehq(a)darkhelm.org> --- Created attachment 63715 --> https://bugs.winehq.org/attachment.cgi?id=63715 glxinfo -v -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #3 from Cliff Hill <winehq(a)darkhelm.org> --- Created attachment 63716 --> https://bugs.winehq.org/attachment.cgi?id=63716 wine debug output when running WoW.exe -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #4 from Cliff Hill <winehq(a)darkhelm.org> --- Created attachment 63717 --> https://bugs.winehq.org/attachment.cgi?id=63717 GPU Caps Viewer - Shark info display -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #5 from Cliff Hill <winehq(a)darkhelm.org> --- Created attachment 63718 --> https://bugs.winehq.org/attachment.cgi?id=63718 output from lspci -nn -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |joseph.kucia(a)gmail.com Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #6 from Józef Kucia <joseph.kucia(a)gmail.com> --- I sent a patch: https://source.winehq.org/patches/data/159430 I'm not sure if it will fix your issues with vkd3d. Do you have Vulkan libraries and vkd3d installed? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #7 from Cliff Hill <winehq(a)darkhelm.org> --- yes, I do. and I have tested that gears-vkd3d and triangle-vkd3d work. The issue does not appear to be with vkd3d. The issue appears to be with Wine's directx-d3d component. It is not handling the card 8086:5916. Ref: https://forum.winehq.org/viewtopic.php?f=8&t=32035&p=121106#p121103 It appears your patch might handle this. If so, then my problem might be resolved. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #8 from Józef Kucia <joseph.kucia(a)gmail.com> --- (In reply to Cliff Hill from comment #7)
yes, I do. and I have tested that gears-vkd3d and triangle-vkd3d work. The issue does not appear to be with vkd3d.
Does your Wine is built with vkd3d support? Can you run the Windows version (cross-compiled) of the vkd3d gears in Wine? -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #9 from Cliff Hill <winehq(a)darkhelm.org> --- (In reply to Józef Kucia from comment #8)
Does your Wine is built with vkd3d support? Can you run the Windows version (cross-compiled) of the vkd3d gears in Wine?
I am using wine-staging from winehq. My understanding is that version 4.0+ defaults to being able to do vkd3d. I also am using a vkd3d that is specifically patched for being able to use with WoW. Here is my version info: Distro: Linux Mint 19.2 (Tara) Wine: (staging) 4.2~bionic -- Set to Windows 10 vkd3d: package from cybermax-dexter/vkd3d bionic PPA - specifically built with patches for WoW. 1.1cybmod23-bionic~1ppa1 intel integrated graphics: Intel HD Graphics 620 (rev 02) vulkan from Padoka Stable PPA (mesa implementation) 1.1.97.0~rc1-1lunarg18.04.1.1 mesa version: 18.3.3-1~b~padoka0 gears-vkd3d and triangle-vkd3d both work, and work well. I have nothing for dxvk installed. This was a clean wine-staging install. The only thing I added was corefonts. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #10 from Cliff Hill <winehq(a)darkhelm.org> --- Like I said, I have an intel 620 card, and Wine is not identifying the card. The reason WoW is not allowing for DirectX 12 is because it is defaulting to "Intel HD Graphics 4000" when it cannot identify the card -- and the 4000 series does not support DirectX 12. So.... I don't get DirectX 12 as an option in WoW. It is not because vkd3d is broken. I tried the GPU Caps Viewer application (see attached screenshots) based on a recommendation. And it cannot identify the card correctly from what I can tell. So I have narrowed my issue to wine and it not handling Intel 620. It appears the above patch would address that. I need to set up wine for compiling it myself I guess, to verify if it works. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 --- Comment #11 from Cliff Hill <winehq(a)darkhelm.org> --- Building wine myself is proving to be complicated and time-consuming, which I don't have any more time to devote to it. However I am fairly certain your patch will work for me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 Józef Kucia <joseph.kucia(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |88aaee78fe96084f2d1ff5c224b | |04d10c459088e --- Comment #12 from Józef Kucia <joseph.kucia(a)gmail.com> --- Should be fixed by https://source.winehq.org/git/wine.git/?a=commit;h=88aaee78fe96084f2d1ff5c22... The fix will be included in Wine 4.3. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 Alexandre Julliard <julliard(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #13 from Alexandre Julliard <julliard(a)winehq.org> --- Closing bugs fixed in 4.3. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |4.0.x -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=46729 Michael Stefaniuc <mstefani(a)winehq.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|4.0.x |--- --- Comment #14 from Michael Stefaniuc <mstefani(a)winehq.org> --- Removing the 4.0.x milestone from bug fixes included in 4.0.1. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
wine-bugs＠winehq.org