Valkyria Chronicles Wine FX2800M Crash.

rup1034 · 05-09-2017, 12:27 PM

Valkyria Chronicles PC Steam Crashes on the following pc, Lenovo W700 Laptop, Geforce FX2800M Quadro 1GB, Slackware linux, Nvidia proprietary driver 340.101 legacy, x.102 would not compile but does not provide any significant fixes.

I have the same install since I litterally duplicated my desktop install onto my laptop but with legacy nvidia drivers. My desktop has a 660GTX and the game loads and plays fine with wine 1.9.20.

During Configuration of the game on the laptop it shows Geforce FX5800 in the graphics card selection. Then once I launch the game it black screens and crashes with a page fault. This same machine when running Steam on wine I can play counter-strike source, dod:source with allright fps.

I wonder if the graphics card showing up as the wrong name might affect it somehow or if some part of the Legacy NV driver has an issue? Anyone gotten this game to work while using Legacy NV drivers?

Things I have tried:
Different versions of wine I compiled 2.7 with all patches as a test and still got a crash.

I have the correct wine tricks installed msxml,vcrun2010,dx9, and have Windows XP set along with the correct file path.

Tried WINEDEBUG=+relay into a file but too much stuff goes by and I can't decipher what would be wrong among the false positives and fixme's. When I use the laptop tomorrow I will make a pastebin of the crash dump and create a debug file to zip up and post someplace.

As a test I also launched the game inside VMWare workstation 12.5 pro and it runs but has lag at critical moments so I know the graphics card can run the game, and likely if I had windows installed it would work.

RadicalDreamer · 05-10-2017, 04:59 AM

Which version of Slackware specifically? I have the game installed via PlayOnLinux under Slackware64-Current with Multilib. You can use debug in PlayOnLinux to help debug issues.
https://slackbuilds.org/repository/1...ch=playonlinux

