| Summary: | DVI monitor is blank - DVI detected as Display Port ? | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | xorg | Reporter: | Julien Wajsberg <felash> | ||||||||||
| Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||||
| Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||
| Severity: | normal | ||||||||||||
| Priority: | medium | CC: | hramrach, kibi, massimotisi, ricklerre, vjensen | ||||||||||
| Version: | 7.5 (2009.10) | ||||||||||||
| Hardware: | x86 (IA32) | ||||||||||||
| OS: | Linux (All) | ||||||||||||
| Whiteboard: | |||||||||||||
| i915 platform: | i915 features: | ||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Julien Wajsberg
2010-04-29 15:37:39 UTC
Created attachment 35337 [details]
Dmesg boot log
Your laptop's video bios is reporting LVDS, VGA and 2xDP connectors. Is the "DVI" port on a docking station? If so, this makes sense as there's probably docking stations with DP connectors instead. In any case, I pushed several fixes to nouveau git yesterday, one of which should probably fix your issue. It'd be useful to see verbose (load drm module with debug=1 option) logs from nouveau git if things still don't work correctly. If that's the libuevent thingy, we probably could cherry-pick that one without having to worry too much about the possible ABI issues and put that in the Debian package. Julien, we can arrange some testing if you like (private mail to me will do the job). No, it's specifically 2cf43e3fa8b2de237908b6b0b24e42003e94f1db "drm/nv50: fix monitor detection on certain chipsets". Christopher just pointed me to it in the meanwhile, sorry for the noise. I guess we'll have to wait for it to pop up in some stable updates, or point our kernel people to that patch. You're right, the DVI port is on a docking station, so this makes sense. I'll see with Cyril how I could test this. Thanks ! Created attachment 35347 [details]
dmesg with debug output for the drm module
I managed to backport the change to Debian's current kernel. I had to apply also changeset d62823c984102a6f96df147a65bf1ffa7acaef1d "drm/nv50: store full dcb i2c entry from vbios", and to change some minor things, but I think I applied it correctly. But I still get the same bug. I attached the log for dmesg with debug output for drm, as you suggested. Thanks. Ah sorry! Can I get debug=15 instead. Created attachment 35384 [details]
dmesg log with drm debug=15 option
As requested.
According to your log you have 2 external displays plugged in (VGA-1, DisplayPort-1), as well as your laptop's panel (LVDS-1). The card only has 2 CRTCs, so can only bring up 2 displays. LVDS-1 is closed; in nv, it means it is disconnected. Please see xrandr outputs below. Also, I tried the following command lines : xrandr --output LVDS-1 --off xrandr --output DP-1 --auto -> nothing happens. Screen DVI-1 is still blank. Then I open the laptop and issued : xrandr --output LVDS-1 --auto I got : xrandr: cannot find crtc for output LVDS-1 It means that it tries to display on both DP-1 and VGA-1, right ? BTW, in gnome's display preferences, I correctly get both monitors displayed, but still, the monitor on DVI stays blank. Again : I have no monitor on DisplayPort (and I have no DisplayPort on the docking station). I have one monitor on VGA and one monitor on DVI (and LVDS as well, which is off most of the time). Thanks ---- xrandr output when the laptop is closed : LVDS-1 unknown connection (normal left inverted right x axis y axis) 1440x900 60.0 + 40.0 1152x864 60.0 1024x768 59.9 800x600 59.9 640x480 59.4 720x400 59.6 640x400 60.0 640x350 59.8 VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.0*+ 75.0 1280x960 60.0 1152x864 75.0 70.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 DP-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0*+ 75.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) ---- xrandr output when the laptop is opened : Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 8192 x 8192 LVDS-1 connected (normal left inverted right x axis y axis) 1440x900 60.0 + 40.0 1152x864 60.0 1024x768 59.9 800x600 59.9 640x480 59.4 720x400 59.6 640x400 60.0 640x350 59.8 VGA-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm 1280x1024 60.0*+ 75.0 1280x960 60.0 1152x864 75.0 70.0 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 640x480 72.8 75.0 66.7 60.0 720x400 70.1 DP-1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm 1280x1024 60.0*+ 75.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) (In reply to comment #12) > LVDS-1 is closed; in nv, it means it is disconnected. Please see xrandr outputs > below. I don't recall nv (unless by nv you mean the proprietary driver) doing anything of the sort. In any case, nouveau does something similar in this case, hence LVDS being reported as "unknown connection". We do this instead of "disconnected" so that X will setup LVDS still if the lid is closed and nothing else is plugged in. > > Also, I tried the following command lines : > xrandr --output LVDS-1 --off > xrandr --output DP-1 --auto > > -> nothing happens. Screen DVI-1 is still blank. Right, so now you're probably hitting another bug I've seen reported in a few places where docking station DVI fails on systems where it could be either DP or DVI on the docking station. > Then I open the laptop and issued : > > xrandr --output LVDS-1 --auto > > I got : > > xrandr: cannot find crtc for output LVDS-1 > > It means that it tries to display on both DP-1 and VGA-1, right ? Correct. > > BTW, in gnome's display preferences, I correctly get both monitors displayed, > but still, the monitor on DVI stays blank. > > Again : I have no monitor on DisplayPort (and I have no DisplayPort on the > docking station). I have one monitor on VGA and one monitor on DVI (and LVDS as > well, which is off most of the time). As I mentioned above, the VBIOS reports the connectors as DisplayPort as the docking station could potentially have DP instead of DVI-D connectors. There's no way for us to tell which the manufacturer wired up, so we assume it's DP. This has no effect on functionality. Ok, my question for you is: Are you able to make your VBIOS setup the DVI display during POST instead of the LVDS panel? There may be options in your BIOS setup to allow this. If so, let me know and we may be able to get traces that'll help me track this problem down for you. Ben. (In reply to comment #13) > I don't recall nv (unless by nv you mean the proprietary driver) doing anything > of the sort. In any case, nouveau does something similar in this case, hence > LVDS being reported as "unknown connection". We do this instead of > "disconnected" so that X will setup LVDS still if the lid is closed and nothing > else is plugged in. Yes, and that's good. > As I mentioned above, the VBIOS reports the connectors as DisplayPort as the > docking station could potentially have DP instead of DVI-D connectors. There's > no way for us to tell which the manufacturer wired up, so we assume it's DP. > This has no effect on functionality. So that's ok :-) > Ok, my question for you is: Are you able to make your VBIOS setup the DVI > display during POST instead of the LVDS panel? There may be options in your > BIOS setup to allow this. If so, let me know and we may be able to get traces > that'll help me track this problem down for you. That is my current set up: BIOS POST and Linux kernel messages are shown on the DVI display until nouveau is loading. (In reply to comment #14) > (In reply to comment #13) > > > Ok, my question for you is: Are you able to make your VBIOS setup the DVI > > display during POST instead of the LVDS panel? There may be options in your > > BIOS setup to allow this. If so, let me know and we may be able to get traces > > that'll help me track this problem down for you. > > That is my current set up: BIOS POST and Linux kernel messages are shown on the > DVI display until nouveau is loading. Ah, great! In that case, can you boot with "nomodeset 3" so you're at a VGA text console and get some VBIOS traces for me? Instructions on grabbing vbtracetool are at http://nouveau.freedesktop.org/wiki/DumpingVideoBios I'll need: ./vbtracetool -2 2>vbios.rom ./vbtracetool -lp 2>post.iolog ./vbtracetool -dp 2>post.log (this will possibly take several minutes to complete) If you could "bzip -9" those, and mail to mmio.dumps@gmail.com I'll take a look when I get a chance and see if I can find the missing magic. Is it sufficient to boot with nomodeset=3 and be in a text console, with X loaded ? Or should I boot single to not have X at all ? (In reply to comment #16) > Is it sufficient to boot with nomodeset=3 and be in a text console, with X > loaded ? Or should I boot single to not have X at all ? Look more closely, it is "nomodeset 3", not "nomodeset=3" :) The "3" will cause your system to boot to runlevel 3, which doesn't start X server. Oh you're right ;) (except that it's not true everywhere) I'll do whatever I must do to boot without X. But not until monday, so please try to sleep. :-) </noise> I'm also having this issue, with kernel 2.6.35 and xorg version 7.5. My nVidia card is the same (Quadro NVS 160M). The DVI response on my docking station is identical to the response I get when I'm plugged in directly to the DP on my laptop or my dock. Is there any additional info I can provide to you all to help this along? Thanks I'm not sure if this is helpful, but it looks like Redhat fixed this same bug: https://bugzilla.redhat.com/show_bug.cgi?id=532711 Not sure if that made it upstream or not. I have the same problem on and off. If it hits me, the notebook display goes blank for X. Having to drive to the office so I can actually see my desktop kinda sucks. System is debian with 3.0.0-1-amd64. Is this still an issue with the latest kernel? I don't have this computer anymore so I can't check it, sorry... No re-test in a month. Closing as invalid. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.