|
|
#25 | |
|
Registered User
Join Date: Dec 2009
Posts: 10
|
Ok guys, it sounds like there's a lot of you with the GT 240 that have it working without a problem. Unfortunately, it's still not working for me. I've tried stepping through the installation as described in the sticky thread in this forum, but I'm still getting the WAIT error and a locked system when attempting to start X.
Attached is my full nvidia-bug-report.log.gz (which is actually not compressed for some reason). If anyone else is experiencing the same problem, please post your nvidia-bug-reports (with "startx -- -logverbose 6"). Hopefully we can find something in common with our environments... |
|
|
|
|
|
|
#26 | |
|
Registered User
Join Date: Dec 2009
Posts: 5
|
Quote:
|
|
|
|
|
|
|
#27 | |
|
Registered User
Join Date: Dec 2009
Posts: 10
|
Quote:
I tried using the Ubuntu 9.10 supplied nvidia driver (180), it had the same problem. I have manually tried the 190.42 packages as well, but they gave the same error. I tried using the ppa packages, but that didn't make any difference. If anyone can help, please do! |
|
|
|
|
|
|
#28 | |
|
Registered User
Join Date: Feb 2007
Posts: 10
|
195.30 beta 'officially' supports GT240.
(but, on my system, the fan is still running 100% all the time, with the GPU staying at room temperature, which is quite annoying) |
|
|
|
|
|
|
#29 |
|
Registered User
Join Date: Oct 2008
Posts: 8
|
Not fixed powermizer bug in 195.30, not switches to 3D clock frequencies. GLXGears show 4000 fps on current clocks 240GT, but 9600gt show 21000 fps. Cuda perfomance 240GT in linux is very bad, but on windows very cool. PLEASE FIX it.
|
|
|
|
|
|
#30 | |
|
Registered User
Join Date: Dec 2009
Posts: 10
|
Quote:
After executing startx, the system locks up. See attached nvidia-bug-report for details. |
|
|
|
|
|
|
#31 |
|
Registered User
Join Date: Dec 2009
Posts: 10
|
I found another thread that mentioned the WAIT error in the Xorg log:
http://www.nvnews.net/vbulletin/showthread.php?t=125824 gimpel mentioned that a motherboard BIOS updated solved the problem for him. I tried the same, and it worked! ![]() In my case, I have the ASUS M2A-VM HDMI motherboard (http://asus.com/product.aspx?P_ID=DkEhMfgo4ExcGXpn) I was at an old BIOS version 0502 (2007/04/03) and upgraded to version 2302 (2009/02/13) using the FlashROM utility (http://www.flashrom.org). I am using the nVidia driver 195.30 beta, if that matters. I hope this helps somebody out! Now I am going to test out VDPAU! Last edited by mr_helamonster; 12-27-09 at 06:35 PM. Reason: I clarified that this is the motherboard BIOS, not the video card BIOS |
|
|
|
|
|
#32 | |
|
Registered User
Join Date: Dec 2009
Posts: 11
|
Quote:
Can you use the 1.7GHz mode? i.e. what happens when you run glxgears and ... Code:
nvidia-settings -q all | grep GPUCurrentClockFreqs Code:
Attribute 'GPUCurrentClockFreqs' (home:0.0): 405,324. It appears that with the current drivers (195.30 and 190.53), performace level 3 is disabled in GT240/GDDR5, and the result is abysmal performance in almost everything: glxgears scores around 4000 fps (!), and CUDA code runs between 10% - 30% of the corresponding speed under Windows (depending on how much the algorithm depends on memory accesses). This is basically making the card slower than 30$ cheap NVIDIA models... Please fix this, NVIDIA. |
|
|
|
|
|
|
#33 |
|
Registered User
Join Date: Dec 2009
Posts: 6
|
I just installed this card in my PC and it's working so far with the 195.42 driver on Debian testing (using packages from sid). X-Plane gives me a much higher framerate than anything I had so far (Intel on-board), even with the clock problem mentioned before; indeed I'm also stuck at 405,324 all the time. :-(
Suspend-resume also seems to work. The only thing I miss now is TV-Out, but that seems to be more a hardware limitation. |
|
|
|
|
|
#34 |
|
Registered User
Join Date: Jan 2010
Posts: 6
|
I'm running Ubuntu karmic and the 195.30 beta drivers from nvidia-vdpau's ppa and also get the WAIT error, requiring me to hit the reset button. It happens about every 4 hours, usually when I'm playing a game or I change desktops in compiz.
(WW) Jan 01 16:12:56 NVIDIA(0): WAIT (2, 6, 0x8000, 0x00003454, 0x00004aa8) (WW) Jan 01 16:13:03 NVIDIA(0): WAIT (1, 6, 0x8000, 0x00003454, 0x00004aa8) |
|
|
|
|
|
#35 |
|
Registered User
Join Date: Dec 2009
Posts: 6
|
FWIW I noticed the Coolbits xorg.config option today and tried it out. It enables a "Clock Frequency" menu in nvidia-settings, meant for overclocking but of course you can also use it to manually set the clock frequency to values inside the spec.
Initially it seemed to have some effect, but after some more thorough testing that seemed more like an illusion. Even if I use that menu to set the frequencies to something ridiculously low, the fps rate doesn't change. Maybe I forgot one step or so though, someone else may be more patient and lucky. ![]() |
|
|
|
|
|
#36 |
|
Registered User
Join Date: Oct 2008
Posts: 8
|
Coolbits changed clocks, but doesn't change PerfLevel. Cuda/vdpau/gl perfomance still bad. Today GT240 DDR5 normally works only in windows. I've bought GT240 DDR5 two month ago and this bug not yet fixed. Please, FIX IT!
p.s. Sorry for bad english. |
|
|
|
![]() |
| Thread Tools | |
|
|