Date: Thu, 3 Mar 2005 05:33:12 -0500 From: Anish Mistry <mistry.7@osu.edu> To: Rong-En Fan <grafan@gmail.com> Cc: freebsd-mobile@freebsd.org Subject: Re: Using VESA to restore display settings on resume Message-ID: <200503030533.21126.mistry.7@osu.edu> 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
--nextPart3522222.cV02p8EnUv Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 02 March 2005 10:44 pm, Rong-En Fan wrote: > On Mon, 28 Feb 2005 20:26:16 +0000, Ian Dowse <iedowse@maths.tcd.ie>=20 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. > Does adding the following to your /boot/device.hints to fix the mouse=20 resume issue: hint.psm.0.flags=3D"0x3000" =2D-=20 Anish Mistry --nextPart3522222.cV02p8EnUv Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCJufxxqA5ziudZT0RAkicAJ94Npip/5KH0fbK+lfxdPodC+ZAQwCgrBPw 3A+dUImqzi5vCIYmYUYpVF8= =Ms92 -----END PGP SIGNATURE----- --nextPart3522222.cV02p8EnUv--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200503030533.21126.mistry.7>