Comment 23 for bug 137234
Revision history for this message
|
|
#23 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
The behavior described by the user is pretty weird. I don't think the pipea force quirk is the problem though, that would just leave the output on but shouldn't break anything.
Moreover, the resolutions for the VGA connected displays seem to be detected properly, so I'm not sure why things aren't working for him.
The screen shot looks typical of what you'd expect a cloned configuration to look like where one head was running at a different resolution than the LCD (that's why the desktop is smaller).
Maybe you can try setting different modes by hand on the external displays by hand? E.g.
$ xrandr --output VGA --mode 800x600 --right-of LVDS
or something. Also choosing a lower refresh rate might help.
The last comment in the launchpad entry is disturbing too, he says with the latest bits VGA isn't even detected properly, even when a display is plugged in? That sounds bad...
The logs actually look pretty normal; what you'd expect for a dual head config.