Red Hat Bugzilla – Bug 22948
ddc probed monitor: just a bunch of weird characters
Last modified: 2007-04-18 12:30:24 EDT
AcerView54eL. Generally I configure it as AcerView54es or AcerView54e. VideoCard: TridentBlade3D (Generic) I tried 2 installs. On the 1st try anaconda said DDC probed monitor: GSldf37 On the 2nd DDC probed monitor: MVCb75d The frequencies were clearly wrong. If the DDC probed monitor is just a string of weird chars (I agree it's very difficult to say what is a string of "weird chars") it would be better to let the user pick the right (or more suitable) monitor type from the list instead of presenting a screen with a weird kind of monitor selected. A new user would be confused "I have a monitor very similar to that one on the list, but the installer says I have "MVCb75d". Lets' call tech support" :)
We have observed this occurs with some monitors. Is the monitor attached thru a KVM?
No, the monitor is attached directly to the videocard. Sometime ago i was given this code snippet to debug some other problems I had: == ddcprobe #!/usr/bin/python import kudzu devices=kudzu.probe(kudzu.CLASS_MONITOR,kudzu.BUS_DDC,kudzu.PROBE_ALL) print devices == [root@i5 go]# date && ./ddcprobe mer gen 10 16:30:12 CET 2001 [Desc: None Id: CU]9f15 Mem on card: 8192 HSync: 0-0 VSync: 0-0 ] [root@i5 go]# date && ./ddcprobe mer gen 10 16:30:14 CET 2001 [Desc: None Id: O^]bf5f Mem on card: 8192 HSync: 0-0 VSync: 0-0 ] [root@i5 go]# date && ./ddcprobe mer gen 10 16:30:15 CET 2001 [Desc: None Id: URK97b5 Mem on card: 8192 HSync: 0-0 VSync: 0-0 ] [root@i5 go]# ... ...
DDC probing can be unreliable with some card/monitor combinations. Can you see what another OS (windows?) detects the monitor as?
winme cannot detect the kind of monitor either. It installs it as "predefined monitor". I think you could do 3 ddcprobe in a row, and if the results are not the same let the user pick the monitor without preselecting anything.
Interesting proposal, I will forward it to a developer.
I think this is probably a pretty rare occurance, and I'm reluctant to add code for it. I think most users would see that the monitor was not correctly identified and would select the right one. I just don't think doing the ddcprobe more than once is the right thing to do.