From owner-freebsd-x11@freebsd.org Thu Nov 24 12:51:30 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 423F4C511A7 for ; Thu, 24 Nov 2016 12:51:30 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from proxy.tng.vnc.biz (zimbra-vnc.tngtech.com [83.144.240.98]) (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 DDEF8A3A for ; Thu, 24 Nov 2016 12:51:28 +0000 (UTC) (envelope-from stefan.wendler@tngtech.com) Received: from localhost (localhost [127.0.0.1]) by proxy.tng.vnc.biz (Postfix) with ESMTP id 39E7A1E2E18; Thu, 24 Nov 2016 13:51:18 +0100 (CET) X-Spam-Flag: NO X-Spam-Score: -1.5 X-Spam-Level: X-Spam-Status: No, score=-1.5 tagged_above=-10 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-0.5, LOCAL_FROM_TNG=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Received: from proxy.tng.vnc.biz ([127.0.0.1]) by localhost (proxy.tng.vnc.biz [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id GoRxx94EsegV; Thu, 24 Nov 2016 13:51:17 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by proxy.tng.vnc.biz (Postfix) with ESMTP id 9AA8A1E2FFD; Thu, 24 Nov 2016 13:51:17 +0100 (CET) X-Virus-Scanned: amavisd-new at Received: from proxy.tng.vnc.biz ([127.0.0.1]) by localhost (proxy.tng.vnc.biz [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id f77tM2iUaD-V; Thu, 24 Nov 2016 13:51:17 +0100 (CET) Received: from mbx02.tng.vnc.biz (mbx02.tng.vnc.biz [10.11.11.22]) by proxy.tng.vnc.biz (Postfix) with ESMTP id 834441E2E18; Thu, 24 Nov 2016 13:51:17 +0100 (CET) Date: Thu, 24 Nov 2016 13:51:17 +0100 (CET) From: Stefan Wendler To: "O. Hartmann" Cc: "freebsd-x11@freebsd.org" Message-ID: <808601972.2288955.1479991877510.JavaMail.zimbra@tngtech.com> In-Reply-To: <20161123073745.0394f186@thor.walstatt.dynvpn.de> References: <20161123073745.0394f186@thor.walstatt.dynvpn.de> Subject: Re: nvidia-driver and vt - blank console on FreeBSD 11 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Mailer: Zimbra 8.6.0_GA_1182 (ZimbraWebClient - GC54 (Win)/8.6.0_GA_1182) Thread-Topic: nvidia-driver and vt - blank console on FreeBSD 11 Thread-Index: i/FVxcCAKtfOKrAa57fovKjOXhLq4Q== 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: Thu, 24 Nov 2016 12:51:30 -0000 ----- Original Message ----- > From: "O. Hartmann" > To: "Stefan Wendler" > Cc: "freebsd-x11@freebsd.org" > Sent: Wednesday, November 23, 2016 7:37:45 AM > Subject: Re: nvidia-driver and vt - blank console on FreeBSD 11 > Am Mon, 21 Nov 2016 22:50:29 +0100 > Stefan Wendler schrieb: > >> Hi, >> >> I am using the latest nvidia-driver-367.44_2 (modules nvidia.ko and >> nvidia-modeset.ko have to be loaded in order for X to work) and while X >> works great after I have started X and want to switch back to console. >> Alle ttys are just black. The Keyboard is still working and I can switch >> back to the X session or press Ctrl-C on the black tty and startx again. >> >> My system is a UEFI install and at boot vt_efifb is used automatically >> no matter what I set kern.vty to.except for "sc" of course. With "sc" >> set, the system won't boot because with uefi >> >> I have tried like everything I have found on the web (changing kern.vty, >> setting textmode to 1, etc). But I have also found that nvidia and vt >> have had some problems when FreeBSD 11 was still CURRENT and that this >> was fixed? >> >> Is this an open bug again? Is there a way for me to set an option/add a >> patch or something to make ttys work again after I have started X? >> >> Thx for your support, >> Stefan >> _______________________________________________ >> 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" > > This phenomenon is well known since a couple of months for now. On Quadro GPUs, > the > console is black in our case and with consumer cards we have a garbled/blocky > console. > The Quadro based GPUs tend to refuse a reboot as long as the nvidia-modeset.ko > kernel > module is loaded: "shutdown -r now" remains in a kind of endless loop. > > Maybe nVidia has not been informed about this. I'm using 370.28 with UEFI/vt and > nonUEFI/vt and it is still the same. > > Regards, > O. Hartmann > > -- > O. Hartmann I went to the nividia-page to maybe write the support-team when I have seen this changelog(*) entry for the current version 375.20 - Added support for FreeBSD 11.0-RELEASE This version contains some other fixes that have to do with blank consoles(375.20) and vt stuff (375.10) as well. Even though they are not directly related to our problem. I will try this version tonight and report back. Hopefully this will fix the problems ... (*)http://www.nvidia.com/Download/driverResults.aspx/111598/en-us Cheers, Stefan