PDA

View Full Version : nvidia drivers w/ glx problem


Stinkmarder
03-25-03, 03:49 PM
Hi...

when I start the X server the screen content is ... well.. scrambled... or distorted...
One can guess that it wants to display the nvidia logo... *g*
(BTW it's not a issue of a too high screen refresh rate, my monitor's OSD tells me that the proper display mode and refresh rate is set.)
X doesn't crash thereby. It keeps running and I can switch between the text console and X with [Ctrl+]Alt+Fx (even I don't see anything) and type commands blindly.
I need to reboot my system to get back a working display. (terminating X with Ctrl+Alt+BS and starting X with a working configuration doesn't help.)

This is the only error in the log file:

(EE) NVIDIA(0): Failed to obtain a shared memory identifier.

If GLX is commented out in the config file, X starts normally. (even I can't use the text console anymore, but this seems to be a common issue :( ).
Also everything is fine if I am using the nv drivers.

I tried he following nvidia driver versions:
1.0-4191
1.0-3123
1-0-2960
and the following XFree86 versions:
4.0.2
4.2.1
4.3.0
without any success. Everytime the same problem. :(
I also played around with the AGP support without any success.


I'm using Debian sid, Kernel 2.4.18 with AGP support build into kernel.
Geforce 3, Athlon 1.4GHz, VIA ... chipset.

I attached my XF86Config-4 file even I don't think that there is anything wrong with it.

Ideas or comments of any kind are welcome...
Many thanks !!!

Joe

Stinkmarder
03-25-03, 04:04 PM
and the log file

merlin42
03-26-03, 01:48 PM
I am taking a guess that shared memory in general is not working.

Do you have tmpfs support in your kernel?
Have you mounted /dev/shm?

Taken from the help for CONFIG_TMPFS:

You should mount the file system somewhere to be able to use
POSIX shared memory. Adding the following line to /etc/fstab should
take care of things:

tmpfs /dev/shm tmpfs defaults 0 0

Remember to create the directory that you intend to mount tmpfs on
if necessary (/dev/shm is automagically created if you use devfs).


If it got left out please reconfigure/recompile your kernel and make sure to say yes to the Virtualmemory filesystem option under Filesystems.

Stinkmarder
03-26-03, 02:14 PM
I am taking a guess that shared memory in general is not working.
Do you know an easy way to check this ?

Do you have tmpfs support in your kernel?
Yes.

Have you mounted /dev/shm?

joke@ws-jf:~$ mount |grep tmpfs
tmpfs on /dev/shm type tmpfs (rw)
joke@ws-jf:~$


(/dev/shm is automagically created if you use devfs)
I remember that i had to create /dev/shm manually...
mkdir /dev/shm should be ok ?

Thanks so far...

Stinkmarder
04-03-03, 09:50 AM
*bump*
Forgot to post the solution to my problem... :)
All people who get that "Failed to obtain a shared memory identifier" error should check if Sys V IPC support is in the kernel. I forgot that in mine.
Shared memory won't work without it.
Now everything is working fine. Switching to a text console, too.