Re: Using VESA to restore display settings on resume
Anish Mistry <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.mobile |
|---|---|
| Message-ID | <[email protected]> |
On Wednesday 02 March 2005 10:44 pm, Rong-En Fan wrote: > On Mon, 28 Feb 2005 20:26:16 +0000, Ian Dowse <[email protected]> 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 resume issue: hint.psm.0.flags="0x3000" -- Anish Mistry
signature.asc
(application/pgp-signature, 187 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBCJufxxqA5ziudZT0RAkicAJ94Npip/5KH0fbK+lfxdPodC+ZAQwCgrBPw 3A+dUImqzi5vCIYmYUYpVF8= =Ms92 -----END PGP SIGNATURE-----