Summary: | [NVE7] DisplayPort output on nVidia Quadro K2000M (ThinkPad W530) doesn't work | ||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Eric Swanson <e.swanson+xorgbugs> | ||||||||||||||||||
Component: | Driver/nouveau | Assignee: | Nouveau Project <nouveau> | ||||||||||||||||||
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> | ||||||||||||||||||
Severity: | normal | ||||||||||||||||||||
Priority: | medium | CC: | ayers, jcollins | ||||||||||||||||||
Version: | git | ||||||||||||||||||||
Hardware: | x86-64 (AMD64) | ||||||||||||||||||||
OS: | Linux (All) | ||||||||||||||||||||
Whiteboard: | |||||||||||||||||||||
i915 platform: | i915 features: | ||||||||||||||||||||
Attachments: |
|
Created attachment 63376 [details]
VBIOS Dump
Can you retry with "nouveau.vbios=ACPI" appended in your boot options? (In reply to comment #2) > Can you retry with "nouveau.vbios=ACPI" appended in your boot options? Same symptoms. I'll attach the new VBIOS dump and kernel log. Created attachment 63387 [details]
Kernel Log with nouveau.vbios=ACPI
Created attachment 63388 [details]
VBIOS Dump with nouveau.vbios=ACPI
Information added as requested. Not sure which status I should set, so putting it back to NEW. Sorry if that's incorrect. I've just pushed a patch to nouveau kernel git which should help you out here, I'm typing this from a W530 connected to an external DP monitor :) Let me know how you go! I'm still getting "Input not supported" on my monitor. I followed the guide at http://nouveau.freedesktop.org/wiki/InstallNouveau to make sure I had the latest libdrm and xf86-video-nouveau. I see your commit in my kernel source, but still, no luck. $ uname -a Linux svoboda 3.5.0-ARCH-g3f3dbea #1 SMP PREEMPT Fri Jul 27 14:58:16 EDT 2012 x86_64 GNU/Linux dmesg attached. Created attachment 64806 [details]
Dmesg
Is this still an issue with the latest kernel (3.11-rc7 or nouveau/master)? I've been stuck on 3.9 because there's a bug with the nvidia blob, kepler gpus, and optimus on 3.10 or later. I tried nouveau's arch linux packages on 3.10, but it was still an issue then. I can try building 3.11-rc7 to test later this weekend if that'd be helpful information. There were a number of kepler-related initialization fixes that went into 3.11-rc1, perhaps they'll help. Worth testing, IMO. BTW, please clarify -- are you using DP or HDMI? From my reading of your first message, you're using a DP->HDMI adapter (square peg/round hole problem solver, not a signal converter), so it's effectively using the HDMI machinery. Yes? That's correct. I'm using a passive MiniDP -> HDMI adaptor (this one, in fact: http://www.amazon.com/gp/product/B003OC6LWM/ref=wms_ohs_product?ie=UTF8&psc=1). Upgrading to 3.11 is probably fairly painless, but downgrading back to 3.9 if it doesn't work is quite annoying. I might put together a dual boot with the nouveau kernel and packages to make testing easier. I just installed Arch's linux-mainline AUR package, which built and installed linux 3.11rc7. The problem still exists. :( $ uname -a Linux svoboda 3.11.0-1-mainline #1 SMP PREEMPT Mon Sep 2 10:32:12 EDT 2013 x86_64 GNU/Linux $ xrandr Screen 0: minimum 320 x 200, current 3600 x 1080, maximum 8192 x 8192 LVDS-1 disconnected (normal left inverted right x axis y axis) VGA-1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm 1680x1050 60.0*+ 1280x1024 75.0 60.0 1152x864 75.0 1024x768 75.1 60.0 800x600 75.0 60.3 640x480 75.0 60.0 720x400 70.1 DP-1 connected primary 1920x1080+1680+0 (normal left inverted right x axis y axis) 510mm x 287mm 1920x1080 60.0*+ 50.0 59.9 1920x1080i 60.1 50.0 60.0 1280x1024 75.0 60.0 1280x960 60.0 1280x800 59.9 1152x864 75.0 1280x720 60.0 50.0 59.9 1024x768 75.1 70.1 60.0 832x624 74.6 800x600 72.2 75.0 60.3 56.2 720x576 50.0 720x480 60.0 59.9 640x480 75.0 72.8 66.7 60.0 59.9 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) I'll attach a new dmesg and vbios dump. Can I provide any other information in this configuration? Created attachment 85065 [details]
Dmesg on 3.11rc7
Created attachment 85066 [details]
garbage, disregard
Dumped using vbtracetool:
$ ./vbtracetool -w 2> myvga.rom
Created attachment 85067 [details]
VBios dump on 3.11rc7
VBios dumped with:
# cat /sys/kernel/debug/dri/0/vbios.rom > vbios.rom
My attempt to dump with vbtracetool (as root this time :) failed - my machine locked up and required a hard reboot.
Oh and one more piece of data: I experienced the same problem using the 2013.09.01 arch installer. It did KMS for my nvidia GPU and showed "Input Not Supported" on my Acer. It's running linux-3.10, and has never had the properietary nvidia driver installed (obviously). Also, it wasn't running X. I've captured some mmiotraces of the blob. There's a 26MB file at: http://www.alloscomp.com/files/mmiotrace_minidp_hdmi.tar.bz2 To create these dumps, I: - closed X - disconnected my VGA monitor, leaving only the DP->HDMI monitor connected - rmmod nvidia - rmmod nouveau - enabled mmiotrace - modprobe (nvidia or nouveau, depending on the trace) - xinit "/bin/sleep 10" - disabled mmiotrace To create the hotplug dump, I: - closed X (VGA monitor still connected) - rmmod nvidia - enabled mmiotrace - modprobe nvidia - xinit (to an xterm) - unplugged and replugged my DP monitor (with trace markers) - closed X - disabled mmiotrace I just bought a MiniDisplayPort++ to DVI adaptor. It works great under linux-3.11. This problem is NOT solved (lots of places only have HDMI), but at least I can use nouveau for day-to-day tasks now. I just tested a Lenovo W530 with Quadro K2000M (also with Optimus disabled), running 3.13 kernel and associated nouveau driver, along with a mini display port to HDMI cable. The combination worked flawlessly. Marking this as resolved. $ xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 LVDS-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.0*+ 60.0 50.0 1680x1050 60.0 1400x1050 60.0 1280x1024 59.9 1280x960 59.9 1152x864 60.0 1024x768 59.9 800x600 59.9 640x480 59.4 720x400 59.6 640x400 60.0 640x350 59.8 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 50.0 59.9 1920x1080i 60.1 50.0 60.0 1280x1024 75.0 60.0 1152x864 75.0 1280x720 60.0 50.0 59.9 1440x576i 50.1 $ xrandr Screen 0: minimum 320 x 200, current 3840 x 1080, maximum 8192 x 8192 LVDS-1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.0*+ 60.0 50.0 1680x1050 60.0 1400x1050 60.0 1280x1024 59.9 1280x960 59.9 1152x864 60.0 1024x768 59.9 800x600 59.9 640x480 59.4 720x400 59.6 640x400 60.0 640x350 59.8 VGA-1 disconnected (normal left inverted right x axis y axis) DP-1 connected 1920x1080+1920+0 (normal left inverted right x axis y axis) 531mm x 299mm 1920x1080 60.0*+ 50.0 59.9 1920x1080i 60.1 50.0 60.0 1280x1024 75.0 60.0 1152x864 75.0 1280x720 60.0 50.0 59.9 1440x576i 50.1 1024x768 75.1 60.0 1440x480i 60.1 60.1 800x600 75.0 60.3 720x576 50.0 720x480 60.0 59.9 640x480 75.0 60.0 59.9 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) 1024x768 75.1 60.0 1440x480i 60.1 60.1 800x600 75.0 60.3 720x576 50.0 720x480 60.0 59.9 640x480 75.0 60.0 59.9 720x400 70.1 DP-2 disconnected (normal left inverted right x axis y axis) DP-3 disconnected (normal left inverted right x axis y axis) |
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.
Created attachment 63375 [details] Kernel Log I've disabled Optimus in the BIOS, so only the K2000M is running. Xrandr shows all my available ports, but no matter what mode I set on the DisplayPort (connected to an Acer monitor via a known-good MiniDP to HDMI adapter), I get the error "Input Not Supported" on my monitor. What other information besides the kernel log can I submit to help with this bug?