http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c2 --- Comment #2 from Ulrich Windl --- I tried booting the previous kernel (via GRUB menu), but that didn't change a thing. Next thing I tried was to remove the Nvidia "G03" packages via Yast software management, and surprisingly those modules were not removed, but replaced with Nvidia "G04" modules: nvidia-uvm-gfxG04-kmp-default-352.79_k4.1.12_1-19.1.x86_64 Mon Feb 1 13:12:37 2016 x11-video-nvidiaG04-352.79-19.1.x86_64 Mon Feb 1 13:09:20 2016 nvidia-computeG04-352.79-19.1.x86_64 Mon Feb 1 13:09:15 2016 nvidia-glG04-352.79-19.1.x86_64 Mon Feb 1 13:09:01 2016 nvidia-gfxG04-kmp-default-352.79_k4.1.12_1-19.1.x86_64 Mon Feb 1 13:08:06 2016 These modules cauise a complete failure to star tthe X server (it seems). I had to switch to the text console. There I removed those "G04" packets (which worked). Then I could start an X session with the usual resolution again. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c4 --- Comment #4 from Ulrich Windl --- Created attachment 663997 --> http://bugzilla.opensuse.org/attachment.cgi?id=663997&action=edit Xorg.1.log, the working case without the Nvidia packages -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c6 Takashi Iwai changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |X11 3rd Party Driver Assignee|kernel-maintainers@forge.pr |xorg-maintainer-bugs@forge. |ovo.novell.com |provo.novell.com QA Contact|qa-bugs@suse.de |sndirsch@suse.com --- Comment #6 from Takashi Iwai --- (In reply to Ulrich Windl from comment #2)

I tried booting the previous kernel (via GRUB menu), but that didn't change a thing.

So this is no kernel regression, as it seems.

Next thing I tried was to remove the Nvidia "G03" packages via Yast software management, and surprisingly those modules were not removed, but replaced with Nvidia "G04" modules: nvidia-uvm-gfxG04-kmp-default-352.79_k4.1.12_1-19.1.x86_64 Mon Feb 1 13:12:37 2016 x11-video-nvidiaG04-352.79-19.1.x86_64 Mon Feb 1 13:09:20 2016 nvidia-computeG04-352.79-19.1.x86_64 Mon Feb 1 13:09:15 2016 nvidia-glG04-352.79-19.1.x86_64 Mon Feb 1 13:09:01 2016 nvidia-gfxG04-kmp-default-352.79_k4.1.12_1-19.1.x86_64 Mon Feb 1 13:08:06 2016

It's because of the dependency, I suppose.

These modules cauise a complete failure to star tthe X server (it seems). I had to switch to the text console. There I removed those "G04" packets (which worked). Then I could start an X session with the usual resolution again.

