Bug 140651 - Belinea 10 30 52 monitor not listed in hwdata
Belinea 10 30 52 monitor not listed in hwdata
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: hwdata (Show other bugs)
2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
: FutureFeature
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2004-11-23 19:11 EST by Kevin Kofler
Modified: 2014-03-16 22:50 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-11-23 21:23:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Kevin Kofler 2004-11-23 19:11:34 EST
Description of problem:
Under the Maxdata manufacturer, there are 3 Maxdata Belinea screens 
listed, but mine isn't.

Version-Release number of selected component (if applicable):
0.120-1

How reproducible:
Always.

Steps to Reproduce:
1. Run system-config-display.
2. Choose the option to change the screen.
3. Look at what's listed under Maxdata.
  
Actual results:
No Belinea 10 30 52.

Expected results:
A Belinea 10 30 52 entry.

Additional info:
Here are the proper settings for the screen (a 17" screen), as listed 
in the technical data:
	VendorName   "Maxdata"
	ModelName    "Belinea 10 30 52"
	DisplaySize  320	240
	HorizSync    30.0 - 97.0
	VertRefresh  50.0 - 150.0
	Option	     "dpms"
(The visible diagonal as given is 401.3 mm, which gives 321.04 mm 
horizontal and 240.70 mm vertical. The HorizSync and VertRefresh 
parameters come straight from the technical data. The screen supports 
DPMS.)

These settings follow straight from the specs and work fine for me, 
but if you don't trust me, you can also look straight at the 
manufacturer's INF file: 
ftp://ftp.maxdata.com/Belinea_Treiber_Driver/Belinea_346.inf
Comment 1 Bill Nottingham 2004-11-23 21:23:17 EST
Added in CVS, will be in future builds.

Note You need to log in before you can comment on or make changes to this bug.