From owner-freebsd-stable@FreeBSD.ORG Fri Mar 19 03:42:51 2010 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CFDED106564A for ; Fri, 19 Mar 2010 03:42:51 +0000 (UTC) (envelope-from smithi@nimnet.asn.au) Received: from sola.nimnet.asn.au (paqi.nimnet.asn.au [115.70.110.159]) by mx1.freebsd.org (Postfix) with ESMTP id 50A868FC0C for ; Fri, 19 Mar 2010 03:42:50 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by sola.nimnet.asn.au (8.14.2/8.14.2) with ESMTP id o2J3gijp034173; Fri, 19 Mar 2010 14:42:44 +1100 (EST) (envelope-from smithi@nimnet.asn.au) Date: Fri, 19 Mar 2010 14:42:43 +1100 (EST) From: Ian Smith To: Kevin Oberman In-Reply-To: <20100318153342.4450C1CC26@ptavv.es.net> Message-ID: <20100319142102.P85436@sola.nimnet.asn.au> References: <20100318153342.4450C1CC26@ptavv.es.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: stable@freebsd.org, delphij@freebsd.org Subject: Re: DPMS broken on ThinkPad T43 since update for amd64 support X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2010 03:42:51 -0000 On Thu, 18 Mar 2010, Kevin Oberman wrote: > Since the update of DPMS to support amd64 on March 2, it has broken > rather badly on my ThinkPad T43 laptop. The problem showed up on > 8-stable built on March 3 and is still present after an update to stable > of March 17. > > When in vty text mode, after the idle normal delay, the display blanks, > but the backlight remains on, so the P in DPMS seems to be less than > effective. At that point, the non-graphics display is dead. It never > comes back when characters are entered. I can't get the display to come > back without a reboot. > > I can, however, start X (and Gnome) and everything is fine. But > switching back to any vty results in a blank screen. > > Any idea what happened and if there is a fix or workaround? Any data I > can collect? Have you tried kldloading vesa? Might be a workaround until you find a proper fix? Had a similar issue with my T23 at one stage on 7.0, after a suspend/resume cycle, which hw.syscons.sc_no_suspend_vtswitch=1 also helped .. no idea how the T43 might respond to the latter. FWIW, Ian