These forums have been archived and are now read-only.

The new forums are live and can be found at https://forums.eveonline.com/

Linux

 
  • Topic is locked indefinitely.
 

Returning after months: everything is broke

Author
Lex Sathanas
Spartan Shipyards
#1 - 2012-03-24 03:48:13 UTC  |  Edited by: Lex Sathanas
Apologies for making a new topic because I know the answers are probably here, but there were so many changes that I'm having trouble sorting through all of the responses and fixes. I just re-activated my account. My EVE version is 7.11.306979 and wine version 1.2.3 (Ubuntu 10.04)

I can't update. Trying to sort through fixes it looks like I've got two separate issues: I can't update because I can't run the launcher, and I can't run the launcher because stuff has changed. I've tried getting msvcr80,90,100 and setting them to (builtin, native) but all that does is make the game crash after splash screen.

Is my install just borked and I need to re-download the whole new install? Am I even going down the right path? I can't tell if all the instructions are for this issue, or for an issue further down the patch line. (It seems like what most people would have gone through would be manual patching until a later version, then dealing with the .dll updates to make it run after that)

Basically, there's so much information to sort through and I don't know what's relevant, please point me in the right direction?

EDIT: Doing more reading, it looks like I need wine 1.4 as a minimum to even try and get this working. Can someone confirm this is necessary? I think I might have a lot of painful upgrading to do.

EDIT 2: Downloaded a whole new offline install. Upgraded to wine 1.4 Set mscvr80,90,100 all to builtin, native.

Crashes before startup screen with err:module:attach_process_dlls "msvcr90.dll" failed to initialize, aborting

Help?
Talis Mahn
Aliastra
Gallente Federation
#2 - 2012-03-24 07:26:35 UTC
Yeah, its kind of a pain, but to run the launcher set the libraries to (native, builtin). Then close the launcher, and set the libraries back to (builtin, native) to run the game. Unfortunately you have to do this every time there is an update. And CQ still crashes the client.

After a few updates the process gets kind of automatic.

One of the rare Linux Eve players

Whitehound
#3 - 2012-03-24 08:26:52 UTC  |  Edited by: Whitehound
The answers are already out there. You can start here: http://wiki.eveonline.com/en/wiki/Install_EVE_on_linux_with_wine

You should install WINE 1.4 as the first thing and update your Linux and graphics driver to a reasonable state before you start.

There is some good news, too. You do not need to install anything but EVE itself these days. There is no need to use winetricks to install fonts or libraries, but it all comes shipped with EVE now. You can just create a directory, point $WINEPREFIX to it and install the client and you are done.

What you need to look out for are two things at the moment. One is that the Captains' Quarters (CQ) are broken under Linux and you have another good reason to turn them off. So expect to see EVE crash when you forget to disable the option Load Station Environment in your settings. Once you have docked at a station can you turn it on again. At first you will see that you are docked inside a station like in the good old times, but that you cannot spin your ship. Turning the option on will allow you to spin your ship again! Just avoid entering the station itself (it is a button on the right panel).

The other issue is with the launcher and how you need to start the game and the launcher itself. The problem here is that these need different libraries at the moment in order to run. You can use $WINEDLLOVERRIDES to change this and do it all in one command or with a desktop icon. Here is an example:

# Start the launcher for patching:
env WINEPREFIX="..." WINEDLLOVERRIDES="msvcr80,msvcr90,msvcr100=n,b" wine explorer "/desktop=EVE1,1680x1050" ".../drive_c/Program Files/CCP/EVE/eve.exe"


# Start the EVE client:
env WINEPREFIX="..." WINEDLLOVERRIDES="msvcr80,msvcr90,msvcr100=b,n" wine explorer "/desktop=EVE1,1680x1050" ".../drive_c/Program Files/CCP/EVE/bin/ExeFile.exe"


b and n stand for "builtin" and "native" and means that for the launcher you have to use the shipped libraries for msvcr80, 90 and 100, but in order to run the client can you use just the builtins of WINE. Setting the variable $WINEDLLOVERRIDES makes this fairly easy.

I have seen others using a mix of libraries and using winetricks. I do not know why they need it. How I described it here works fine for me.

Before I forget it, there is a third issue. The performance can be weak. It may be that your game runs on multiple cores, but that each core only gets about 20%-30% of work load. If you are using a CPU governor like "ondemand" will your CPU cores likely only run at half the speed. The "ondemand" governor, which is often the default for most distributions, only speeds up the cores when they reach 95% CPU load. You can change this in three different ways:

  1. You can use the command "taskset -c 0" to force EVE to run on a single core, thereby pushing the load of one core to 100% and avoid any negative effects of scheduling and multi-threading.
  2. You can use the "performance" CPU governor to disable the "ondemand" governor.
  3. You can tweak the parameters of the "ondemand" governor to speed up the cores at lower settings.

I went with 3. and changed it to 50%. You can check with the cpufreq-info command how often each core runs at full speed.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.

Lex Sathanas
Spartan Shipyards
#4 - 2012-03-24 19:51:12 UTC
Thank you, that was a very informative summary of a lot of the stuff I had been reading.

