Rechercher | Connexion Forums | Nouveaux posts | Ces dernières 24h

Entraide GNU/Linux
uiWebPrevious1uiWebNext

#1 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
Hi, I am running Arch Linux x64 with a Nvidia 8600GT card using the nouveau drivers. I downloaded Ryzom and installed it to a folder in my home directory. I ran the updater from the command line then tried to run the client the same way. After an few seconds the terminal spits out "Segmentation fault" and nothing happens. After reading around I noticed someone using Slackware x64 had the same problem and it was because they forgot to install something. I am wondering if I am having a similar problem. Can anyone help me troubleshoot this problem because I'm stumped at this point?

I have also been trying out the proprietary Nvidia drives, for this and other games. The client still didn't work. Something about glib error. I don't remember exactly.

log.log is around 700 lines, so it hasn't been much use to me either.

Dernière édition par Paintchip(arispotle) (il y a 1 décénie).

#2 Ajouté par Danto(arispotle) il y a 1 décénie [en] 

{translate}
you need to enable the lib32 repository in your /etc/pacman.conf

then do: pacman -Sy

then, install lib32-nvidia-utils (you can also use nouveau driver, but the game it's quite slow) and a bunch of other lib32-xxxx dependencies (lib32-glibc, et al) although from now on the game would complain about missing libraries and you need to just do pacman -S lib32-[library]

#3 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
I would prefer to use the nouveau driver unless it's going to really hurt game play. I like the KMS that nouveau offers. Also, do you mean the multilib? I believe that's where pacman gets 32 bit binaries from for x64 systems. If so I already have it enabled and synced. With the nouveau driver the only error the terminal gives me is "segmentation fault." So I don't know which lib32 dependencies I am missing, if any. Is there a list somewhere so that I can check to make sure that I have all of the dependencies?

Additional: I loaded up the Nvidia driver and my error is actually "ERR f55cb700 driver_opengl_window.cpp 1068 setDisplay <Unknown> : glXChooseVisual() failed"

Also says, "NeL3D: OpenGL isn't initialized"

I think I may have a problem in my xorg.conf or xorg.conf.d. I don't know why else it would be having a problem. After looking on the net someone else didn't have a glx extention, but when I checked I did.

Here is the post http://dev.ryzom.com/boards/18/topics/5605

I would still prefer to get it working with nouveau.

Dernière édition par Paintchip(arispotle) (il y a 1 décénie).

#4 Ajouté par Danto(arispotle) il y a 1 décénie [en] 

{translate}
check this: http://dev.ryzom.com/boards/18/topics/3748

I'm agreed with you in how useful KMS is for working and daily use (and for its FLOSS background), but for ryzom nouveau driver isn't a good choice (for me): although it works, it is slow and almost unplayable (GF 8400 GS card on a core2duo 1.6 GHz Inspiron 1420)

Dernière édition par Danto(arispotle) (il y a 1 décénie). | Raison: creating a link

#5 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
Thank you very much for the suggestion and continued support. I was excited when I saw that I didn't have the lib32 of xrandr and dc++5; however, it still isn't working for me. Perhaps I am still missing some 32bit libs? An official dependency list would be great. We have pretty similar hardware. I am on an Inspiron 1720 with a core2duo 2.0 GHz :D

#6 Ajouté par Karu il y a 1 décénie [en] 

{translate}
Paintchip
Thank you very much for the suggestion and continued support. I was excited when I saw that I didn't have the lib32 of xrandr and dc++5; however, it still isn't working for me. Perhaps I am still missing some 32bit libs? An official dependency list would be great. We have pretty similar hardware. I am on an Inspiron 1720 with a core2duo 2.0 GHz :D

you can check which libraries are needed and used by running 'ldd ryzom_client' from terminal.

to see where segfault occurs, you need to run 'gdb ./ryzom_client' and then 'bt' after it has crashed

---

Hello!

#7 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
Thanks for the advice Karu. Unfortunately I still can't get it to work. I ran ldd on ryzom client, but didn't turn up anything that I don't already have installed(I think). I checked for all of them with pacman and google. So maybe I just don't have something configured right?

Also, I ran gdb ./ryzom_client and got "Reading symbols from /home/paintchip/ryzom/ryzom_client...(no debugging symbols found)...done."

bt resulted in it saying "No stack."

Any more suggestions? I feel like we are narrowing it down. Thanks guys.

#8 Ajouté par Karu il y a 1 décénie [en] 

{translate}
Paintchip
bt resulted in it saying "No stack.".
ohh sorry. you need to run it with 'r' command first.

---

Hello!

#9 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
Alright, this is what I got after the r command

Starting program: /home/rpaintchip/ryzom/ryzom_client
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/libthread_db.so.1".
[New Thread 0xf7a8bb40 (LWP 2396)]
[New Thread 0xf5fa2b40 (LWP 2400)]
[New Thread 0xf57a1b40 (LWP 2401)]

Program received signal SIGSEGV, Segmentation fault.
0xf4f22f5e in ?? ()
(gdb) bt
#0 0xf4f22f5e in ?? ()
#1 0xf4f638db in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)


When I ran it again I got

Program received signal SIGSEGV, Segmentation fault.
0xf4f22f5e in ?? ()
(gdb) bt
#0 0xf4f22f5e in ?? ()
#1 0x54f638db in ?? ()
#2 0x100b94b7 in ?? ()
#3 0x8cb12514 in ?? ()
#4 0x000b94af in ?? ()
#5 0x74000000 in ?? ()
#6 0x44000000 in ?? ()
#7 0xe0000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb)

I'm not sure how to use the output of this command. I'm not much of a programmer (just a little perl). Is there anyway I can use the numbers given to find a spot in the code where the problem is occurring? Thanks again.

#10 Ajouté par Karu il y a 1 décénie [en] 

{translate}
Paintchip
I'm not sure how to use the output of this command. I'm not much of a programmer (just a little perl). Is there anyway I can use the numbers given to find a spot in the code where the problem is occurring? Thanks again.
I was hoping it shows bit more info, but it's probably in OpenGL code.

I installed ArchLinux myself for testing.

Got ryzom working with 'nvidia nvidia-utils lib32-nvidia-utils' packages
It probably fails in glXChooseVisual(), because you probably still have lib32-libgl installed.

Dernière édition par Karu (il y a 1 décénie). | Raison: typo

---

Hello!

#11 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
i do still have libgl installed because it is required by the nouveau driver. when i tried out the nvidia driver i had to remove it because it conflicts with nvidia-utils. i still couldn't get the client to start. how did you install it? i just unpacked the game into a folder in my home dir. could libgl be having trouble resizing my screen because of a setting somewhere? sorry about the lack of capitalization, i'm typing from a phone.

#12 Ajouté par Karu il y a 1 décénie [en] 

{translate}
Paintchip
i do still have libgl installed because it is required by the nouveau driver. when i tried out the nvidia driver i had to remove it because it conflicts with nvidia-utils.
if you installing nvidia-utils, you replacing libgl for 64bit side. Because ryzom client is 32bit, you also meed to install lib32-nvidia-utils which will replace libgl for 32bit side.

I was not able to get ryzom working with nouveau driver. It kept segfault'ing.

---

Hello!

#13 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
I should have specified that I exchanged both libgl and lib32-libgl for nvidia-utils and lib32-nvidia-utils. I still have the same problem. I even tried re-installing after I installed the nvidia driver and utils.

Also, here is the output of gdb and bt with the nvidia driver

Program received signal SIGABRT, Aborted.
0xf7fdb430 in __kernel_vsyscall ()
(gdb) bt
#0 0xf7fdb430 in __kernel_vsyscall ()
#1 0xf7ad939f in raise () from /usr/lib32/libc.so.6
#2 0xf7adad25 in abort () from /usr/lib32/libc.so.6
#3 0x08eb26f6 in NLMISC::nlFatalError(char const*, ...) ()
#4 0x09a1a8c3 in NL3D::CDriverGL::setDisplay(int, NL3D::GfxMode const&, bool, bool) ()
#5 0x090684af in NL3D::CDriverUser::setDisplay(int, NL3D::UDriver::CMode const&, bool, bool) ()
#6 0x09068a9a in NL3D::CDriverUser::setDisplay(NL3D::UDriver::CMode const&, bool, bool) ()
#7 0x08701ba2 in prelogInit() ()
#8 0x086f7855 in main ()

Dernière édition par Paintchip(arispotle) (il y a 1 décénie).

#14 Ajouté par Paintchip(arispotle) il y a 1 décénie [en] 

{translate}
Great news, I figured out the user error! I got the game working with the Nvidia driver, but still haven't figured out what was wrong with the nouveau driver. I will explain how I got it so anyone with the same problem can just read this.

The problem I was having was that the Nvidia driver was using the nouveau settings in /etc/X11/xorg.conf.d instead of the settings in /etc/X11/xorg.conf, which is created by running the nvidia-xconfig command. To fix this I just created a "save" directory in /etc/X11/xorg.conf.d and put 10-monitor.conf and 20-nouveau.conf in there. That way x.org didn't read the settings in 10-monitor.conf and 20-nouveau.conf and use them in place of the ones in xorg.conf. I think I just needed to move 10-moniter.conf, but I moved both just to be sure. Once it was using the correct settings the game ran flawlessly, although my default kebindings were different than my window's ones :D Be sure not to get rid of xorg.conf.d because it handles other settings, like keyboard input and touchpad settings. Messing with other files might cause your keyboard and touchpad not to work once X starts. If I figure out how to get Nouveau to work I will post that as well. Thanks for all of the help guys.

#15 Ajouté par Danto(arispotle) il y a 1 décénie [en] 

{translate}
it's nice to know you're now able to play ;)
good luck
uiWebPrevious1uiWebNext
  
Last visit jeudi 30 Janvier 03:22:08 UTC
P_:G_:PLAYER

powered by ryzom-api