[PC-BSD Testing] NVidia Driver 185.18.14 Release June 5th
yerenkow at uct.ua
Tue Jun 9 09:11:23 PDT 2009
On 09.06.2009 18:46, Jeff wrote:
> Still nothing on AMD64 support however.
> I posted yesterday
> <http://www.nvnews.net/vbulletin/showthread.php?t=41545&page=27> on
> the NVidia news forum looking for some time frame, but still waiting
> for a response. At least there's some activity
> on FreeBSD towards fixing the technical issues that are holding this up.
> Bad timing for me as I want to buy a new laptop (portable desktop
> really) with a lot of power, hence this beast
> <http://www.avadirect.com/product_details_configurator.asp?PRID=13880>, by
> far the fastest laptop ever built
> <http://www.notebookreview.com/default.asp?newsID=5084>, is at the top
> of my list in spite of the $3K price tag.
Very impressive laptop ;)
> Not sure if PCBSD-64 is worth the grief though, unless it and its 64
> bit apps are faster than their 32 bit counterparts. Perhaps someone
> here could weigh in on that issue on the PCBSD forum, here
64 bit generic driver (btw, not only VESA, but also nv) give to you
average speed 2d desktop; which will be enough for web-development,
assuming you have good processor and a lot of ram;
I think you should get option "No OS at all", save a little bit money,
and try 64bit PC-BSD, if somehow it'll fail, you always can use 32bit;
btw, you even can set up dual boot, 32bit for games with nvidia drivers,
and 64 bit for working.
That's what I'd did :)
> --- On *Tue, 6/9/09, Arthur /<A-Koziol at neiu.edu>/* wrote:
> From: Arthur <A-Koziol at neiu.edu>
> Subject: [PC-BSD Testing] NVidia Driver 185.18.14 Release June 5th
> To: "PC-BSD Testing list" <testing at lists.pcbsd.org>
> Date: Tuesday, June 9, 2009, 10:36 AM
> For all the NVidia people.
> FreeBSD Display Driver – x86
> *Version: 185.18.14
> Operating System: FreeBSD x86
> Release Date: : June 05, 2009*
> *Release Highlights:*
> * Modified VDPAU to dlopen libpthread.so (on all platforms),
> to avoid conflicts between the current libc and a compat
> * Improved compatibility with recent Linux kernels.
> * Fixed a Xinerama drawable resource management problem that
> can cause GLXBadDrawable errors in certain cases, such as
> when Wine applications are run.
> * Fixed XineramaQueryScreens to return 0 screens instead of 1
> screen with the geometry of screen 0 when XineramaIsActive
> returns false. This conforms to the Xinerama manual page and
> fixes an interaction problem with Compiz when there is more
> than one X screen.
> * Added support for new horizontal interlaced and checkerboard
> passive stereo modes.
> * Fixed a DisplayPort interaction problem with power
> management suspend/resume events.
> * Fixed occasional X driver memory management performance
> problems when a composite manager is running.
> * Fixed a bug with VT-switching or mode-switching while using
> Compiz; the bug could lead to a corrupted desktop (e.g., a
> white screen) or in the worst case an X server crash.
> * Fixed a bug that could cause GPU errors in some cases while
> driving Quadro SDI products.
> * Fixed a several second hang when VT-switching while OpenGL
> stereo applications were running on pre-G80 Quadro GPUs.
> * Added support for multiple swap group members on G80 and
> later Quadro GPUs.
> * Fixed the behavior of the NV_CTRL_FRAMELOCK_SYNC_DELAY
> NV-CONTROL attribute on Quadro G-Sync II.
> * Fixed a problem with Quadro SDI where transitioning from
> "clone mode" to "OpenGL mode" would fail.
> * Fixed VDPAU to eliminate some cases of corruption when
> decoding H.264 video containing field-coded reference frames
> on G84, G86, G92, G94, G96, or GT200 GPUs. Such streams are
> commonly found in DVB broadcasts.
> * Slightly improved the performance of the VDPAU noise
> reduction algorithm.
> * Enhanced VDPAU to validate whether overlay usage is
> supported by the current hardware configuration, and to
> automatically fall back to the blit-based presentation queue
> if required.
> * Fixed error checking in VdpVideoMixerRender, to reject calls
> that specify more layers than the VdpMixer was created with.
> * Modified VDPAU's VDPAU_DEBUG code to emit a complete
> backtrace on all platforms, not just on 32-bit Linux.
> * Improved interaction between VDPAU and PowerMizer;
> appropriate performance levels should now be chosen for
> video playback of all standard resolutions on all supported
> * Fixed a bug in VDPAU that sometimes caused "display
> preemption" when the VdpDecoderCreate function failed.
> * Fixed a potential segfault in the VDPAU trace library,
> triggered by a multi-threaded application creating a new
> VdpDevice in one thread, at the same time that another
> thread detected "display preemption".
> *Pre-Installation Notes*
> * If you are using FreeBSD 6.x, you will need to make sure
> that the 'compat5x' package is installed.
> * The 'nvidia-settings' utility can be built from source
> (available from
> ) if the binary included in the 185.18.14.tar.gz package
> doesn't work (e.g. due to a ports/ library version conflict).
> *To download and install the drivers, follow the steps below:
> STEP 1*: /Review the NVIDIA Software License
> You will need to accept this license prior to downloading any files.
> *STEP 2*: /Review Documentation
> / README
> <http://us.download.nvidia.com/freebsd/185.18.14/README/index.html> -
> FreeBSD installation and configuration information.
> *STEP 3*: /Download the driver
> / NVIDIA-FreeBSD-x86-185.18.14.tar.gz
> *STEP 4*: /Check dependencies/
> The dependencies are listed in the README.
> *STEP 5*: /Install/
> See the README
> <http://us.download.nvidia.com/freebsd/185.18.14/README/index.html> for
> detailed installation instructions. If you have any questions or
> problems, please check the NVIDIA FreeBSD Discussion forum
> <http://www.nvnews.net/vbulletin/forumdisplay.php?f=47>. If you
> don't find an answer to your question there, you can send email
> (in English) to freebsd-gfx-bugs at nvidia.com
> </mc/compose?to=freebsd-gfx-bugs at nvidia.com>. When emailing
> freebsd-gfx-bugs at nvidia.com
> </mc/compose?to=freebsd-gfx-bugs at nvidia.com> please attach an
> nvidia-bug-report.log, which is generated by running
> -----Inline Attachment Follows-----
> Testing mailing list
> Testing at lists.pcbsd.org </mc/compose?to=Testing at lists.pcbsd.org>
> Testing mailing list
> Testing at lists.pcbsd.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Testing