And can you also attach the Xorg.0.log from Jaunty? To get the most information out of it, you should add
Option "ModeDebug" "true"
to you xorg.conf, restart X (by for example logging out and in again) and then grab /var/log/Xorg.0.log.
I suspect the EDID error you get is because the get-edid program doesn't properly support the E-EDID standard. If you run `get-edid | hd` you will see that the second last byte is 01, which means that there is one extension. For most monitors this is 00 (for no extensions) and I guess that maybe get-edid does not support extensions. There is a new version of EDID in the PPA https://launchpad.net/~intuitivenipple/+archive/ppa/ which you may try (see also bug https://bugs.launchpad.net/debian/+bug/242043), but I don't know if this issue addressed here. Anyway, this should be independent of the EDID handling in Xorg.
Also, if you have a ~/.config/monitors.xml, please rename it or delete it as there may be some old resolution settings there.
And can you also attach the Xorg.0.log from Jaunty? To get the most information out of it, you should add Xorg.0. log.
Option "ModeDebug" "true"
to you xorg.conf, restart X (by for example logging out and in again) and then grab /var/log/
I suspect the EDID error you get is because the get-edid program doesn't properly support the E-EDID standard. If you run `get-edid | hd` you will see that the second last byte is 01, which means that there is one extension. For most monitors this is 00 (for no extensions) and I guess that maybe get-edid does not support extensions. There is a new version of EDID in the PPA https:/ /launchpad. net/~intuitiven ipple/+ archive/ ppa/ which you may try (see also bug https:/ /bugs.launchpad .net/debian/ +bug/242043), but I don't know if this issue addressed here. Anyway, this should be independent of the EDID handling in Xorg.
Also, if you have a ~/.config/ monitors. xml, please rename it or delete it as there may be some old resolution settings there.