Date: Wed, 31 Aug 2016 08:33:30 -0700 From: Conrad Meyer <cem@freebsd.org> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: Guido Falsi <mad@madpilot.net>, Jan Henrik Sylvester <me@janh.de>, Alexey Dokuchaev <danfe@freebsd.org>, x11-list freebsd <freebsd-x11@freebsd.org> Subject: Re: After nvidia 346.96 to 367.35 upgrade, no valid display anymore Message-ID: <CAG6CVpVnyAhYhC3PZh6qTpeZGCNWkv9VzDb-qZ4aTDehq7VLYw@mail.gmail.com> In-Reply-To: <20160831134459.176e764b@freyja.zeit4.iv.bundesimmobilien.de> References: <c65ce344-77b0-cb82-d2a1-ca8f785886eb@janh.de> <20160829145229.GA42512@elch.exwg.net> <a34b977f-429b-27bb-2912-e419245250da@madpilot.net> <20160829180438.4e64307d.ohartman@zedat.fu-berlin.de> <52f8372b-9da0-9552-25a6-99bda9bbb769@madpilot.net> <20160830135321.0f9b1f71@freyja.zeit4.iv.bundesimmobilien.de> <e5200c46-9c77-7cc2-57af-f67c6564c7e1@madpilot.net> <20160831134459.176e764b@freyja.zeit4.iv.bundesimmobilien.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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 <ohartman@zedat.fu-berlin.de> wrote: > On Tue, 30 Aug 2016 14:57:09 +0200 > Guido Falsi <mad@madpilot.net> wrote: > >> On 08/30/16 13:53, O. Hartmann wrote: >> > On Mon, 29 Aug 2016 18:17:40 +0200 >> > Guido Falsi <mad@madpilot.net> 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpVnyAhYhC3PZh6qTpeZGCNWkv9VzDb-qZ4aTDehq7VLYw>