From owner-freebsd-mobile  Tue Mar 14 23:23: 7 2000
Delivered-To: freebsd-mobile@freebsd.org
Received: from quack.kfu.com (quack.kfu.com [170.1.70.2])
	by hub.freebsd.org (Postfix) with ESMTP id 74F9937B91A
	for <freebsd-mobile@FreeBSD.ORG>; Tue, 14 Mar 2000 23:23:04 -0800 (PST)
	(envelope-from nsayer@quack.kfu.com)
Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.17])
	by quack.kfu.com (8.9.2/8.9.3) with ESMTP id XAA37130;
	Tue, 14 Mar 2000 23:23:03 -0800 (PST)
	(envelope-from nsayer@quack.kfu.com)
Received: from quack.kfu.com by icarus.kfu.com  with ESMTP
        (8.9.3//ident-1.0) id XAA01865; Tue, 14 Mar 2000 23:22:32 -0800 (PST) 
Message-ID: <38CF3A38.54307FEF@quack.kfu.com>
Date: Tue, 14 Mar 2000 23:22:32 -0800
From: Nick Sayer <nsayer@quack.kfu.com>
X-Mailer: Mozilla 4.72 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Boris Gelfand <bg@cse.msu.edu>
Cc: freebsd-mobile@FreeBSD.ORG
Subject: Re: green_saver acting wacky in 3.4-R
References: <200003081601.LAA07044@dog.cse.msu.edu>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-mobile@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Boris Gelfand wrote:
> 
> Hello all,
> 
> Prior to a complete re-install with 3.4-R, I ran 3.0 and 3.2
> on my Panasonic CF-35 as well as a Gateway Solo at work with no
> problems.  Since going to 3.4-R on both machine, my green_saver
> in console mode has started to go wacky.  Whenever it fires up,
> both displays show color bleed and ghost images  -- pretty scary
> stuff.
> 
> One laptop has Neomagic and the other Chips&Tech.  I've got my
> kernel with the speudo-device splace, and "VM86" & "VESA" options
> turned on.  Other screen savers work fine (blank, snake, etc.)
> "power_saver" mode in XFree86 works fine as well -- suspend
> properly turns off the backlight, etc.
> 
> Any idea as to what's up?

Try using the apm saver instead of the green one. The apm one
actually uses the APM bios to do its work. This is likely to
be friendlier to your LCD.

One way to know if the apm saver will work for you is to type

apm -d 0 ; sleep 30 ; apm -d 1

and see if your display blanks out for 30 seconds and comes back.
This is exactly the same thing as what the apm saver does.

I _think_ the apm saver is in 3.x, but I could be wrong. It is certainly
in 4.x. Unfortunately, the apm saver is not one of the choices in
sysinstall.
It relies on apm being available, and by default it's disabled (not only
is apm_enable NO by default, but the driver itself is disabled in
GENERIC).


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-mobile" in the body of the message