Public bug reported:

There are still a lot of Monitors which don't have a propper EDID. The
autodetection can't detect them right, but there is no solution provided
to configure these Mpnitors manually or Displayconfig-gtk is broken. It
is a big bad expirience for a user if the resolution or the refresh-rate
is stck at a undisireble configuration. A too low refresh-rate is also
bad for health (60hz).


(A comment from the blueprints: 2008-03-10 bryce: This is considered complete 
now. There are a few corner cases where monitors aren't reporting proper EDID 
(such as if used with a KVM that drops the EDID pin) where rates must be 
manually specified, but it will never be possible to autodetect these; 
something like displayconfig-gtk is the right tool to use in these cases if one 
wishes to not deal with direct xorg.conf editing. Other unique cases, where the 
monitor is reporting EDID, but improperly, are being handled via monitor quirks 
into xserver on a case-by-case basis as they're discovered.)

** Affects: ubuntu
     Importance: Undecided
         Status: New

** Summary changed:

- Hardy - Monitors whitout EEID
+ Hardy - Monitors whitout EDID

** Description changed:

- There are still a lot of Monitors which don't have a propper EEID. The
- autodetection can't detect them right, but ther is no solution provided
+ There are still a lot of Monitors which don't have a propper EDID. The
+ autodetection can't detect them right, but there is no solution provided
  to configure these Mpnitors manually or Displayconfig-gtk is broken. It
  is a big bad expirience for a user if the resolution or the refresh-rate
  is stck at a undisireble configuration. A too low refresh-rate is also
  bad for health (60hz).
  
  
  (A comment from the blueprints: 2008-03-10 bryce: This is considered complete 
now. There are a few corner cases where monitors aren't reporting proper EDID 
(such as if used with a KVM that drops the EDID pin) where rates must be 
manually specified, but it will never be possible to autodetect these; 
something like displayconfig-gtk is the right tool to use in these cases if one 
wishes to not deal with direct xorg.conf editing. Other unique cases, where the 
monitor is reporting EDID, but improperly, are being handled via monitor quirks 
into xserver on a case-by-case basis as they're discovered.)

-- 
Hardy - Monitors whitout EDID
https://bugs.launchpad.net/bugs/219815
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to