© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Update:
Since numerous people have seen this problem during installation when the Xserver is probed I've looked into what's happening at this stage:
The Xserver is started with a standard config - only the line containing the bus id and driver name is special. The installation program then connects to the xserver to obtain the randr version and information about the available outputs. Nothing is ever drawn (except for the standard X background.
For now I would also rule out drm as it is initialized but never used (2d operations don't do use drm on this driver).
The probing scenario during installation can be reproduced on any running system with the command:
sysp -s xstuff
I'm currently condensing down the part that involves the X connection of this for better reproduction.
My goal is to narrow down where to look. The X driver is still a considerable chunk of code so it would be beneficial to reduce the possible sources of the problem.