Though, I should be OK without X as long as I find out how to fix the problem. Just need to download a kernel, decompress, and get nvidia back
Off to try it now.
Thanks tpowa, saved the day once again!
I would be completely ecstatic (X works, 6106 is loaded, nvidia-settings works ), but when I just started X (or rather, KDE) Kwin reported a segmentation fault, and I lost the KDE windows! So, I couldn't click any apps, close them, nothing.
Anyway, hopefully that was just chance, everything seems to be fine after a reboot
Thanks again people,
Knew it was too good to be true.
Not quite everything is running smoothly. UT2004 seems to run well (mouse clicking was a little unresponsive, not sure if that's just my mouse though), but there's an extremely annoying bug whereby X restarts everytime I quit UT?????
Haven't tried any other OpenGL apps yet, I'll try AA and some others. Are there some logs I can check to see what happened before the restart?! I could try the 5336 drivers too, see if that solves the problem.
i have that X crash after rerunning nvidia-settings
i deleted the .nvidia-xxx-rc file in home
i don't touch nvidia-settings again (with this driver release ;-))
now it runs very smooth without any crash
Some people say some games do not work well with the new nvidia driver (including UT). Check the nvidia forums for more info (but that's not a fault of the nvidia installer or the package :-))
EDIT: I tried bzflag which is opengl game and it worked fine (no crashes so far). Nvidia says opengl was updated with some new functionality (check the readme for details). For now I haven't noticed any visual difference or any speed improvement. But as I said before I'm not a gamer ;-)
do you run the latest version of ut2004?
i run 3236 patch
OK tpowa, i'll give that a crack when I get home, hope it works. Nvidia-settings doesn't really seem to do anything all that useful anyway does it?
I'll have a look at the nvidia forums too about UT, hope it works OK :S
And yeh, I am running 3206-patched UT2004.
I'll try deleting that file, see if X stops crashing, and get back later.
The only thing I did was downloading a kernel from kernel.org
Set the linux symbolic link to the sources.
Downloaded the nvidia installer.
Executed the installer.
And next, next, next
I think nvidia is doing some nice things, lately.
Bugger, it's still not working.
I've deleted that file, but X keeps restarting. It also restarted when I
from UT2004 to change my alsamixer, then
back into grahical terminal.
No idea why it's happening, extremely annoying though. Don't think I have any strange configs that would cause this to happen.
Any useful logs I can post?
if it doesn't work try the old driver here is the PKGBUILD:
http://bbs.archlinux.org/viewtopic.php? … sc&start=0
and search nv forum
have you deleted your .nvidia-setting-rc in your home directory?
EDIT: OH I SEE YOU DELETED THE FILE :-(
You can also look in the README at /usr/share/doc/NVIDIA...
there are some hints to increase stability
Hmm well that's a bit of a bugger. Perhaps if I install from the package instead of the Nvidia binary... tho I guess that won't make too much difference.
Thanks for all the help anyway.
Btw correct, what do you mean by 'set the linux symbolic link to the sources'? You mean the link in /usr/src yeah?
Aren't there some links for the nvidia GL files somewhere? I remember I had a problem with that before, where the nvidia files weren't correctly linked, and so Mesa drivers were trying to be used.
Duno though, I'll keep playing about, see how deeply the prob goes.
Just for anyone else who might be having similar probs, the terminal switching problem seems to only occur when I switch back to UT2004 on terminal 7 after switching to another terminal. If I change when UT2004 is not running, I don't get the X server restart.
I'm off to peruse the nv forums a while.
Hmm there's another problem with this as well.
When I switch out of (or exit) UT2004, and then login again, I still get lots of ut2004-bin and kdeinit processes hogging my memory, so I can't re-run UT2004 (it's very jittery).
Here's the output from top:
Is this to do with the Nvidia drivers? I haven't been able to get onto the nv forums, nvnews doesn't seem to be responding at the moment.
Looks like I'll have to go back to the 5336s if I can't sort this out.
doesn't do anything, am I using the right command?
there must be somethingwrong
i have only one kdeinit
how you start kde?
startx or do you use kdm in rc.conf or by init 5 and inittab?
if killall doesn't work
try killall -9
Erm, well I have the kdm daemon loaded in rc.conf, I think that's what controls the whole logging in/out/reboot etc, right?
I also have runlevel 5 set in inittab - am I supposed to use both of these? I'll try runlevel 5 without kdm running, see if that changes anything.
If I remove kdm from rc.conf, I get twm window manager, which for me at least is a little cryptic.
I tried adding startkde to rc.local -- incidentally, is this the correct file? Which config file is used for global system startup, and which for individual user startup? I.e., when logging into KDE? I'll go and have a look for the details myself, but if anyone knows offhand, great
Not sure yet about going to runlevel 3 and then startx-ing. I know I'll have to add startkde to some startx config file too, I'll go and find that out too.
if you use kdm in rc.conf
i think there is no need of runlevel 5
what happens if you use startx to start kde?
your /home/user/.xinitrc file should look like this for kde:
rc.local is not the right file for this.
# Executed by startx (run your window manager from here)
# exec xfwm4
# exec icewm
# exec blackbox
# exec fluxbox
if it works with normal startx
try using init 3 and kdm in rc.conf
Yeah I'm using startx now, bit of a pain, but only slightly. I can now switch between terminals with no problems at all (tho I haven't tried switching out of Ut2004 - this shouldn't be a problem anyway, I've fixed my alsamixer problem, heh).
Looks like it should be running OK now. Thanks for all the help from everyone
Take it easy,