Hide Forgot
Created attachment 490870 [details] Xorg.log when running nouveau Description of problem: Nouveau sets the wrong mode on my large monitor, and instead thinks I have two equally sized and identical monitors. ( I have two monitors of different size&fabricate ) Version-Release number of selected component (if applicable): xorg-x11-drv-nouveau-0.0.16-24.20110324git8378443.fc15.x86_64 How reproducible: Every time
Created attachment 490871 [details] Xorg.log when running nvidia driver
Can I get the output from running the "dmesg" command please (while running nouveau, with both screens attached)
Would the logs in: https://bugzilla.redhat.com/show_bug.cgi?id=694917 Help? that's with drm.debug flags, so the dmesg output may be too verbose.
Yep, far too verbose, the info I was after is missing!
Created attachment 491370 [details] dmesg output with nouveau driver As requested, dmesg output. Sorry for the delay.
Ugh. Your VBIOS says that the digital output of the first connector, and the analog output of second connector share an i2c line. This leads to us detecting an analog monitor attached to the second connector (which is really your digital one on the first connector). Now, this is the third case I've seen of this, and haven't determined yet if it's a VBIOS issue (that we can add a quirk for), or the hardware is *actually* wired up this way and we need to somehow flip a switch to decide which to talk to. Can you do the following: yum install i2c-tools modprobe i2c-dev i2cdetect -l Then for every i2c-N with nouveau-0000:01:00 in it, can you run (and attach the output of): i2cdetect N (where N is the i2c-N number from "i2cdetect -l") Thanks!
Actually. Both of those are digital. There's nothing hooked up to the analogue (third) connector. Yeah, it really is that bad. The i2c things will have to wait until tomorrow unless it's doable with the nvidia driver running.
With the nvidia driver loaded I get this: [root@Waves ~]# modprobe i2c-dev [root@Waves ~]# i2cdetect -l i2c-0 i2c NVIDIA i2c adapter I2C adapter i2c-1 i2c NVIDIA i2c adapter I2C adapter i2c-2 i2c NVIDIA i2c adapter I2C adapter [root@Waves ~]# i2cdetect 0 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-0. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- [root@Waves ~]# i2cdetect 1 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-1. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- 3a -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- [root@Waves ~]# i2cdetect 2 WARNING! This program can confuse your I2C bus, cause data loss and worse! I will probe file /dev/i2c-2. I will probe address range 0x03-0x77. Continue? [Y/n] y 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- I'll make sure you get nouveau driver data as well tomorrow.
There's a third connector? Interesting.. Your VBIOS tables are definitely broken then, it only mentions two DVI-I connectors. What *is* actually physically present? VGA, DVI-I and HDMI ?
Exactly that, VGA, DVI-I and HDMI. The Asus monitor ( Identified as Ancor Communications Inc MW221) is on DVI, the Dell monitor is on HDMI, and the vga is empty. During bios and bootloader/early linux boot/windows boot, the machine will flat-out refuse to use anything except for the lowest monitor. So if VGA is connected, that's in use, if DVI is connected, that's in use, if only HDMI is connected, that's the one. This only changes once the graphics-driver has been probed properly.
This time with nouveau. i2c-0 i2c nouveau-0000:01:00.0-2 I2C adapter i2c-1 i2c nouveau-0000:01:00.0-0 I2C adapter i2c-2 i2c nouveau-0000:01:00.0-1 I2C adapter 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- -- 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- 3a -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- -- 50: 50 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- -- --
Anything else you'd need right now?
There's a scratch kernel build with a patch rewriting your VBIOS's output table (it doesn't modify the VBIOS, just overrides nouveau's use of it) here: http://koji.fedoraproject.org/koji/taskinfo?taskID=3001069 Are you able to give that a try? Also, if you have any way to test the VGA output, and the analog function of the DVI-I connector that'd be great!
Installed it, gonna give it a whirl in the evening. VGA output I can probably test. DVI-I analog might be worse, no way that I know of to force my monitors into accepting that, ( unless if I use an DVI->VGA converter piece, should be one around here ) What do you want tested? How it works with dual monitors, with HDMI+VGA and so on?
Actually, a DVI->VGA adaptor is perfect for testing that :) Testing everything you possibly can and ensuring it works correctly would be great, to ensure the replaced output table is correct for your card. You should see: 1. VGA output should show up as VGA-1 being connected 2. DVI-I output should show up as DVI-I-1 being connected 3. HDMI output should show up as DVI-I-2 (yes, the name is wrong) being connected 4. Any combination of two monitors on the above connectors should work 5. Plugging/Unplugging from DVI/HDMI should show the correct connector name in plugged/unplugged messages Thank you!
Cheers, I'll give that a go this evening/saturday morning then. And in a completely unrelated issue, when/how can we get some power-management/fan control working, and how can I help? The lack of it is currently preventing me from moving to the OSS-driver fulltime, the sound of these fans is enough to turn the room way past survivable levels of noise.
Way too late reply, but a (partially) succesful one. I've been unable to dig up a vga-cable (Seems I cleaned house at some point) so the analogues have been untested. Various combination orders of Digital appears to work, correct identification and ordering.
This message is a notice that Fedora 15 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 15. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '15' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 15 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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