Laptop: Toshiba Tecra P10 with a single DB15 VGA output GPU: nVidia Corporation G86M [Quadro NVS 150M] (according to lspci) PCI id: 10de:06ea (rev a1) Docking station: a second VGA output and a DVI output Issue: Nouveau driver will drive the LVDS laptop screen and either VGA output but will not drive the DVI output, even though it seems to be correctly listed in xrandr's output. The DVI monitor simply remains blank with "no signal" displayed. This is the case at the framebuffer console level and when X is started. Kernel: 2.6.35 DRM, libdrm, nouveau, etc: all recent versions from git There are some potentially interesting kernel messages when the docking station is attached - i.e. the "unknown type" messages. Aug 11 19:15:00 its-ess-sb kernel: [ 3.739304] [drm] nouveau 0000:01:00.0: TMDS table revision 2.0 not currently supported Aug 11 19:15:00 its-ess-sb kernel: [ 3.740063] [drm] nouveau 0000:01:00.0: DCB connector table: VHER 0x40 5 16 4 Aug 11 19:15:00 its-ess-sb kernel: [ 3.740166] [drm] nouveau 0000:01:00.0: 0: 0x00000040: type 0x40 idx 0 tag 0xff Aug 11 19:15:00 its-ess-sb kernel: [ 3.740287] [drm] nouveau 0000:01:00.0: 1: 0x00000100: type 0x00 idx 1 tag 0xff Aug 11 19:15:00 its-ess-sb kernel: [ 3.740407] [drm] nouveau 0000:01:00.0: 2: 0x00001255: type 0x55 idx 2 tag 0x07 Aug 11 19:15:00 its-ess-sb kernel: [ 3.740526] [drm] nouveau 0000:01:00.0: unknown type, using 0x31 Aug 11 19:15:00 its-ess-sb kernel: [ 3.740628] [drm] nouveau 0000:01:00.0: 3: 0x00000351: type 0x51 idx 3 tag 0xff Aug 11 19:15:00 its-ess-sb kernel: [ 3.740747] [drm] nouveau 0000:01:00.0: unknown type, using 0x00 Aug 11 19:15:00 its-ess-sb kernel: [ 3.740842] [drm] nouveau 0000:01:00.0: 4: 0x00000462: type 0x62 idx 4 tag 0xff Aug 11 19:15:00 its-ess-sb kernel: [ 3.740962] [drm] nouveau 0000:01:00.0: unknown type, using 0xff I am about to reboot with the docking station removed. I'll attach the same part of the boot sequence plus exact details about driver versions, etc.
Can I see a dmesg log with "drm.debug=14 nouveau.reg_debug=0x0200 log_buf_len=2M" appended to your kernel boot options. Thanks.
dmesg output attached libdrm: git commit b04515c5d6c95f573457a94267b855cceb639105 xf86-video-nouveau: git commit 1cb6c91a9afe88d73f8a1180b00f56a9150a16ed kernel modules: git commit 63c5e51ea78dd6e76e0d03b119c464dbd45d711e
Created attachment 37808 [details] dmesg output with drm.debug=14 nouveau.reg_debug=0x0200 log_buf_len=2M options dmesg output /proc/version: Linux version 2.6.35 (scott@its-ess-sb.its.tils.qut.edu.au) (gcc version 4.4.3 (Debian 4.4.3-3) ) #3 SMP Sun Aug 8 16:27:53 EST 2010 /proc/cmdline: root=/dev/sda6 resume=/dev/sda5 no_console_suspend earlyprintk=vga snd-hda-intel.model=toshiba drm.debug=14 nouveau.reg_debug=0x0200 log_buf_len=2M
(In reply to comment #2) > dmesg output attached > > libdrm: git commit b04515c5d6c95f573457a94267b855cceb639105 > > xf86-video-nouveau: git commit 1cb6c91a9afe88d73f8a1180b00f56a9150a16ed > > kernel modules: git commit 63c5e51ea78dd6e76e0d03b119c464dbd45d711e This might be fixed already, can you please try with latest git?
Created attachment 37836 [details] dmesg output Thanks for your assistance so far. I am now using the latest kernel modules. The DVI output is still not working. Here is the dmesg output with options: drm.debug=14 nouveau.reg_debug=0x0200 log_buf_len=2M
Created attachment 38327 [details] Gzipped Tar file containing 6 dmesg outputs (text format). Hi, I have performed further testing using the following versions: git://anongit.freedesktop.org/nouveau/linux-2.6 1a8315a37e0e3b11daf923d9637321e0ff612e7e git://anongit.freedesktop.org/nouveau/xf86-video-nouveau 065576d5df0df4da61050d789f548801656b62d5 git://anongit.freedesktop.org/git/mesa/drm/ 23287f05cf2443ddf9e028e29beb5bd30979c6cf After booting with the DVI monitor connected, the DVI monitor remains blank (dmesg > 1.txt). After unplugging the DVI cable (2.txt) and plugging it back in, the DVI monitor displays correctly (3.txt). After starting X, the DVI monitor only displays the (mouse) cursor (4.txt). After typing "xrandr --output DVI-D-1 --mode 640x350" the DVI monitor displays the X screen properly (although at the reduced resolution) (5.txt). After typing "xrandr --output DVI-D-1 --auto" the DVI monitor displays at the correct native resolution (6.txt). Note: This command doesn't seem to cause the DVI monitor to display correctly unless the previous xrandr command (i.e. at the reduced resolution) is executed. Two further issues, possibly related issues: * The mouse cursor dissappears permanently sometimes from LVDS-1, although X is apparently otherwise unaffected. * The DVI monitor won't work again after a suspend/resume, even by unplugging/re-connecting/trying lower resolutions, etc. as above. Scott
Created attachment 39378 [details] Dmesg output Using the (latest) nouveau driver and kernel from: Repository: git://anongit.freedesktop.org/nouveau/linux-2.6 Commit: 4ec13442f9f9dfedb15473fdfc99fa71967ed48e I still see the same issue. If I boot with the DVI monitor attached, only the LVDS on the laptop is initialised, but as soon as I physically unplug the DVI and plug it back in, the DVI starts working. Dmesg output attached - DVI unplugged at about 16 seconds and reconnected at about 18 seconds.
It appears that this bug report has laid dormant for quite a while. Sorry we haven't gotten to it. Since we fix bugs all the time, chances are pretty good that your issue has been fixed with the latest software. Please give it a shot. (Linux kernel 3.10.7, xf86-video-nouveau 1.0.9, mesa 9.1.6, or their git versions.) If upgrading to the latest isn't an option for you, your distro's bugzilla is probably the right destination for your bug report. In an effort to clean up our bug list, we're pre-emptively closing all bugs that haven't seen updates since 2011. If the original issue remains, please make sure to provide fresh info, see http://nouveau.freedesktop.org/wiki/Bugs/ for what we need to see, and re-open this one. Thanks, The Nouveau Team
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.