https://bugs.freedesktop.org/show_bug.cgi?id=27452
--- Comment #1 from Dave Witbrodt <dawit...@sbcglobal.net> 2010-04-10 10:03:39
PDT ---
Seeing the recent set of commits touch on Evergreen support, I tested a new
kernel using "drm-radeon-testing" up to commit 98e5963 of Apr. 9, 2010. I'm
not interested in UMS, so I configured to default to KMS. My monitor only has
VGA and HDMI inputs, and I'm only interested in seeing the problem with HDMI
support for Evergreen solved in this bug report, so I only tested with the HDMI
cable.
Results:
- still have pink line along left side of screen (2 pixels wide)
- monitor OSD still reports crazy 1922x1200 mode (instead of 1920x1200)
- it is known that the hardware (both video card and monitor) are fine:
Windows uses HDMI-to-HDMI cable (and DVI-to-HDMI cable) without problems
- as before, X runs fine; I will include Xorg.0.log for completion (problem is
in KMS/radeondrmfb, not X, though) in case any helpful info is present there
Brainstorming:
- looked at some of the DRM code, but couldn't understand HDMI connection
code; apparently something in the ATOMBIOS functionality between HD 4XXX
and HD 5XXX is subtly different
- possibly the problem arises with the KMS equivalent of what would be called
modelines in X: the Xorg.0.log shows that the preferred mode for the monitor
(1920x1200) is set using detailed timings reported by the monitor; this is fine
with UMS (and KMS on HD 4850), but fails with KMS on HD 5750 ...
(II) RADEON(0): Supported detailed timing:
(II) RADEON(0): clock: 154.0 MHz Image Size: 593 x 371 mm
(II) RADEON(0): h_active: 1920 h_sync: 1968 h_sync_end 2000
h_blank_end 2080 h_border: 0
(II) RADEON(0): v_active: 1200 v_sync: 1203 v_sync_end 1209
v_blanking: 1235 v_border: 0
[FYI: the "drm-radeon-testing" commits now require JUNIPER*.bin firmware blobs,
but I did download them and add them to my kernel with a built-in initramfs --
see attached 'dmesg' output.]
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
