SHINODATT, I believe what you are experiencing was a bug in the older versions of compiz, use the current live ebuilds from the desktop effects overlay, your problems should go away_________________Billy DeVincentis

The tree has only the oldest 6 series versions, they had a bug that caused X to freeze because of certain karamba and gkrellm windows, I know because I reported the bug to the compiz developers and worked with them to get it straight.

run these commands to use the overlay and be sure to add /usr/portage/local/desktop-effects to your make.conf like so

The tree has only the oldest 6 series versions, they had a bug that caused X to freeze because of certain karamba and gkrellm windows, I know because I reported the bug to the compiz developers and worked with them to get it straight.

run these commands to use the overlay and be sure to add /usr/portage/local/desktop-effects to your make.conf like so

I just realized I made an absolutely moronic mistake; the video card config that was being pulled in in my xorg.conf file was not the config I was editing! I have three devices defined and was modifying the device section that was not associated with the device being called!!!!

Hello, i ma getting a few problems on my 64bit system, details in sig.

If playing ETQW the keyboard response becomes very slow, i have to hold key down for ages to get a response, often after leaving game the keyboard no longer works in X

When using gimp heal or clone tool the same thing can happen.

Leaving PC without using it for while can result in it not returning from monitor power saving, or does not even go into power saving, can also having issue where mouse and keyboard stop responding altogether?

These are the only things that otherwise spoil a nice stable system

I am not using compiz but am using Nvidia 8800 GTS xorg-server-1.3.0.0-r6

I just upgraded to a GeForce 8800 GTS, after my old 6800 GT died (a moth flew into the heatsink).

Before I upgraded, I was able to get the command line, with glitchy graphics even during the BIOS, but it would die as soon as I reached X (similar thing happened in Windows).

After the upgrade, I can still get the command line, but no amount of tinkering with my xorg.conf will give me X. I've tried using the nv driver, and disabling RenderAccel. Every time I try, it either kicks me out claiming there are no screens, or locks up, and I don't even get to see a glimpse of X before this happens. I've also tried booting with noapic, acpi=off, apic=off, pci=nommconf, and every combination thereof.

Eventually (after about 10 minutes or so, enough time to make and drink a cup of tea), I get back to the command line, with an invalid mem allocation error, and the nvrm Xid errors in dmesg.

I think the only real difference between my situation and other users who have posted, is that most of them at least get into X for a little while, but I never get a glimpse.

Just for comparison in other OSes, I tried an Ubuntu livecd, which gave me X, probably using the nv driver, but died when I tried to switch to the nvidia driver, and Windows behaves just fine, with the graphics card passing the nTune stress test, so I'm pretty sure the graphics card is still kicking.

Any advice? Have I missed anything obvious?

Cheers.

-- UPDATE --

In my general stupidity, I flashed my BIOS (I know it's generally not recommended doing that, but I'm reckless). As long as I have RenderAccel off, I can now start X, although xdm still refuses to start. This is definitely progress.

Last edited by spaceLem on Thu Jul 10, 2008 2:51 pm; edited 1 time in total

I don't know if this suggestion has been posted before since I never really follow this thread anymore. Anyways, for those having lockups and general weirdness and a nVidia card, you can try the suggestions found here:
http://us.download.nvidia.com/XFree86/Linux-x86/173.14.09/README/chapter-12.html
Scroll down to the AGP Rate section. They talk about patching the driver. A similar thing might be doable for PCI-E as well.

As a person who has suffered considerable trouble with these lockups and tried pretty much everything, before finally discovering the real cause to be something I never thought of.

It may be your power source failing gradually.

For me the freezes appeared after I had replaced my motherboard. I suspected everything from coincident software updates/recompiles to BIOS settings to the northbridge fan providing inadequate cooling. I got rid of my problems for several months by replacing the northbridge fan with a better-conducting (and passive) one, but now I see it worked only because it reduced my computer's power use by one active fan. And after a few months the lockups were back worse than ever.

My Antec power source had probably been failing since the beginning, but it had taken time and a chance to a new motherboard until the power level had decreased enough to cause problems. The final clue was that I started to experience problems that my motherboard manual were usually caused by overclocking too much... but I wasn't overclocking at all. My system has been 100% stable for over six months now with a new power source, so I can definitely say the power source is something you need to keep in mind.

I have some X lockups, too. I also assume that this is my power source's fault. I also have some other strange hardware problems. I'll check this out and report whether this was the reason.