<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16809" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face="Lucida Sans Unicode" size=2>Kris - this "sorta" fixed itself
after two "skips" for the display setup. Now X is working.
??</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode"
size=2>===========================================================</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>Had been using pre-beta
versions with display OK. (Gone now with new beta.)</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>Network loaded 3-8 i386 from mirror
this PM without trouble. Booted and arrived at display setup
with screen looking fine. Left all entries as they came up. The
trial screen was dead and the screen stayed dead for minutes - until I killed
system. It looks like X worked OK for the download and for the display
setup but then got lost, never to return.</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>System is an ASUS board with Intel
82845 graphics. Monitor is a Compaq FS7600.</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>I rebooted several times
selecting the vesa, intel, sis-intel and vga drivers, with and without entering
the display refresh rate. About the same result except erratic behavior
for acpi and ctl-alt-BS. (Often neither signal worked and I had
to kill power. Recovery on reboot looked OK.) Sometimes the
invisible display would get to the organ grinder sound but more often not.
When the acpi signal did work the text display looked normal as the system shut
down.</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>Depending in the driver
the monitor may or may not get turned back on as display setup gets into
trial. (You can hear the relay and see the power led.)</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>I had a similar situation very
early in the alpha series - I think it just went away with an early
update.</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2>Peter Brewster</FONT></DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV><FONT face="Lucida Sans Unicode" size=2></FONT> </DIV>
<DIV style="FONT: 10pt arial">----- Original Message -----
<DIV style="BACKGROUND: #e4e4e4; font-color: black"><B>From:</B> <A
title=fabrizio@bibivu.com href="mailto:fabrizio@bibivu.com">Fabrizio
Parrella</A> </DIV>
<DIV><B>To:</B> <A title=testing@lists.pcbsd.org
href="mailto:testing@lists.pcbsd.org">PC-BSD Testing list</A> </DIV>
<DIV><B>Sent:</B> Monday, March 09, 2009 2:42 PM</DIV>
<DIV><B>Subject:</B> Re: [PC-BSD Testing] Fix for some nvidia
systems</DIV></DIV>
<DIV><BR></DIV>this sounds like a great fix that can be used to test the system
update..<BR><BR>I do not use the nvidia driver, so it would not cause any issues
with my <BR>beta, but I would be more than happy to install it as system update
to test <BR>the new tool.<BR><BR>Fabry<BR>----- Original Message ----- <BR>From:
"Kris Moore" <<A href="mailto:kris@pcbsd.com">kris@pcbsd.com</A>><BR>To:
"PC-BSD Testing list" <<A
href="mailto:testing@lists.pcbsd.org">testing@lists.pcbsd.org</A>><BR>Sent:
Monday, March 09, 2009 2:38 PM<BR>Subject: [PC-BSD Testing] Fix for some nvidia
systems<BR><BR><BR>><BR>> Bill and others may experience issues with using
the nvidia driver on<BR>> BETA1, related to libwfb being incorrectly replaced
with nvidia's<BR>> version. Here is the fix:<BR>><BR>> Install PC-BSD
7.1-BETA1<BR>> Skip the video setup, or use vesa mode, (Do not use the nvidia
driver,<BR>> it will remove some files incorrectly)<BR>> Once up at the
desktop, download this file<BR>><BR>> <A
href="http://www.pcbsd.org/~kris/nv-fix.tgz">http://www.pcbsd.org/~kris/nv-fix.tgz</A><BR>><BR>>
Run these commands:<BR>> # rm /PCBSD/packages/*<BR>> # cd /<BR>> # tar
xvzf nv-fix.tgz<BR>><BR>> Then reboot, and choose option 7 to re-run the
x-setup tool. You should<BR>> have new nvidia drivers available, such as
180.37, and they won't delete<BR>> libwfb incorrectly
anymore.<BR>><BR>> Bill, can you confirm this gets your card working
again? I didn't catch<BR>> it before, because not all setups use the libwfb
driver it seems, and<BR>> just ignored if it was bad.<BR>><BR>>
Thanks!<BR>><BR>><BR>>
_______________________________________________<BR>> Testing mailing
list<BR>> <A
href="mailto:Testing@lists.pcbsd.org">Testing@lists.pcbsd.org</A><BR>> <A
href="http://lists.pcbsd.org/mailman/listinfo/testing">http://lists.pcbsd.org/mailman/listinfo/testing</A><BR>>
<BR><BR>_______________________________________________<BR>Testing mailing
list<BR><A
href="mailto:Testing@lists.pcbsd.org">Testing@lists.pcbsd.org</A><BR><A
href="http://lists.pcbsd.org/mailman/listinfo/testing">http://lists.pcbsd.org/mailman/listinfo/testing</A>
<P>
<HR>
<P></P>_______________________________________________<BR>Testing mailing
list<BR>Testing@lists.pcbsd.org<BR>http://lists.pcbsd.org/mailman/listinfo/testing<BR></BODY></HTML>