Language Selection

English French German Italian Portuguese Spanish

NVIDIA GeForce GT 220

Filed under
Hardware

Days prior to AMD's release of the ATI Radeon HD 5750 and Radeon HD 5770 graphics cards, NVIDIA released their GeForce G 210 and GeForce GT 220 graphics cards. Both of these NVIDIA graphics cards are for low-end desktop systems, but part of what makes them interesting is that they are the first NVIDIA GPUs built upon a TSMC 40nm process. To Linux users these graphics cards are also interesting in that they fully support all of the current features of VDPAU for Linux video decoding, including MPEG-4 support. We picked up an XFX GT220XZNF2 GeForce GT 220 1GB graphics card for this round of benchmarking on Ubuntu Linux.

The GeForce GT 220 is using NVIDIA's GT216 graphics processor core, which is clocked at 625MHz and possesses 48 CUDA cores / shader units while boasting just 486 million transistors. The video memory with the GT 220 can be either 512MB or 1024MB, with our XFX graphics card boasting the higher capacity. The DDR2 memory has a 128-bit bus width and is clocked at 790MHz. The NVIDIA GeForce GT 220 supports NVIDIA PureVideo, PhysX, and CUDA technologies. This NVIDIA GPU supports Microsoft DirectX 10.1 as well as boasting OpenGL 3.1 support. Connectors supported by NVIDIA GeForce GT 220 graphics cards include dual-link DVI, VGA, and HDMI. The graphics card supports HDMI audio, however, there is no integrated audio processor, but a HDA or SPDIF header must be connected from an audio source. The maximum power that will be pulled by the GeForce GT 220 is 58 Watts.

Rest Here

More in Tux Machines

Phoronix on Graphics

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