SEO

Hello all,

I just downloaded the latest nvidia driver to have 3D extension and
installed via YaSt.

Everything worked fine and desktop information stated the nvidia driver with
3D enabled is installed. The I installed xgl and compiz. Taht gave an error
message after kde start so I went back to normal Xorg server.
All went well. The I did some more etsts and shut down. Getting into the
system today I found that X stop with fatal error.

This is an extract from Xorg.0.log:

II) Loading extension NV-GLX
(II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
(II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
(==) NVIDIA(0): Backing store disabled
(==) NVIDIA(0): Silken mouse enabled
(**) Option "dpms"
(**) NVIDIA(0): DPMS enabled
(II) Loading extension NV-CONTROL
(==) RandR enabled
(II) Setting vga for screen 0.
(II) Initializing built-in extension MIT-SHM
(II) Initializing built-in extension XInputExtension
(II) Initializing built-in extension XTEST
(II) Initializing built-in extension XKEYBOARD
(II) Initializing built-in extension LBX
(II) Initializing built-in extension XC-APPGROUP
(II) Initializing built-in extension SECURITY
(II) Initializing built-in extension XINERAMA
(II) Initializing built-in extension XFIXES
(II) Initializing built-in extension XFree86-Bigfont
(II) Initializing built-in extension RENDER
(II) Initializing built-in extension RANDR
(II) Initializing built-in extension COMPOSITE
(II) Initializing built-in extension DAMAGE
(II) Initializing built-in extension XEVIE
(II) Initializing extension GLX
(**) Option "CoreKeyboard"
(**) Keyboard[0]: Core Keyboard
(**) Option "Protocol" "Standard"
(EE) "Standard" is not a valid keyboard protocol name
(EE) PreInit failed for input device "Keyboard[0]"
(II) UnloadModule: "kbd"
(**) Option "Protocol" "explorerps/2"
(EE) Mouse[1]: Unknown protocol "explorerps/2"
(EE) PreInit failed for input device "Mouse[1]"
(II) UnloadModule: "mouse"
(WW) No core pointer registered
(II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type:
Other)
No core keyboard

This is amazing because I did not change by hand anything in xorg.conf.

Also desktop information now shows nvida without 3D enabling.

Are thee some more startup/config files which interfere here?
Any ideas?

Thanks and Regards,

NoKo
--
"Careful with that VAX, Eugene!"

Norbert Kolvenbach wrote:
> Hello all,
>
> I just downloaded the latest nvidia driver to have 3D extension and
> installed via YaSt.
>
> Everything worked fine and desktop information stated the nvidia driver with
> 3D enabled is installed. The I installed xgl and compiz. Taht gave an error
> message after kde start so I went back to normal Xorg server.
> All went well. The I did some more etsts and shut down. Getting into the
> system today I found that X stop with fatal error.
>
> This is an extract from Xorg.0.log:
>
> II) Loading extension NV-GLX
> (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
> (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
> (==) NVIDIA(0): Backing store disabled
> (==) NVIDIA(0): Silken mouse enabled
> (**) Option "dpms"
> (**) NVIDIA(0): DPMS enabled
> (II) Loading extension NV-CONTROL
> (==) RandR enabled
> (II) Setting vga for screen 0.
> (II) Initializing built-in extension MIT-SHM
> (II) Initializing built-in extension XInputExtension
> (II) Initializing built-in extension XTEST
> (II) Initializing built-in extension XKEYBOARD
> (II) Initializing built-in extension LBX
> (II) Initializing built-in extension XC-APPGROUP
> (II) Initializing built-in extension SECURITY
> (II) Initializing built-in extension XINERAMA
> (II) Initializing built-in extension XFIXES
> (II) Initializing built-in extension XFree86-Bigfont
> (II) Initializing built-in extension RENDER
> (II) Initializing built-in extension RANDR
> (II) Initializing built-in extension COMPOSITE
> (II) Initializing built-in extension DAMAGE
> (II) Initializing built-in extension XEVIE
> (II) Initializing extension GLX
> (**) Option "CoreKeyboard"
> (**) Keyboard[0]: Core Keyboard
> (**) Option "Protocol" "Standard"
> (EE) "Standard" is not a valid keyboard protocol name
> (EE) PreInit failed for input device "Keyboard[0]"
> (II) UnloadModule: "kbd"
> (**) Option "Protocol" "explorerps/2"
> (EE) Mouse[1]: Unknown protocol "explorerps/2"
> (EE) PreInit failed for input device "Mouse[1]"
> (II) UnloadModule: "mouse"
> (WW) No core pointer registered
> (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type:
> Other)
> No core keyboard
>
> This is amazing because I did not change by hand anything in xorg.conf.
>
> Also desktop information now shows nvida without 3D enabling.
>
> Are thee some more startup/config files which interfere here?
> Any ideas?
>
> Thanks and Regards,
>
> NoKo
> --
> "Careful with that VAX, Eugene!"


It is interesting that I have almost same situation after I installed
ATI dispaly driver on my laptop!

All windows are attached to the top of the screen and there is no
regular menus or max, min and close (x) icon on top corners of the
windows. Also, I get a message saying that "No windows manager is
running".

amit.

Norbert Kolvenbach wrote:

> Hello all,
>
> I just downloaded the latest nvidia driver to have 3D extension and
> installed via YaSt.
>
> Everything worked fine and desktop information stated the nvidia driver
> with 3D enabled is installed. The I installed xgl and compiz. Taht gave an
> error message after kde start so I went back to normal Xorg server.
> All went well. The I did some more etsts and shut down. Getting into the
> system today I found that X stop with fatal error.
>
> This is an extract from Xorg.0.log:
>
> II) Loading extension NV-GLX
> (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
> (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
> (==) NVIDIA(0): Backing store disabled
> (==) NVIDIA(0): Silken mouse enabled
> (**) Option "dpms"
> (**) NVIDIA(0): DPMS enabled
> (II) Loading extension NV-CONTROL
> (==) RandR enabled
> (II) Setting vga for screen 0.
> (II) Initializing built-in extension MIT-SHM
> (II) Initializing built-in extension XInputExtension
> (II) Initializing built-in extension XTEST
> (II) Initializing built-in extension XKEYBOARD
> (II) Initializing built-in extension LBX
> (II) Initializing built-in extension XC-APPGROUP
> (II) Initializing built-in extension SECURITY
> (II) Initializing built-in extension XINERAMA
> (II) Initializing built-in extension XFIXES
> (II) Initializing built-in extension XFree86-Bigfont
> (II) Initializing built-in extension RENDER
> (II) Initializing built-in extension RANDR
> (II) Initializing built-in extension COMPOSITE
> (II) Initializing built-in extension DAMAGE
> (II) Initializing built-in extension XEVIE
> (II) Initializing extension GLX
> (**) Option "CoreKeyboard"
> (**) Keyboard[0]: Core Keyboard
> (**) Option "Protocol" "Standard"
> (EE) "Standard" is not a valid keyboard protocol name
> (EE) PreInit failed for input device "Keyboard[0]"
> (II) UnloadModule: "kbd"
> (**) Option "Protocol" "explorerps/2"
> (EE) Mouse[1]: Unknown protocol "explorerps/2"
> (EE) PreInit failed for input device "Mouse[1]"
> (II) UnloadModule: "mouse"
> (WW) No core pointer registered
> (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type:
> Other)
> No core keyboard
>
> This is amazing because I did not change by hand anything in xorg.conf.
>
> Also desktop information now shows nvida without 3D enabling.
>
> Are thee some more startup/config files which interfere here?
> Any ideas?
>
> Thanks and Regards,
>
> NoKo


OK - I now am a step further. As I said, it worked 2 days immediately after
installation. I thought about what might have changed. I guess I know now.
I updated sax2 via YaSt on Sunday. Went off the system and yesterday i
crashed.

I analysed the xorg.conf and found three dangerous lines there.

load "glx" which I need

Option Protocol "Standard" and
Option Protocol "exploreps/2"

Which caused the problem. Now I commented out the Load "glx"
and it worked again!

Then I took the commment out of the load directive, I changed "Standard" to
"standard" and "exploreps/2" to "ExplorePS/2" and guess what? X server
starts but the screen is a complete mess.

I then commented out "Load" directive again and all worked fine.

Soo - without "glx" the "Options" work with either small and/or big letters.
with "glx" only "standard" and "ExplorePS/2" work, but screen is white,
nothing to see, no cursor, some scrambled unstructured black lines.

What else could YaSt and sax2 mess up? - BTW: nvidia 3D cannot be switched
on.

sax2 -m 0:nvidia

will cause sax2 to write a new xorg.conf file and I am back on square one!

That's what I like with Linux, once you sorted out one problem (sound in my
case) you immediately are facing a new challenge! ;-))

NoKo


--
"Careful with that VAX, Eugene!"

Norbert Kolvenbach wrote:

> Hello all,
>
> I just downloaded the latest nvidia driver to have 3D extension and
> installed via YaSt.
>
> Everything worked fine and desktop information stated the nvidia driver
> with 3D enabled is installed. The I installed xgl and compiz. Taht gave an
> error message after kde start so I went back to normal Xorg server.
> All went well. The I did some more etsts and shut down. Getting into the
> system today I found that X stop with fatal error.
>
> This is an extract from Xorg.0.log:
>
> II) Loading extension NV-GLX
> (II) NVIDIA(0): NVIDIA 3D Acceleration Architecture Initialized
> (II) NVIDIA(0): Using the NVIDIA 2D acceleration architecture
> (==) NVIDIA(0): Backing store disabled
> (==) NVIDIA(0): Silken mouse enabled
> (**) Option "dpms"
> (**) NVIDIA(0): DPMS enabled
> (II) Loading extension NV-CONTROL
> (==) RandR enabled
> (II) Setting vga for screen 0.
> (II) Initializing built-in extension MIT-SHM
> (II) Initializing built-in extension XInputExtension
> (II) Initializing built-in extension XTEST
> (II) Initializing built-in extension XKEYBOARD
> (II) Initializing built-in extension LBX
> (II) Initializing built-in extension XC-APPGROUP
> (II) Initializing built-in extension SECURITY
> (II) Initializing built-in extension XINERAMA
> (II) Initializing built-in extension XFIXES
> (II) Initializing built-in extension XFree86-Bigfont
> (II) Initializing built-in extension RENDER
> (II) Initializing built-in extension RANDR
> (II) Initializing built-in extension COMPOSITE
> (II) Initializing built-in extension DAMAGE
> (II) Initializing built-in extension XEVIE
> (II) Initializing extension GLX
> (**) Option "CoreKeyboard"
> (**) Keyboard[0]: Core Keyboard
> (**) Option "Protocol" "Standard"
> (EE) "Standard" is not a valid keyboard protocol name
> (EE) PreInit failed for input device "Keyboard[0]"
> (II) UnloadModule: "kbd"
> (**) Option "Protocol" "explorerps/2"
> (EE) Mouse[1]: Unknown protocol "explorerps/2"
> (EE) PreInit failed for input device "Mouse[1]"
> (II) UnloadModule: "mouse"
> (WW) No core pointer registered
> (II) XINPUT: Adding extended input device "NVIDIA Event Handler" (type:
> Other)
> No core keyboard
>
> This is amazing because I did not change by hand anything in xorg.conf.
>
> Also desktop information now shows nvida without 3D enabling.
>
> Are thee some more startup/config files which interfere here?
> Any ideas?
>
> Thanks and Regards,
>
> NoKo


Noboddy experienced similar effects?

Noko
--
"Careful with that VAX, Eugene!"

Well finally I got it to work.

The Suse nvidia howto tells me to use
sax2 -m 0:nvidia
this seems to be root of problem.

I then used

sax2 -r -m 0:nvidia

The xorg.conf file looked exactly the same but now it works! Also the
howto does not mention to link symbolically /var/X11R6/bin/X
to /usr/X11R6/bin/Xgl.

Done this and 3D fires up! Next challenge will be to let this work to other
users also. If other users than me (i do not log in as root!) trie to
startx, the server complains about wron font paths (odd!).

So I have to find out, why it does not complain with me.

Cheers,

NoKo



--
"Careful with that VAX, Eugene!"