Date: Fri, 6 Aug 2010 08:15:13 +0400 From: Oleg Sharoyko <osharoiko@gmail.com> To: Christian Zander <czander@nvidia.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: PCI config space is not restored upon resume (macbook pro) Message-ID: <AANLkTim-xFd9ve=M0iWBZRHrysSQ=aRGz8_1O1mT%2BW0f@mail.gmail.com> In-Reply-To: <20100805200022.GB3610@panther.nvidia.com> References: <AANLkTikMFhG1QLDf4raf%2BrxOKhobjoA-dRbUew2-8KeF@mail.gmail.com> <201008041112.28704.jhb@freebsd.org> <AANLkTimQA9hJMB_r7c9gRnEBzu4e1yZ5S8sO89ZT9_cW@mail.gmail.com> <201008051145.53737.jhb@freebsd.org> <AANLkTimZxusSpj6BqKAYO_6YPCWVLW2hv_33K7C1rOus@mail.gmail.com> <20100805200022.GB3610@panther.nvidia.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6 August 2010 00:00, Christian Zander <czander@nvidia.com> wrote: > Neither the `nv' nor the `vesa' driver have support for power > management. You'll typically only be able to get X back > with those drivers if you're starting it from scratch following > an S4 cycle, or an S3 cycle that involved a POST (either > issued by the SBIOS or via software). Actually, this is exactly what I was trying to do. And I suspect that it doesn work, because I don't have bios emulation initialized properly. > When using the NVIDIA driver, you will need to make sure that > you're using 256.44, you'll need to be running X at the time of > entry to S3/S4, and you'll need to make sure you've switched > away from X's VT (this didn't happen automatically on FreeBSD > last time I checked). I'll give 256.44 a try, but at first I'll try to fix bios emulation issues. -- Oleg Sharoyko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTim-xFd9ve=M0iWBZRHrysSQ=aRGz8_1O1mT%2BW0f>