- Added support for OpenGL 3.2.
- Added support for the following GPUs:
- GeForce G102M
- GeForce GT 220
- GeForce G210
- GeForce G210M
- GeForce GT 230M
- GeForce GT 240M
- GeForce GTS 250M
- GeForce GTS 260M
- Updated the NVIDIA X driver to allow, on GeForce 8 or greater GPUs, more modes to validate on digital display devices whose EDIDs report very constrained HorizSync or VertRefresh ranges.
- Fixed a randomly occuring X server crash caused by the PixmapCache option.
- Increased the allowed amount of overscan compensation from 100 to 200.
- On GPUs with VDPAU feature set B, VDPAU's handling of some corrupted or incorrectly formatted H.264 and MPEG streams has been improved.
- Fixed a memory allocation problem with pre-GeForce 8 GPUs that caused GLX_EXT_texture_from_pixmap clients (e.g., Compiz, KDE 4) to display incorrect contents.
NVIDIA Accelerated FreeBSD Graphics Driver Set for FreeBSD/i386
is available for download via FTP
Please see the README
for more information about this release.
If you are using FreeBSD 6.0-RELEASE
or a more recent FreeBSD 6.x
release, please make sure that the compat5x-i386
package is installed.
Note that the gtk-2.x ports package(s) shipped with FreeBSD releases > 5.3-RELEASE
are binary incompatible with those shipped with FreeBSD 5.3-RELEASE
; due to this, the `nvidia-settings`
binary shipped with 190.40
will not work on FreeBSD > 5.3-RELEASE
. This problem can be solved by (re-)building `nvidia-settings`
# fetch ftp://download.nvidia.com/XFree86/nv...-190.40.tar.gz
# tar zxf nvidia-settings-190.40.tar.gz
# cd nvidia-settings-1.0# gmake
# install nvidia-settings /usr/X11R6/bin
This NVIDIA FreeBSD graphics driver release supports GeForce 6 series and newer
NVIDIA GPUs. GeForce FX GPUs are supported through the 173.14.xx
driver series, while GeForce4 and older GPUs are supported through the 96.43.xx
NVIDIA legacy graphics drivers.
Please also note:
If you encounter any problems with the 190.40
NVIDIA FreeBSD graphics driver release, please start a new thread and include a detailed description of the problem, reproduction steps and generate/attach an nvidia-bug-report.log
file (please see http://www.nvnews.net/vbulletin/showthread.php?t=46678