From owner-freebsd-mobile@FreeBSD.ORG  Mon Feb 28 20:26:19 2005
Return-Path: <owner-freebsd-mobile@FreeBSD.ORG>
Delivered-To: freebsd-mobile@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 109BF16A4DA
	for <freebsd-mobile@freebsd.org>;
	Mon, 28 Feb 2005 20:26:19 +0000 (GMT)
Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11])
	by mx1.FreeBSD.org (Postfix) with SMTP id 2039B43D2D
	for <freebsd-mobile@freebsd.org>;
	Mon, 28 Feb 2005 20:26:18 +0000 (GMT)
	(envelope-from iedowse@maths.tcd.ie)
Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP
          id <aa38504@salmon>; 28 Feb 2005 20:26:17 +0000 (GMT)
To: vova@fbsd.ru
In-Reply-To: Your message of "Mon, 28 Feb 2005 10:16:48 GMT."
             <200502281016.aa49779@salmon.maths.tcd.ie> 
Date: Mon, 28 Feb 2005 20:26:16 +0000
From: Ian Dowse <iedowse@maths.tcd.ie>
Message-ID: <200502282026.aa38504@salmon.maths.tcd.ie>
cc: freebsd-mobile@freebsd.org
Subject: Re: Using VESA to restore display settings on resume 
X-BeenThere: freebsd-mobile@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Mobile computing with FreeBSD <freebsd-mobile.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-mobile>
List-Post: <mailto:freebsd-mobile@freebsd.org>
List-Help: <mailto:freebsd-mobile-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-mobile>,
	<mailto:freebsd-mobile-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Feb 2005 20:26:19 -0000

In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes:
>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov writes:
>>Also if I try this patch with vesa module loaded it just carsh in vm86
>>mode on zzz (curproc acpiconf).
>
>It is probably necessary to get this working with VESA to have much
>of a chance of it helping, since otherwise only the basic VGA
>registers will be saved and restored.
>
>One possible reason for the vm86 crash is that it appears our VESA
>code cannot handle saving more than 4k of state data. Does it make
>any difference if you revert the part of the patch that changed
>STATE_MOST to STATE_ALL? i.e. change the two uses of STATE_ALL in
>vesa.c back to STATE_MOST. I found that with SAVE_MOST, I needed
>to switch to X and back before the console would display, but the
>backlight did come on immediately.

I've updated the patch at

	http://people.freebsd.org/~iedowse/vesa_restore.diff

so that the VESA code allows up to 8k of state storage and will
fail if the BIOS claims to need more space. Could you try this with
the vesa module loaded and with both 0 and 1 for hw.acpi.reset_video?

Ian