You are not logged in.
Pages: 1
Hello!
This happens since the upgrade from nvidia 1.0.178 to the latest version, what i've now. I only use current, extra and community repos.
This is the situation:
1- Starting the PC, Xorg with 'nv' driver, "startx" and all goes fine
2- Starting the PC, Xorg with 'nvidia' driver, "startx" and KDE can't start. It freezes during the boot up (of KDE) and nothing is seen, nor letters, nor graphics... only one thing: it seems tant want to draw the "rectangle" that usually appears, but it only can a bit of it and the whole PC deads.
3- Starting the PC, Xorg with 'nvidia' driver, "X" and the X server starts fine (well, only the black background, and mouse pointer). Shutdown the X server with "Ctrl+Alt+Supr", type "startx" and in a moment i'm inside KDE
I'm really lost. Any help?
thanks
Dienadel
Offline
Hi again, well, i've been doing a few tests with the nvidia driver. Also, i've installed windowmaker to test the response.
The Xorg (only X, without window manager) server always and, in every situation goes fine.
The conflict appears a few moments after the desktop inits (the X server always loads ok). In KDE as said in previous post, and in wmaker after all the desktop is completed.
In wmaker, the background and the "applets" appears, and the mouse was ok, it moves (in KDE too), but, the buttons seems not to work.
In both cases, the PC is completetly freezed (nor "bloq num", nor "bloq mayus" work...) after the crash.
These crashes, only happen if i start the window manager after turn on the PC. If i turn on it, start only X, shutdown it, and start the windowmanager, no error appears.
The "lsmod | grep nvidia" is always the same in every situation, before and after entering X, windomanager, the Xorg.log doesn't say errors...
I don't know where to take a look, whose is the crash, what to try next... :-(
Offline
Hello,
As the nivida module always started, i supossed that the error was in the options of X, particularly with composite, render... but i didn't know what was the correct "combination".
Reading the nvidia manual didin't solved it, but in this howto of ubuntu, i find the solution
http://doc.gwos.org/index.php/Latest_Nvidia_Dapper
I don't know if this is the best option or not, but, at least, i have again 3D acceleration, and, the most important thing, i can now use google earth. This is what i use now:
-------------------------------
Section "Device"
Option "NvAGP" "0"
Option "RenderAccel" "Off"
Option "IgnoreDisplayDevices" "DFP,TV"
Option "NoRenderExtension" "Off"
Option "AllowGLXWithComposite" "True"
EndSection
Section "Extensions"
Option "Composite" "Enable"
Option "RENDER" "Enable"
Option "DAMAGE" "Enable"
EndSection
---------------------------------
The only error that appears in xorg.log.0 is:
(WW) NVIDIA(0): No size information available in CRT-0's EDID; cannot compute
(WW) NVIDIA(0): DPI from EDID.
It isn't important and i'll try to resolve it later.
By the way, i'd like to comment a thing.
In the "dark" days with no 3D aceleration, i desinstalled nvidia, and was using mesa, , and i noticed that nvidia package overwrites the glx "things" of mesa. So, although mesa is installed you don't hace glx extensions. So mesa must be reinstalled.
Perhaps, it'd be nice that during the nvidia package is installed a note saying that nvidia overwrites "mesa glx", so, if you desinstall nvidia, you'd reinstall mesa again.
Bye
dienadel
Offline
Pages: 1