Bug 485019 - Unable to detect Envision LCD Display : G19LWK
Unable to detect Envision LCD Display : G19LWK
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-nv (Show other bugs)
i386 Linux
low Severity medium
: ---
: ---
Assigned To: Ben Skeggs
Fedora Extras Quality Assurance
: Triaged
Depends On:
  Show dependency treegraph
Reported: 2009-02-11 02:13 EST by terrian
Modified: 2018-04-11 14:13 EDT (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:53:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
in3ight: needinfo-

Attachments (Terms of Use)
Xorg.0.log (25.54 KB, text/plain)
2009-02-26 00:05 EST, terrian
no flags Details
Xorg.0.log.old (25.84 KB, text/plain)
2009-02-26 00:06 EST, terrian
no flags Details

  None (edit)
Description terrian 2009-02-11 02:13:30 EST
Description of problem:

Version-Release number of selected component (if applicable):
Release 10 ( Cambridge )
Kernel Linux

How reproducible:
Using Envision LCD Display : Model G19LWK

Steps to Reproduce:
1.System - Hardware -Screen Resolution
2.Detect Displays
3.Result - Unknown

Actual results:

Expected results:
Should detect Envision LCD Display - G19LWK

Additional info:
19" LCD - Max Resolution : 1440x900

Only able to set to 800x600 resolution
Comment 1 Matěj Cepl 2009-02-25 18:30:16 EST
Thanks for the bug report.  We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please try to run without any X server config file (/etc/X11/xorg.conf whatsoever, and attach X server log file (/var/log/Xorg.*.log) to this bug report as individual uncompressed file attachment using the bugzilla file attachment link below.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.
Comment 2 terrian 2009-02-26 00:05:01 EST
Created attachment 333279 [details]

Attached Xorg.0.log
Comment 3 terrian 2009-02-26 00:06:19 EST
Created attachment 333280 [details]

attached Xorg.0.log.old
Comment 4 Ben Skeggs 2009-08-23 21:42:15 EDT
I know this is an old bug, but if you still have the hardware, is there any chance of trying either F11 or rawhide?
Comment 5 Bug Zapper 2009-11-18 06:05:11 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '10'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 10's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 10 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 6 Bug Zapper 2009-12-18 02:53:22 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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