Date: Tue, 01 Mar 2005 11:52:29 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume Message-ID: <1109667149.1098.5.camel@localhost> In-Reply-To: <200502282026.aa38504@salmon.maths.tcd.ie> References: <200502282026.aa38504@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
=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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1109667149.1098.5.camel>