[PC-BSD Testing] PCBSD 8.0-RC2-x86 & Nvidia Legacy Driver Screen Corruption

Ian Robinson fitchkendall at gmail.com
Mon Feb 22 08:43:15 PST 2010

Kris --

I have two machines with "legacy" nVidia cards -- a Geforce Ti4200 ("GeForce
4") that would ordinarily take the 96.43.xx driver and the other a GeForce
FX5500 that would ordinarily take the 173.xx.xx driver.  I will make fresh
installs of PCBSD 8.0-RELEASE on both today and track the impact of both the
nVidia drivers and VESA.  The nv driver is deprecated for FreeBSD 8.0.


On Mon, Feb 22, 2010 at 11:19 AM, Kris Moore <kris at pcbsd.com> wrote:

> On 02/21/2010 11:45, Ian Robinson wrote:
>> PCBSD 8.0-RC2-x86&  Nvidia Legacy Driver Screen Corruption
>> On 2/19/10, Kris Moore<kris at pcbsd.org>  wrote:
>>> Thanks! BTW, I think the nvidia port just got updated today to fix that
>>> compile error, you may want to run portsnap again shortly to try
>>> recompiling.
>> I downloaded and compiled the new 96.43.16 successfully.
>> Although the opening screens were promising because there was little
>> or no speckled dots at all on the screen.  However, after approx 40
>> minutes, the screen corrupted badly.  The colors were much 'prettier'
>> which you can see from the attached screen capture but all menus were
>> unreadable.
>> The system itself functioned without problem, but using it consisted
>> of a braille-like trial&  error method (i.e., as if blind).  For
>> example, to get the screen capture utility, I used the barely visible
>> search box function at the top of the kicker menu to locate 'screen
>> capture', clicked the corrupted choice, and clicked the corrupted
>> 'save' button.  I rebooted with a 'reboot now' command in the terminal
>> window that lay behind everything.   Thus, the system is functional if
>> you can guess where your mouse is clicking and type in the commands,
>> but the newest driver is not helpful for this corruption problem.  The
>> cause remains unknown.
>> Ian Robinson
>> Salem, Ohio
> Ok, that helps confirm at least that the issue still occurs in the latest
> drivers. Just for kicks again, can you re-confirm that switching back to
> "nv" or "vesa" gets rid of these problems? If we can for sure confirm that
> its only "nvidia" 96.43.xx related, we can then take this to nvidia with
> details. We'll need to let them know your particular card, with details
> about OS, such as FreeBSD 8.0 / xorg-server 1.6.5, etc:
> Here's where we've been communicating a lot with Christian Zander @ Nvidia.
> He's aware of some issues on 8.0 right now and will hopefully be fixing them
> soon, but if he doesn't know about this one we can get him to add it to the
> list :)
> http://www.nvnews.net/vbulletin/forumdisplay.php?f=47
> --
> Kris Moore
> PC-BSD Software
> http://www.pcbsd.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.pcbsd.org/pipermail/testing/attachments/20100222/a8cfb298/attachment.html 

More information about the Testing mailing list