Unfortunately, it does not seem to work. I get a blank wine desktop and no error messages.
Whitehound
#5 - 2012-03-24 20:24:38 UTC  |  Edited by: Whitehound
Lex Sathanas wrote:
Thank you, that was a very informative summary of a lot of the stuff I had been reading.

Unfortunately, it does not seem to work. I get a blank wine desktop and no error messages.

Can you run a normal OpenGL application, i.e. glxgears?

Edit:
I see you are trying to run the patcher with "b,n". It needs to be "n,b" for the patching however.

If you have not patched it yet then you need to run the launcher first, with "n,b", let it download and patch the client. Once it is ready do you end the launcher and start the client with "b,n". Make sure you get this right.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.

Lex Sathanas
Spartan Shipyards
#6 - 2012-03-24 20:58:58 UTC
OpenGL works fine.

I downloaded a new offline install. Do I need to patch or should it run as is? Neither the patcher nor ExeFile will run. Attempts to run either with builtin, native opposite of what they should be do get me an error in msvcr90.

I do not have a wineprefix setup. that's the only difference in my setup from the commands you gave me.
Whitehound
#7 - 2012-03-24 22:11:18 UTC
Lex Sathanas wrote:
OpenGL works fine.

I downloaded a new offline install. Do I need to patch or should it run as is? Neither the patcher nor ExeFile will run. Attempts to run either with builtin, native opposite of what they should be do get me an error in msvcr90.

I do not have a wineprefix setup. that's the only difference in my setup from the commands you gave me.

Do you have something already installed in your .wine directory?

If so then create an empty directory like "~/ .eve" and use it exclusively for running EVE and do not install anything else in it. Use your ~/.wine for experiments or little stuff.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.

Lex Sathanas
Spartan Shipyards
#8 - 2012-03-25 06:38:13 UTC
Ok, I got a separate prefix setup for EVE and tried installing it again. Now I can't even install it. I get an error about python27.dll and the text of the installer is mangled. Googled a bit and came up with the recommendations to install corefonts and vcrun2008. neither helped.

I can run the installer on my normal .wine setup, but not on the prefix.

On the .wine install I tried every combination of builtin, native on msvcr80, 90, 100.

Nothing.
Whitehound
#9 - 2012-03-25 07:36:48 UTC  |  Edited by: Whitehound
Lex Sathanas wrote:
Ok, I got a separate prefix setup for EVE and tried installing it again. Now I can't even install it. I get an error about python27.dll and the text of the installer is mangled. Googled a bit and came up with the recommendations to install corefonts and vcrun2008. neither helped.

If you cannot install EVE from scratch into an empty directory then you have some problem with your Linux distribution.

Try this:

> rm -rf ~/.eve/
> mkdir ~/.eve
> export WINEPREFIX=/home/you/.eve
> winecfg
> wine EVE_Online_Installer_352940.exe


In short, delete ~/.eve, make a new directory, set the $WINEPREFIX variable to it, configure WINE and install EVE. Make sure the bold text matches what you have got.

If this does not work then your WINE installation is broken or incomplete and you first need to install WINE properly.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.

Lex Sathanas
Spartan Shipyards
#10 - 2012-03-25 08:44:26 UTC  |  Edited by: Lex Sathanas
Yeah, that's what I did, and it fails.

I'm using Ubuntu 10.04 and the wine1.3 package (which installs wine 1.4, I have no idea what is up with the versioning, but it was how I was told to install wine 1.4 on the ubuntu forums.)

Any idea how to more 'properly' install wine? Please don't say compile from source. I did that once and it was a nightmare.

EDIT:

I copied my installed copy of eve from .wine to the .eve wineprefix and it failed with an error in msvcr100. If that means anything.
Whitehound
#11 - 2012-03-25 11:31:38 UTC  |  Edited by: Whitehound
Lex Sathanas wrote:
Yeah, that's what I did, and it fails.

I'm using Ubuntu 10.04 and the wine1.3 package (which installs wine 1.4, I have no idea what is up with the versioning, but it was how I was told to install wine 1.4 on the ubuntu forums.)

Any idea how to more 'properly' install wine? Please don't say compile from source. I did that once and it was a nightmare.

EDIT:

I copied my installed copy of eve from .wine to the .eve wineprefix and it failed with an error in msvcr100. If that means anything.

Sorry, I have compiled it myself... I checked on your Ubuntu version, because I remember seeing 12.xx as the latest. Your version 10.04 is about 2 years old! Try installing the latest, stable Ubuntu, which is version 11.10 (version 12 is said to be released in April this year). WINE needs a lot of libraries to run, i.e. the "ia32-libs", and when they are outdated will you get a lot of problems. So you better get your Linux distribution into shape before you try anything else.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.

Godfrey Silvarna
Arctic Light Inc.
Arctic Light
#12 - 2012-03-25 13:09:42 UTC  |  Edited by: Godfrey Silvarna
Some people have had that python dll bug when they run eve on a non-english environment. For example I need to start eve, repair tool and installer with:

