Just as a data point, I just tried this as well... The daemon saver was ok,
the fire saver was ok, but as soon as I loaded logo_saver and it activated,
I got a 'dc0 timeout'(?) and I was unable to access any of the vtys after
that... I could switch vtys, but could not type anything.
The fire_saver module is obviously using a VESA mode, but I had no problem
problem with it...
On Mon, Dec 04, 2000 at 06:41:55PM -0800, John Baldwin wrote:
>
> On 05-Dec-00 Andrea Campi wrote:
> >> > More details: this is an IBM Thinkpad laptop with APM enabled and in the
> >> > kernel.
> >> > As usual, any hint is more than welcome. This used to work...
> >>
> >> Which screen saver? Does it do it with all of them? Just graphical ones,
> >> just
> >> text ones, just green_saver, etc.?
> >
> > Rrrright... I can assure you I would never have thought this could make a
> > difference...
>
> That's ok, it didn't occur to me either at first. However, the green_saver
> calls into APM, and the graphical ones will call into VESA, so it might make a
> difference.
>
> > Ok, I will try each one. At the moment, I'm using logo_saver.
> > I will let you know.
> >
> > Bye,
> > Andrea
> >
> > --
> > Weird enough for government work.
>
> --
>
> John Baldwin <[EMAIL PROTECTED]> -- http://www.FreeBSD.org/~jhb/
> PGP Key: http://www.baldwin.cx/~john/pgpkey.asc
> "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
