kern/82036: loading green_saver makes screen go blank
immediately.
Giorgos Keramidas
keramida at freebsd.org
Sun Jul 17 23:20:21 GMT 2005
The following reply was made to PR kern/82036; it has been noted by GNATS.
From: Giorgos Keramidas <keramida at freebsd.org>
To: bug-followup at freebsd.org
Cc: User Trasz <trasz at pin.if.uz.zgora.pl>
Subject: Re: kern/82036: loading green_saver makes screen go blank immediately.
Date: Mon, 18 Jul 2005 02:18:00 +0300
On 2005-07-17 23:00, Giorgos Keramidas <keramida at freebsd.org> wrote:
>% Date: Sun, 17 Jul 2005 16:32:18 +0200
>% From: User Trasz <trasz at pin.if.uz.zgora.pl>
>%
>% > I haven't had the time to test this, but I suspect this is because you
>% > don't have blanktime="" set in your rc.conf and the timeout defaults to
>% > a short time.
>%
>% timeout defaults to zero, but in that case screen saver should be disabled.
>%
>% > Can you verify that when blanktime is set to a non-zero
>% > value in rc.conf kldloading the green_saver works as expected?
>%
>% yes. the problem, however, is that screen savers blank the screen
>% right after being kldloaded. i load it from /boot/loader.conf, so it
>% blanks the screen somewhere during kernel initialization, before boot
>% scripts can set blanktime.
AHA! Bingo! This is why it blanks out when /etc/rc.d/syscons runs.
Loading the saver module from /boot/loader.conf is what makes this
trigger. If you load the screen saver module from rc.conf using:
saver="snake"
it all works as expected. I'm not sure if this is a bug though.
- Giorgos
More information about the freebsd-bugs
mailing list