Hi, I'm runnung Fedora Core 4 on x86_64 with xorg-x11-6.8.2-37.FC4.45. My graphics card is Gigabyte GV-NX66128DP (http://www.gigabyte.com.tw/VGA/Products/Products_GV-NX66128DP.htm) with passive heat-pipe cooling. If I'm boot my PC, log to KDE and just do nothing, in few minutes radiator/heat pipes on graphics card are extremly hot (I can't touch them), and some graphics glitches appear on screen (something like white noise), so I can't do anything because I just can't see anything, this is probably caused by overheat of GeForce 6600 chip. If I load proprietary NVIDIA drivers (version 1.0-7676) when the heat pipes are extremly hot then in 15-20 (hard to say) minutes temperature become _muuuch_ lower (I can touch heat pipes by infinite time :)), no glitches on screen. Even when I run DOOM 3 (on proprietary drivers) temperature is lower than in KDE (on open source dirvers). It would be great if my graphics card won't burn on open source dirvers under KDE session :)
Is this still an issue using a more current version of xorg and the nv driver?
Yes it is still an issue. But maybe now temperature increase slower (it was 9 month ago so I don't remeber how it was exactly before), it take more time to go extremly hot (but still I can't touch radiator longer then 1s). The good thing is I don't get that graphics glitches (X is up for about 30 min, don't know what will happen later). Fedora Core 5, xorg-x11-drv-nv-1.0.1.5-3.1 and org-x11-server-Xorg-1.0.1-9.fc5.1.1, switching to nvidia-1.0.8762 bring temperature down to normal cool state.
Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.