Thanks everyone, this fleshes in the table a lot better. It confirms what I suspected at the beginning - it's a mixed bag, great for some, poor for others, and unfortunately there's not a strong correlation between success and chip family, so black/whitelisting doesn't seem to be an option for us.
From what I gather, upstream is going to be sticking with UXA. Earlier on it sounded like they would backport stuff to EXA once it was ready, but recent comments make it sound like that is no longer the plan. So going forward I anticipate that Intel will be prioritizing support for UXA issues over EXA, which means we are going to be faced with the situation of a) user for whom UXA is better than EXA will be pushing us to move to UXA by default, and b) people for whom EXA has been working ok but UXA brings problems will be upset to see the regressions.
In my ideal world, what I would like to see is for us the distro to hold off on moving to UXA until it is more stable, and have technically able users such as yourselves take the initiative of working with upstream directly at getting the issues you've found investigated and solved. This would help Ubuntu out a lot in paving a path of stability with UXA that we can follow for Jaunty+1 (and maybe even Jaunty if enough work gets done in the next few weeks).
So I would like to encourage each of you to forward the issues you find upstream. Here is a link to use in filing your bugs:
When filing your bugs upstream, please always include your Xorg.0.log (and/or Xorg.0.log.old) after reproducing the issue with Option "ModeDebug" "true" in your xorg.conf. Also include your PCI IDs, which you can get by running the command `lspci -vvnn | grep -A2 "VGA compat"`.
Additional guidelines on filing bugs upstream to Intel are at http://intellinuxgraphics.org/how_to_report_bug.html - please be concise and specific in your reports, and be sure to follow up; this will help ensure the issue gets examined and addressed in a timely fashion for us. I'm particularly concerned for 8xx since it seems to get ignored too much, and I'd like to get awareness for the known issues upstream ASAP.
Once you've filed your bug, it would be wonderful if you could also include a link to the bug in your comments on the UxaTesting wiki page - https://wiki.ubuntu.com/X/UxaTesting - as this will help others with similar bugs, and make it easier for me to keep tabs on how stabilization is going. In particular, update the Result section once the issues you've encountered are no longer occurring on your system.
Thanks everyone, this fleshes in the table a lot better. It confirms what I suspected at the beginning - it's a mixed bag, great for some, poor for others, and unfortunately there's not a strong correlation between success and chip family, so black/whitelisting doesn't seem to be an option for us.
From what I gather, upstream is going to be sticking with UXA. Earlier on it sounded like they would backport stuff to EXA once it was ready, but recent comments make it sound like that is no longer the plan. So going forward I anticipate that Intel will be prioritizing support for UXA issues over EXA, which means we are going to be faced with the situation of a) user for whom UXA is better than EXA will be pushing us to move to UXA by default, and b) people for whom EXA has been working ok but UXA brings problems will be upset to see the regressions.
In my ideal world, what I would like to see is for us the distro to hold off on moving to UXA until it is more stable, and have technically able users such as yourselves take the initiative of working with upstream directly at getting the issues you've found investigated and solved. This would help Ubuntu out a lot in paving a path of stability with UXA that we can follow for Jaunty+1 (and maybe even Jaunty if enough work gets done in the next few weeks).
So I would like to encourage each of you to forward the issues you find upstream. Here is a link to use in filing your bugs:
https:/ /bugs.freedeskt op.org/ enter_bug. cgi?bug_ severity= major&component =Driver% 2Fintel& op_sys= Linux (All)&priority= high&product= xorg&version= 7.4
When filing your bugs upstream, please always include your Xorg.0.log (and/or Xorg.0.log.old) after reproducing the issue with Option "ModeDebug" "true" in your xorg.conf. Also include your PCI IDs, which you can get by running the command `lspci -vvnn | grep -A2 "VGA compat"`.
Additional guidelines on filing bugs upstream to Intel are at http:// intellinuxgraph ics.org/ how_to_ report_ bug.html - please be concise and specific in your reports, and be sure to follow up; this will help ensure the issue gets examined and addressed in a timely fashion for us. I'm particularly concerned for 8xx since it seems to get ignored too much, and I'd like to get awareness for the known issues upstream ASAP.
Once you've filed your bug, it would be wonderful if you could also include a link to the bug in your comments on the UxaTesting wiki page - https:/ /wiki.ubuntu. com/X/UxaTestin g - as this will help others with similar bugs, and make it easier for me to keep tabs on how stabilization is going. In particular, update the Result section once the issues you've encountered are no longer occurring on your system.