Page 21 of 37
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Mon Aug 21, 2006 7:19 am
by lardok
You have to compile the kernel yourself. It's not in the respository yet.
Follow the guide I posted above to do so.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Mon Aug 21, 2006 8:35 pm
by zyrom
gonesolo wrote:Well I went through the wine walkthrough (except I already have wine installed so I just went with no sound to see if it would work)
.
As long as it is a fairly resent Wine that should be ok ( the more resent the better ).
gonesolo wrote:
initially all was good - copied my windows installation to the wine install and it started ok - was able to select my character but as soon as I tried to start the game I got a box up with a load of "Thread?" errors (this may be wrong I'm posting from memory)
The exact error messages would help a lot.
gonesolo wrote:
I'm using Kubuntu 6.06 but I'm pretty sure my kernel is 2.6.15 should I be using the 17 kernel I've tried checking for updates with adept and apt-get but there are no updates to apply.
the 2.6.15 kernel is ok, you only need the 2.6.17 or later for the sound issue.
Make sure you get hold of the latest ATi Drivers, as i understand it they are suposed to be much better. and you absoloutly need to use OGL, the D3d support in wine is not up to par yet. But afaik there is flurry of activity going on in that area of wine so in a couple of version i expect it to work , if not great, then at least, passable.
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Fri Aug 25, 2006 8:38 am
by rabcaz
OOC :
Small update for Nvidia users. they have
released a new driver today.
I'll try it when I get home later today.
//Drakfot
//OOC
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Mon Sep 18, 2006 5:10 pm
by akicks
I get all the way up to my character loading before it crashes.
I'm running Suse 10.0x64 and followed the guide here.
Code: Select all
wine: Unhandled exception (thread 0009), starting debugger...
WineDbg starting on pid 0x8
Unhandled exception: page fault on read access to 0x0000001c in 32-bit code (0x55fcc215).
Register dump:
CS:0023 SS:002b DS:002b ES:002b FS:1007 GS:0063
EIP:55fcc215 ESP:55c07c44 EBP:55c07d18 EFLAGS:00010202( - 00 - -RI1)
EAX:00000000 EBX:55ff262c ECX:55c081d8 EDX:55937db0
ESI:00000000 EDI:00000000
Stack dump:
0x55c07c44: ffffffff 00000000 73200000 00000000
0x55c07c54: 00000000 00000000 00000000 00000000
0x55c07c64: 00000000 00000000 00000000 00000000
0x55c07c74: 00000000 00000000 00000000 00000000
0x55c07c84: 00000000 55c0e054 00000000 00000000
0x55c07c94: 00000000 00000000 00000000 00000000
0200: sel=1007 base=5556c000 limit=00001f97 32-bit rw-
Backtrace:
=>1 0x55fcc215 in msvcrt (+0xc215) (0x55c07d18)
2 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c07d3c)
3 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c080a4)
4 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c080ec)
5 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c081a8)
6 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c081c4)
7 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c085d0)
8 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c085f4)
9 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0895c)
10 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c089a4)
11 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c08a60)
12 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c08a7c)
13 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c08e88)
14 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c08eac)
15 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c09214)
16 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0925c)
17 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c09318)
18 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c09334)
19 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c09740)
20 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c09764)
21 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c09acc)
22 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c09b14)
23 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c09bd0)
24 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c09bec)
25 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c09ff8)
26 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0a01c)
27 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0a384)
28 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0a3cc)
29 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0a488)
30 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0a4a4)
31 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0a8b0)
32 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0a8d4)
33 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0ac3c)
34 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0ac84)
35 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0ad40)
36 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0ad5c)
37 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0b168)
38 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0b18c)
39 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0b4f4)
40 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0b53c)
41 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0b5f8)
42 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0b614)
43 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0ba20)
44 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0ba44)
45 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0bdac)
46 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0bdf4)
47 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0beb0)
48 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0becc)
49 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0c2d8)
50 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0c2fc)
51 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0c664)
52 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0c6ac)
53 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0c768)
54 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0c784)
55 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0cb94)
56 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0cbb8)
57 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0cf20)
58 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0cf68)
59 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0d024)
60 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0d040)
61 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0d450)
62 0x55fcc5ed __regs___CxxFrameHandler+0x3d in msvcrt (0x55c0d474)
63 0x5573fba6 __wine_call_from_32_regs+0xb6 in ntdll (0x55c0d7dc)
64 0x55fcb965 __CxxFrameHandler+0x5 in msvcrt (0x55c0d824)
65 0x5571349b __regs_RtlRaiseException+0x25b in ntdll (0x55c0d8e0)
66 0x5573515c DbgUserBreakPoint+0x180 in ntdll (0x55c0d8fc)
67 0x5573fc14 __wine_call_from_32_restore_regs+0x0 in ntdll (0x55c0dca0)
fixme :d bghelp:sffip_cb NIY on 'R:\code\ryzom\client_ryzom_rd.pdb'
68 0x005cdddd in client_ryzom_rd (+0x1cdddd) (0x62d2f2e0)
69 0x00000000 (0x011fd60c)
70 0x0064b4d0 in client_ryzom_rd (+0x24b4d0) (0x0076fa50)
71 0x00000038 (0xe8f18b56)
72 0x00000000 (0x00000000)
0x55fcc215: movl 0x1c(%eax),%edx
Modules:
Module Address Debug info Name (103 modules)
PE 0x00400000-01591000 Export client_ryzom_rd
PE 0x10000000-10007000 Deferred wwwfile
ELF 0x55555000-5556c000 Deferred ld-linux.so.2
ELF 0x55574000-5557f000 Deferred libgcc_s.so.1
ELF 0x55582000-5558b000 Deferred libsm.so.6
ELF 0x5558b000-55590000 Deferred libxxf86dga.so.1
ELF 0x55591000-555aa000 Deferred libwine.so.1
ELF 0x555ab000-555bd000 Deferred libpthread.so.0
ELF 0x555bd000-556dc000 Deferred libc.so.6
ELF 0x556dc000-556e0000 Deferred libdl.so.2
ELF 0x556e1000-5575d000 Export ntdll<elf>
\-PE 0x55700000-5575d000 \ ntdll
ELF 0x5575d000-55852000 Deferred libwine_unicode.so.1
ELF 0x55852000-55878000 Deferred libm.so.6
ELF 0x558ad000-558af000 Deferred libnvidia-tls.so.1
ELF 0x559c0000-55ad0000 Deferred kernel32<elf>
\-PE 0x559f0000-55ad0000 \ kernel32
ELF 0x55b03000-55b08000 Deferred libxxf86vm.so.1
ELF 0x55b0a000-55b0e000 Deferred libxrandr.so.2
ELF 0x55b0e000-55b10000 Deferred xlcutf8load.so.2
PE 0x55c10000-55c29000 Deferred wwwcore
ELF 0x55c29000-55c46000 Deferred wsock32<elf>
\-PE 0x55c30000-55c46000 \ wsock32
ELF 0x55c46000-55c71000 Deferred ws2_32<elf>
\-PE 0x55c50000-55c71000 \ ws2_32
ELF 0x55c71000-55da4000 Deferred user32<elf>
\-PE 0x55c90000-55da4000 \ user32
ELF 0x55da4000-55e57000 Deferred gdi32<elf>
\-PE 0x55dc0000-55e57000 \ gdi32
ELF 0x55e57000-55e78000 Deferred iphlpapi<elf>
\-PE 0x55e60000-55e78000 \ iphlpapi
ELF 0x55f56000-55f99000 Deferred advapi32<elf>
\-PE 0x55f70000-55f99000 \ advapi32
PE 0x55fa0000-55fa8000 Deferred wwwutils
ELF 0x55fa8000-5600d000 Export msvcrt<elf>
\-PE 0x55fc0000-5600d000 \ msvcrt
PE 0x56010000-56016000 Deferred wwwtrans
ELF 0x56016000-5601e000 Deferred libxrender.so.1
PE 0x56020000-56029000 Deferred wwwmime
PE 0x56030000-56037000 Deferred wwwcache
ELF 0x56037000-56040000 Deferred libxcursor.so.1
PE 0x56040000-56047000 Deferred wwwstream
PE 0x56050000-5605d000 Deferred wwwapp
PE 0x56060000-56073000 Deferred gnu_regex
ELF 0x56073000-5607e000 Deferred libnss_files.so.2
PE 0x56080000-5608e000 Deferred wwwhttp
PE 0x56090000-5609b000 Deferred wwwhtml
ELF 0x5609b000-5612c000 Deferred comdlg32<elf>
\-PE 0x560b0000-5612c000 \ comdlg32
ELF 0x5612c000-561f6000 Deferred shell32<elf>
\-PE 0x56150000-561f6000 \ shell32
ELF 0x561f6000-56255000 Deferred shlwapi<elf>
\-PE 0x56210000-56255000 \ shlwapi
ELF 0x56255000-562e3000 Deferred ole32<elf>
\-PE 0x56270000-562e3000 \ ole32
ELF 0x562e3000-5632e000 Deferred rpcrt4<elf>
\-PE 0x56300000-5632e000 \ rpcrt4
ELF 0x5632e000-563f2000 Deferred comctl32<elf>
\-PE 0x56340000-563f2000 \ comctl32
ELF 0x563f2000-5641e000 Deferred winspool.drv<elf>
\-PE 0x56400000-5641e000 \ winspool.drv
PE 0x56420000-564de000 Deferred stlport_vc645
ELF 0x564f0000-56571000 Deferred winmm<elf>
\-PE 0x56500000-56571000 \ winmm
ELF 0x56571000-5658b000 Deferred imagehlp<elf>
\-PE 0x56580000-5658b000 \ imagehlp
ELF 0x5658b000-565cb000 Deferred dbghelp<elf>
\-PE 0x56590000-565cb000 \ dbghelp
ELF 0x565cb000-565e1000 Deferred psapi<elf>
\-PE 0x565d0000-565e1000 \ psapi
ELF 0x565e1000-56600000 Deferred ximcp.so.2
ELF 0x56606000-56674000 Deferred libfreetype.so.6
ELF 0x56674000-56687000 Deferred libz.so.1
ELF 0x56687000-566b7000 Deferred libfontconfig.so.1
ELF 0x566b7000-566d7000 Deferred libexpat.so.0
ELF 0x566d7000-5675e000 Deferred winex11.drv<elf>
\-PE 0x566f0000-5675e000 \ winex11.drv
ELF 0x5675e000-56776000 Deferred libice.so.6
ELF 0x56776000-56784000 Deferred libxext.so.6
ELF 0x56784000-5687d000 Deferred libx11.so.6
ELF 0x5687d000-568fc000 Deferred libgl.so.1
ELF 0x568fc000-57065000 Deferred libglcore.so.1
ELF 0x570c0000-570de000 Deferred imm32<elf>
\-PE 0x570d0000-570de000 \ imm32
ELF 0x572e2000-572fb000 Deferred msacm.drv<elf>
\-PE 0x572f0000-572fb000 \ msacm.drv
ELF 0x57307000-57325000 Deferred libcups.so.2
ELF 0x57325000-57355000 Deferred libssl.so.0.9.7
ELF 0x5738a000-573ae000 Deferred msacm32<elf>
\-PE 0x57390000-573ae000 \ msacm32
ELF 0x57484000-5757e000 Deferred libcrypto.so.0.9.7
ELF 0x57770000-57785000 Deferred midimap<elf>
\-PE 0x57780000-57785000 \ midimap
PE 0x586d0000-587b8000 Deferred nel_drv_opengl_win_rd
ELF 0x587b8000-587cc000 Deferred dinput8<elf>
\-PE 0x587c0000-587cc000 \ dinput8
ELF 0x59160000-591fe000 Deferred opengl32<elf>
\-PE 0x591a0000-591fe000 \ opengl32
ELF 0x591fe000-5927d000 Deferred libglu.so.1
ELF 0x5a3bf000-5a3fd000 Deferred dinput<elf>
\-PE 0x5a3d0000-5a3fd000 \ dinput
PE 0x780c0000-78121000 Deferred msvcp60
ELF 0x7bf00000-7bf03000 Deferred <wine-loader>
Threads:
process tid prio (all id:s are in hex)
00000008 (D) Y:\Documents\Ryzom\client_ryzom_rd.exe
0000000b 0
00000009 0 <==
WineDbg terminated on pid 0x8
Anyone know what's going on here? What else can I try to stop crashing? Thanks
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Mon Sep 18, 2006 6:23 pm
by blaah
akicks wrote:Anyone know what's going on here? What else can I try to stop crashing? Thanks
one that you might try/check is if you really have msvcrt.dll in your wine installation (windows/system, windows/system32 or ryzom directory)
if i read dump correctly, wine own msvcrt is used.
not saying it helps with your problem as i can run with wine msvcrt just have lag spikes (and long loading times)
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Sep 19, 2006 7:25 am
by akicks
blaah wrote:one that you might try/check is if you really have msvcrt.dll in your wine installation (windows/system, windows/system32 or ryzom directory)
if i read dump correctly, wine own msvcrt is used.
not saying it helps with your problem as i can run with wine msvcrt just have lag spikes (and long loading times)
ok, changed to be using the windows msvcrt.dll, loading is quicker (much), and I actually get to run aroud for a few minutes
Ofcourse, I am crashing now after those few minutes. Will check I
really have sound turned off before asking for help.
Edit-
Whenever I enter a building (my apartment, guildhall) I get the ryzom crash box with the error message "Failed assertation Occured".
If I run around for a couple of minutes I crash. The last line from the wine dump says "Failed to reassign memory"
Any ideas?
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Tue Sep 19, 2006 4:03 pm
by zyrom
first, my general experience with crashes is that they are mostly caused by corrupt files, so the fist thing you could try is to get rid of the cache files, those you find in the data directory and are typically called rsfe002.juk.shards.nevrax.com.string_cache just delete them all they are recreated when needed. then you could rename the save folder, but be aware that you will loose your flags, stanzas macros etc, that why you whant to rename the directory so you can move the files back one by one.
Second. versions...
kernel 2.6.17 or better.
Wine: to me, 0.9.17 is the most stbale to date, even though 0.8.21 is out and
is stable, i find it a bit laggy, 18.19 and 20 i have had crashing on me once in
a while.
Nvida. latest there are 1.0.8774
Third, memory, the more the better, but try to keep it above a Gig, also check that you don't have a marginal memory stick, try to mix them around and or remove one.
Ryzom is hungry beast, and *will* task your system, when i get into problems i have a "dummy" setup has a clean X/desktop setup, meaining no desktop manager and just starting X and a xterm, you can get that by just running xinit...
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Thu Sep 21, 2006 10:43 pm
by jgmrazek
Has anybody installing Ryzom on Linux using Cedega had a problem with InstallShield?
Re: [FAQ] Ryzom in Linux (The Unofficial HOW-TO)
Posted: Sun Sep 24, 2006 3:38 pm
by zyrom
haven tested Cedega for almost a year, since the game will not run under it... see posts a bit higher up. so unless they have done some mayor work lately , youre better of with plain wine.
Re: Ryzom in Linux Unofficial how-to: ATI, Linux, and Hope
Posted: Tue Oct 24, 2006 12:58 pm
by ecobear
I was very excited about this game because it said that there was a linux client in the works and that it ran well in Cedega. I was leary about that since I have an ATI card, unfortunately, the fear turned about to be legitimate. I have searched Google Linux and all else beyond with no luck.
My problem is that I have Cedega and ATI card (which for the most part equates to a waste of money). Cedega claims its giving better ATI support, although as of version 5.2.6, I am still out in the cold. I have my fingers crossed for the next release.
My other is question is probably common. Is there a release date for the linux client? I was VERY excited when I saw the word Debian in the Q&A section and was very hopeful.
Hopefully this post might yield an answer one way or the other. I would really appreciated any feedback. For contact, I use Gmail, and I am ecobear on there as well. Emails are welcome. Thanks.