Will you please add the boot option of "drm.debug=0x04" and attach the output of dmesg?

Thanks.

It's well possible I may not be able to test this before beginning of June.  Please bear with me.

Sorry, beginning of July, even.

Wow, this is an old one.  Assuming it's fixed though.

X will configure the outputs differently depending on what's connected at startup, so this could be expected behavior.  You may have to unclone or unmirror the displays after starting up this way before you can change things.

Created attachment 40650 [details]
dmesg log with drm.debug=0x04

(In reply to comment #4)
> Wow, this is an old one.  Assuming it's fixed though.

Old?  It's only been a few months old.  I apologize for the delay beyond the previously envisioned month of July.  I travel a lot and for extended periods of time and I can only test this at home.

Today, I booted with the latest Ubuntu mainline kernel (2.6.36-999-generic) and the issue is still present, albeit differently and to a much less severe degree.  The gdm login on my netbook will not be 1024*600 but 800*600.  Once I'm logged in to X, the resolution on the internal and external display is at it should be.

I attach the requested log.

The kernel is behaving correctly; the fbcon is expected to be complete on all attached displays (its primary design role is for kernel panics). Your gui display applet is at fault here, convince yourself by using xrandr from the commandline instead.