Date: Thu, 3 Mar 2005 11:44:59 +0800 From: Rong-En Fan <grafan@gmail.com> To: Ian Dowse <iedowse@maths.tcd.ie> Cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume Message-ID: <6eb82e05030219447bdda412@mail.gmail.com> In-Reply-To: <200502282026.aa38504@salmon.maths.tcd.ie> References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 28 Feb 2005 20:26:16 +0000, Ian Dowse <iedowse@maths.tcd.ie> wrote: > > 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 use 3/3's current with this patch on IBM TP X31. I can now successfully suspend/resume in X with dri enable on RADEON! (can't do that before, with dri, after resume screen mess up). reset_video 0 or 1 both works. It even works without vesa module loaded. The only problem is that my tracepoint (psm0) dead after resume. demsg (verbose) and suspend/resume dmesg are both at http://rafan.infor.org/tmp/vesa/ rafan.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e05030219447bdda412>