Bug 86021
Summary: | HYUNDAI ImageQuest Q910 (19 inch) not found | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | lupus <de_lupus> |
Component: | rhpl | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED RAWHIDE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 8.0 | CC: | de_lupus, mharris |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-07-28 23:33:32 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: |
Description
lupus
2003-03-12 16:01:11 UTC
Can you run 'ddcprobe' as root on the command line and attach the output? We need to know what the monitor ID number is before we can add it to the MonitorsDB. I ran ddcprobe but it said: no dcc monitor connected? but on the site of HYUNDAI: Plug-and-Play VESA DDC 1/2B so it should find it, not? this is the inf file for windows maybe this helps ; Q910.INF ; ; Copyright 2002, ImageQuest Co., Ltd. ; ; This is a INF file for installing monitors for Windows. ; [Version] signature="$CHICAGO$" Class=Monitor ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318} Provider=%ImageQuest% [ClassInstall32] AddReg=ClassAddReg32 [ClassAddReg32] HKR,,,,%MonitorClassName% HKR,,Icon,,"-1" HKR,,NoInstallClass,,1 [DestinationDirs] DefaultDestDir=11 Q910.CopyFiles=23 [SourceDisksNames] 1="ImageQuest Monitor Installation Disk",,1 [SourceDisksFiles] Q910.icm=1 [Manufacturer] %ImageQuest%=ImageQuest [ImageQuest] %Q910%=Q910.Install, Monitor\IQT2910 [Q910.Install] DelReg=DEL_CURRENT_REG AddReg=Q910.AddReg, 1600, DPMS CopyFiles=Q910.CopyFiles [DEL_CURRENT_REG] HKR,MODES HKR,,MaxResolution HKR,,DPMS HKR,,ICMProfile [640] HKR,,MaxResolution,,"640,480" [800] HKR,,MaxResolution,,"800,600" [1024] HKR,,MaxResolution,,"1024,768" [1280] HKR,,MaxResolution,,"1280,1024" [1600] HKR,,MaxResolution,,"1600,1200" [DPMS] HKR,,DPMS,,1 [Q910.AddReg] HKR,"MODES\1600,1200",Mode1,,"30.0-110.0,50.0-150.0,+,+" HKR,,ICMProfile,0,"Q910.icm" [Q910.CopyFiles] Q910.icm [Strings] MonitorClassName="Monitor" ImageQuest="ImageQuest Co., Ltd." Q910="ImageQuest Q910" SiSoftware Sandra Monitor Setup Name : Plug en Play-monitor Maximum Resolution : 1600x1200 DPMS Energy Star Compliant : Yes PnP/DDC Monitor Data Manufacturer : IQT Model ID : 2910 Serial Number : 01317F20 Manufacture Date : 2002 week 43 Display Type : RGB colour CRT/Panel Size : 18 in Max. Horizontal/Vertical CRT/Panel Size : 360 mm / 270 mm Input Signal Type : Analog Sync on Green 0.7/0.3V Gamma Factor : 2.00 DPMS Modes Supported : Off Suspend Standby EDID Version : 1.03 Monitor Established Timings Video Mode 0 : 640x480 at 60Hz NI Video Mode 1 : 640x480 at 75Hz NI Video Mode 2 : 800x600 at 60Hz NI Video Mode 3 : 800x600 at 72Hz NI Video Mode 4 : 800x600 at 75Hz NI Video Mode 5 : 1024x768 at 75Hz NI Monitor Standard Timings Video Mode 0 : 800x600 at 85Hz Video Mode 1 : 1024x768 at 85Hz Video Mode 2 : 1152x864 at 75Hz Video Mode 3 : 1280x1024 at 85Hz Video Mode 4 : 1600x1200 at 75Hz Video Mode 5 : 1600x1200 at 85Hz That's all the info I have :) but why ddcprobe can"t find him is weird :s Hmm, if ddcprobe can't get the Monitor ID by probing the hardware, then it can't look it up in the MonitorsDB. I'm going to transfer this bug to rhpl, which is the package that contains ddcprobe. DDC requires both the video card and the monitor to cooperate. If ddcprobe says that there's no DDC monitor connected, there's not a lot we can do. got a nforce GPU If you are using a KVM switch, DDC may fail. That is not however a bug. If you're not using a KVM, then DDC should generally work if the monitor, video card, and driver all support DDC in a compatible manner. The nv driver supports DDC2. There is code for DDC1 #if'd out, as well as vesa DDC commented out. If there is any problem with the "nv" driver's DDC support however, Nvidia will have to fix it personally since they are the only ones who know how their video hardware works and do not release their specifications to others so there is not much we can do in any case unfortunately. I'm using nv driver with edid under windows 2000 I retrieve this: http://users.pandora.be/foryourneeds/edid.jpg Sorry, but raw hexadecimal values in a screenshot isn't really useful information. Your monitor supports the required functionality, however in order for DDC to work, it requires several things: 1) The monitor must support DDC 2) The video card must also support DDC, and must support the same version(s) of DDC that the monitor supports, and on the type of display (CRT/DFP/etc.) that the display is. 3) The video driver for your video card must support DDC, and must also support DDC on the type of display (CRT/DFP/etc.) that you are trying to use. The video driver must implement a version of DDC that is compatible with the CRT/DFP also. 4) There must not be any KVM switch or other hardware in between the video card and the CRT/DFP that might prevent the DDC probe from working 5) The CRT/DFP must be powered on when the video driver attempts to perform the probe (assuming that all of the above points are all met) If for whatever reason any of those conditions are not true, then DDC may fail or be unuseable, and there is nothing that we can do about it. In particular, the "nv" driver is not something that we can readily fix or hack around with as we do not have Nvidia's specifications for how their video hardware works. This requires Nvidia to fix the "nv" driver if it is a video driver issue. Please attach your Monitor's .INF file to the bug report as a file attachment (not cut and paste, which is kind of useless), and we can ensure it is listed in the database. Also attach your X server log and config file from after running "redhat-config-xfree86 --reconfig" manually. That should provide the necessary information to determine what the problem is, and wether or not there is anything that we can do about it. Thanks. I guess that that nv driver is the cause then :s cause with win2k there are no probs to probe it the inf file you asked for ;) http://users.pandora.be/foryourneeds/Q910.INF should I contact xfree for the probing problem? I'm using 8.1 beta and in 8.0 it wasn't found also but maybe it is resolved in xfree86-4.3? Thanks. I've processed the .INF file. Please try adding the following line to the file: /usr/share/hwdata/MonitorsDB ImageQuest Co., Ltd.; ImageQuest Q910; IQT2910; 30.0-110.0; 50.0-150.0; 1 MonitorsDB updated with entry. |