Red Hat Bugzilla – Bug 428828
hwdata, MonitorsDB, LG List
Last modified: 2009-01-20 17:11:14 EST
this is part of my attempt to unify MonitorDB over all releases
+++ This bug was initially created as a clone of Bug #367111 +++
I decided to make a patch insted of placing everything here. It's a very long list.
The patch is based on the hwdata-0.207-1 package
Added 656 LG monitors
Added 2 NEC monitors
Added 1 OKI monitor
Added 3 ACER monitors
The EISA ID has been checked before submitting the new entires. No duplicates.
Some existing duplicade entries has been removed and corrected. Example:
Acer; Acer 1768i; api424c; 30.0-69.0; 50.0-110.0; 1
Acer; Acer 76ie; API424C; 30.0-69.0; 50.0-110.0
Where the model name '1768i' is the windows drivers name and not the monitors
model name. These entries has been corrected as:
Acer; Acer 76ie; API424C; 30.0-69.0; 50.0-110.0; 1
12 double entries has been corrected.
Some existing entries has been updated where DPMS suppor is available.
In some places, LG is using different modelnames 'xy', 'FLATRON xy' or 'FLATRON
LCD xy' for the same model/EISA ID. I skipped those fancy FLATRON names and used
simply the short name version 'xy'.
Hope this helps and it's usefull. Use it as you whish.
Ps: Why does LG need over 600 model name???
-- Additional comment from firstname.lastname@example.org on 2007-11-05 12:16 EST --
Created an attachment (id=248441)
MonitorsDB LG patch
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.