So, this looks more like an issue of Nvidia stuff. Changed the component. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c7 --- Comment #7 from Stefan Dirsch --- Monitor could not be detected: [ 371.712] (WW) NVIDIA(0): The EDID read for display device DFP-0 is invalid: the [ 371.712] (WW) NVIDIA(0): checksum for EDID version 1 extension is invalid. [ 371.712] (--) NVIDIA(0): [ 371.712] (--) NVIDIA(0): Raw EDID bytes: [ 371.712] (--) NVIDIA(0): [ 371.712] (--) NVIDIA(0): 00 ff ff ff ff ff ff 00 10 ac 4e 40 53 4e 54 41 [ 371.712] (--) NVIDIA(0): 0f 15 01 03 80 2f 1e 78 ee ee 95 a3 54 4c 99 26 [ 371.712] (--) NVIDIA(0): 0f 50 54 a5 4b 00 71 4f 81 80 b3 00 01 01 01 01 [ 371.712] (--) NVIDIA(0): 01 01 01 01 01 01 7c 2e 90 a0 60 1a 1e 40 30 20 [ 371.712] (--) NVIDIA(0): 36 00 da 28 11 00 00 1a 00 00 00 ff 00 34 57 31 [ 371.712] (--) NVIDIA(0): 4d 44 31 34 45 41 54 4e 53 0a 00 00 00 fc 00 44 [ 371.712] (--) NVIDIA(0): 45 4c 4c 20 50 32 32 31 30 0a 20 20 00 00 00 fd [ 371.712] (--) NVIDIA(0): 00 38 4b 1e 53 10 00 0a 20 20 20 20 20 20 01 82 [ 371.712] (--) NVIDIA(0): [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff 10 00 ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff [ 371.712] (--) NVIDIA(0): ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff 83 [ 371.712] (--) NVIDIA(0): [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 371.712] (--) NVIDIA(0): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Please check your monitor/and or cable. With nvidia being uninstalled X falls back to fbdev X driver, which uses the 1680x0150 frameubffer mode, you've configured somehow with grub/grub2. [ 2.562645] vesafb: mode is 1680x1050x32, linelength=6720, pages=0 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c9 --- Comment #9 from Ulrich Windl --- The system fell into powersave mode (suspend to disk), and when I woke it up, I did not get any picture on the screen; that has always been working until the recent updates. I tried to unplug/replug the monitor, but that didn't help. Switching to "text mode" also showed no image on the monitor, and even reboot did not help. Eventually I removed most of the boot flags like "quiet splash=silent", and then I got an image on the monitor again to be able to write this! The monitor is connected through DVI to a "Lindy KVM Switch No 32777" that connects this Linux machine and a Windows 7 machine to KVM. In the current Xorg.0.log EDID works: [ 63.414] (II) NOUVEAU(0): Monitor name: DELL P2210 [ 63.414] (II) NOUVEAU(0): Ranges: V min: 56 V max: 75 Hz, H min: 30 H max: 83 kHz, PixClock max 165 MHz [ 63.414] (II) NOUVEAU(0): EDID (in hex): [ 63.414] (II) NOUVEAU(0): 00ffffffffffff0010ac4e40534e5441 [ 63.414] (II) NOUVEAU(0): 0f150103802f1e78eeee95a3544c9926 [ 63.414] (II) NOUVEAU(0): 0f5054a54b00714f8180b30001010101 [ 63.414] (II) NOUVEAU(0): 0101010101017c2e90a0601a1e403020 [ 63.414] (II) NOUVEAU(0): 3600da281100001a000000ff00345731 [ 63.414] (II) NOUVEAU(0): 4d4431344541544e530a000000fc0044 [ 63.414] (II) NOUVEAU(0): 454c4c2050323231300a2020000000fd [ 63.414] (II) NOUVEAU(0): 00384b1e5310000a2020202020200083 [ 63.414] (II) NOUVEAU(0): Printing probed modes for output DVI-I-1 [...] But in the previous Xorg.0.log.old it did not. Maybe the EDID code is a bit fragile. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c11 Ulrich Windl changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | --- Comment #11 from Ulrich Windl --- Created attachment 664018 --> http://bugzilla.opensuse.org/attachment.cgi?id=664018&action=edit Previous Xorg.0.log.old that did not send a valid video signal to the monitor. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c14 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) | --- Comment #14 from Stefan Dirsch --- Well, probably before the NVIDIA packages were uninstalled but the nvidia kernel module still active, so nouveau module could not be loaded and X falls back to fbdev. After reboot nouveau X driver could be started. It's weird to see nvidia failing detecting EDID record though. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c16 --- Comment #16 from Egbert Eich --- (In reply to Ulrich Windl from comment #2) [..]

These modules cauise a complete failure to star tthe X server (it seems). I had to switch to the text console. There I removed those "G04" packets (which worked). Then I could start an X session with the usual resolution again.

