SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I marked my last thread as solved since I was just using the updated 440.XX one.
I'm still having this problem today with 450.80.02.
The 440 ones seems so old now I don't want to run an old one anymore.
Anything DXVK seems to be not working, not sure what to try. Did a full system upgrade today, if I turn off DXVK the game works but at reduced performance (14fps in cities).
What version of WINE are you using? Later versions of DXVK need a newer version of WINE. I played Diablo III with dx11/dxvk this morning and it was fine. I'm on the 455.28 drivers with wine-5.19 staging. wayland was added to multilib. Are you missing a package or two? (I was having problems with 32-bit dxvk, and it turned out I was missing the wayland packages. slackpkg install multilib.)
I'm having the same issue. I was on 440.100, and I tried 450.80.02 and 455.28. All of them exhibit the same behavior. "World of Warcraft was unable to start up 3D acceleration". I too, have 2 video cards, a pair of Nvidia GTX 1080 TIs. I get the same behavior with my current system wine (5.6) with DXVK 1.7.2 and Lutris wine (5.7-10) with DXVK 1.7.1L-743f309. I am thinking that there is something else going on here if you have it working under 440.100 and I can't even get that to work.
OK, y'all gave me the WoW bug. If I resubscribe, I'm blaming people in this thread. :P
When I launched WoW from Battle.net, it would crash with an error 132. I launched it directly (in World of Warcraft/_retail_/Wow.exe), logged in, and in subsequent launches, it seems to work fine through battle.net. (I'm using wine 5.19 staging, dxvk 1.7.2, and nvidia drivers 455.28. I compiled wine-staging with Alien Bob's MinGW and Dugan's slackbuild. (Note, you do need to do su -l to build it with mingw, otherwise it won't pick up the path correctly.)
WoW does need a PE-enabled build now...if Alien Bob's build doesn't work, give Dugan's slackbuild a try. (Alien Bob made a Mingw package, too.)
... like 15 times, I wasnt able to boot into my install. My motherboard seems to be random cause after several reboots it sometimes doesn't recognize UEFI devices at all. Made a bootable usb boot stick so I could boot from that and load my root drive, but then I have to make updates to the bootstick each time I upgrade the kernel and have it plugged in 24/7...
at last I gave up because of time restraints and I just want it to work som I am a noob now, running Ubuntu 20 LTS and everything is working. Maybe I'll be back d:
tbh I think my hardware is too much Unicorn for -current
@garpu sorry man, I feel you. The only reason that I'm trying to get this to work is because a friend wants me to re-sub.
@trite your boot issue after having removed one of your cards was likely due to an xorg mis-configuration.
I've seen posts around the net about people resolving this by reinstalling their OS of choice with a clean install, but that doesn't really get to the root of the issue. Ideally, I'd really like to troubleshoot this in order to help others that may be running across this. My problem is I don't really know where to look to figure out what is going on here.
I did try to launch wow.exe from a command line call with wine64 and get the following error:
"err: Failed to create surface". There is a lot more, before this, so let me know if you want more of the output.
I will also state that I had this working on a previous nvidia driver (430.50), but I quit wow in december 2019 and then upgraded to 440.59 shortly after (Jan 2020). I have since upgraded to 440.100 but I haven't tried to run WoW until recently (last few days) and it failed with the "unable to start up 3d acceleration" error. The two most common results for this error (related to linux) are either drivers or a clean reinstall of the OS.
Lastly, I'll add that this happens in WoW/WoW Classic and Overwatch. Everything else on my system runs fine, including StarCraft II and lots of steam games (through proton).
If anyone has any ideas or troubleshooting steps or where to look for help it would be greatly appreciated.
@trite your boot issue after having removed one of your cards was likely due to an xorg mis-configuration.
No I did a clean install of slacklive and that got stuck in boot loop/BIOS hell aswell. When I did that clean install I installed on a new harddrive and made the partitions from scratch and made new filesystems so it was clean.
What version of wine are you using? AFAIK, WoW and other blizzard games need 5.18 or 5.19 staging or above. I don't know if lutris 5.7 will work. (I also don't use lutris.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.