MonitorsDB doesn't include Samsung SyncMaster 214T (which reports wrong capabilities)

Bug #84588 reported by Arne Christensen
4
Affects Status Importance Assigned to Milestone
kde-guidance (Ubuntu)
Fix Released
Wishlist
Unassigned

Bug Description

I Installed Kubuntu 6.10 on a system with a Samsung SyncMaster 214T flatpanel display, and found that this particular display was not auto-detected.

Launching System Settings, selecting "Monitor & Display", then "Hardware" I did not find this particular display in the list either, and it couldn't be auto-detected (that's consistent at least). "Detect monitor" gives me a "Plug'n'play" display which gives me a 65 Hz refresh - which causes the 214T to complain every time it is turned on, because this is not the optimal refresh rate. It wants 60 Hz. I finally selected in the list under "Generic" a "Flat panel 1600x1200" and now it's working nicely.

By the way I notice that the SyncMaster 244T too is missing in the selection list of displays. Maybe the list is just a bit old?

Revision history for this message
Brian Murray (brian-murray) wrote :

Thanks for your bug report. Could you please add your '/var/log/Xorg.0.log' file and the output of 'sudo xresprobe videodriver' where videodriver is the driver you use for your video card? (For example radeon or fglrx.) Thanks in advance.

Revision history for this message
Arne Christensen (arne-chr) wrote :

Thanks for a very fast reply. I'm attaching the requested Xorg.0.log and including the results from xresprobe below. The "freq" part matches exactly the numbers that "Detect Monitor" finds. The rest makes me start thinking if the 214T is at fault?

root@bbb:/var/log# xresprobe i810
id: SyncMaster
res: 1600x1200 1280x1024 1280x960 1152x864 1024x768 832x624 800x600 720x400 640x480
freq: 30-81 56-75
disptype: crt

Revision history for this message
Brian Murray (brian-murray) wrote :

Yes, it does seem to be your monitors fault. In your Xorg.0.log file you can see the monitor is probed via DDC to determine what resolutions the monitor supports. The monitor then returns information equalivalent to what we saw with the output of xresprobe. Unfortunately there is nothing we can do to resolve your issue. You may consider contacting the manufacturer of the monitor and let them know about the issue. With your permission I would like to close the bug report.

Revision history for this message
Arne Christensen (arne-chr) wrote :

I see the problem with the automatic detection. However, there is one improvement that maybe could be done: The 214T could be added to the monitor list in the manual configuration GUI. Then anyone would be able to correct the configuration easily (more easily at least). I have absolutely no idea where that list is found or who might be responsible for maintaining it? (Now I'm thinking of the next guy with a Samsung - part of my reason for installing Kubuntu was to evaluate its usefulness for the less technically minded.)
But kudos for an extremely fast response! Thanks for the help.

Revision history for this message
Sebastian Kügler (sebasje) wrote :

I'm also asking myself if we shouldn't use the hwdata package (which brings the MonitorsDB file with it). Guidance ships the same file (but I'm unsure if not the hwdata version is used anyway.)

In any case, it probably makes more sense to file this bug against the hwdata package. The guidance team only updates the file shipped from time to time, and the 214T doesn't seem to be in there.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

hwdata is not used in Ubuntu. This monitor is included at least in 7.10.

Changed in hwdata:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.