From owner-freebsd-stable@FreeBSD.ORG Wed Oct 8 19:46:18 2014 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B79CD6C8; Wed, 8 Oct 2014 19:46:18 +0000 (UTC) Received: from mail-wi0-x229.google.com (mail-wi0-x229.google.com [IPv6:2a00:1450:400c:c05::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 2E5B7226; Wed, 8 Oct 2014 19:46:18 +0000 (UTC) Received: by mail-wi0-f169.google.com with SMTP id cc10so12978267wib.0 for ; Wed, 08 Oct 2014 12:46:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:references:date:message-id :mime-version:content-type; bh=Vygb0oW0KYrokKaYbpuPQkbxB1no3UgL/VX2OaKUX0E=; b=w+z7WuQJiWKig1HTly4lY/jraaTU6BpLE8tPX6+EuINNdHquheB5VpL4iZxZlpQaEs 8ANjoXUgt4lGO0zJgNS4RqtzQPBHAFzQCp6YB5WoNFhvoFvbapb9v/Khs1UY+u+OA+y6 IdMVZlZhHzZs7DXxewACcMJLJkCmjlAID8epVbZ3sQcZ2SuZ58rebH9CL5Su12sa1xAc knHmwxCTne0lg0XN9fOTtaUYeD3IXWytyXVkOvDM6fKbbHnK898zNJfoib6akmMjcciO hz5vqNXpWUanMivIwKQNi/IYFjTUtY0Dx/fg2n6Yq/9aYIonidOnVUSF1ZqAR+Qr4pIr /rjw== X-Received: by 10.194.249.164 with SMTP id yv4mr14042731wjc.34.1412797576408; Wed, 08 Oct 2014 12:46:16 -0700 (PDT) Received: from localhost (ns314608.ip-188-165-240.eu. [188.165.240.102]) by mx.google.com with ESMTPSA id y5sm3204198wix.10.2014.10.08.12.46.14 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 08 Oct 2014 12:46:15 -0700 (PDT) From: marekrud@gmail.com To: John Baldwin Subject: Re: vt does not resume properly after zzz In-Reply-To: <1526283.Onb3mfWQFN@ralph.baldwin.cx> References: <864mvqfabt.fsf@gmail.com> <1506050.d54hhbRZ6V@ralph.baldwin.cx> <86h9ze9zi9.fsf@gmail.com> <1526283.Onb3mfWQFN@ralph.baldwin.cx> Date: Wed, 08 Oct 2014 21:46:29 +0200 Message-ID: <86d2a29wfe.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain Cc: Kevin Oberman , freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 Oct 2014 19:46:18 -0000 John Baldwin writes: > On Wednesday, October 08, 2014 08:39:58 PM marekrud@gmail.com wrote: >> John Baldwin writes: >> > On Wednesday, October 08, 2014 05:47:14 PM marekrud@gmail.com wrote: >> >> John Baldwin writes: >> >> > On Saturday, October 04, 2014 04:24:11 PM Kevin Oberman wrote: >> >> >> On Thu, Oct 2, 2014 at 1:52 PM, wrote: >> >> >> > - DELL M1330 with Intel graphics card (Xorg used to work with intel >> >> >> > >> >> >> > driver >> >> >> >> >> >> All of the information I can find says that this unit has nVidia >> >> >> graphics, >> >> >> but Intel may be a low-priced option, as well. Again, >> >> >> /var/log/Xorg.0.log >> >> >> should have this information as should "pciconf -lv | grep -A3 vga". >> >> >> This >> >> >> laptop goes back to 2007, so it should be using the old UMS Intel >> >> >> graphics. >> >> >> It should not be using VESA, but if it is, that might point out a >> >> >> common >> >> >> thread. >> >> >> >> >> >> I don't know the details and the actual problem was never identified, >> >> >> but >> >> >> I >> >> >> know that some systems needed to have a kernel built with "NOOPTION >> >> >> VESA" >> >> >> to get it to resume. I had this problem on my Lenovo T520 (which I am >> >> >> using >> >> >> to send this reply). >> >> > >> >> > That doesn't apply to his system. I have an older HP netbook (i386) >> >> > that >> >> > resumes fine in text mode with syscons, but does not resume in text >> >> > mode >> >> > in >> >> > vt(4). (This is a case where the VESA bits actually help rather than >> >> > hurt.) However, if I kldload the kms driver ('kldload i915kms') when >> >> > using vt(4), then resume works fine (and it also works fine in X). >> >> > >> >> > Marek, >> >> > >> >> > Can you try 'kldload i915kms' before you suspend and see if that fixes >> >> > your >> >> > issue? >> >> >> >> 1. On the laptop with Intel graphics card, when i915kms is loaded, vt >> >> resumes without problems. On the laptop with the ATI graphics card >> >> (Radeon HD 8240), I use vesa driver at the moment, and it does not >> >> resume the screen. >> > >> > Let's just be clear: >> > >> > For laptop 1 with Intel graphics card: >> > - syscons + text mode: resumes ok >> > - syscons + X: resumes ok? >> > - vt: blank screen >> > - vt + i915kms + text mode: resumes ok >> > - vt + X: resumes ok? >> >> For laptop 1 with Intel graphics card: >> - syscons + text mode: resumes ok >> - syscons + X: resumes ok >> - vt: blank screen >> - vt + i915kms + text mode: resumes ok >> - vt + X: blank screen >> - vt + i915kms + X: resumes ok > > Ok, this is similar to my little HP netbook where-in suspend/resume on the > console without kms loaded is a regression relative to syscons. This is not > trivial to fix I'm afraid, though the idea would be to take the existing VESA > code for suspend and resume from syscons and port it to vt, but in a way that > i915kms can disable it when it is loaded. > >> > For laptop 2 with ATI graphics card: >> > - syscons + text mode: resumes ok >> > - syscons + X: resumes ok? >> > - vt + text mode: blank screen >> > - vt + X: ??? >> >> For laptop 2 with ATI graphics card: >> - syscons + text mode: resumes ok >> - syscons + X: resumes ok >> - vt + text mode: blank screen >> - vt + X: blank screen > > I assume with X here that radeonkms is not being auto-loaded? (i.e. you are > using the vesa driver or some such)? Yes, using vesa. >> > For ATI, there is a radeonkms driver I believe. Can you try loading that >> > when you are using vt(4) to see if it makes a difference? >> >> - vt + text mode + radeonkms: blank screen > > Ok. You might try e-mailing dumbbell@ about the laptop with an ATI card as he > is maintaining the radeonkms bits. Thank you, I'll try that. Marek