2008-02-09 06:02:48 |
Bruce Miller |
bug |
|
|
added bug |
2008-02-09 07:39:23 |
Timo Aaltonen |
xorg: status |
New |
Incomplete |
|
2008-02-09 16:55:53 |
Bruce Miller |
bug |
|
|
added attachment 'Xorg.0.log_brm-2008-02-09T1100-5' (Xorg.0.log_brm-2008-02-09T1100-5) |
2008-02-12 14:55:33 |
Bruce Miller |
bug |
|
|
added attachment 'Xorg.0.log' (Xorg.0.log) |
2008-02-12 17:25:14 |
Timo Aaltonen |
description |
I had an opportunity to discuss a few days ago with members of Dell's Ubuntu support team the known failure of their popular Dell 2405 FPW widescreen monitor to provide EDID information.
These Dell staff told me that they had provided Canonical with information necessary to allow automatic identification of this monitor and to file a bug if it did not work in current versions of Ubuntu. Hence this bug report based on my current installation of Kubuntu Hardy Alpha 4.
The resolutions, horizontal and vertical refresh rates in the automatically generated xorg.conf are all wrong:
HorizSync 30.0 - 110.0 # should be 30 kHz to 81 kHz
VertRefresh 50.0 - 150.0 # should be 56 Hz to 76 Hz
... <snip> ...
Modes "1600x1200" "1280x1024" "1024x768" "800x600" "640x480" # should include 1920x1200 |
The free nv driver crashes after being used 20-30 seconds. |
|
2008-02-12 17:25:14 |
Timo Aaltonen |
title |
edidfail for widescreen lcd (Dell 2405 FPW) causes incorrect resolution and refresh rates |
[hardy] nv crashes after a while |
|
2008-02-12 17:26:53 |
Timo Aaltonen |
xorg: importance |
Undecided |
High |
|
2008-02-12 18:45:21 |
Bruce Miller |
bug |
|
|
added attachment 'xsession-errors' (xsession-errors) |
2008-02-12 18:46:21 |
Bruce Miller |
bug |
|
|
added attachment 'Xorg.0.log.nv.didntwork-20080212' (Xorg.0.log.nv.didntwork-20080212) |
2008-02-12 18:47:02 |
Bruce Miller |
bug |
|
|
added attachment 'xorg.conf.gutsy.nv.didntwork-20080212' (xorg.conf.gutsy.nv.didntwork-20080212) |
2009-02-22 03:47:27 |
Duane Hinnen |
xserver-xorg-video-nv: status |
Incomplete |
Invalid |
|
2009-02-22 03:47:27 |
Duane Hinnen |
xserver-xorg-video-nv: statusexplanation |
Ok, now we are talking ;)
Does the nv-driver work fine with gutsy? |
We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|