Date: Mon, 05 May 2014 06:25:21 +0000 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Ian Smith <smithi@nimnet.asn.au> Cc: Kevin Oberman <rkoberman@gmail.com>, Adrian Chadd <adrian@freebsd.org>, "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: proposal: set default lid state to S3, performance/economy Cx states to Cmax Message-ID: <85787.1399271121@critter.freebsd.dk> In-Reply-To: <20140505153421.W11699@sola.nimnet.asn.au> References: <CAJ-Vmo=mUtpjgVwNHg8af05vCxVchZdsaekR9_Wf-pOfFjnABQ@mail.gmail.com> <20140505011654.O11699@sola.nimnet.asn.au> <2223.1399233644@critter.freebsd.dk> <CAJ-Vmo=aCtMb-Tavz86GbwENiT5Oe1N8Ju7%2Bpw55XAZCWG3HEw@mail.gmail.com> <20140505153421.W11699@sola.nimnet.asn.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20140505153421.W11699@sola.nimnet.asn.au>, Ian Smith writes: >I need to do more tests on stable/9; it didn't work with the offered >workarounds on 9.2-RELEASE (leaving VESA out of kernel leaves me with no >screen on resume in console mode, setting sysctl dev.[ue]hci.*.wake=1 Do we have a canonical page with all the various workarounds one should attempt in order to get suspend/resume to work ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?85787.1399271121>