Please define: 'a complete failure to star the X server'. In our nomenclature 'a complete failure' refers to the Xserver not starting at all - in which case you *are* in text console. (In reply to Ulrich Windl from comment #11)

Created attachment 664018 [details] Previous Xorg.0.log.old that did not send a valid video signal to the monitor.

Looking at this file, the time stamps reveal that the Xserver had been active for 1.5 hours. I don't think there were any issues with the video signal. (In reply to Egbert Eich from comment #15)

A single bit has tipped over in the 2nd last byte of the EDID block: < 00384b1e5310000a2020202020200182 ---

...

00384b1e5310000a2020202020200083

Actually, both EDID blocks are right: one has the extension flag set (the checksum is changed accordingly). The checksum of the extension block seems to be wrong (in which case the NVIDIA driver should probably ignore it). Ulrich, the information you've supplied is still to piecemeal to get NVIDIA involved: It is not clear at all if the log file you supplied in comment #3 is for the G03 or the G04 driver. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c18 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) --- Comment #18 from Egbert Eich --- (In reply to Ulrich Windl from comment #17)

(In reply to Egbert Eich from comment #16)

...

Please define: 'a complete failure to star the X server'.

As I wrote: There was no graphical login, but some message saying that the X server wouldn't start. I had to switch to another (text) console to log in.

Ok, now I understand. I seem to be missing a log file for this. The log file from comment #3 shows the Xserver starting and terminating normally. it didn't live ver long (all in all ~6 sec) which indicates that your DM (which one are you using?) terminated it. This might indicated that the DM had issues loading the required libs. Without knowledge of your DM we cannot find out where it logs to, though.

...

(In reply to Ulrich Windl from comment #11)

...

Created attachment 664018 [details] Previous Xorg.0.log.old that did not send a valid video signal to the monitor.

Looking at this file, the time stamps reveal that the Xserver had been active for 1.5 hours. I don't think there were any issues with the video signal.

I deduced from the fact that the monitor went into power save mode that there was no valid video signal. I wouldn't deduce that there was a valid video signal (on the correct output) from the fact that the server process was running for a while.

The screen usually goes into power save mode when it's idle for so long. 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.

...

Ulrich, the information you've supplied is still to piecemeal to get NVIDIA involved: It is not clear at all if the log file you supplied in comment #3 is for the G03 or the G04 driver.

OK: Suggest instructions on how to get the NVIDIA driver working. And if it doesn't, suggest what log files you really need.

This is not the prime purpose if this bugzilla. We are trying to determine if there is a bug in the software or the installation procedure. Once these things are fixed it should start working for you again if it hasn't before by the things we asked you to try. 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. 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? This ticket has seen attempts with too many drivers: NVIDIA G03, G04, fbdev and nouveau. All this is confusing and obfuscating the goal. Please 1. disable the NVIDIA repo, 2. deinstall whatever NVIDIA driver you've installed, 3. update the system to the current maintenance level doing 'zypper dup', 4. re-enable the NVIDIA repo and run 'zypper inr; zypper dup' This should give you the NVIDIA driver back - please let us know which ones... If it works now, 1. is fixed for this driver. BTW: The surest thing to determine if X is basically working and lighting up your screen, is by logging in to the text console as root and do: '/usr/bin/Xorg -retro & sleep 3; xterm -display :0'. You should get an X screen with the old fashioned root weave and an xterm. To determine if there are issues with the openGL libraries (ie you have installed unsuitable ones) you do 'gxlinfo' in this xterm and observe the output and any messages. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c20 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #20 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. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c31 --- Comment #31 from Ulrich Windl --- (In reply to Egbert Eich from comment #18)

This should give you the NVIDIA driver back - please let us know which ones...

These packages were in use: x11-video-nvidiaG03-340.96-40.1.x86_64 Wed 10 Feb 2016 02:07:13 PM CET nvidia-computeG03-340.96-40.1.x86_64 Wed 10 Feb 2016 02:07:07 PM CET nvidia-glG03-340.96-40.1.x86_64 Wed 10 Feb 2016 02:07:05 PM CET nvidia-uvm-gfxG03-kmp-default-340.96_k4.1.12_1-40.1.x86_64 Wed 10 Feb 2016 02:06:30 PM CET nvidia-gfxG03-kmp-default-340.96_k4.1.12_1-40.1.x86_64 Wed 10 Feb 2016 02:05:05 PM CET

If it works now, 1. is fixed for this driver.

I still have 800x600 resolution and an invalid EDID. It's hard to believe that the KVM reports an invalid EDID now; more likely the NVIDIA driver cannot read it correctly. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c33 --- Comment #33 from Ulrich Windl --- Created attachment 665087 --> http://bugzilla.opensuse.org/attachment.cgi?id=665087&action=edit /var/log/Xorg.0.log from NVIDIA driver without timestamps (for easy compare) This is the Xorg.0.log at 800x600 with timestamps removed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c35 --- Comment #35 from Ulrich Windl --- When I hacked the EDID override into /etc/X11/xorg.conf.d/50-device.conf, the resolution was OK. Effective lines were: Section "Device" Identifier "Nvidia" Driver "nvidia" Option "CustomEDID" "DFP-0:/etc/Dell-P2210.edid" EndSection -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=964429 http://bugzilla.opensuse.org/show_bug.cgi?id=964429#c37 Stefan Dirsch changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(Ulrich.Windl@rz.u | |ni-regensburg.de) --- Comment #37 from Stefan Dirsch --- So workaround via EDID file works. What's left would be to figure out, whether this is a regression in the driver. See comment #24 -- You are receiving this mail because: You are on the CC list for the bug.