I've re-installed Fedora GNU/Linux recently and proceeded to install latest nVidia driver. After that was done, I installed wine so that I could play Civilization 4. I started it from console and I got "Segmentation fault". Google couldn't find me any coherent answer that'd address the issue, nor one that'd fix the problem. I tried to memtest, turned out fine. I tried to start it with the commands "WINEARCH=win32 WINEPREFIX=~/.wine32 wine Civilization4.exe" and "WINEARCH=win64 WINEPREFIX=~/.wine64 wine64 Civilization4.exe". Both returned the same results. I know that Civilization4.exe is known to access low level memory, so I made a policy to enable such access to wine. That didn't work either, so I went with disabling SELinux altogether. Same results.
I wanted to run another game because at this time I was rather annoyed by the fact that I've wasted time for this only to have it not work, whereas in the past it'd work just fine. To my absolute surprise every Windows game that required hardware acceleration returned the same result! What the heck could possibly be wrong?
Specs: Fedora 17, Linux 3.4.4 amd64, Wine 1.5.8, nVidia 295.59
Segmentation faults in every hw accelerated game
^ tried that too.
BTW in the post before I was using a kernel optimized for my CPU with safe flags, no crazy ricing. I repeated the process today, this time on a stock kernel from my repo, and this time I only got as far as having a couple games work. Civ4 is still fubar, as I need to install msxml3, but wine usually comes bundled with it, what did go wrong? I tried winetricks to accomplish that:
You gotta be kidding me!
This happens when I create a wineprefix with WINEARCH=win32. I rm -rf'd my wineprefix and started without any fruity variables.
So yeah, now I have working games but there still remains a question that winds up me up: why having a WINEARCH set to win32 during wineprefix creation makes it have deficiencies big enough to not run winetricks?
BTW in the post before I was using a kernel optimized for my CPU with safe flags, no crazy ricing. I repeated the process today, this time on a stock kernel from my repo, and this time I only got as far as having a couple games work. Civ4 is still fubar, as I need to install msxml3, but wine usually comes bundled with it, what did go wrong? I tried winetricks to accomplish that:
Code: Select all
[drush@puter ~]$ sh winetricks
------------------------------------------------------
wine cmd.exe /c echo '%ProgramFiles%' returned unexpanded string '%ProgramFiles%' ... can be caused a corrupt wineprefix, an old wine, or by not owning /home/drush/.wine
------------------------------------------------------Code: Select all
[drush@puter ~]$ ls -la | grep .wine
drwxrwxr-x. 4 drush drush 4096 07-19 04:02 .wineSo yeah, now I have working games but there still remains a question that winds up me up: why having a WINEARCH set to win32 during wineprefix creation makes it have deficiencies big enough to not run winetricks?
It shouldn't. Normally the problem is the opposite: some things (like .NET) will only install to 32 bit wineprefixes.drush wrote: So yeah, now I have working games but there still remains a question that winds up me up: why having a WINEARCH set to win32 during wineprefix creation makes it have deficiencies big enough to not run winetricks?
