Bug 161013
Summary: | No apparent support for a Samsung SyncMaster 910v Monitor | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | alien | ||||
Component: | system-config-display | Assignee: | Adam Jackson <ajax> | ||||
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | |||||
Severity: | medium | Docs Contact: | |||||
Priority: | medium | ||||||
Version: | 4 | ||||||
Target Milestone: | --- | ||||||
Target Release: | --- | ||||||
Hardware: | i386 | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | 0.160-1 | Doc Type: | Bug Fix | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2007-04-03 18:22:04 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: | |||||||
Attachments: |
|
Description
alien
2005-06-19 20:29:57 UTC
Do you have a INF file for this monitor? Yes... here is the .INF file... ;================================================== ; SM910V.inf 01/30/2004 ver. 1.0 ; ; Copyright 2004 Samsung Electronics Corporation ; ; This is a Setup information file for Samsung Monitor. ;================================================== [Version] signature="$CHICAGO$" Class=Monitor ClassGuid={4D36E96E-E325-11CE-BFC1-08002BE10318} Provider=%Samsung% CatalogFile=SM910V.cat DriverVer=01/30/2004,1.0 ;-------------------------------------------------- [ControlFlags] ExcludeFromSelect.nt=Monitor\SAM0115 [ClassInstall32] AddReg=ClassAddReg32 [ClassAddReg32] HKR,,,,%MonitorClassName% HKR,,Icon,,"-1" HKR,,NoInstallClass,,1 [DestinationDirs] DefaultDestDir = 11 SM910V.CopyFiles = 23 [SourceDisksNames] 1=%DISK%,,, [SourceDisksFiles] SM910V.icm=1 [Manufacturer] %Samsung%=Samsung ; Manufacturer sections ;----------------------------------------------------- [Samsung] %SM910V%=SM910V.Install, Monitor\SAM0115 ; Install Sections ;----------------------------------------------------- [SM910V.Install] DelReg=DEL_CURRENT_REG AddReg=SM910V.AddReg, 1280, DPMS CopyFiles=SM910V.CopyFiles ; Addreg & DelReg sections ;----------------------------------------------------- [DEL_CURRENT_REG] HKR,MODES HKR,,MaxResolution HKR,,DPMS HKR,,ICMProfile [1280] HKR,,MaxResolution,,"1280,1024" [DPMS] HKR,,DPMS,,1 ; AddReg sections ;----------------------------------------------------- [SM910V.AddReg] HKR,"MODES\1280,1024",Mode1,,"30-81,56-75,+,+" HKR,,ICMProfile,0,"SM910V.icm" ;------------------------------------------------------ [SM910V.CopyFiles] SM910V.icm ;------------------------------------------------------ [Strings] DISK="Samsung Monitor Installation Disk" MonitorClassName="Monitor" Samsung="Samsung" SM910V="SyncMaster 910V/910M/913V" Thanks, added in CVS, will be in hwdata-0.160-1. Ummm.... please excuse my ignorance here. The fact that it has now been added to hwdata-0.160-1 ... I guess means that the situation has now been resolved ?!? Again, I am sitting here with 4 CDs burnt from the June 13th ISO images for the x86_64 Linux code. I am not quite sure what I am supposed to do right now !! Created attachment 116016 [details]
updated monitors database
The data for the monitor will be added to the MonitorsDB as of that release of
the hwdata package.
In the meantime, I'd suggest booting in text mode, and dropping this file in
/usr/share/hwdata; you'd then at least be able to pick it if you then run
system-config-display. This could be problematic if the config is illegible,
though.
For that, probably the best is to just pick a Generic 640x480 or 800x600
display, and *then* copy in this file and pick the correct monitor. If, once
you have the correct monitor selected, it still doesn't work, that's probably
an X bug.
Well I finally downloaded hwdata-0.164-1.noarch.rpm onto my test (i386) Linux system (not the system mentioned above)... and extracted the MonitorsDB file and copied it to a floopy disk I then, once again, went through the process of completely re-installing the FC4 x86 code onto my AMD Athlon 64 3400+ system.. the one that has the Samsung SyncMaster 910v monitor When the install procesf completed its code install, and requested a system restart... I intervened with the FC4 "rescuecd"... mounted the drives... copied the MonitorsDB file into /usr/share/hwdata.... then rebooted again... (and removed the rescuecd. I then let the post-install process of the FC4 (x86) package to complete. Again, it detected an unknown monitor (screen)... i then selected from the available list of known monitors/screens... I saw that SysncMaster 910v was noavailable... and I selected it ! I couple of more screen-panels later... the install code reset the screen... it was all BLACK ! Again I can not do anything. !@#$% Again, using the rescuecd, I updated the /etc/inittab, and changed the init-mode from '5' (graphical) to '3' (text) Now when I re-boot the system, it comes up in test-mode... and I am able to logon with no problems. (wo-pee !) Once logged onto my general (non-root) userid, I enter "startx".... again get into a BLACK screen ! Is there some text-based configurator I can possible use to dig my way out of this problem? Any help would be certainly appreciated. Thanks. /Alan If this is still a problem with FC5, please attach the X log from the broken startup (ie, wait for X to start and the screen to go black, ssh in and copy the log file off). NEEDINFO timeout, resolving as INSUFFICIENT_DATA. If you are still experiencing this bug in FC6 or FC7, please reopen. Thanks for the report! |