1. Computers
  2. Display Drivers
  3. Graphics Cards
  4. Memory
  5. Motherboards
  6. Processors
  7. Software
  8. Storage
  9. Operating Systems


Facebook RSS Twitter Twitter Google Plus


Phoronix Test Suite

OpenBenchmarking.org

ECS NVIDIA GeForce GT 240 512MB

Michael Larabel

Published on 22 January 2010
Written by Michael Larabel
Page 3 of 9 - 23 Comments

The ECS GeForce GT 240 was installed into a system running an Intel Core i7 920 processor clocked to 3.60GHz, used an ASRock X58 SuperComputer motherboard, had 3GB of DDR3 system memory, and ran with a 320GB Seagate ST3320620AS SATA HDD. On the software side was Ubuntu 9.10 (x86_64) with the Linux 2.6.31 kernel, X Server 1.6.4, and the NVIDIA 195.30 beta display driver was installed.

The GeForce GT 240 booted up just fine with the binary NVIDIA graphics driver and had properly mode-set to 2560 x 1600. The PCI ID for this graphics card was 0x0ca3 while the PCI vendor ID is of course 0x10de. Compiz was working and OpenGL applications were running just fine. PowerMizer also had no problems dynamically changing the performance levels based upon load, but when we tried using CoolBits to overclock the GPU was the first signs of a problem. When attempting to change the 3D clock frequencies manually or using the auto detect feature, the clocks would not change from 550MHz for the CPU and 1700MHz for the GDDR5 memory. Attempting to apply any other core/memory clock values would not take. We could not overclock (or underclock) this ECS GeForce GT 240 graphics card under Linux and all attempts to do so had failed. This is either a bug within NVIDIA's binary Linux driver, an issue with the video BIOS on this ECS graphics card, or some combination thereof.

Due to this overclocking issue and another set of problems to be mentioned in this article, the ECS GeForce GT 240 graphics card was then installed in an entirely different AMD-based system and it was running with the NVIDIA 190.53 stable Linux driver rather than the 195 series beta. With this driver, CoolBits claimed to work and the optimal 3D clocks that it found was 720MHz for the graphics processor and 2040MHz for the memory. These optimal clocks are rather high and equates to the GPU running 30% faster and the memory running 20% above its rated speed. These values seemed to apply fine, but once carrying out the testing following this, there was no difference in the performance compared to its stock speeds. When polling the NV-CONTROL extension to see what the clocks were reading, they were back at their stock frequencies.

Latest Linux Hardware Reviews
  1. Rosewill RS-MI-01: An Ultra Low-Cost Mini-ITX Chassis
  2. D-Link DCS-2330L HD Wireless Network Camera
  3. Gigabyte AM1M-S2H
  4. AMD's New Athlon/Semprons Give Old Phenom CPUs A Big Run For The Money
Latest Linux Articles
  1. The Performance Of Fedora 20 Updated
  2. Clang Fights GCC On AMD's Athlon AM1 APU With Jaguar Cores
  3. Ubuntu 14.04 LTS vs. Oracle Linux vs. CentOS vs. openSUSE
  4. How Much Video RAM Is Needed For Catalyst R3 Graphics?
Latest Linux News
  1. Red Hat Enterprise Linux 7.0 Is Looking Fantastic
  2. Intel Is Launching An Interesting Bay Trail NUC Next Week
  3. Another X.Org EVoC Proposed For OpenGL 4+ Tests
  4. The Best Features Coming With Qt 5.3
  5. Red Hat's RHEL7 RC ISO Is Now Publicly Available
  6. Nuclear Dawn Seems To Run Fine On AMD Linux
  7. KDE 4.14 Release Schedule Published
  8. GCC 4.9.0 Released, Brings Many Compiler Features
  9. OpenSSL Forked By OpenBSD Into LibreSSL
  10. GNOME Has Big Plans For Its Maps Application
  11. NVIDIA Will Soon Probably Introduce OpenCL 1.2 Linux Support
  12. Google Is Financing A Lot Of Great Open-Source Work This Summer
Latest Forum Discussions
  1. Announcing radeontop, a tool for viewing the GPU usage
  2. New card. Open source drivers only.
  3. The GNOME Foundation Is Running Short On Money
  4. Linux Kernel Developers Fed Up With Ridiculous Bugs In Systemd
  5. The Most Amazing OpenGL Tech Demo In 64kb
  6. Script for Fan Speed Control
  7. Torvalds Is Unconvinced By LTO'ing A Linux Kernel
  8. ReactOS Working On A Community Windows OS