From owner-freebsd-mobile@FreeBSD.ORG Wed Mar 2 07:21:11 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 DCCA216A4CE for ; Wed, 2 Mar 2005 07:21:11 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B1B443D39 for ; Wed, 2 Mar 2005 07:21:11 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D6E1U-0000oZ-4k; Tue, 01 Mar 2005 23:31:16 +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 23:31:15 +0300 Message-Id: <1109709075.1329.3.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: Wed, 02 Mar 2005 07:21:12 -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? I've rechecked patch with fresh kernel build and firewire console. It does not panics and does not awake :(=20 As in previous variant it sleeps ok, but on awake it only spin up HDD. No any other activity seen, it does not react on keys, firewire console is dead. It does not answer on network activity. Probably It hangs while try to restore console, and I should try to disable console at all ?=20 Any other ideas ? >Ian --=20 Vladimir B. Grebenchikov vova@fbsd.ru