From owner-freebsd-x11@FreeBSD.ORG Wed Jan 29 15:51:03 2014 Return-Path: Delivered-To: freebsd-x11@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 75A12BCE; Wed, 29 Jan 2014 15:51:03 +0000 (UTC) Received: from wp376.webpack.hosteurope.de (wp376.webpack.hosteurope.de [IPv6:2a01:488:42::50ed:8591]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 32B591861; Wed, 29 Jan 2014 15:51:03 +0000 (UTC) Received: from xdsl-78-34-137-130.netcologne.de ([78.34.137.130] helo=dijkstra-old.cruwe.de); authenticated by wp376.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) id 1W8XPo-0008Gc-1P; Wed, 29 Jan 2014 16:51:00 +0100 Date: Wed, 29 Jan 2014 16:50:58 +0100 From: "Christopher J. Ruwe" To: freebsd-questions@freebsd.org Subject: Re: Black screen and strange error on GeForce GT 730M / Thinkpad T440p Message-ID: <20140129165058.59990d06@dijkstra-old.cruwe.de> In-Reply-To: <20140127010351.2e450a9b@dijkstra-old.cruwe.de> References: <20140127010351.2e450a9b@dijkstra-old.cruwe.de> X-Mailer: Claws Mail 3.9.3 (GTK+ 2.24.22; amd64-portbld-freebsd9.2) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-bounce-key: webpack.hosteurope.de;cjr@cruwe.de;1391010663;48ea769e; Cc: danfe@FreeBSD.org, freebsd-x11@freebsd.org X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jan 2014 15:51:03 -0000 On Mon, 27 Jan 2014 01:03:51 +0100 "Christopher J. Ruwe" wrote: > I have got a new Thinkpad T440p with dual Intel / Nvidia graphics. As > Intel Haswell is of now unspupported I had high hopes for the nvidia > GPU. However, with x11/nvidia-driver I get a black screen and > following error message on dmesg: > > nvidia0: on vgapci0 > vgapci0: child nvidia0 requested pci_enable_io > vgapci0: child nvidia0 requested pci_enable_io > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch > - Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) > ACPI Error: Field [TBF3] at 270336 exceeds Buffer [NULL] size 262144 > (bits) (20130823/dsopcode-249) ACPI Error: Method parse/execution > failed [\134_SB_.PCI0.PEG_.VID_.GETB] (Node 0xfffff80005341e00), > AE_AML_BUFFER_LIMIT (20130823/psparse-553) ACPI Error: Method > parse/execution failed [\134_SB_.PCI0.PEG_.VID_._ROM] (Node > 0xfffff80005341e40), AE_AML_BUFFER_LIMIT (20130823/psparse-553) ACPI > Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch - > Found [Buffer], ACPI requires [Package] (20130823/nsarguments-97) em0: > link state changed to UP ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: > Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] > (20130823/nsarguments-97) > > I updated BIOS with > http://support.lenovo.com/en_US/downloads/detail.page?DocID=DS037576 > to have the newsest version. > > > I have seen such an error message reported to the letter in Sep '13 by > Hiren. Can anybody help me understand what's happening here, I have > absolutely no idea what that should mean. > > Thanks and cheers, cc'ing MAINTAINER of x11/nvidia-driver and freebsd-x11 After some investigation, it appears that due to "errors" in the acpi implementation, the driver issues non-conforming acpi calls. Similiar problems have been reported on Archlinux. https://bbs.archlinux.org/viewtopic.php?id=170074 https://bugs.archlinux.org/task/37465 https://github.com/Bumblebee-Project/bbswitch/issues/65 I have opened a topic on devtalk.nvidia.com https://devtalk.nvidia.com/default/topic/680155/freebsd/x11-nvidia-driver-331-20-malfunction/ I have can be of any assistance debugging, please say so. Thanks for any attention, -- Christopher TZ: GMT + 1h GnuPG/GPG: 0xE8DE2C14 FreeBSD 9.2-STABLE #1 r256184: Thu Oct 10 19:12:54 CEST 2013 cjr@dijkstra.cruwe.de:/usr/obj/usr/home/cjr/media/src/freebsd/base/stable/9/sys/GEN_WDTRACE Punctuation matters: "Lets eat Grandma." or "Lets eat, Grandma." - Punctuation saves lives. "A panda eats shoots and leaves." or "A panda eats, shoots, and leaves." - Punctuation teaches proper biology. "With sufficient thrust, pigs fly just fine. However, this is not necessarily a good idea. It is hard to be sure where they are going to land, and it could be dangerous sitting under them as they fly overhead." (RFC 1925)