http://bugs.freedesktop.org/show_bug.cgi?id=15989 --- Comment #2 from Marcelo E. Magallon 2008-05-17 09:11:08 PST --- Created an attachment (id=16602) --> (http://bugs.freedesktop.org/attachment.cgi?id=16602) Configuration file used to disable RandR -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|lverhaegen@suse.de |eich@pdx.freedesktop.org --- Comment #4 from Egbert Eich 2008-05-19 07:59:43 PST --- There is no HPD info in the connector table (although the LVTMA has an HPD assigned). One could generate a connector table but as this problem seems to be consistent across all RS690 systems it is hard to fix for all. I've checked how else we can work around this issue - unfortunately i have no idea. Marcelo, do you really have two monitors connected? I don't see any DDC output from the one connected to DVI-D_1. In this case this connector should have the state disconnected. I've got the same board so I will check where this comes from. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 --- Comment #6 from Marcelo E. Magallon 2008-05-20 21:55:50 PST --- Created an attachment (id=16659) --> (http://bugs.freedesktop.org/attachment.cgi?id=16659) X log with -logverbose 7, no configuration file -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 --- Comment #8 from Egbert Eich 2008-07-21 00:10:14 PST --- Looking at the log file more closely it seems that the DVI-1 (the DDIA block on the HDMI connector) block detects an output (thru DDC) which however doesn't provide DDC data. (II) RADEONHD(0): rhdRROutputDetect: Output DVI-D_1 (II) RADEONHD(0): FUNCTION: rhdRS69WriteRead (II) RADEONHD(0): FUNCTION: rhdRS69I2CSetupStatus (II) RADEONHD(0): FUNCTION: RHDAtomBiosFunc (II) RADEONHD(0): FUNCTION: rhdAtomGPIOI2CInfoQuery (II) RADEONHD(0): GPIO_I2C_Clk_Mask: 0x1f90 (II) RADEONHD(0): rhdRS69I2CSetupStatus: DDC Line: 2 val: 0 port: 0x1f90 (II) RADEONHD(0): FUNCTION: rhdRS69I2CStatus (II) RADEONHD(0): rhdRROutputGetModes: Output DVI-D_1 Since there is no DDC data for this output some low ranges are assumed which contain the 1280x800 mode. So the driver drives the HDMI output with 1280x800 although nothing is there and the mode that the gnome desktop sees is exactly this mode. Marcelo: Are you sure there is nothing connected to the HDMI port? I've tried to reproduce this with exactly the same board here however I don't see this issue. Could you refetch the latest driver (the version I've just pushed) and regenerate a verbose log file (this time -logverbose 8 !!!). Please use the same setup as you have used before: an LCD connected to the DVI port, nothing connected to HDMI. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 Marcelo E. Magallon changed: What |Removed |Added ---------------------------------------------------------------------------- Version|unspecified |git -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 --- Comment #11 from Egbert Eich 2008-08-01 03:52:37 PST --- (In reply to comment #9)

Created an attachment (id=18048) --> (http://bugs.freedesktop.org/attachment.cgi?id=18048) [details] Xorg.log file without a configuration, -logverbose 9

This is the new log file with -logverbose 9.

Thanks a lot! It was quite helpful.

Yes, I'm sure there's nothing connected to the HDMI connector, only to the DVI conector. Actually the other day I opened the case just to inspect it and look for anything suspicious and I couldn't spot anything.

I've got exactly the same board but the HDMI variant. It comes with an HDMI riser card that's plugged into the PEG slot (PCI-E 16x). Now your VBIOS the connector table shows this HDMI port although the HDMI riser card is not present. This would not be a problem, but according to the log that you've sent there is i2c data transaction on the DDC line that belongs to this non-existing HDMI port. On my system (with the riser card present) I get a NACK when I try to start an I2C transaction on this DDC line without any device detected. Apparently the checksum of the data that's transferred is incorrect according to the DDC specs so the Xserver doesn't try to interpret it as an EDID block. I wonder how this data looks like... rhd_conntest will help you to dump this data: ./rhd_conntest 1:5.0 -x 128 Presently with no hot plug information available we check for the presence of a device by trying to access the DDC line. If we receive an ACK on addressing the DDC slave address we assume a device is present. This heuristic seems to fail in your case which would be bad. It would mean that we'd have to transfer a full EDID blck and calculate the checksum to know if anything is connected. Here it would be good if RandR could be instructed to treat an output reading an existing but invalid EDID block as unconnected - especially for digital interfaces as for them the availability of EDID data is a requirement. But this would be more an randr less a driver issue.

Should I consider the possibility of a bad motherboard? Something else happens, namely every now and then the screen goes black for a second or two and then it resumes to normal. Initially I blamed the driver, but I've noticed that this happens with all the drivers that I've tried. Then I thought it could be the monitor, but I attached it to another machine and it seemed to work fine for a couple of hours (that's not conclusive, since the problem doesn't seem to have a pattern to it, sometimes hours go by before it happens and sometimes it happens several times in a row). I have noticed that it happens less often with this driver.

It could be that the electrical characteristics of the TMDS link to the monitor are slightly off. You could also try to switch to coherent mode. This is implemented as an output property. Please use xrandr --prop to check and xrandr --set <property> <value> change the state. Once I get face time with my machine again I will try to reproduce this by pulling out the HDMI riser card.

I used 3e2ee2f4722db20dcaf0d08f572b39541b8ec19f to test.

Something else: I'm running a amd64 distribution, if that's somehow relevant.

No, this is completely irrelevant here. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 --- Comment #13 from Egbert Eich 2008-08-02 06:37:05 PST --- OK, i've pulled the HDMI riser board from my system and it started to exhibit the same behavior: *all* I2C slave addresses on DDC2 start responding. When reading one gets all zeros. I then went ahead and disabled HDMI support in the BIOS with the hope that this would modify the connector table in the Video BIOS (like on a Gigabyte RS780 board). But this didn't happen. I didn't see any effect when doing this. I guess one could modify the DDC Probe to read the first to bytes of an EDID block and check that they are 0x00 0xff. This is really a hardware brokenness. I wonder if a BIOS update would make a difference here. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 --- Comment #15 from Egbert Eich 2008-08-04 04:49:24 PST --- Marcelo, I've made a patch for the driver which should address this issue. This 'improved' detection code should be able to handle slightly broken hardware - like this ASUS board. commit 20f3df0900f7a03ef9b56710590a4523fa1c74ed should take care of this. I've tested it here with my board and it seems to work. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org

http://bugs.freedesktop.org/show_bug.cgi?id=15989 Egbert Eich changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED --- Comment #17 from Egbert Eich 2008-08-04 07:20:20 PST --- OK, so let's mark this fixed. -- Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ xorg-team mailing list xorg-team@lists.x.org http://lists.x.org/mailman/listinfo/xorg-team -- To unsubscribe, e-mail: radeonhd+unsubscribe@opensuse.org For additional commands, e-mail: radeonhd+help@opensuse.org