From owner-freebsd-current@FreeBSD.ORG Fri May 16 20:31:39 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 29A4891; Fri, 16 May 2014 20:31:39 +0000 (UTC) Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA256 (256/256 bits)) (Client CN "mout.kundenserver.de", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 93BEE25FD; Fri, 16 May 2014 20:31:38 +0000 (UTC) Received: from [192.168.178.36] (p57AEF0F7.dip0.t-ipconnect.de [87.174.240.247]) by mrelayeu.kundenserver.de (node=mreue103) with ESMTP (Nemesis) id 0Mfjsa-1WOD6i0rQq-00NABU; Fri, 16 May 2014 22:31:28 +0200 Message-ID: <537675A0.8000108@janh.de> Date: Fri, 16 May 2014 22:31:28 +0200 From: Jan Henrik Sylvester User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: Adrian Chadd , Stefan Ehmann Subject: Re: Thinkpad T410: resume broken References: <53762216.8020205@gmx.net> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:INcbXyLp7/oKtmuzpnL9u8Q0e+zd5z4L/hXf/rBoLW4 SumyNIO8dSdDSQggPpOHLIQT1aGE3+EgCcf0wSZ0u/whoHIUO3 Ij6JnywhMyRrxEyB4fLRZEUzdrvnaGHUJCqLPcmCJqYZXB/pc2 JCNTEQdhlja5zlBk/VG8uZ6Jb2SlDZmd5438UykEbsJ8X1QTJF voDpNgiF08Gr1at2S1JeT5Ufg5CemZAIXeGfh/vhayN4rp3w1N 8NxbfsTF9P9vaq3PMFDLYD6zWg2X6j+dQEEuCkRJ+Xk3rxdokR CO0gFB4d20dvcJQGaMgBLQ8SHkI6w0o41PYL2DylSFnECQRjSV UAXuI7B8ZTyDcI8W0IJE= Cc: Kevin Oberman , current-list freebsd , "freebsd-mobile@freebsd.org" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2014 20:31:39 -0000 On 05/16/2014 20:10, Kevin Oberman wrote: > On Fri, May 16, 2014 at 10:44 AM, Adrian Chadd wrote: > >> Hi! >> >> I wonder what changed between 9.2-RELEASE and 10.0-RELEASE. >> >> Please poke me about this next week. I'm busy this week with work and >> maker faire but I will try to help you later. >> >> (It's possible something like ACPI updates or a driver update has >> broken things.) >> >> >> -a >> > > Does your kernel include VESA? My T320 behaved as you describe until I > removed VESA from my kernel. I think using vt may also fix this without the > need to remove VESA, bug I have not gotten around to confirming this. (Sorry, this is more or less a lengthy "me, too":) I am observing exactly the same on my T510 (not surprisingly, as it is basically the same with a different screen size) using Nvidia (in contract to most other recent mailing list reports, which are using Intel). >From 8.1-RELEASE to 9.2-RELEASE, suspend and resume used to work with a generic kernel (I like generic release kernels and freebsd-update) -- except for a short time, which was due to the Xorg port. Especially 9.X-RELEASE were really stable with all the hardware working after resume (maybe except firewire). After going to 10.0-RELEASE, resuming would briefly turn the screen on, but it would go back to black with the power LED continuing to blink (as it does while sleeping). After a while, I realized that I lost the non-default option ACPI_PM for x11/nvidia-driver installing 10.0. With ACPI_PM for x11/nvidia-driver, I had at least one resume with most of the hardware working: The screen was still unusable being static with colorful lines, but I could ssh into the machine over wireless. I have not had time to try 10-STABLE with vt, but from reading various reports on the lists, that is probably the only way. I hope there will be a vt enabled kernel on the 10.1-RELEAS media, if vt is going to be required even for configurations that would work just fine on 9.X (WITH_NEW_XORG=yes is very usable with x11/nvidia-driver even without vt). >From what you said, you already have ACPI_PM for x11/nvidia-driver as it is listed on the wiki. Have you? Cheers, Jan Henrik