I emerged my shining new system from a 1.4rc2 and emerged kde 3.1.1 Keramik is default, and the one i like best, but it kept freezing my machine. Mouse kept working, but keyboard input was lost (no ctrl-alt-bksp or ctrl-alt-del), and the screen freezed, usually when some screen refresh happened, e.g. when I opened a menu, moved the mouse, or maximized a window. Initially I emerged using CFLAGS="-O3 -pipe -fomit-frame-pointer -mcpu=athlon-xp -arch=athlon-xp", which are the 'Gentoo aproved', then I suspected i could be tha cause, the I re-emerged kde and xfree using just "-O2 -mcpu=athlon-xp -march=athlon-xp". but it kept crashing. I am currently using .net style, and it does NOT freeze. I emerged nvidia-kernel and nvidia-GLX, just to let you know. I suspect it is a keramik bug... My machine: Duron 1GHz 256 MB ddr nono-ECC 266mhz (224 + 32mb shared video) ASUS A7N 266-VM HD 40GB 7200 RPM
or maybe not. it just freezed with .net, but I used it for quite a long time. It ws the first freeze with .net. i am now using icewm, will not use kde apps and see if it freezes. then i'll switch back to kde and see what happens. maybe nvidia_GLX?
Created attachment 10454 [details] make.conf This is the current make.conf and was used to compile the system.
This happens to me too. It seems to occur almost 100% of the time when I am moving icons around on my desktop. When I move my icons around, after a minute or two, the icon I was currently dragging disappears and the system locks up but will return upon a hard reboot (power button). However, I've noticed that I am always able to move the mouse pointer around, and that the keyboard input isn't received (ctrl-alt-bkspace doesn't work and I can't switch virtual terminals) and the led's will always go out no matter what I've had them set on. Also, I cannot turn them back on once my system locks, I'm assuming this is because the computer isn't receiving the signal. I have changed the default icons to custom ones incase this makes a difference. This seems to only affect my user account, while my root account is fine. Another bit of info, the root account has the Noia-Warm-0.95 icon set installed, and none of the icons are changed from that set while the user account uses the default crystal icons with many of them changed through either the menu editor or by right clicking the desktop. I have attached my make.conf (before I submitted this) if you'd like to check it. Currently, I am running: 2.4.20-gento0-r2, gcc-3.2.2, glibc-3.2.1-r4, KDE-3.1.1, XFree-4.3.0-r1, mosfet-liquid-widgets-0.9.6_pre4, xft-2.0.1-r2, freetype-2.1.4, nvidia-1.0.4349, libpng-1.2.5-r4, and I don't know what else is relevant. If you need me to provide anymore information (files, etc) please let me know.
Hmm, I decided to give a try to the new nvidia drivers, and also inadvertedly upgraded my X to 4.3. n00b, still learning abouthis emerge stuff. Anyway, this solved things for me. never crashed again. Unfrtunately, can't tell if the problem vanished after the driver update only, or only after X update.
I am using the same versions of X and Nvidia drivers as you are, but the problem still persists on my machine. I don't think the emerge of X that you inadvertantly did was a solution to the problem, but maybe it cured it on your machine. I tried re-emerging both my Nvidia drivers and X, but the problem has not been fixed.
Has anyone taken a look at this yet? I can reproduce this bug 100% of the time and it results in my system being unuseable. I'm more than willing to post any additional info needed but if no interest is shown in getting more information soon, I'm going to have to toast my system and start fresh because I can't think of anything else that I could possibly try to re-emerge. I've re-emerged KDE to version 3.1.1a and the problem still exists!
are you using the Option "RenderAccel" "on" in your XF86Config? If so try to disable it. Otherwise, take a look of the nvidia documentation, to see if your motherboard chipset is known to have problems with nvidia-driver, keep us informed about result of tests
I just read about the RenderAccel problem with the Nvidia drivers, and I will try shutting it off when I get home on Monday. Also, I have already read the docs and I know that my chipset/motherboard is supported by the drivers and internal AGP driver as well. I am not using the linux AGP driver since Nvidia suggested that with my chipset/card/motherboard uses the Nvidia one. I will post once I see if the RenderAccel feature was causing the problems.
For now this seems to have solved the problem, although I could only do a few quick tests on it. I'll give my machine a more complete workout tonight when I have more time.
well while this is a known nvidia drivers bug, i close this report, if problems persist you can reopen it
