Bug 22977

Created attachment 28055 [details]
Screenshot.png

Will you please double check whether it can work well if not using the external monitor?
Will you please attach the xorg.log with option modedebug in xorg.conf and vbios dump?
   The vbios dump can be obtained by using the following command:
    echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
    cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump
    echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom

Thanks.

Im nore sure i understand what you ask? enabled modebug in xorg.conf and change resolution on the laptop monitor?

Or reproduce the problem with modebug enabled? 

(In reply to comment #3)
> Im nore sure i understand what you ask? enabled modebug in xorg.conf and change
> resolution on the laptop monitor?
> 
To add the modedebug option in xorg.conf is only to get more debug info.
Please attach the xorg.log after adding the modedebug option in xorg.conf.
Thanks.
> Or reproduce the problem with modebug enabled? 
> 

I have added the xorg-edgers repository on Launchpad to get the xserver-xorg-intel package directly from upstream. It works like a charm. But instead im experiencing performance drops on weird places. 

since fixed in upstream, I'll mark this bug as resolved. for the performance dropping issue, please open a new bug to track it. thanks.

Michael, please indicate the release version that will contain this fix?

Or if you're unsure, just point me at the patch you think fixed it so I can include it in Karmic.

(In reply to comment #5)
> I have added the xorg-edgers repository on Launchpad to get the
> xserver-xorg-intel package directly from upstream. It works like a charm. But
> instead im experiencing performance drops on weird places. 
> 

 Benedikt Kristinsson, would you please be able to help bi-sect? thanks!

(In reply to comment #7)
> Michael, please indicate the release version that will contain this fix?
> 
> Or if you're unsure, just point me at the patch you think fixed it so I can
> include it in Karmic.
> 

I can only assume it's in the latest 2.8.1, given the time the Benedikt tested the xorg-edgers repository on Launchpad. without Benedikt's bi-sect, it's hard for me to figure out exact commit that caused the problem and fixed the problem..sorry..

(In reply to comment #9)
> I can only assume it's in the latest 2.8.1, given the time the Benedikt tested
> the xorg-edgers repository on Launchpad. without Benedikt's bi-sect, it's hard
> for me to figure out exact commit that caused the problem and fixed the
> problem..sorry..

bi-sect?

I have been away on vacation (just got home yesterday) without my laptop (and screen of course). Tomorrow I will set up karmic alpha4 and test the version of -intel there and then upgrade to edgers (upstream) and see how that one works. If it is still causing the slow rendering I will try to eliminate the package causing the problem. 

I will leave it as "resolved" until I can confirm it is still broken for me. 

Testing with Karmic Alpha 4

Boots up in dock (port replicator) with laptop screen blinking between green, blue
and red. Screen is connected to VGA through dock. Loading bar is shown, but with
strange artifacts. X loads with the wrong (1024x768) resolution instead of the right
(1600x1200) and laptop screen continues to flash the colors.

I disable the laptop screen with the display tool. After that, resolution change
to 1600x1200 works fine. Trying to move the display to the laptop screen with
the display applet results in the same color madness. Waiting 15 seconds makes
the applet switch back to the external monitor.

man intel shows xf86-video-intel 2.8.0. Shouldn't this be xorg?

Booting with the screen disconnected results in the color madness during boot.
X doesnt come up and the other tty's are inaccessible. Tried twice, waited for
~10 minues. Then plugged the laptop into the port replicator with the screen and
works like described before (color madness on laptop screen, loads on external
with artifacts). Est loading time 3-4 minutes.

This behavior is nothing like jaunty or alpha2 of karmic. Attached is the Xorg
log file for the successful boot.

Why did the manpage say xf86 at the bottom. The rest of the man page talks
about XOrg.

Created attachment 29084 [details]
Xorg log from Karmic alpha 4. xf86-video-intel 2.8.0

Xorg log from Karmic alpha 4. Booted with screen in port replicator. Laptop screen loops colors. xf86-video-intel 2.8.0

(In reply to comment #12)
> Created an attachment (id=29084) [details]
> Xorg log from Karmic alpha 4. xf86-video-intel 2.8.0
> 
> Xorg log from Karmic alpha 4. Booted with screen in port replicator. Laptop
> screen loops colors. xf86-video-intel 2.8.0
> 

please attach a regdump grabbed after system boot up ( without any changing ). 

if you didn't connect the external monitor, everything works fine for you, right? again, please attach a regdump in this case as well. thanks.

intel_reg_dumper is available in the xserver-xorg-video-intel-dbg package.

Also, please have a try to make the settings using xrandr tool directly - somehow, I don't trust the resolution applet ...

(In reply to comment #13)
> (In reply to comment #12)

> please attach a regdump grabbed after system boot up ( without any changing ). 
Attached. Was run with the external monitor (it's the only display working). 

> if you didn't connect the external monitor, everything works fine for you,
> right? again, please attach a regdump in this case as well. thanks.
No. If I don't connect the external monitor the laptop monitor displays the color madness (blinking between: white, black, red, green and blue). 

If I connect the external minotor it works, but doesnt get the native resolution without disabling the laptop monitor. 

> Also, please have a try to make the settings using xrandr tool directly -
> somehow, I don't trust the resolution applet ...
Same result here. 

I am still curious why the driver name features "xf86"?

Created attachment 29124 [details]
intel_reg_dumper run with external monitor on Karmic.

this size of panel has to be a dual-channel , but i see 

 LVDS: 0xc0300300 (enabled, pipe B, 18 bit, 1 channel)

(In reply to comment #2)
> Will you please double check whether it can work well if not using the external
> monitor?
> Will you please attach the xorg.log with option modedebug in xorg.conf and
> vbios dump?
>    The vbios dump can be obtained by using the following command:
>     echo 1 > /sys/devices/pci0000:00/0000:00:02.0/rom
>     cat /sys/devices/pci0000:00/0000:00:02.0/rom >vbios.dump
>     echo 0 > /sys/devices/pci0000:00/0000:00:02.0/rom
> 
> Thanks.
> 

 Benedikt, this is still useful, please provide. thanks.

Created attachment 29279 [details]
vbois dump on karmic, xserver-xorg-video-intel 2.8.0

Created attachment 29282 [details]
Xorg.0.log with Option ModeDebug

X starts with just a blank screen with this X config.

I don't know that much about X, but if I might speculate I might have a vague idea of what is going on. 

To be able to modify the xorg.conf and start up with Option ModeDebug I ssh'ed from another machine. When I killed X, the tty's came up on the external monitor (utilizing its 1600x1200 resolution). It looks to me as it has decied to ignore the laptop monitor totally. 

I have no idea why the laptop monitor just shows that color madness, but it obvously has something to do with the fact that X has decided to ignore that screen. 

Please correct me if I am wrong, or tell me more if I am correct. 

might be dup of bug# 20115. pls try the kernel patch at the last comment

reopen if the patch in bug# 20115 doesn't work for you... thanks.

*** This bug has been marked as a duplicate of bug 20115 ***