From owner-freebsd-x11@freebsd.org Wed Aug 31 15:41:16 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 E4E9BBCACC8 for ; Wed, 31 Aug 2016 15:41:16 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f50.google.com (mail-it0-f50.google.com [209.85.214.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B4C9FBBF; Wed, 31 Aug 2016 15:41:16 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f50.google.com with SMTP id e124so50924213ith.0; Wed, 31 Aug 2016 08:41:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=YQ6N9Za9x1E4ElSjohA57x+Z3ax16VkOUN0vfStxZno=; b=eGRFD4BHMGJ9qGLTB3szaPgQfmSemUrElh/rzFciDBTsbhmSpMV6NI7CUmaKegT2FS cNAAtj3RB6ysU0WCfMF51xmSYIXeaxyCf6PPfW4c6STk40HQRVpZcVMr7ciL+mouCFrd Ac3ib1Y36kHYlHlfGs69oUyPxMWDexCMTqjxkdPRf3CvemoHnfwtVjQkTYqcv8oe1Osi wO1avbfJWFizltgkNX0RZlJQJCoLLWa3taRjdsPc3BV8QlF3ZXFPn0i9nq+LCiTe+Bho tW9oAKQmOXDlnftfBGuQg8LPzl4j9un2iHVOuErH5DKUOw0Mm2FZ//3tFR9eq2lEdXPZ ODrA== X-Gm-Message-State: AE9vXwN/ma3XsCil1Nfpyg8q/XHARf7B13zrHx2i+utgBeR70WPAyqRwMZsx2uNU8ZJ8wA== X-Received: by 10.36.210.68 with SMTP id z65mr15053067itf.32.1472657612174; Wed, 31 Aug 2016 08:33:32 -0700 (PDT) Received: from mail-it0-f42.google.com (mail-it0-f42.google.com. [209.85.214.42]) by smtp.gmail.com with ESMTPSA id v7sm5549830itd.6.2016.08.31.08.33.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Aug 2016 08:33:31 -0700 (PDT) Received: by mail-it0-f42.google.com with SMTP id e124so14901328ith.0; Wed, 31 Aug 2016 08:33:31 -0700 (PDT) X-Received: by 10.107.175.223 with SMTP id p92mr7242348ioo.7.1472657611519; Wed, 31 Aug 2016 08:33:31 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.36.220.129 with HTTP; Wed, 31 Aug 2016 08:33:30 -0700 (PDT) In-Reply-To: <20160831134459.176e764b@freyja.zeit4.iv.bundesimmobilien.de> References: <20160829145229.GA42512@elch.exwg.net> <20160829180438.4e64307d.ohartman@zedat.fu-berlin.de> <52f8372b-9da0-9552-25a6-99bda9bbb769@madpilot.net> <20160830135321.0f9b1f71@freyja.zeit4.iv.bundesimmobilien.de> <20160831134459.176e764b@freyja.zeit4.iv.bundesimmobilien.de> From: Conrad Meyer Date: Wed, 31 Aug 2016 08:33:30 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: After nvidia 346.96 to 367.35 upgrade, no valid display anymore To: "O. Hartmann" Cc: Guido Falsi , Jan Henrik Sylvester , Alexey Dokuchaev , x11-list freebsd Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-x11@freebsd.org X-Mailman-Version: 2.1.22 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, 31 Aug 2016 15:41:17 -0000 I've gone ahead and filed https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212287 to track this update. On Wed, Aug 31, 2016 at 4:44 AM, O. Hartmann wrote: > On Tue, 30 Aug 2016 14:57:09 +0200 > Guido Falsi wrote: > >> On 08/30/16 13:53, O. Hartmann wrote: >> > On Mon, 29 Aug 2016 18:17:40 +0200 >> > Guido Falsi wrote: >> > >> >> On 08/29/16 18:04, O. Hartmann wrote: >> >> >> >>>> BTW I also have another minor issue now, the text VTYs display some >> >>>> ascii art style garbage. It also changes if I press keys, so they do >> >>>> react to input. >> >>> >> >>> This is a well known issue (see PR >> >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201340). >> >>> >> >>> It seems vt() is broken with the new nVidia code, which is, by the way, >> >>> 367.44 right now, .35 has some issues with dark screen at first Xorg init >> >>> (after reboot) for me on GTX960, which is gone with .44 >> >> >> >> I see, thanks for the info. It's a minor issue to me, so I am in no >> >> hurry for this to be fixed. >> >> >> > >> > having a dark screen initially when using xd/Xorg may be a "minor issue for >> > you", it is a medium issue for others if they do not know how to fix it >> > (Ctrl-Alt-FX to get to a console which is black on vt() and then go back >> > with Alt-FX to the tty where the X is active). >> >> The "minor issue" expression was related to having VTYs display garbage >> when X11 works fine. >> >> Having X11 suddenly not working is a major issue, in fact I suggested >> adding a note in UPDATING to help people sort it out. >> >> Sorry if I did not make it perfectly clear. >> > > The problem could be solved by simply changing 367.35 to 367.44. The latter > version still has the vt() issue, but not the dark screen on some graphic > workstations as described. > > Maybe it is logically a new PR, since the update towards a refurbished > framework has already been done. > > Kind regards, > > Oliver Hartmann > _______________________________________________ > 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"