Description of problem: I installed Fedora 12 (latest and greatest with updates and test updates) onto my two-monitor desktop, which has an Nvidia GeForce 9600 GT (rev a1). The primary monitor appears just fine. The secondary monitor is black and says "No Signal". But the screen configuration utility shows both monitors and their correct native resolutions. Noticed these errors in dmesg: [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own [drm] nouveau 0000:01:00.0: Allocating FIFO number 2 [drm] nouveau 0000:01:00.0: nouveau_channel_alloc: initialised FIFO 2 [drm] TMDS-8: set mode 1920x1200 3c [drm] TMDS-10: set mode 1280x1024 3d eth0: no IPv6 routers present [drm] nouveau 0000:01:00.0: PGRAPH_ERROR - nSource: PROTECTION_ERROR DMA_R_PROTECTION, nStatus: [drm] nouveau 0000:01:00.0: PGRAPH_ERROR - Ch 2/4 Class 0x8297 Mthd 0x15e0 Data 0x00000000:0x00000000 Version-Release number of selected component (if applicable): Fedora 12 latest and greatest How reproducible: Always Steps to Reproduce: 1. Boot system at runlevel 5 Actual results: One monitor is black, says "No Signal" Expected results: Both monitors should appear normally as they do with F10. (F11 had worse problems, so I had to stick with F10). Additional info: I'll attach files with further info.
Created attachment 373433 [details] Here are the dmesgs from the failure
Created attachment 373434 [details] Here is my Xorg.0.log file I didn't actually look at this one, but the last one should be the same, and it didn't contain any errors, or "EE" entries.
Created attachment 373439 [details] Here's my lspci output Let me know if you need other information. This is my primary desktop, so it's inconvenient to switch over to F12 to collect info. Since I'm a Red Hat kernel-level developer, let me know if there's anything I can do to help. I can likely set it up to ssh into this box (after booting it back to F12) if need be. I've done this with past xorg bugs relating to mouse movement. I'm addicted to two-monitors so I won't use F12 until this is resolved, just like I didn't use F11.
Thanks for the report. Please don't set the 'priority' field when reporting bugs - by Fedora policy, that field is reserved for the maintainer(s) of the affected components to use however they like. can we get the xrandr output and the specs of the external monitor? Also, how is the external monitor connected to your machine - what kind of cable? is there anything else in the line (e.g. a KVM)? can you also test with the kernel parameter 'nomodeset' just to see if it works with UMS rather than KMS? thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Also, can I get a dmesg log of booting with "drm.debug=15 nouveau.reg_debug=0x200 3". Thanks!
I finally got around to trying these suggestions this morning. 1. Booting the kernel with the nomodeset parameter causes the system to freeze completely. It won't even toggle the num-lock light. The primary monitor was backlit but black. The second monitor had no video signal. 2. Booting the kernel with "drm.debug=15 nouveau.reg_debug=0x200 3" failed to start X. Errors were logged in Xorg.0.log, which I will attach shortly. 3. I booted F12 as before and saved the xrandr output, which I will attach shortly. 4. In answer to the questions about my hardware: This is a desktop unit, x86_64, with the Nvidia card noted above. The card has two external cables for two video outputs. The primary display is attached to a 24-inch Samsung SyncMaster 2433bw monitor via a normal DVI cable. The secondary display is a ViewSonic VA912b, also attached via a normal DVI cable.
Created attachment 375444 [details] dmesg with the debug options
Created attachment 375446 [details] Xorg.0.log file with the debug options
Created attachment 375449 [details] xrandr output from a non-debug boot of F12 This xrandr was taken after rebooting the kernel to a normal F12. As described in the original problem description, there was only the primary monitor displayed and the secondary monitor had no signal, even though the display configuration screen showed both monitors.
Thanks. Your xrandr output does show two monitors, btw - DVI-I-0 and DVI-I-1. DVI-I-1 appears to be the problematic Viewsonic, and it shows it configured at 1280x1024, which sounds reasonable for a 19" LCD. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Yes, 1280x1024 is the native resolution for the Viewsonic.
A couple more questions to try and narrow it down a bit: 1. If you swap the monitors around, does the other one work instead? 2. If the above is true, do either/both monitors work on the "bad" connector if you have *only* one monitor plugged in at a time.
Hi Ben, After a bit of messing around, I was able to capture a complete mmiotrace of my X initialization with dual screens. It's a bit big, so I can't attach it to the bz. However, I bzip2'd it and copied it here: http://www.robertpeterson.org/bobs_mmiotrace.txt.bz2 I haven't tried the experiments in comment #14 yet.
Created attachment 414721 [details] FYI--my Xorg.0.log file Here's my log file too, so you can match what the driver did to the initialization sequence in the trace. Ben, I can also get you ssh access to this system. I've done this for other developers in situations like this, most notably, "whot" who did some remote debugging on a screen switching problem I had long ago. Let me know if you want to set it up sometime. My irc nick is bob and you can find me in Red Hat's #devel.
Thanks for that, I'll take a look at those and see if anything obvious sticks out. As you can see, it's a *lot* of data, so unless it's a big change from other chipsets, it's a "needle in a haystack" kind of deal. The other thing that'd be worth knowing (when you get to the nouveau experiments) is that if you configure *both* displays to a lower resolution (say, 1280x1024 to be safe), do they both work? It could be a memory bandwidth problem too. You'll need to 'xrandr --output NAME --set "scaling mode" None' both of the connectors to make sure the displays definitely receive a lower clocked mode.
Over the weekend, I tried some of the experiments suggested in comment #14. The "bad" monitor worked perfectly if I plugged it into the "good" monitor's output, but the "good" monitor did not work in the "bad" monitor's output. So the problem followed the output from the card, not the monitor. Neither "good" nor "bad" monitor worked stand-alone when plugged into the "bad" port. When the system boots, I get normal BIOS messages on whatever monitor is plugged into the "bad" port but nothing once the kernel starts. I tried the xrandr command but never got it to work properly. I figured out how to specify the output port from the Xorg.0.log file, but it didn't seem to like "scaling mode" or "scaling_mode". I tried many variations but finally gave up.
Thanks for that, the info you gave shows it's something specific to one of the connectors, which narrows things down a little. I think the fact that they don't work individually in that connector rules out memory bandwidth issues, and we're left with some magic to find which'll make the connector work. Something like this goes much much faster with the card in front of me, as I can bash registers until I see the display light up :) But I'll take another look anyways.
Hey, I have a scratch build prepared which *may* fix your issue. Are you able to test it for me and let me know? http://koji.fedoraproject.org/koji/taskinfo?taskID=2299699 Thanks!
When you test, can you please try with this build instead: http://koji.fedoraproject.org/koji/taskinfo?taskID=2307587
Hi Ben, I don't have this environment set up anymore. I would love to try your latest build, but it might take some time. I would likely need to reinstall F13 to a new hard drive and set up the environment again. Not a big deal but it will take some time because this is my primary workstation (taking the machine offline for a few hours will impact my other work). I'll see what I can do.
Ok, thank you. The fixes in the above scratch build are available in kernel-2.6.34.1-11.fc13 (http://koji.fedoraproject.org/koji/buildinfo?buildID=183346). I'll leave this NEEDINFO until you've had a chance to test.
Hi Ben, Unfortunately, my Kernel is 2.6.34.7-61.fc13.x86_64 and I still have a black second monitor :-( Like Robert, I am dual-monitor addicted and have no fun with just a tiny single monitor in front of me. As you can see my English is not the best. Also I am not a Linux guy. In fact I am coming from the Windows world and do not know how I get needed information out of the black box called Linux. Anyway, I hope I can give you all information which you want. Regards, Wolfgang
Ups, some information would be a good idea... Hardware: Main monitor NEC 1920x1200 Second monitor: Samsung 1680x1050 First I tried to enable the second monitor with the neuveau driver. But I got only a single screen (screen 0) with a resolution of 3600 x 1200. 1920 x1200 was visible the rest was black but reachable. That means, I could move a window outside the 1920 px resolution and it was visible in the virtual desktop pane. Then, I installed the nvidia driver and set up the second monitor with the nvidia-settings dialog. After restarting the X-Server the second monitor is still black and I get errors like the following when I start the nvidia-settings dialog again: ERROR: Invalid X Screen 1 specified on line 92 of configuration file '/root/.nvidia-settings-rc' (there is only 1 X Screen on this Display). Unfortunately, my nvidia-settings-rc file is gone, but I think I can it reproduce if you need it. Regards, Wolfgang
Fedora has no interest in the NVIDIA driver at all, we don't ship it, and as it's closed source we can't support it. So if you'd like help from Fedora developers, please use the nouveau driver. Do you actually have the same video adapter as mentioned in this bug? You haven't posted to this bug before and you don't provide any description of your graphics card. It's likely that you're suffering from a different bug, unrelated to this one, which happens to have the same symptom, in which case it would be best to open a new report. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
As of NVIDIA driver I understand. However, with the nouveau driver I have the same problem and the video adapter is also a Nvidia 9600 GT. So I believe that is the same problem.
Please provide all the info listed at https://fedoraproject.org/wiki/How_to_debug_Xorg_problems , then (after switching back to nouveau, of course). Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hello, I switched back to the nouveau driver and even removed the nvidia driver. Here the data: All bug reports In all cases, the following should be attached to your bug report: > All of the X server log file(s): /var/log/Xorg.*.log I attached the Xorg.0.log because the older one are still full with nvidia entries. > Your smolt profile. You can dump it to /tmp/smoltprofile.txt with the Attached. > If you use a xorg.conf, please include it in the bug report, otherwise... Attached. This one is created from the scratch after removing the nvidia driver and deleting the old xorg.con file. > output of the dmesg command (please add drm.debug=14 log_buf_len=16M... boot parameters added and rebooted. Then the dmesg.txt created and attached here. I hope these info help, Wolfgang
Created attachment 456495 [details] dmesg after rebooting with the boot parameter
Created attachment 456496 [details] smoltprofile
Created attachment 456497 [details] Old xorg.con removed and rebooted. That is the automatically created new one.
Created attachment 456498 [details] Xorg log.
one more thing (I should update the 'how to debug' page...) - can you also include the output of 'xrandr' run at a console? Thanks! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 456605 [details] xrandr Here you are
Thanks. So, just to be clear, what is your symptom? The xrandr output shows two displays connected and activated. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Hi Adam, Thanks a lot for you effort in this. Its weird, I know, but the symptoms is the second monitor stays black. The monitor is not in stand-by mode is recognized by gnome and configured. The cable is plugged in tight and it works with Window. As Robert described above doesn't matter which monitor is plugged in the first monitor output. The second monitor output does not work. Or in fact it works, but only a black screen is shown even the desktop has got the resolutions of both monitors. When I take a screenshot I get a picture of the whole desktop, that means I can see the background picture and windows on the second monitor which is shown in the picture but not on the monitor. The monitor might gets only a "black" signal by the video card. Thanks, Wolfgang
Okay, thanks. Just wanted to make sure we had all the details :) Ben, over to you! -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Can you give the latest f14 kernel from koji a try and see how that goes?
Of course, but how? I am a newbie and I even don't know what 'koji' means :-(
So, with a little help I installed the kernel and booted with it. Unfortunately, nothing changed. The monitor is still black :-( I enabled/disabled it several times, nothing changed.
What kernel version did you end up getting?
this one: http://koji.fedoraproject.org/koji/buildinfo?buildID=202926 Should be the right one.
Are you able to post your dmesg log with that kernel from after activating the external display?
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Created attachment 457874 [details] dmesg output I enabled the second monitor and rebooted. Then stored the dmesg output in that file. I hope that helps
I just tried F14 on the same system. Now nouveau driver won't start gnome at all. I get: (nautilus:1758): GdkPixbuf-CRITICAL **: gdk_pixbuf_format_get_name: assertion `format != NULL' failed [drm] nouveau 0000:01:00.0: EvoCh 0 Mthd 0x0080 Data 0x00000000 (0x100e 0x05) The only EE I see in Xorg.0.log is: (EE) HID 0b38:0010: failed to initialize for relative axes. This is a stock F14 2.6.35.6-48.fc14.x86_64 kernel.
The nouveau driver is working perfectly with gnome3 on Fedora 16 so I'm closing this as CURRENTRELEASE.