From owner-freebsd-mobile@FreeBSD.ORG Tue Mar 1 08:52:40 2005 Return-Path: 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 B109A16A4CE for ; Tue, 1 Mar 2005 08:52:40 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6CBB43D1F for ; Tue, 1 Mar 2005 08:52:39 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D637F-0000NG-Rj; Tue, 01 Mar 2005 11:52:29 +0300 From: Vladimir Grebenschikov To: Ian Dowse In-Reply-To: <200502282026.aa38504@salmon.maths.tcd.ie> References: <200502282026.aa38504@salmon.maths.tcd.ie> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Tue, 01 Mar 2005 11:52:29 +0300 Message-Id: <1109667149.1098.5.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov 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 Reply-To: vova@fbsd.ru List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Mar 2005 08:52:40 -0000 =F7 =D0=CE, 28/02/2005 =D7 20:26 +0000, Ian Dowse =D0=C9=DB=C5=D4: >In message <200502281016.aa49779@salmon.maths.tcd.ie>, Ian Dowse writes: >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschikov wr= ites: >>>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? Unfortunately it panics on boot with this patch. (before mounting root). I have console just now to check what happens, will do this later and send you panic output.=20 >Ian --=20 Vladimir B. Grebenchikov vova@fbsd.ru