Comment # 20 on bug 964429 from Egbert Eich

(In reply to Ulrich Windl from comment #19)
> (In reply to Egbert Eich from comment #18)
> > Without knowledge of your DM we cannot find out where it logs to, though.
> 
> GNOME, so I guess gdm.
> 
> > The screen usually goes into power save mode when it's idle for so long.
> 
> I know.
> 
> > Moreover, this log file is for the fbdev driver which is unlikely to show a
> > black screen if your console was working at all. Also it is even more
> > unlikely that the screen is loosing the video signal when using this driver.
> 
> I was worried about the message: "Use of other console drivers including,
> but not limited to, vesafb, may result in corruption and stability problems,
> and is not supported."

Right. I see this as a disclaimer so that NVIDIA does not have to support
and debug this if anything fails due to this.

> > Currently, I see two issues:
> > 1. the G03 driver you've used reads a defective EDID extension block which
> > is supplied by your monitor. So either the read procedure is wrong or the
> > block sent by the monitor - in which case the NVIDIA driver should simply
> > ignore it.
> 
> I suspected my KVM switch to need a reset (which I did in the meantime).

You should have done this right away.

> > This is something for NVIDIA to fix.
> > 2. when you deinstall the G03 driver you will get the G04 driver (according
> > to your comment #2). Not sure why this happened. This is something for us to
> > determine. If the G04 packages support your hardware (PCI ID: 10de:0640) as
> > well, it should have worked. 
> > Have you rebooted in between?
> 
> AFAIR: No (it takes too much time)

Now I'm getting slightly upset. You do not want to reboot the system because 
it takes too much time although the kernel driver has changed - but you expect 
me to either spend my company's or my spare time in supporting you?

Sorry, I'm ending this here and now.