| View previous topic :: View next topic |
| Author |
Message |
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
 Posted: Fri Jul 08, 2011 4:08 pm Post subject: nVidia card and X freeze [solved] |
 |
|
I recently did a system-wide update (emerge -e system && emerge -e world) that included a --sync update as well. Included with this update was KDE version to 4.6.2. I saw the kde4.6 migration guide and followed that, including the removal of hal (which, for the aforementioned update I had to remove in lieu of upower) and some USE flag updates. This precipitated another update, although I only did an `emerge world -uND`. Prior to this last update, however, I discovered that when my computer turned on, and kdm was loaded, after a moment or two the screen would flicker once and I would notice graphical distortion throughout the screen (small, flickering clusters of pixels at seemingly random parts of the screen). The fonts are visible, but seem to change color with every few letters I type. Still, I am able to use my mouse and keyboard and enter my username and password.
At this point things become problematic. If the system loads (which it only does about 75% of the time, the other 25% it hangs in the (usually hardware) loading part of the 'kde load animation') it will SLOWLY load into KDE, my mouse will become more and more twitchy (acting as if the system is under heavy load) and only parts of KDE seem to actually load, before everything comes to a grinding halt and no key/mouse/other input occurs nor is anything else loaded, it just sits there.
It was at this point that I discovered the 4.4-4.6 migration guide, which I followed to ensure that wasn't the issue (after following it, I still have the same problem) and I also checked to make sure my kernel was alright (which it seems to be, but with kernels I can never be too sure) and that my graphics drivers were okay (I have an nvidia gForce 7600GS).
Checking the logs I found the following:
| grep -e EE -e WW /var/log/Xorg.0.log: | [ 386.424] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi".
[ 386.428] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi".
[ 386.428] (WW) The directory "/usr/share/fonts/TTF/" does not exist.
[ 386.428] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 386.428] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
[ 386.428] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 386.428] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 387.907] (II) Loading extension MIT-SCREEN-SAVER
[ 387.971] (WW) Warning, couldn't open module dri
[ 387.971] (EE) Failed to load module "dri" (module does not exist, 0)
[ 387.971] (WW) Warning, couldn't open module dri2
[ 387.971] (EE) Failed to load module "dri2" (module does not exist, 0)
[ 389.818] (WW) NVIDIA(0): Option "PixmapCacheSize" is not used
[ 389.818] (WW) Warning, couldn't open module dri2
[ 389.818] (EE) NVIDIA: Failed to load module "dri2" (module does not exist, 0)
[ 390.518] (WW) Mouse1: ignoring absolute axes.
[ 390.626] (WW) Logitech USB Receiver: device file is duplicate. Ignoring.
[ 390.634] (EE) PreInit returned 8 for "Logitech USB Receiver"
[ 390.642] (WW) Logitech USB Receiver: device file is duplicate. Ignoring.
[ 390.650] (EE) PreInit returned 8 for "Logitech USB Receiver"
[ 411.755] (EE) NVIDIA(0): Error recovery failed.
[ 411.755] (EE) NVIDIA(0): *** Aborting ***
[ 411.862] (WW) NVIDIA(0): The NVIDIA X driver has encountered too many errors. Falling
[ 411.862] (WW) NVIDIA(0): back to write-back cached memory.
[ 411.990] (EE) NVIDIA(0): Error recovery failed.
[ 411.990] (EE) NVIDIA(0): *** Aborting ***
[ 412.185] (EE) NVIDIA(0): Error recovery failed.
[ 412.186] (EE) NVIDIA(0): *** Aborting *** |
| cat /var/log/kdm: |
klauncher(2535) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2529)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected" |
consolekit, policykit, and dbus are all started at boot, and hal has been removed from the startup scripts as well as from the computer (including -hal USE flag in the most recent system update). Here is a more complete list:
| rc-update show: | acpid | default
alsasound | default
bootmisc | boot
consolefont | boot
consolekit | default
cupsd | default
dbus | default
devfs | sysinit
device-mapper | boot
dmcrypt | boot
dmesg | sysinit
fsck | boot
hddtemp | default
hostname | boot
hwclock | boot
keymaps | boot
killprocs | shutdown
local | default nonetwork
localmount | boot
lvm | boot
modules | boot
mount-ro | shutdown
mtab | boot
mysql | default
net.eth0 | default
net.lo | boot
netmount | default
ntp-client | default
procfs | boot
root | boot
savecache | shutdown
sshd | default
swap | boot
sysctl | boot
sysstat | default
termencoding | boot
udev | sysinit
udev-postmount | default
urandom | boot
xinetd | default |
I've found that if I don't log in to anything graphically (ie: I don't start xdm at boot) then the computer works just fine. If I stay in KDM without logging in, the graphical glitches I described earlier occur, but the computer doesn't necessarily freeze. From the error messages and some vague notions I gathered on google (I couldn't find someone with this exact problem - or they were otherwise helped by an nvidia upgrade, which did not work for me) seem to indicate either an issue with my nvidia driver (currently version 275.09.07) or with part of the KDE installation itself (ie: interaction between dbus/hal/etc...)
Last edited by alienjon on Tue Jul 26, 2011 1:52 am; edited 2 times in total |
|
| Back to top |
|
 |
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Fri Jul 08, 2011 7:13 pm Post subject: |
|
|
Hi alienjon,
Have you experienced these problems with other nvidia-driver versions? Actually, the current "stable" version of the nvidia-drives is 270.41.06.
These are the drawbacks from running things in the blinding edge. Take care.
ferreirafm |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Sat Jul 09, 2011 3:22 am Post subject: |
|
|
ferreirafm: Thanks for the reply! I have not had this problem with previous nvidia-drivers versions, but now that I'm experiencing it, all driver versions in portage between nvidia-drivers-173.14.30 and the masked latest (nvidia-drivers-275.09.07) are resulting in this weird behavior. Also, in checking the kdm log file in the most recent boot, I discovered the following:
| Code: |
klauncher(2535) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2529)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
klauncher(2540) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
kdmgreet(2534)/kdecore (K*TimeZone*): KSystemTimeZones: ktimezoned initialize() D-Bus call failed: "Not connected to D-Bus server"
[mi] EQ overflowing. The server is probably stuck in an infinite loop.
Backtrace:
0: /usr/bin/X (xorg_backtrace+0x28) [0x4a00c8]
1: /usr/bin/X (mieqEnqueue+0x203) [0x49fa73]
2: /usr/bin/X (xf86PostMotionEventM+0x96) [0x47ce16]
3: /usr/bin/X (xf86PostMotionEventP+0x3c) [0x47cf0c]
4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fb63b42f000+0x5294) [0x7fb63b434294]
5: /usr/bin/X (0x400000+0x6be97) [0x46be97]
6: /usr/bin/X (0x400000+0x118b96) [0x518b96]
7: /lib64/libpthread.so.0 (0x7fb63f87f000+0xf2f0) [0x7fb63f88e2f0]
8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (_nv001669X+0x83) [0x7fb63b698303] |
Could this be an issue with X?
**update**
I ssh'd into my desktop and started up xdm to see if anything is going on behind the scenes that I wasn't seeing before. I was able to check dmesg and top before the computer locked up. First off, this is what dmesg gave to me. Mostly gibberish to me, but maybe someone else can make sense of it?
| Code: |
[ 1315.423652] NVRM: Xid (0000:05:00): 13, 0000 e0014200 00000062 00000188 0001a3db 00000002
[ 1315.474838] NVRM: Xid (0000:05:00): 2, CCMDs 00000000 00000057 00000300 00000003 0000001c
[ 1315.508329] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000005 M 00000198 Data e0014200
[ 1315.529184] NVRM: Xid (0000:05:00): 2, CCMDs 00000000 00000057 00000300 00000003 0000001c
[ 1315.541928] NVRM: Xid (0000:05:00): 7, Ch 00000000 M 000007f4 D 0012aa04 intr 00010000
[ 1315.555387] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000004 M 00000300 Data 81840f00
[ 1315.569428] NVRM: Xid (0000:05:00): 7, Ch 00000000 M 00000300 D 81840f00 intr 00010000
[ 1315.599834] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000003 M 0000018c Data e0014400
[ 1326.244065] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context |
Secondly, I ran top and found that X is, indeed, using 100% of the processor (it's definitely in an endless loop somewhere). That's all I was able to do before the system slowed down enough that I had to hard-reboot :-/ |
|
| Back to top |
|
|
artbody
Guru
Joined: 15 Sep 2006
Posts: 494
Location: LB
|
| Posted: Sun Jul 10, 2011 5:16 pm Post subject: |
|
|
perhaps this Errormessage has the same reason
xterm :
| Code: | # VirtualBox
klauncher(31008) kdemain: No DBUS session-bus found. Check if you have started the DBUS server.
kdeinit4: Communication error with launcher. Exiting!
Segmentation fault
|
that happens everytime when i'll join some Files with the VirtualBox -> Filemanager Button
dmesg:
| Code: | vboxdrv: Found 2 processor cores.
VBoxDrv: dbg - g_abExecMemory=ffffffffa0fa42e0
vboxdrv: fAsync=1 offMin=0x160172 offMax=0x160172
vboxdrv: TSC mode is 'asynchronous', kernel timer mode is 'normal'.
vboxdrv: Successfully loaded version 4.0.10 (interface 0x00180000).
VirtualBox[25175]: segfault at 0 ip 00007fa0bf9c3cd2 sp 00007fff407e1060 error 4 in libkio.so.5.6.0[7fa0bf7d1000+2b5000]
VirtualBox[25369]: segfault at 0 ip 00007f10b36c5cd2 sp 00007fff4fdcc850 error 4 in libkio.so.5.6.0[7f10b34d3000+2b5000]
VirtualBox[27309]: segfault at 0 ip 00007f209e992cd2 sp 00007fff152a9f10 error 4 in libkio.so.5.6.0[7f209e7a0000+2b5000]
ISO 9660 Extensions: Microsoft Joliet Level 3
ISOFS: changing to secondary root
VirtualBox[27969]: segfault at 0 ip 00007f424c4abcd2 sp 00007fff967dd910 error 4 in libkio.so.5.6.0[7f424c2b9000+2b5000]
VirtualBox[29007]: segfault at 0 ip 00007faeaa01d8b3 sp 00007fffca0c9100 error 4 in libkio.so.5.6.0[7faea9e27000+2b5000]
|
special note:
WM = enlightenment
so the system didn't freeze
_________________
Never give up
WM : E16 the true enlightenment
achim |
|
| Back to top |
|
|
artbody
Guru
Joined: 15 Sep 2006
Posts: 494
Location: LB
|
| Posted: Sun Jul 10, 2011 5:32 pm Post subject: |
|
|
/usr/bin/qdbusviewer
| Code: | Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
|
_________________
Never give up
WM : E16 the true enlightenment
achim |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Mon Jul 11, 2011 3:14 pm Post subject: |
|
|
Hi alienjon,
So X is you problem. Double check your xorg.conf and xorg.conf.d files and if you eselect opengl nvidia. After a full upgrade, I have experienced a black flicker screen when starting KDE. In my previous kde version I had composite effects set based on openggl, however, my opengl was set to X11. You can also try to rename your .kde4 directory and start a fresh kde configuration to see if the problem persist.
G'Luck
Last edited by ferreirafm on Tue Jul 19, 2011 7:33 pm; edited 1 time in total |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Mon Jul 11, 2011 3:50 pm Post subject: |
|
|
| Resetting ~/.kde4/ didn't work for me. It occurred to me as I was testing it, though, that as my graphical glitch occurs before I even login, it would be a system-wide configuration if anything (etc-update is up to date too). Here's my current xorg.conf (sans all comments) |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Mon Jul 11, 2011 3:57 pm Post subject: |
|
|
alienjon,
Comment lines 4 and 5 from you xorg.conf. Could you post your Xorg.0.log please? and also the results from:
| Code: | | qlist -IC x11-drivers/ |
It seems you hasn't a pure xorg.conf.d configuration. What do you have your /etc/X11/xorg.conf.d/10-evdev.conf??
Last edited by ferreirafm on Wed Jul 13, 2011 12:49 pm; edited 2 times in total |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Mon Jul 11, 2011 4:14 pm Post subject: |
|
|
| Sure thing! The parts that I thought were interesting are in the first post (all the errors), but for the full, current logs check here for Xorg.0.log, kdm.log, and xdm.log. |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Mon Jul 11, 2011 4:25 pm Post subject: |
|
|
Your mouse and keyboard drivers are right. Comment lines 4 and 5 and restart.
What do you have in your /usr/share/X11/oxorg.conf.d/10-evdev.conf?
Last edited by ferreirafm on Tue Jul 19, 2011 7:34 pm; edited 1 time in total |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Mon Jul 11, 2011 4:54 pm Post subject: |
|
|
| ferreirafm wrote: | | Uncomment lines 4 and 5 and restart. |
In my xorg.conf? I'm sorry, I'm not quite sure what you're referring to. I only posted uncommented lines and lines 4 and 5 in my actual xorg.conf is copyright information. Also:
| qlist -IC x11-drivers: | x11-drivers/nvidia-drivers
x11-drivers/xf86-input-evdev
x11-drivers/xf86-input-joystick
x11-drivers/xf86-input-keyboard
x11-drivers/xf86-input-mouse
x11-drivers/xf86-video-fbdev |
<ignore>As for xorg.conf.d, I don't have this this directory on my system (I never created it and I guess it wasn't automatically generated by xorg-server at any point). I just discovered the xorg-server 1.8 upgrade guide and made a few changes to my xorg.conf regarding my mouse and keyboard (changing them to InputClass instead of InputDevice). Would running nvidia-xconfig generate this structure for me, or is that now deprecated too?</ignore>
** Update **
Sorry, two steps back here. Apparently the xorg.conf.d isn't where I had thought it was. I do have it and the only file in that directory is the one you asked about. Here's the contents:
| Code: | #
# Catch-all evdev loader for udev-based systems
# We don't simply match on any device since that also adds accelerometers
# and other devices that we don't really want to use. The list below
# matches everything but joysticks.
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchpad catchall"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev tablet catchall"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev touchscreen catchall"
MatchIsTouchscreen "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection |
So does that mean you wanted me to comment the lines indicating CoreKeyboard and CorePointer (should I also remove the mouse/keyboard InputDevice sections as well?) I tried doing this and restarting, but I still get the same thing as before. Graphical oddities leading up to and including freezing the machine. |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Mon Jul 11, 2011 6:06 pm Post subject: |
|
|
alienjon,
| Quote: | | o does that mean you wanted me to comment the lines indicating CoreKeyboard and CorePointer (should I also remove the mouse/keyboard InputDevice sections as well?) |
As in my previous post I was refering to the lines 4 and 5 of your xorg.conf file. Your 10-evdev.conf is fine. According to the official gentoo xorg-server-1.10 migration guide "Xorg no longer does autodetect devices using xf86-input-keyboard and xf86-input-mouse". Remove xf86-input-mouse&keyborad and full update. The necessary packages is going to be pulled as dependencies. Restart X and check the Xorg.0.log if your mouse and keyboard have been installed.
| Code: | | emerge -C $(qlist -IC x11-drivers/) && emerge -uDN world |
I suggest you try a simpler xorg.conf first. I mean with less keywords and a basic configuration.
You've mentioned that had already done that, however, I don't know if the order is important. So follow these steps to see if you get ride of the problem. If it doesn't work you should consider another possibility.
G'Luck |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Tue Jul 12, 2011 4:05 pm Post subject: |
|
|
ferreirafm: Thanks for the assistance, my system apparently needed some updating with the X configuration (not to mention that I was wholly unfamiliar with this news until you brought it up). Unfortunately, cleaning up the the X configuration does not seem to have resolved my issue. The remaining errors in my Xorg.0.log are regarding either the glx module (which I have now disabled while testing and does not come up in the log file), regarding font paths (which I may have fixed), and the nvidia issues. I did a bit more searching around the internet regarding the dmesg errors I was coming across (I posted similar ones a while back):
| Code: | [ 630.554744] NVRM: Xid (0000:05:00): 13, 0000 e0014200 00000062 00000188 0001a3db 00000002
[ 630.610179] NVRM: Xid (0000:05:00): 2, CCMDs 00000000 00000044 00000300 00000003 0000001c
[ 630.637407] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000004 M 0000018c Data e0014400
[ 630.655109] NVRM: Xid (0000:05:00): 13, 0000 e0013900 00000039 00000184 0001a3db 00000002
[ 630.667945] NVRM: Xid (0000:05:00): 7, Ch 00000000 M 00000000 D 00017c00 intr 00010000
[ 630.693705] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000003 M 00000180 Data e0010430
[ 630.714719] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000003 M 00000180 Data e0010430
[ 630.736990] NVRM: Xid (0000:05:00): 3, C 00000000 SC 00000003 M 00000188 Data e0011900 |
It was seem that nvidia themselves report that this kind of error indicates a broken/failed graphics card. One thought that has passed through my mind is that the card overheated and may be malfunctioning as a result (ie: a hardware issue vs a software issue). My only doubt is that I can see the console just fine, so it would really boil down to putting too much power into the card causes it to malfunction (ie: X would require a heavier load than the console). With this in mind I tried booting into windows and the Gentoo livecd, both of which ALSO fail to boot once it gets to the graphical side of things. I saw another post at one point indicating that the Xid errors specifically referred to a power consumption problem, but the solution referred to a change of configuration (which I had not done recently). I would be interested in some feedback on this before I start looking around for new graphics cards, but I daresay I've figured this one out. As this is clearly not a KDE issue, but a lower-level X/nvidia-drivers/hardware issue I am also changing the topic subject. |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Tue Jul 12, 2011 9:18 pm Post subject: |
|
|
alienjon,
That's would be my another possibility, a hardware fail. Indeed, there wasn't anything else to do. Test your video card in another computer using the gentoo live CD and/or get a video card from a friend and test it on your mother board before buy a newer.
Best of Luck,
ferreirafm
Last edited by ferreirafm on Wed Jul 13, 2011 4:13 pm; edited 1 time in total |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Wed Jul 13, 2011 12:04 am Post subject: |
|
|
Will do and will post results when I can (may be several days - maybe a week or two - before I can test). Seriously, though, thanks for the help. I was a bit lost on this one  |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Wed Jul 13, 2011 1:20 pm Post subject: |
|
|
Hi alienjon,
I'm sorry. In one of my previous posts I wrongly suggested you uncomment the lines 4 and 5 of your xorg.conf. I have corrected the post, which means that those line should not be there. So, please, COMMENT/REMOVE lines 4 and 5 of your xorg.conf and see if you get your mouse and keyboard at least.
All the Best,
ferreirafm |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Wed Jul 13, 2011 3:38 pm Post subject: |
|
|
| ferreirafm wrote: | | COMMENT/REMOVE lines 4 and 5 of your xorg.conf and see if you get your mouse and keyboard at least |
That's what I had meant in a question in a previous post, but I guessed this is what you had meant. I have now commented those 2 lines, but there isn't a difference (other than less warnings/having a cleaner xorg.conf). The lack of mouse/keyboard input is definitely related to the system freezing (ie: they both work initially, but after a few moments slow down until neither work at all). Thanks for the clarification, though! |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Fri Jul 15, 2011 1:50 pm Post subject: |
|
|
Hi alienjon,
Just by chance. Your xorg.conf has several uncommon nvidia keywords. Do those keywords make any difference in your video performance? How did you test them?
All the Best,
ferreirafm |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Fri Jul 15, 2011 3:50 pm Post subject: |
|
|
| Which ones are you looking at specifically? At least one of them was added (I'd have to check to see which one) because I kept having an issue with the card and SDL, where fullscreen SDL would cutoff parts of the screen with the option disabled. |
|
| Back to top |
|
|
ferreirafm
Guru
Joined: 28 Jul 2005
Posts: 487
Location: Sao Paulo, Brazil
|
| Posted: Fri Jul 15, 2011 7:27 pm Post subject: |
|
|
Hi alienjon,
I was wondering about lines 53 and 56 to 59.
Thanks in advance.
ferreirafm
P.S.: I have a nvidia GTX285. |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Sat Jul 16, 2011 12:09 am Post subject: |
|
|
Well, keep in mind that these are options that have been added over time, so they may be deprecated or may not have the same effect anymore (if any), but the reasons I added (or at least I think I added)...
| Code: | | Option "AllowGLXWithComposite" "true" |
"AllowGLXWithComposite" is a command that allows you to use OpenGL while compositing is running. Apparantly it can be buggy, though, so if you have problems you might want to disable compositing in your xorg.conf whenever you want to use opengl. I put this in my xorg a while back when I had composite enabled, but it slowed my games down or they wouldn't work at all (I don't have nearly as impressive a rig as I'd like to admit). At the time it allowed me to play 3D games without disabling composite, but I've had enough problems with composite that I just disabled it entirely a while back and, I guess, never removed it from my xorg.conf.
| Code: | | Option "TripleBuffer" "true" |
| Quote: | | In triple buffering the program has two back buffers and can immediately start drawing in the one that is not involved in such copying. The third buffer, the front buffer, is read by the graphics card to display the image on the monitor. Once the monitor has been drawn, the front buffer is flipped with (or copied from) the back buffer holding the last complete screen. Since one of the back buffers is always complete, the graphics card never has to wait for the software to complete. Consequently, the software and the graphics card are completely independent, and can run at their own pace. Finally, the displayed image was started without waiting for synchronization and thus with minimum lag.[1] |
This option enables triple buffering for nVidia cards BUT (as I just discovered) is ONLY enabled when vsync is ALSO enabled. Needless to say, this line probably should be removed.
| Code: | | Option "ModeValidation" "DoubleScanPriority" |
This is the one I mentioned I added because fullscreen SDL wasn't working for me. Setting the mode validation to double scan priority (whatever all that means) fixed the problem. Without this, the lower portion (although not the side) was cutoff - even if the resolution evenly matched my monitor (ie: 800x600 on a 1024x768 screen) |
|
| Back to top |
|
|
alienjon
Veteran
Joined: 09 Feb 2005
Posts: 1732
|
| Posted: Tue Jul 26, 2011 1:51 am Post subject: |
|
|
| Definitely the card got burnt/half-burnt out. Thanks for the help in diagnostics! |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
