From owner-freebsd-current@FreeBSD.ORG Sun Apr 20 16:09:05 2003 Return-Path: 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 B28C237B408 for ; Sun, 20 Apr 2003 16:09:05 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA58443F85 for ; Sun, 20 Apr 2003 16:09:02 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.12.9/8.12.9) with SMTP id h3KN9Gua050519; Sun, 20 Apr 2003 19:09:17 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Sun, 20 Apr 2003 19:09:15 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ben Laurie In-Reply-To: <3EA28393.5020409@algroup.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: FreeBSD Current Subject: Re: Laptop update... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Apr 2003 23:09:06 -0000 On Sun, 20 Apr 2003, Ben Laurie wrote: > so, where does this leave me? Well, the display still dies if I am in X > and the screen times out - I can reboot blind, but I can't get the > screen back - am I missing a trick? When you wake the box up again, try switching to another virtual console and back again, and/or changing the display resolution using ctrl-alt-[keypad + or -]. I've noticed similar things with my Dell notebook, and seem to recall a discussion of this issue previously. Basically, when things wake up, some piece of something forgets to power the backlight back on again. There may have been a kernel option floating around to deal with this, but it's worth a try to see if that can kick things into action. If your notebook supports a CRT/LCD function key, you could try fiddling that a few times to see if it jogs things back to life. Killing and restarting X might also do it? Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories