|
Bugzilla – Full Text Bug Listing |
| Summary: | Samsung SyncMaster 955b monitor configuration ... | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Meeks <mmeeks> |
| Component: | SaX2 | Assignee: | Marcus Schaefer <ms> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | ||
| Version: | Beta 2 | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: |
hwinfo
xorg config sax log inc. DDC output |
||
|
Description
Michael Meeks
2005-08-19 10:21:09 UTC
Created attachment 46666 [details]
hwinfo
Created attachment 46667 [details]
xorg config
47: None 00.0: 10000 Monitor
[Created at fb.70]
Unique ID: rdCR.EY_qmtb9YY0
Hardware Class: monitor
Model: "Generic Monitor"
Vendor: "Generic"
Device: "Monitor"
Resolution: 1280x1024@77Hz
Driver Info #0:
Max. Resolution: 1280x1024
Vert. Sync Range: 50-90 Hz
Hor. Sync Range: 31-82 kHz
Config Status: cfg=new, avail=yes, need=no, active=unknown
your monitor couldn't be detected as you can see only a "generic"
entry which is based on your current framebuffer settings is available
Reasons:
--------
- monitor is not able of doing DDC
- monitor is connected via BNC
- graphics card driver doesn't support reading EDID record
- monitor is connected via switch which does not report DDC info
I'm sorry this is hardware issue I can't fix this
I find it amazing that nothing can be done; clearly something can be detected from the monitor - since it auto-selects the 'Samsung S4' (or something) in yast2 - which at least gets the vendor name right etc. The above output from hwinfo is (presumably) based on me manually setting up the monitor myself, and tweaking the display properties with the xvidtne thing. I attach the SaX.log that shows that DDC is there, and (apparently) working - unfortunately Sax2 generates an invalid setup based on it - and the monitor has this nice bouncing 'Sync out of range' thing it shows instead [ it's really quite a high-end monitor in fact ]. Created attachment 46676 [details]
sax log inc. DDC output
In this case the information you provided is inconsistent. your first hwinfo information points out that the monitor couldn't be detected. But if you have a SAMSUNG:SYNCMASTER 4S there is another bug report telling me the same story which may be a wrong entry in the CDB, still waiting for information on that bug *** This bug has been marked as a duplicate of 105577 *** I don't have a Syncmaster 4S; sax2 is however incorrectly identifying the monitor as a 4S. Apologies if you wanted the original broken X config attached - that doesn't seem to me that useful - if you do I can generate it. The attached above actually works - thought it'd be more helpful. Syncmaster Name: 955b: Model code: AQ19LS9T/EDC Some details snarfed from the web: 18 inch Çözünürlük : 1600x1200 (68Hz), 1280x1024 (79Hz), 1024x768 (104Hz) Frekansları : Yatay: 30 ~ 85 kHz. Dikey: 50 ~ 160 Hz Are you certain this is a duplicate ? Holy cow ... this is supposed to be support. Now i reported a similar issue with a Samsung Monitor very much like this one: https://bugzilla.novell.com/show_bug.cgi?id=167857 Let me repeat: Fedora has supported those monitors for more thaan 2 years. Why can't SuSE? Well - my SM955b at least does something sensible by default when I install newer distros; of course, it's prolly not the full resolution, but - I at least see things :-) |