From owner-freebsd-x11@freebsd.org Tue Sep 6 05:09:34 2016 Return-Path: Delivered-To: freebsd-x11@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 18D3CA9DEF9 for ; Tue, 6 Sep 2016 05:09:34 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D198E695; Tue, 6 Sep 2016 05:09:33 +0000 (UTC) (envelope-from ohartman@mail.zedat.fu-berlin.de) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost.zedat.fu-berlin.de (Exim 4.85) with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id <1bh8dQ-0041a3-Pl>; Tue, 06 Sep 2016 07:09:24 +0200 Received: from p578a69f9.dip0.t-ipconnect.de ([87.138.105.249] helo=hermann) by inpost2.zedat.fu-berlin.de (Exim 4.85) with esmtpsa (TLSv1.2:AES256-GCM-SHA384:256) (envelope-from ) id <1bh8dQ-002u4A-Hl>; Tue, 06 Sep 2016 07:09:24 +0200 Date: Tue, 6 Sep 2016 07:09:23 +0200 From: "Hartmann, O." To: Conrad Meyer Cc: blubee blubeeme , x11-list freebsd Subject: Re: MacBook Pro 11,3 Nvidia Drivers Message-ID: <20160906070923.1c8141bb@hermann> In-Reply-To: References: Organization: FU Berlin MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Originating-IP: 87.138.105.249 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: X11 on FreeBSD -- maintaining and support List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Sep 2016 05:09:34 -0000 On Mon, 5 Sep 2016 20:53:34 -0700 Conrad Meyer wrote: > Hi, > > Have you tried changing 'nvidia_load="YES"' to > 'nvidia-modeset_load="YES"'? It's documented in UPDATING and > pkg-message, but I understand this is a surprising change. At least > one other user has reported a garbled screen on 367.44, but I don't > know what hardware they had. > > Best, > Conrad > > On Mon, Sep 5, 2016 at 8:39 PM, blubee blubeeme > wrote: > > I seem to be having issues recently when I build nvidia-driver from > > ports. > > > > Installing 346.44 from pkg works fine but If I go and install > > 367.44 from ports then my screen gets garbled and the nvidia driver > > doesn't seem to get loaded, even though nvidia_load="YES" is still > > in /boot/loader.con but if I revert back to 346.44 then things work > > again. > > > > Is this a known issue? How can I fix/ avoid this? > > > > _______________________________________________ > > freebsd-x11@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > > To unsubscribe, send any mail to > > "freebsd-x11-unsubscribe@freebsd.org" > _______________________________________________ > freebsd-x11@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-x11 > To unsubscribe, send any mail to "freebsd-x11-unsubscribe@freebsd.org" Prior to 367.35, I also ran into an garbled screen issue once with the new modeset driver. This happened on all nVidia Quadro based cards we have around here, at least that built into my workstation, a Quadro NV315, one of the low-end Quadros nVidia offers. But that has gone with the most recent series of divers. The garbled console is still with consumer GPUs (GTX 960, GTX 560Ti) when using UEFI with required vt() console driver. The above mentioned Quadro boards have a black console - no garbled, no distorted screen so far but black. This goes away immediately after unloading the nvidia_modeset.ko kernel module. Kind regards, Oliver