Windows version is set to XP. Here is the libraries I have installed (probably don't need them all)

Code:

"*d3d8"="builtin"
"*d3d9"="builtin"
"*d3dcompiler_33"="native, builtin"
"*d3dcompiler_34"="native, builtin"
"*d3dcompiler_35"="native, builtin"
"*d3dcompiler_36"="native, builtin"
"*d3dcompiler_37"="native, builtin"
"*d3dcompiler_38"="native, builtin"
"*d3dcompiler_39"="native, builtin"
"*d3dcompiler_40"="native, builtin"
"*d3dcompiler_41"="native, builtin"
"*d3dcompiler_42"="native, builtin"
"*d3dcompiler_43"="native, builtin"
"*d3dim"="native"
"*d3drm"="native"
"*d3dx10_33"="native, builtin"
"*d3dx10_34"="native, builtin"
"*d3dx10_35"="native, builtin"
"*d3dx10_36"="native, builtin"
"*d3dx10_37"="native, builtin"
"*d3dx10_38"="native, builtin"
"*d3dx10_39"="native, builtin"
"*d3dx10_40"="native, builtin"
"*d3dx10_41"="native, builtin"
"*d3dx10_42"="native, builtin"
"*d3dx10_43"="native, builtin"
"*d3dx11_42"="native, builtin"
"*d3dx11_43"="native, builtin"
"*d3dx8"="native"
"*d3dx9_24"="native, builtin"
"*d3dx9_25"="native, builtin"
"*d3dx9_26"="native, builtin"
"*d3dx9_27"="native, builtin"
"*d3dx9_28"="native, builtin"
"*d3dx9_29"="native, builtin"
"*d3dx9_30"="native, builtin"
"*d3dx9_31"="native, builtin"
"*d3dx9_32"="native, builtin"
"*d3dx9_33"="native, builtin"
"*d3dx9_34"="native, builtin"
"*d3dx9_35"="native, builtin"
"*d3dx9_36"="native, builtin"
"*d3dx9_37"="native, builtin"
"*d3dx9_38"="native, builtin"
"*d3dx9_39"="native, builtin"
"*d3dx9_40"="native, builtin"
"*d3dx9_41"="native"
"*d3dx9_42"="native, builtin"
"*d3dx9_43"="native, builtin"
"*d3dxof"="native"
"*dciman32"="native"
"*ddrawex"="native"
"*devenum"="native"
"*dinput"="builtin"
"*dinput8"="builtin"
"*dmband"="native"
"*dmcompos"="native"
"*dmime"="native"
"*dmloader"="native"
"*dmscript"="native"
"*dmstyle"="native"
"*dmsynth"="native"
"*dmusic"="native"
"*dmusic32"="native"
"*dnsapi"="native"
"*dplay"="native"
"*dplayx"="native"
"*dpnaddr"="native"
"*dpnet"="native"
"*dpnhpast"="native"
"*dpnlobby"="native"
"*dsound"="builtin"
"*dswave"="native"
"*dxdiag.exe"="native"
"*dxdiagn"="native"
"*msdmo"="native"
"*qcap"="native"
"*quartz"="native"
"*streamci"="native"
"*xinput1_1"="native, builtin"
"*xinput1_2"="native, builtin"
"*xinput1_3"="native, builtin"
"*xinput9_1_0"="native, builtin"

rup1034 · 05-10-2017, 02:20 PM

I am also on slackware-current multilib from about a few months ago.

I am currently not using PlayOnLinux because it segfaults when ever I try to change prefix settings not sure how to fix that, I compiled wine from source code using a modified .SlackBuild, I manually create prefixes using my own scripts. Would be pretty cool to use PoL I am sure.

So far to keep the variables limited in the test case I used the same wine version 1.9.20 that works at home on my desktop pc. I kept the same exact os as I just tarballed my / directory moved it to my laptop and changed some configs and hostname and changed the NV driver. The laptop has as new of Legacy Nvidia driver as I could compile 340.101. I also deleted and re created the wine prefix doing wineboot, winecfg (adding drives), then winetricks msxml6 vcrun2010. Then ran Steam, started the game it installed dx9, starts to launch then black screen. Doing the exact same on my desktop does work and I can play just fine but not the laptop.

I also tested compiling wine 2.0 stable, 2.3, 2.6, 2.7(latest commit that works with all patches applied) with wine-staging patches applied and had the same results with all versions, it was a very lengthly process testing all those versions.

Now on the laptop I am using Nvidia 340.101 and wonder if that is breaking it due to how old the laptops graphics card is it is legacy. My desktop has modern nvidia drivers as it has a Geforce GTX660Ti.

I can try to manually add all those builtin/native flags you told me and see if it helps but I would not think they would be needed. I will try it this afternoon and type them in unless there is a faster way to do overrides with a script or something.

My Crash Dump on pastebin: https://pastebin.com/iKhDLgLz

This is my configure options from my slack build:
./configure \
--prefix=/usr \
--mandir=/usr/man \
--docdir=/usr/doc/$PRGNAM-$VERSION \
--with-gnutls=yes \
--with-opengl \
--with-x \
--x-includes=/usr/include \
--with-alsa \
--without-oss \
--with-pulse \
--without-cups \
--with-dbus \
--with-openal \
--with-opengl \
--without-jpeg \
--with-png \
--without-mpg123 \
--with-fontconfig \
--with-freetype \
--build=$ARCH-slackware-linux

RadicalDreamer · 05-11-2017, 04:07 AM

Are you using the nouveau driver?
Did you try the slackbuilds for the NV legacy driver?
https://slackbuilds.org/repository/1...acy340-kernel/
https://slackbuilds.org/repository/1...acy340-driver/

I'm no expert on Wine. Its best to install other versions of Wine in PlayOnLinux that is not the system version. Also don't install a 64 bit and 32 bit build of the same version with PlayOnLinux because it seems to get confused on which one is desired. Its a GUI, its easy, and I'm lazy.

I used the latest wine-staging 32 bit at SlackBuilds with PlayOnLinux and got it to work on a new graphics card.

rup1034 · 05-11-2017, 08:34 AM

Nope not using nouveau, I do not even have it compiled into the kernel. I used the Nvidia official .run file 340.101 by doing extract here then applying the patch to allow it to build against kernel 4.8.15. NV drivers just do not get updated as often for new kernel versions. 340.102 only adds one feature. The slackbuilds listed above would be too old to use for me and would require a ancient kernel. I may just have to deal with valkyria chronicles not working. I have a fully working operating system with all libs/opengl32 stuff, other games work in windows steam on wine, and all my linux steam games work on native, I also play Crazy Stone DLE, Skype works, PSP emulator works, EQ2 loads plays but crashes but I just used that as a benchmark, Diablo II v1.13 works for playing on lan with my buddy at work, DOSBOX is aok. Hopefully one day the new starcraft remake 1.18 patch will work.

Once I know I can build legacy + vmware against 4.11 I am gonna build a new kernel for that. Though I will still be in the same boat with my game though lol.

Thanks for the attempt.

Edit:
Looks like there is a 4.11 nvidia patch for 340.102 I know its a long shot but I will give that driver update a try at work today.
https://devtalk.nvidia.com/default/t...x-kernel-4-11/

Edit 2:
I updated to kernel 4.11 and got 340.102 to build and am using wine-2.7-29-g7cd7f14 still no go on launching the game.

RadicalDreamer · 05-11-2017, 07:01 PM

Have you tried nouveau with it?

rup1034 · 05-11-2017, 08:39 PM

I will test it tomorrow depending on how busy I am at work to see if Valkyria chronicles launches. I have a separate install I have been prepping to upgrade to a newer Slackware current and to do it cleanly and that version for now has nouveau on it. I know that on nouveau the native version of Steam for Linux does not work just wont boot up. But I can finally nail down if it is a driver issue if I test wine steam on it. I will post back here once I have tested it.

RadicalDreamer · 05-12-2017, 04:38 AM

One thing I know that can cause problems in PlayOnLinux is the libs it installs in .PlayOnLinux/wine:
https://www.playonlinux.com/en/topic..._prefixes.html

I had to remove the installed zlib for a 64 bit wine build in that location because it was causing problems.

rup1034 · 05-12-2017, 06:49 PM

Gave it a test on nouveau drivers on a separate install and managed to get it to work. Very laggy but does function so I am going to do a wine debug to file for both probably tomorrow if work isn't too busy. I want to see which function fails so that I can make up a proper wine bug report. I am using wine-2.7-29-g7cd7f14 (Staging) with all patches applied.

Edit:
So for sure it is the nvidia driver causing it. To make sure it wasnt any library version mismatches or something else I took my install which was using nouveau with working valkyria chronicles, blacklisted nouveau, installed nvidia legacy 340.102, then valkyria chronicles returns back to crashing. There is alot of debug info when I do WINEDEBUG=+relay and when doing winedbg I can either choose to dump to file or to the console screen. So its hard for me to tell what's what when its going by live too much info.

Is there a way to have winedbg output to console and to a file so that I can make a note of the break point as it scrolls by in the console right when I click start game? Thus I can later go into the output text file and find break point x and have a place to start.

Edit 2:
Found a better way, just did WINEDEBUG=-all,+d3d researching which things it could be graphics related.

Edit 3:
Here is my wine output from WINEDEBUG,-all,+d3d for only starting Valkyria Chronicles with Nvidia Legacy Driver and wine 2.7 staging with patches.
Just before the crash is wined3d_texture_invalidate_location not sure what it means yet.
https://pastebin.com/DGhSsehM