Date: Thu, 3 Mar 2005 21:52:48 +0800 From: Rong-En Fan <grafan@gmail.com> To: Anish Mistry <mistry.7@osu.edu> Cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume Message-ID: <6eb82e0503030552c9506e6@mail.gmail.com> In-Reply-To: <200503030533.21126.mistry.7@osu.edu> References: <200502281016.aa49779@salmon.maths.tcd.ie> <200502282026.aa38504@salmon.maths.tcd.ie> <6eb82e05030219447bdda412@mail.gmail.com> <200503030533.21126.mistry.7@osu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 3 Mar 2005 05:33:12 -0500, Anish Mistry <mistry.7@osu.edu> wrote: > On Wednesday 02 March 2005 10:44 pm, Rong-En Fan wrote: > > 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. > > > Does adding the following to your /boot/device.hints to fix the mouse > resume issue: > hint.psm.0.flags="0x3000" Yes, thanks. And in fact, 0x2000 works :) BTW, 0x2000 is PSM_HOOKRESUME in kernel conf. Regards, rafan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6eb82e0503030552c9506e6>