open All Channels
seplocked Linux
blankseplocked Singularity Build 276337 (was: 265540)
 
This thread is older than 90 days and has been locked due to inactivity.


 
Pages: [1] 2

Author Topic

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.06.02 20:50:00 - [1]
 

Edited by: Palovana on 05/07/2011 23:30:01
NOTE: subject edited to most recent SiSi version as of 2011-07-05 23:30 GMT

Can anyone using Linux and Wine connect to Sisi?

Despite 290 players online, I get STATUS: UNKNOWN.

Two different computers with different Internet providers, running Linux and Wine 1.3.21 (one is Ubuntu 10.10, one Xubuntu 11.04).

I can telnet to the 87.237.38.50 IP, port 26000 on both computers and get a response from the server, so it's not routing.

I don't have a dual-boot system to test with, but if anyone with a dual-boot box could put the latest Sisi build on both their Windows and Linux installs and test which one can connect, I'd wager a few million ISK that Windows will work but Linux on the same machine will not.

Pharum
Gallente
Posted - 2011.06.02 21:38:00 - [2]
 

Originally by: Palovana
Can anyone using Linux and Wine connect to Sisi?

Despite 290 players online, I get STATUS: UNKNOWN.

Two different computers with different Internet providers, running Linux and Wine 1.3.21 (one is Ubuntu 10.10, one Xubuntu 11.04).

I can telnet to the 87.237.38.50 IP, port 26000 on both computers and get a response from the server, so it's not routing.

I don't have a dual-boot system to test with, but if anyone with a dual-boot box could put the latest Sisi build on both their Windows and Linux installs and test which one can connect, I'd wager a few million ISK that Windows will work but Linux on the same machine will not.


You would win that bet windows vista works fine wine 1.3.21 status: unknown
seems the networking layer has changed: Network layer using: IOCP
WINEDEBUG=+winsock gives lots of:warn:winsock:WS2_sendto -> ERROR 10014

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.06.03 02:16:00 - [3]
 

Edited by: Palovana on 04/06/2011 15:43:28
Bug Report 111854 filed with CCP.
Not an EVE code issue, CCP bug report closed.

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.06.03 14:21:00 - [4]
 

Preliminary bug response is "Linux is unsupported, check the forums, kindly **** off now" - I'm not posting the actual response to avoid getting this thread locked.

I've asked for more information regarding what is being changed in the networking (which has always worked under Wine) but I don't think there will be a useful response coming.

Pharum
Gallente
Posted - 2011.06.03 14:48:00 - [5]
 

Someone should probably file a bug report with wine http://bugs.winehq.org/

Elegbara
Posted - 2011.06.03 19:38:00 - [6]
 

Edited by: Elegbara on 03/06/2011 19:48:58
Edited by: Elegbara on 03/06/2011 19:43:53
Some additional info:
Quote:
trace:winsock:WSASocketA af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1
trace:winsock:WSASocketW af=2 type=1 protocol=0 protocol_info=(nil) group=0 flags=0x1
trace:winsock:WSASocketW created 060c
trace:winsock:WS_connect socket 060c, ptr 0x8771e70 { family AF_INET, address 87.237.38.50, port 26000 }, length 16
warn:winsock:wsaErrno errno 115, (Operation now in progress).
trace:winsock:WS_getaddrinfo "www.eveonline.com", "80" 0x6b26fd0 -> 0x6b27070 0
trace:winsock:WS_getnameinfo { family AF_INET, address 87.237.39.197, port 80 } 16 0x339b18 1025 (nil) 0 2
trace:winsock:WSASocketA af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1
trace:winsock:WSASocketW af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1
trace:winsock:WSASocketW created 05c0
trace:winsock:WS_connect socket 05c0, ptr 0x6b26ff0 { family AF_INET, address 87.237.39.197, port 80 }, length 16
warn:winsock:wsaErrno errno 115, (Operation now in progress).
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
trace:winsock:WSASocketA af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1
trace:winsock:WSASocketW af=2 type=1 protocol=6 protocol_info=(nil) group=0 flags=0x1
trace:winsock:WSASocketW created 0610
trace:winsock:WS_connect socket 0610, ptr 0x81a2778 { family AF_INET, address 87.237.39.197, port 80 }, length 16
warn:winsock:wsaErrno errno 115, (Operation now in progress).
trace:winsock:DllMain 0xb7410000 0x2 (nil)
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
fixme:d3d:resource_check_usage Unhandled usage flags 0x8.
trace:winsock:WS_closesocket socket 060c
trace:winsock:WS2_recv_base socket 05c0, wsabuf 0xe03a96c, nbufs 1, flags 0, from (nil), fromlen -1, ovl 0x87b0638, func (nil)
trace:winsock:WS2_recv_base fd=321, options=0
trace:winsock:WS2_recv_base socket 0610, wsabuf 0xdf3a96c, nbufs 1, flags 0, from (nil), fromlen -1, ovl 0x87b17d0, func (nil)
trace:winsock:WS2_recv_base fd=324, options=0
trace:winsock:WS2_sendto socket 0610, wsabuf 0x87b1900, nbufs 1, flags 0, to (nil), tolen 0, ovl 0x87b1874, func (nil)
trace:winsock:WS2_sendto fd=327, options=0
warn:winsock:WS2_sendto -> ERROR 10014
trace:winsock:WS_shutdown socket 0610, how 0 0
Could we point CCP devs to this problem and ask them to fix it?

