From owner-freebsd-mobile@FreeBSD.ORG Thu Mar 3 07:40:14 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 C96EA16A4CE for ; Thu, 3 Mar 2005 07:40:14 +0000 (GMT) Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E6B643D58 for ; Thu, 3 Mar 2005 07:40:14 +0000 (GMT) (envelope-from vova@vbook.fbsd.ru) Received: from vova by vbook.fbsd.ru with local (Exim 4.44 (FreeBSD)) id 1D6jYw-00076q-5s; Thu, 03 Mar 2005 09:11:54 +0300 From: Vladimir Grebenschikov To: Kevin Oberman In-Reply-To: <20050302220235.DB1E95D08@ptavv.es.net> References: <20050302220235.DB1E95D08@ptavv.es.net> Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable Organization: SWsoft Date: Thu, 03 Mar 2005 09:11:53 +0300 Message-Id: <1109830313.1629.8.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.1.5 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov cc: Ian Dowse 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: Thu, 03 Mar 2005 07:40:15 -0000 =F7 =D3=D2, 02/03/2005 =D7 14:02 -0800, Kevin Oberman =D0=C9=DB=C5=D4: >> From: Vladimir Grebenschikov >> Date: Thu, 03 Mar 2005 00:36:51 +0300 >> Sender: Vladimir Grebenschikov >>=20 >> =F7 =D3=D2, 02/03/2005 =D7 11:18 -0800, Kevin Oberman =D0=C9=DB=C5=D4: >> >> From: Vladimir Grebenschikov >> >> Date: Tue, 01 Mar 2005 23:31:15 +0300 >> >> Sender: owner-freebsd-mobile@freebsd.org >> >>=20 >> >> =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 wri= tes> : >> >> >>In message <1109545918.1537.8.camel@localhost>, Vladimir Grebenschi= kov> writes: >> >> >>>Also if I try this patch with vesa module loaded it just carsh in = vm8> 6 >> >> >>>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= ? >> >>=20 >> >> I've rechecked patch with fresh kernel build and firewire console. >> >>=20 >> >> 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 conso= le >> >> is dead. >> >> It does not answer on network activity. >> >>=20 >> >> Probably It hangs while try to restore console, and I should try to >> >> disable console at all ?=20 >> > >> >Is the disk active LED on? Many systems have had trouble with this, >> >although I thought Soren had fixed this. >>=20 >> Both led and sound, it spin-up, shows some activity by both led and >> sound, and then stop any activity. >>=20 >> Probably I should try kernel without ata ? (only md for root)=20 > >Only if the LED comes on and stays on is it an ATA issue. If it seems to >come back but never finishes, it is something else. > >Can you connect to the system over the net after resume?=20 No, I can't ping machine, and firewire console is dead. >If so, it's probably a display issue, as you seem to have suspected. I was= just >bringing up the ATA issue in case you really had two problems. Seems >like you do not. Anyway, I'll try kernel without ATA to be sure. --=20 Vladimir B. Grebenchikov vova@fbsd.ru