Okay, after investigating how NULL EDID is handled a bit more thoroughly (for #288807), I think I understand what is happening.
In general monitors are supposed to provide either EDID or DDC data about their capabilities. Various monitors don't do this, or do this so improperly that they may as well not be doing it. Old model Vaio laptops seem to be particularly afflicted by this. I can imagine that many off-brand monitors do as well. In the case of laptops, I can think of a couple ways to hardcode our way around the problem (see proposed solutions on bug #288807). For desktop systems, well I think there is no way to automatically configure these systems reliably enough, so xorg.conf's will just have to be created in this case. As a better longer term solution for this we're considering an xorg.conf display configuration tool (ref. Alberto Milone's screen-configuration-ui blueprint), but that's going to be in the Jaunty+1/+2 timeframe, and it's going to require user involvement to specify monitor type and so on. Those desperate for a GUI-based solution could look at displayconfig-gtk (there are debs available from one of the reporters on bug #288807), but for a variety of reasons we no longer support that tool in Ubuntu proper. -- Kubuntu live CD (and install) hangs during boot on Vaio PCG-K215Z [Radeon 9200] https://bugs.launchpad.net/bugs/221329 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
