After nvidia 346.96 to 367.35 upgrade, no valid display anymore

[O. Hartmann]

On Tue, 30 Aug 2016 14:57:09 +0200
Guido Falsi <mad at madpilot.net> wrote:

> On 08/30/16 13:53, O. Hartmann wrote:
> > On Mon, 29 Aug 2016 18:17:40 +0200
> > Guido Falsi <mad at 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