They have created a socket and are trying to connect. This fails (errno 115, EINPROGRESS) but they still attempt to send data through it which results in error 10014.

Also the description of EINPROGRESS return value for connect call:
[EINPROGRESS]
O_NONBLOCK is set for the file descriptor for the socket and the connection cannot be immediately established; the connection shall be established asynchronously.

Pharum
Gallente
Posted - 2011.06.03 20:09:00 - [7]
 

Originally by: Elegbara
Edited by: Elegbara on 03/06/2011 19:48:58
Edited by: Elegbara on 03/06/2011 19:43:53
Could we point CCP devs to this problem and ask them to fix it?

They have created a socket and are trying to connect. This fails (errno 115, EINPROGRESS) but they still attempt to send data through it which results in error 10014.

Also the description of EINPROGRESS return value for connect call:
[EINPROGRESS]
O_NONBLOCK is set for the file descriptor for the socket and the connection cannot be immediately established; the connection shall be established asynchronously.

they are sending data expecting it to pass after the connection is made problem is they pass NULL as the 4th parameter to WSASendTo see http://msdn.microsoft.com/en-us/library/ms741693%28v=vs.85%29.aspx it can be null when lpOverlapped is not null but wine just checks its not null see http://source.winehq.org/git/wine.git/blob/HEAD:/dlls/ws2_32/socket.c#l3827 and returns 10014 error we see because it is null

Elegbara
Posted - 2011.06.03 20:15:00 - [8]
 

Edited by: Elegbara on 03/06/2011 20:20:53
So that's in fact wine's fault?

Can we try to fix it, test it and if it works submit it to wine team?

Found this bug on winehq: http://bugs.winehq.org/show_bug.cgi?id=19491

Pharum
Gallente
Posted - 2011.06.03 20:19:00 - [9]
 

Yes I think thats the fault and yes someone would need to change that test so that it did not error and I suspect change some other code further down as the code works on the assumption the pointer is valid if it got that far then build the code with the changes and test if it works then either report the findings or a patch to the wine team for inclusion.

Elegbara
Posted - 2011.06.03 22:13:00 - [10]
 

Got the patch from the bug report linked above, applied it to latest git (manually). Compiled eve. Logged onto sisi. Win?

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.06.04 04:56:00 - [11]
 

Edited by: Palovana on 04/06/2011 05:12:22
That was quick, you guys rock.

So I was barking up the wrong tree the whole time? I suppose I can close the EVE bug report now.

EDIT: The new Sisi build (266924) shows the same behavior with an unpatched Wine.

Adrian Idaho
Posted - 2011.06.04 08:17:00 - [12]
 

Excellent job, thank you very much!

