From owner-freebsd-current Thu Nov 7 13:57:38 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 977A437B401 for ; Thu, 7 Nov 2002 13:57:37 -0800 (PST) Received: from flamingo.mail.pas.earthlink.net (flamingo.mail.pas.earthlink.net [207.217.120.232]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCC343E6E for ; Thu, 7 Nov 2002 13:57:37 -0800 (PST) (envelope-from tlambert2@mindspring.com) Received: from pool0030.cvx40-bradley.dialup.earthlink.net ([216.244.42.30] helo=mindspring.com) by flamingo.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 189ueV-0004QO-00; Thu, 07 Nov 2002 13:57:27 -0800 Message-ID: <3DCAE178.4271FF1C@mindspring.com> Date: Thu, 07 Nov 2002 13:56:08 -0800 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: walt Cc: freebsd-current@freebsd.org Subject: Re: XFree References: <3DCA7531.1040402@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG walt wrote: > Horen wrote: > > Posted a week ago the question, didn't get any reaction. > > > > Everything with current from last night works fine but killing > > X or logging out ends in a black screen. No way to activate the > > display without reboot. Remote login is fine. Typing blind works > > too. > > I have exactly the same problem on my NetBSD box but I haven't > spent any time trying to fix it. > > I wonder if the console font color is being reset to black. > You could try typing 'vidcontrol white black' to test that > theory. Dunno what might be causing it, though. I had the same problem. I made it go away by turning off all acceleration, and then turning on accelleration options, one by one, until the problem reappeared, and then leaving the three that cuased problems off. It seems that the driver was written for a rev. 2 of the NeoMagic chip, and my laptop actually has rev. 3. Most likely, you will find that turning off all chip-specific options, and then turning on only those which actually reliably work, will fix your problem. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message