[FAQ] Ryzom in Linux (The Unofficial HOW-TO)

[dpi209]

Hehe
I'll do my best =)

Would be interesting to know, how many ppl are actually playing under Linux and how many would if there was a native linux port of Ryzom...

[grandma]

dunno, i can think of around 10 people i personally helped get the client working in linux...when a native linux client is released, i'm sure it will definitely be embraced by many linux junkies. tweaking and configurability (modular action system) is what we're all about! :0)

[nafai]

hi grandma, I'll take part of your howto for a french one.

It's nice to see that there is some linux users on the other shards

[neskweek]

Hi Grandma
I just dropped by to tell you, as nafai just said, that your howto had been translated into french. And I'm the guilty one who did it

I'm sorry I should have tell you this sooner

But I was so pleased to find a great working Howto that I wanted to share it with my frenchys friend. So I took it and made a french version. I think you would be please to know that I didn't change a word.

And to answer dpi209 : look at the number of people who read that kind of subject ... It will give you an idea of how many people would be interested in a linux client (of course look in all the shards , 'cause I far as I know, there's now the same subject in all the shards ...)Be sure that makes a lot of people... and many more if the version would be released

Thanks again for your howto Grandma

[grandma]

sweet, good to hear! :0)

[zyrom]

I had a itch, so i scratched it, this particular itch was Qnet the Mtp client for Linux that did not work very well for the Ryzom chat, i sat down and made it work, so now there is a version that does:
get it http://is1.itr.no/~zyrom/linux/qnet/ there 2 versions there one for fedora core 2 and one for fedora core 3, if yo prefer to recompile it yourself the src.rpm is there also and if you are really adventurous you can get the tar file and the patch file and apply them your self .

There are probably a slew of problems with it still but, the basics works, i haven't tested the dessin ( drawing) stuff so that might be out the window (pun intended).

Now i take not responsibility if that code crashes your box, makes you go bald, fries your cat or any other catastrophes that might befall you.

btw. Qnet is , among other things, dependent on fortune, you may safly ignore that and install with --nodeps, if that is the only dependency complaint...

[nofftz]

I tried your HOWTO but have to success running the game or even the configuration utility. Its always crashing showing a "segmentation fault" message.

Any ideas? Here is a strace dump:

...
stat64("/usr/lib/transgaming_cedega//winex/bin/wine-preloader", {st_mode=S_IFREG|0755, st_size=10832, ...}) = 0
brk(0) = 0x8100000
brk(0x8101000) = 0x8101000
getgroups32(32, [0, 6, 24, 29, 33, 44, 1000]) = 7
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [INT CHLD], [], 8) = 0
clone(child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0x4000fbc8) = 13237
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [CHLD], [], 8) = 0
rt_sigaction(SIGINT, {0x8079bd0, [], 0}, {SIG_DFL}, 8) = 0
[{WIFSIGNALED(s) && WTERMSIG(s) == SIGSEGV}], 0) = 13237
write(2, "/usr/bin/cedega: line 348: 13237"..., 156/usr/bin/cedega: line 348: 13237 Segmentation fault $SHELL -c "$RUNWINE $WINVER -debugmsg $DEBUGMSG -use-dos-cwd $WORKDIR $EJECT $DT -- $COMMAND_LINE"
) = 156
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGCHLD (Child exited) @ 0 (0) ---
waitpid(-1, 0xbffff504, WNOHANG) = -1 ECHILD (No child processes)
sigreturn() = ? (mask now [])
rt_sigaction(SIGINT, {SIG_DFL}, {0x8079bd0, [], 0}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
read(255, "", 8176) = 0
exit_group(139) = ?

I'm using Debian unstable, cedega 4.3-1, kernel 2.6.7, xfree 4.3.0.dfsg.1-1 with ATI's FireGL drivers.

[grandma]

not sure...i don't believe i've ever had this kind of problem with ryzom...segmentation fault that is. have you tried Cedega 4.2 (doubt that's what's causing it).

[zyrom]

I tried your HOWTO but have to success running the game or even the configuration utility. Its always crashing showing a "segmentation fault" message.

Any ideas? Here is a strace dump:



I'm using Debian unstable, cedega 4.3-1, kernel 2.6.7, xfree 4.3.0.dfsg.1-1 with ATI's FireGL drivers.

have you tried to run annything else than ryzom? notepad.exe for example, or just run cedega with no program to run...


based on the partial trace, it seems that cdega is getting its segmentation fault before it has even started properly.

this seems to be a problem with cedega and not ryzom, cedega ususally dumps a lot of info if a win prog misbehaves.

one option you could try is adding "-use-pthreads no" to the cedega command line... from cedega 4.3 release notes:
Pthread Stack Size

"If available, Cedega attempts to make use of pthreads (POSIX threads), instead of LinuxThreads. Some distros which use pthreads only support a maximum stack size of 2MB. This can cause problems with some games which require larger stack sizes. Common symptoms of such problems include (but are not limited to) a crash to desktop when starting a game or when loading or saving a level. If this happens, you can work around it by starting Cedega with pthreads disabled."
"

[nofftz]

have you tried to run annything else than ryzom? notepad.exe for example, or just run cedega with no program to run...

That works. I've installed the game using Cedega, so it pretends to work.

However, I don't have tested another game yet.

based on the partial trace, it seems that cdega is getting its segmentation fault before it has even started properly.

this seems to be a problem with cedega and not ryzom, cedega ususally dumps a lot of info if a win prog misbehaves.

Well, it shows the title screen, but crashes before showing the main window (login screen).

one option you could try is adding "-use-pthreads no" to the cedega command line...

That doesn't work at all:

$ cedega -use-pthreads no client_ryzom_rd.exe
wine: exists lstat socket : No such file or directory