Now we need to get this patch into wine. We also need a guide on how to download, patch, and compile the new wine for all the other Linux users (since it'll take a while until the change is in the repos if it gets there at all).

Elegbara
Posted - 2011.06.04 11:10:00 - [13]
 

Edited by: Elegbara on 04/06/2011 13:21:43
I believe it's easier to nag wine maintainers about applying the patch than writing a comprehensive guide which will cover all Linux distributions.

For ubuntu it's quite simple I think...

wget http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh
sudo sh install-wine-deps.sh
git clone git://source.winehq.org/git/wine.git
cd wine
wget http://bugs.winehq.org/attachment.cgi?id=35010 -O overlapped.diff
git apply overlapped.diff
./configure
make
sudo make install

According to the description in install-wine-deps.sh this will also work for Fedora, SuSE, and OpenSolaris. The file itself contains mentions of OpenBSD and FreeBSD too. It does install git.

Update: there's some activity on wine site about the bug. Chances are we're getting it fixed soon.

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.06.04 15:43:00 - [14]
 

Originally by: Elegbara
wget http://winezeug.googlecode.com/svn/trunk/install-wine-deps.sh
sudo sh install-wine-deps.sh
git clone git://source.winehq.org/git/wine.git
cd wine
wget http://bugs.winehq.org/attachment.cgi?id=35010 -O overlapped.diff
git apply overlapped.diff
./configure
make
sudo make install


Confirming the patch worked in Xubuntu 11.04 64-bit, however the install-wine-deps.sh script isn't setup for Xubuntu or for 11.04 (natty) build of Ubuntu, so I used the method from the wine wiki to get my dependencies installed:

sudo add-apt-repository ppa:ubuntu-wine/ppa # I already had this done as I was using this repo to get my wine builds
sudo apt-get build-dep wine1.3 # get the dependencies installed
sudo apt-get remove wine1.3 # uninstall the repo 1.3.21 version
sudo apt-get install git # I didn't have git installed
(continue with "git clone" and all following steps)
Fresh copy of TQ build, patch with SisiLauncher (I need "winetricks vcrun2008" to run SisiLauncher)
Copy launcher and update it for new WINEPREFIX (I keep TQ and Test builds in separate prefix) and " /server:Singularity"
Launch and no more STATUS: UNKNOWN message, success!

Elegbara
Posted - 2011.06.04 16:07:00 - [15]
 

Originally by: Palovana
Fresh copy of TQ build, patch with SisiLauncher (I need "winetricks vcrun2008" to run SisiLauncher)
Copy launcher and update it for new WINEPREFIX (I keep TQ and Test builds in separate prefix) and " /server:Singularity"
Interesting. I use the same prefix for all my eve installations (tq, sisi, duality) and don't copy anything, just sisilauncher for test servers. Also I don't use any additional parameters - I guess launcher handles that.

Badmoons
Posted - 2011.06.07 13:27:00 - [16]
 

Need to get it added quick or there will be a lot of sad pandas on patch day...

Mamede
Posted - 2011.06.12 00:22:00 - [17]
 

Edited by: Mamede on 12/06/2011 00:23:53
Edited by: Mamede on 12/06/2011 00:23:08
It seems the patch works on main build 1.3.22. I'll test it now.
Maybe someone could do an ubuntu package for amd64 and i386 ;).

If someone could give me a good guide with no sweat, I could do it. I have both versions installed somewhere.
Hmm all wine deps are i386 no?

Mamede
Posted - 2011.06.12 00:34:00 - [18]
 

