Red Hat Bugzilla – Bug 176050
KDS monitor not detected correctly during install
Last modified: 2014-03-16 22:57:12 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051215 Fedora/1.7.12-3
Description of problem:
Monitor is dected as a PTS03e5 instead of the KDS XF-9b. I think I had opened one of these up, back in the day Fedora started or something similar, but I couldn't find the bug. So I am going to attach the .inf file to it, if I can find it or get it.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Actual Results: Monitor detected as PTS03e5
Expected Results: Monitor detected as KDS XF-9b
Korea Data Systems; KDS XFlat XF-9b/XF-9c/XF-9e/XF-9p; PTS03E5; 30.0-98.0;
The PTS03e5 DDC id *is* a KDS XF-9b.
Where in the UI are you seeing it reported as PTS03e5?
Rigth when the installer detects video/monitor (I believe before ananconda image
starts) and that is what is shown when firstboot comes up.
I can tell a big difference during the Gnome splash screen when switching from
the picked monitor, to the xf 9b one. So there seems to be a difference or
something, at least.
What are the results of running /usr/sbin/ddcprobe --monitor from a console?
[root@scrappy ~]# /usr/sbin/ddcprobe --monitor
Monitor autoprobe results
Horizontal Sync (kHZ): 30-98
Vertical Sync (HZ) : 50-160
Width (mm): 360
Here is a URL to the monitor specs to compare against what the ID shows..
It's being reported as PTS03e5 instead of KDS XF-9b because we're not getting
back any Name from kudzu. I don't see what performance difference it should
make in rhpxl what it's called as long as the sync and sizes are right (the
syncs are very close to the specs listed on the website, at least).
Bill - any thoughts?
Hm, it *should* be trying to pull the monitor name from monitorsdb. I'll look at
What's the output of 'kudzu -p -b ddc'?
[root@scrappy ~]# kudzu -p -b ddc
desc: "ATI Technologies Inc. V250"
I didn't change that, or at least not on purpose, so I changed it back to
When you reply to a bug in the NEEDINFO state, it automatically gets set back to
ASSIGNED as a way of letting us know that the information has been supplied.