Date: Sat, 5 Mar 2005 21:02:50 +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: <6eb82e050305050284084ca@mail.gmail.com> In-Reply-To: <6eb82e05030219447bdda412@mail.gmail.com> References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Mar 2005 11:44:59 +0800, Rong-En Fan <grafan@gmail.com> wrote: > > 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 I was wrong. drm was broken that time, after apply patch on cvs-all with dri, after resume, my screen mess up as before. rafan. > works without vesa module loaded. The only problem is that my tracepoint > (psm0) dead after resume.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e050305050284084ca>