I'm doing a 11.04 .deb with the patch. Monday I'll come back to update(I'll be busy tomorrow)

Mamede
Posted - 2011.06.12 18:29:00 - [19]
 

Confirmed vanilla wine 1.3.22+patch works

Mamede
Posted - 2011.06.13 20:33:00 - [20]
 

I have an error after compiling wine while making the .deb. I'll try to use Scott's pkgs with the patch in 1.2.21.

Pharum
Gallente
Posted - 2011.06.14 23:19:00 - [21]
 

wine bug report fixed but this only fixed WSASend() as that was what the original bug was filed against. WSARecvFrom() still appears to be broken causing wine to now crash when trying to connect to sisi. Seems Elegbara's patch which covered both send and recv needs the recv half being sent again as a separate bug report to winehq. Easiest solution is still to apply Elegbara's patch to 1.3.21 / 1.3.22

Pharum
Gallente
Posted - 2011.06.15 09:39:00 - [22]
 

updated version of the patch against current git head ( just removes bits for now fixed WSASend ) http://pastebin.com/mnx3Uqq5

Mamede
Posted - 2011.06.15 15:46:00 - [23]
 

Edited by: Mamede on 15/06/2011 21:59:07
Hi , so finally I made the .deb.
You can find a .tar.gz with all the .debs inside(only one is needed, like with wine1.3 done by Scott Ritchie)
wine1.3_1.3.21-0ubuntu1~natty1~ppa3_amd64.deb
I think I have to do one for i386. I'll try to do it tonight in my i386 ubuntu.
You can find the tar.gz with the debs at:
http://dl.free.fr/d7NukXWY2


Please let me know if it works or not.

jansaell
Gallente
Phoenix Industries
Saints Amongst Sinners
Posted - 2011.06.18 18:33:00 - [24]
 

I had some small problems with overlapped2.diff - it was in dos format and missing the last newline. after fixing that the patch worked well.

Pharum
Gallente
Posted - 2011.06.18 19:16:00 - [25]
 

Edited by: Pharum on 18/06/2011 20:36:31
Originally by: jansaell
I had some small problems with overlapped2.diff - it was in dos format and missing the last newline. after fixing that the patch worked well.

Oops sorry about the patch problem it applied fine here so I am guessing I messed up in copy pasting it to pastebin somehow.
Could I persuade you to post your cleaned version of the patch. Saw link to your blog on patching wine with pulse + overlappedIO looks good.

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.06.18 22:54:00 - [26]
 

Edited by: Palovana on 19/06/2011 04:51:26
I uninstalled the compiled-from-1.3.22-source, patched wine that I had been running and installed the 1.3.22 install from the Ubuntu repo and had no trouble at all running the current (271273) Singularity build.

I'll try with an older .deb file of Wine I have lying around (1.3.17 I think it is) and see if that will run. We may not need to patch come Tuesday if CCP reverted some of their networking changes.

Will report back once I have 1.3.22 deinstalled and 1.3.17 installed.

EDIT: After using "sudo make uninstall" to remove my patched 1.3.22 Wine build, I re-installed 1.3.17 from a saved .deb file and the current (271273) Sisi build worked just fine.

I uninstalled the 1.3.17 .deb and installed the current 1.3.22 from the Ubuntu Wine PPA (deb http://ppa.launchpad.net/ubuntu-wine/ppa/ubuntu natty main) and build 271273 also worked just fine.

Just to be sure I did a full install of 271273 on a fresh Wine prefix with the unpatched 1.3.22 from PPA, and no problems.

So it seems that CCP has changed something in their networking code back to the way the current TQ build is doing things, and Linux users won't have mass panic come Tuesday.

jansaell
Gallente
Phoenix Industries
Saints Amongst Sinners
Posted - 2011.06.19 07:58:00 - [27]
 

As requested - my fixed overlapped2.diff is here (in a zip file)

Palovana
Caldari
Inner Fire Inc.
Posted - 2011.07.05 23:36:00 - [28]
 

Edited by: Palovana on 06/07/2011 00:13:06
OK, here we go again.

Soon before the release of Incarna, I found that the networking changes on SiSi were apparently reverted, and that the TQ release candidates (and the TQ release itself from June 21) would run properly on an unpatched Wine install.

So I have been running an unpatched Wine 1.3.23 from the .deb package from the Ubuntu Wine PPA (which contains the WSASend patch but NOT the WSARecvFrom patch).

This has now started breaking on SiSi builds again, and I'm currently in the process of compiling 1.3.23 from source using the "overlapped2.diff" patch from the zip file linked in the above post.

When everything is compiled I'll give build 276337 a go and see if it starts - with the unpatched 1.3.23 I didn't get the "server status unknown" as with older builds, but instead the game would crash before the login screen was displayed.

I'm only running a Core2 Quad and not an i7 so it might be a while before I can update with results.

EDIT: Source for Wine 1.3.23 patched correctly with the "overlapped2.diff" file and compiled successfully. Game now launches properly.

Kadesh Priestess
Scalding Chill
Posted - 2011.07.11 14:25:00 - [29]
 

I've opened bug in wine bugzilla regarding this crash:
http://bugs.winehq.org/show_bug.cgi?id=27762

Also i can confirm that linked above fix works for 1.3.24

Miraqu
Caldari
Posted - 2011.08.26 10:55:00 - [30]
 

Applies cleanly to .26 too.

Also seems to be deployed to tranquility this time. Expect some threads about "broken eve" in after August 30th.


Pages: [1] 2

This thread is older than 90 days and has been locked due to inactivity.


 


The new forums are live

Please adjust your bookmarks to https://forums.eveonline.com

These forums are archived and read-only