> env LC_ALL=en_US.UTF-8 wine "C:\Ohjelmatiedostot\CCP\EVE\eve.exe"

If I run it with languages set to the default fi_FI.UTF-8 it crashes with the same error you had. The usual rules for n,b vs. b,n apply.
Lex Sathanas
Spartan Shipyards
#13 - 2012-03-26 04:37:22 UTC
Tried that language change, no luck.

Kinda out of ideas.
Buzzy Warstl
Quantum Flux Foundry
#14 - 2012-03-26 12:57:12 UTC
winetricks msvcr80 msvcr90 msvcr100

I'm running on Ubuntu 11.04 stock with no trouble at this point, though I do need to bounce back and forth between the native and builtin libraries for those for the launcher.

http://www.mud.co.uk/richard/hcds.htm Richard Bartle: Players who suit MUDs

Princess Layla
We Eat Babies
#15 - 2012-03-29 02:56:07 UTC
Lex Sathanas, I just had the same problem and the solution lies in Whitehound his post, but there is a way to do it without command lines and Wine Prefixes....

run winecfg
set msvcr80,msvcr90,msvcr100 to native then built in
run repair.exe in your Eve installation folder, the patching will work flawlessly
run winecfg (again)
set msvcr80,msvcr90,msvcr100 to builtin then native
run Eve as usual.

Thanks Lex Sathanas, you saved my butt :P
Lex Sathanas
Spartan Shipyards
#16 - 2012-04-16 21:12:14 UTC
Well, I'm glad someone else got something out of all this, I am still having no luck.

I'm not at the affected computer at the moment, but I'll try to recap:

I have two instances setup: One is my old EVE install. I cannot run the patcher, or ExeFile, with any combination of native, builtin. Trust me, I've had enough time, I've tried all possible combinations.

The other setup I have involves installing a new copy of eve (the full build) with a wineprefix. I can't even install this: I get the aforementioned python error.

The problem is, both of these problems seem to have common, easy fixes, which makes it hard to get information because the common responses simply don't work.

Getting pretty frustrated; wish I hadn't been dumb and paid 3 months up front.

When I get home I'll post full errors for both scenarios above. I am assuming my Wine install is just screwed or something, but it's from the Ubuntu repository, and building wine from source is about as fun as a draino enema, and also has never, ever worked for me. If I were to get a live CD do any of those come with wine 1.4 (or are able to install it? not sure how installation / upgrades work with live CD filesystems) so I can test that out?

I am ok with reformatting if that's what it takes to get wine setup correctly but I want to have some kind of assurance (ie, a live cd test that works) that it might work.

Edit: repair.exe won't run either.
Whitehound
#17 - 2012-04-16 21:44:46 UTC
Lex Sathanas wrote:
Well, I'm glad someone else got something out of all this, I am still having no luck.

I'm not at the affected computer at the moment, but I'll try to recap:

I have two instances setup: One is my old EVE install. I cannot run the patcher, or ExeFile, with any combination of native, builtin. Trust me, I've had enough time, I've tried all possible combinations.

The other setup I have involves installing a new copy of eve (the full build) with a wineprefix. I can't even install this: I get the aforementioned python error.

The problem is, both of these problems seem to have common, easy fixes, which makes it hard to get information because the common responses simply don't work.

Getting pretty frustrated; wish I hadn't been dumb and paid 3 months up front.

When I get home I'll post full errors for both scenarios above. I am assuming my Wine install is just screwed or something, but it's from the Ubuntu repository, and building wine from source is about as fun as a draino enema, and also has never, ever worked for me. If I were to get a live CD do any of those come with wine 1.4 (or are able to install it? not sure how installation / upgrades work with live CD filesystems) so I can test that out?

I am ok with reformatting if that's what it takes to get wine setup correctly but I want to have some kind of assurance (ie, a live cd test that works) that it might work.

Edit: repair.exe won't run either.

I am pretty certain that you need to get a newer Linux distro than your two year old Ubuntu. All the libraries WINE depends on will be outdated. Installing WINE with brute force and ignoring the dependencies will not work.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.

Lex Sathanas
Spartan Shipyards
#18 - 2012-04-16 23:16:55 UTC
Whitehound wrote:

I am pretty certain that you need to get a newer Linux distro than your two year old Ubuntu. All the libraries WINE depends on will be outdated. Installing WINE with brute force and ignoring the dependencies will not work.


Interestingly enough I started a thread on the Ubuntu forums about the same time I posted this one here about how to upgrade ubuntu because I broke the upgrade path (Ironically enough, because of wine and eve!) by removing PulseAudio, and the consensus over there was to not bother and that wine 1.4 would work fine on 10.04.

Might see if I can dig up an old harddrive and just install a couple distros and versions and see how they fare.

My wine/alsa setup has been holding me back from upgrading for a long time, I guess since I ran that into the ground I might as well now.
Whitehound
#19 - 2012-04-17 09:55:23 UTC
Lex Sathanas wrote:
Might see if I can dig up an old harddrive and just install a couple distros and versions and see how they fare.

This is a good idea.

Loss is meaningful. Therefore is the loss of meaning likewise meaningful. It is the source of all trolling.