Language Selection

English French German Italian Portuguese Spanish

NVIDIA CoolBits For Linux Guide

Filed under
Hardware

A few months ago here at Phoronix we published an article entitled "The State of Linux NVIDIA Overclocking", which expressed our views of the overclocking options available, or there the lack of, to Linux NVIDIA users. Up until this time, NVClock has been one of the only utilities available to overclock your NVIDIA based graphics card under Linux, without using a BIOS editor. However, when we last tested the NVClock 0.8 CVS we still experienced several problems when paired up with some of our latest NVIDIA 6XXX and FX graphics cards. Although Thunderbird has done a phenomenal job, and continues to do a magnificent job developing NVClock, there still is a lack of overclocking options available for NVIDIA Linux users. NVIDIA, however, has released its new drivers that include some interesting features. In addition to Xinerama and OpenGL 2.0 support, CoolBits also accompanies this latest package. For those who haven't heard of or never used CoolBits, this is a NVIDIA overclocking utility for Microsoft Windows (until now) which could be enabled by a simple registry tweak and allows the user to substantially increase their VPU and memory speeds. However, does this CoolBits Linux port offer the reliability of its Windows counterpart and fix the issues that NVClock has yet to address? Today we have a short guide on how to enable CoolBits with these new NVIDIA drivers (1.0-7664), how to change your core and memory speeds, and the results we obtained when using the CoolBits utility.

Disclaimer: As this article will discuss increasing your VPU and memory frequencies, this can potentially damage or destroy your graphics card and void the warranty with the manufacturer. Phoronix and its staff take absolutely no responsibility for any damage or harm that can potentially occur from the methods discussed in this article.

The first step in setting up CoolBits for Linux, is well acquiring the latest drivers. At the time of publication, the latest available 32-bit and 64-bit NVIDIA display driver is version 1.0-7664. These drivers weigh in at 11.0MB and are available here. After we ran and installed NVIDIA-Linux-x 86-1.0-7664-pkg1.run, we adjusted the xorg.conf, and performed the final steps to properly setup the NVIDIA drivers on the FedoraCore3 systems we were using today for testing.

Full Article.

More in Tux Machines

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers

today's howtos