Bug 176050
Summary: | KDS monitor not detected correctly during install | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mike Chambers <mike> |
Component: | kudzu | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 5 | CC: | notting, rvokal |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-07-17 18:45:21 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 150221 |
Description
Mike Chambers
2005-12-18 13:23:05 UTC
Korea Data Systems; KDS XFlat XF-9b/XF-9c/XF-9e/XF-9p; PTS03E5; 30.0-98.0; 50.0-160.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 ID: PTS03e5 Horizontal Sync (kHZ): 30-98 Vertical Sync (HZ) : 50-160 Width (mm): 360 Height(mm): 260 Here is a URL to the monitor specs to compare against what the ID shows.. http://www.kdsusa.com/ProductDetails.asp?prod=233 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 the code. What's the output of 'kudzu -p -b ddc'? [root@scrappy ~]# kudzu -p -b ddc - class: VIDEO bus: DDC detached: 0 desc: "ATI Technologies Inc. V250" mem: 131072 - class: MONITOR bus: DDC detached: 0 desc: "(null)" id: PTS03e5 horizSyncMin: 30 horizSyncMax: 98 vertRefreshMin: 50 vertRefreshMax: 160 mode: 640x480 mode: 640x480 mode: 800x600 mode: 800x600 mode: 1024x768 mode: 1280x1024 mode: 1600x1200 mode: 640x480 I didn't change that, or at least not on purpose, so I changed it back to needinfo, sorry. 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. |