Bug#623157: xserver-xorg-video-intel: Intel 830MG keeps swapping blank/screen betw. VGA1/LVDS1
tag 623157 moreinfo
kthxbye
On Sun, Apr 17, 2011 at 21:38:32 +0200, Stephan Fuhrmann wrote:
> Package: xserver-xorg-video-intel
> Version: 2:2.13.0-6
> Severity: normal
>
> Hi,
>
> I'm using this video card:
>
> 00:02.0 VGA compatible controller: Intel Corporation 82830 CGC [Chipset
> Graphics Controller] (rev 04) (prog-if 00 [VGA controller])
> Subsystem: IBM Device 0505
> Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
> <TAbort- <MAbort- >SERR- <PERR- INTx-
> Latency: 0
> Interrupt: pin A routed to IRQ 11
> Region 0: Memory at 98000000 (32-bit, prefetchable) [size=128M]
> Region 1: Memory at 90100000 (32-bit, non-prefetchable) [size=512K]
> Expansion ROM at <unassigned> [disabled]
> Capabilities: <access denied>
> Kernel driver in use: i915
>
> but since Debian Squeeze I have problems with it. The screen switches to
> blank and back to display now and then. Notebook is no longer usable.
>
> X-log contains entries like this:
>
> ....
> (II) intel(0): Allocated new frame buffer 1024x768 stride 2048, untiled
> (II) intel(0): Allocated new frame buffer 2048x768 stride 4096, untiled
> (II) intel(0): Allocated new frame buffer 1024x768 stride 2048, untiled
> (II) intel(0): Allocated new frame buffer 2048x768 stride 4096, untiled
> (II) intel(0): Allocated new frame buffer 1024x768 stride 2048, untiled
> (II) intel(0): Allocated new frame buffer 320x200 stride 640, untiled
> (II) intel(0): Allocated new frame buffer 1024x768 stride 2048, untiled
> (II) intel(0): Allocated new frame buffer 2048x768 stride 4096, untiled
> (II) intel(0): Allocated new frame buffer 1024x768 stride 2048, untiled
> (II) intel(0): Allocated new frame buffer 2048x768 stride 4096, untiled
> (II) intel(0): Allocated new frame buffer 1024x768 stride 2048, untiled
> (II) intel(0): Allocated new frame buffer 2048x768 stride 4096, untiled
>
> This call fixes the problem:
>
> xrandr --screen 0 --output LVDS1 --auto --primary --output VGA1 --off
>
> Calls to "xrandr" without parameters switch between blank screen, and after
> a second call always back to normal. It looks like the VGA1 (unconnected)
> connector and the LVDS1 (built-in TFT) get exchanged by random on this
> notebook. This is at least how the output of the good xrandr call and the
> bad xrandr call differ: One shows VGA1 stuff.
>
Does upgrading to a 3.0 or 3.1 kernel improve this? If not please file
a bug upstream following
http://intellinuxgraphics.org/how_to_report_bug.html and include dmesg
when booting with drm.debug=4 and register dumps in the good/bad cases
obtained with the intel_reg_dumper tool from
http://cgit.freedesktop.org/xorg/app/intel-gpu-tools
Cheers,
Julien
Reply to: