Ryzom

My client connects and shows a page where I can probably choose which character I want to use (empty atm as I'm a new user), but when I click on the "Create" button the client crashes just after opening the character creation page (with the 3d model in the middle)

I am getting this error output:

_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local
_X11TransOpen: transport open failed for local/SpeedBase:0
x11drv: Can't open display: :0.0
wine client perror:2: write/writev: Bad file descriptor

anyone would have an idea of the cause of it and how to fix it?

llama25 wrote:My client connects and shows a page where I can probably choose which character I want to use (empty atm as I'm a new user), but when I click on the "Create" button the client crashes just after opening the character creation page (with the 3d model in the middle)

I am getting this error output:

_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local
_X11TransOpen: transport open failed for local/SpeedBase:0
x11drv: Can't open display: :0.0
wine client perror:2: write/writev: Bad file descriptor

anyone would have an idea of the cause of it and how to fix it?

The "x11drv: Can't open display: :0.0" says that the client cant connect the the X server, but this is a bit strange since you obviously have something on the screeen , but it usually happens if you switched user, ie dont have permissions for the local display, it could also be a name confusion on the the machine:
try to set the DISPLAY enviroment var:
export DISPLAY=localhost:0
before starting the game.

the last error:
"wine client perror:2: write/writev: Bad file descriptor"

could be write permissions related, make sure you have write permissions in the directory where Ryzom is installed.

If that doesnt help we probably need some more info like what distro you are running, what versions of cedega/wine, video card...

zyrom wrote:the last error:
"wine client perror:2: write/writev: Bad file descriptor"

could be write permissions related, make sure you have write permissions in the directory where Ryzom is installed.

I don't have exactly this error at each try, in fact sometime I don't have the write error but wine debugger starting at this moment and a flood of debug info which I don't really understand and didn't posted because it is really long. But I'm sure I have write permissions in this directory.

zyrom wrote:If that doesnt help we probably need some more info like what distro you are running, what versions of cedega/wine, video card...

I'm running Debian Sarge with Cedega 4.3.2 and a NVidia FX5200, also most of the time launching 3D games in a second X display with "X :1" as root then "wmaker -display :1" as user (the log I posted was by running on display :0 as it is where I have desktop and browser and such).

But I figured something that might help, my monitor's max depth is 24 bits and I can only choose some 32 bits resolution in config software.

OOC :

Hello

I belive that you should try and run the game in 32-bit resolution as Ryzom is displaying in 32-bit.
So try and switch to that mode and re-run it.

/OOC

// Drakfot

It doesn't really matter that your monitor has a lower resoloution, that is taken care of by the the video card, which *can* handle 32 bits resoloution. I asume youre running with the latest NVDIA drivers etc..
And you have edited the cedega config and told it to use 128 Mb agp.

with "X :1" as root then "wmaker -display :1" as user

this might not work since that would make root the effective user of the X session and the nvidia controll device. you should be able to do it as a normal user, if you cant then the permissions on the nvidia device in /dev/ are probably to restrictive. Also if youre logged in as root on the main console, then there might be a bunch of other device and ordinary files that you don not have access to as a normal user.

Just to elimininate evrything else, have you tried to run it standalone ? with just the X server cedga and Ryzom on the primary display..
You cna do this by making a small xinit_ryz file containing:

xterm -geometry 100x10-10-10 &
cedega client_ryzom_rd.exe &> ryzlog

and then starting X from the text console:

export XINITRC=./xinit_ryz
xinit -- :0

if it craches again the log should tell us what whent wrong..., you could always mail it to me.

zyrom wrote:if it craches again the log should tell us what whent wrong..., you could always mail it to me.

it crashed at exactly at same moment, couldn't find your email (no access to user profile) but I uploaded the ryzlog file to an http server at http://www.speedbass.net/ryzlog

couldn't find your email

Oops, sorry about that, zyrom@itr.no btw

Had a look at the log, The backtrace seems to indicate that the falling function is this one:
Backtrace:
=>0 0x40faa7ba (X11DRV.DLL.Beep+0x8c7b2 in libGL.so.1) (ebp=4fcd24c8)
a bot farther down you see:
0x40faa7ba (X11DRV.DLL.Beep+0x8c7b2 in libGL.so.1): cmpl $0,0x34(%ebx)

So.. you are sure that you have the correct opengl drivers ?
Linux/X comes with its own, the NVIDIA installer usually does a good job of getting rid of them but sometime fails misserably.
Take a look in the NVIDIA readme file under Apendix C. ( you usually find in under /usr/share/doc/NVIDIA_GLX-1.0)


But i'm still a bit suspicious about you getting this:

_X11TransSocketOpen: socket() failed for local
_X11TransSocketOpenCOTSClient: Unable to open socket for local
_X11TransOpen: transport open failed for local/SpeedBase:0
x11drv: Can't open display: :0

Not that i think it matters much but...

it seems to indicate that there is something wrong with the network setup.
you should be able to do a: ping localhost and it should resolve to the 127.0.0.1 ip adress check /etc/hosts it should have to following entry:
127.0.0.1 localhost.localdomain localhost

about nvidia drivers I was using the packages nvidia-kernel-source (that I compiled of course) and nvidia-gx from the non-free debian repository so it wasn't the latest version, I tried with desinstalling them and install the driver provided on nvidia.com but I had same error so I finally reinstalled thoses from debian repository (it's always more handy to have them as debian packages for dependencies and such)

but I managed to play using 1024x768 windowed mode without sound, and had same crash with same debug info when enabling sound once in game and "zoning" (not sure if this word is used in SoR, the crash hapened when I entered the teleporter in the hut and choosed a destination), that is pretty weird as according to the debug log it would rather have been an error with X.

llama25 wrote:.... that is pretty weird as according to the debug log it would rather have been an error with X.

Hmm yes i saw that in the log file and had a strong suspicion about it, i have hadd issues with severe hangs after teleports, that resolved after turning off sound, teleports are instantaneous, the delay is caused by the client loading all the new textures, and it seems that there is an issue with sound here. It seems to be an timing/interrupt overload / buffer overflow or somthing in that venue.
try to turn sound of both in Ryzom and in cedega...

What sound driver are you running ? alsa / oss, personally i have had better results with the alsa drivers but...

the 1027x768 issue is a bit strange, have only seen that on low level cards before that did not have enough AGP memory.. ( i asume your agp setting in bios matches the card [128])

Btw, what kernel version are you running on ?

after further testing it appears that I can play fullscreen in 1280x1024, problem seems to be only with sound, tried using both alsa & oss and even with reducing the max amount of tracks to minimum (8 in config, 4 in game) it crashs either at character selection screen when sound activated via config or when using teleporter when activated in game.

I use precompiled debian kernel 2.6.8-2-686 so alsa but using also oss emulation (which I used for cedega as it worked better for all games I used so far)