Hello,
i've upgraded from 3.2.0-rc7 to post 3.3.0-rc3 git
4903062b5485f0e2c286a23b44c9b59d9b017d53, attached you can find dmesg
with drm.debug=0xfff
This started to appear in logs:
[drm:intel_framebuffer_init] *ERROR* unsupported pixel format
X is getting a wrong resolution (log attached) and there's a lot of
flickering, if i try to play a video the desktop turns black, the other
ttys still works fine though.
Please CC me since i'm not subscribed.
00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA
controller])
Subsystem: Samsung Electronics Co Ltd Device c045
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at f8000000 (64-bit, non-prefetchable) [size=4M]
Memory at d0000000 (64-bit, prefetchable) [size=256M]
I/O ports at 1800 [size=8]
Expansion ROM at <unassigned> [disabled]
Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
Capabilities: [d0] Power Management version 3
Kernel driver in use: i915
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
Integrated Graphics Controller (rev 07)
Subsystem: Samsung Electronics Co Ltd Device c045
Flags: bus master, fast devsel, latency 0
Memory at f8400000 (64-bit, non-prefetchable) [size=1M]
Capabilities: [d0] Power Management version 3
Thanks
--
Riccardo Magliocchetti
On Fri, 17 Feb 2012 21:48:13 +0100
Riccardo Magliocchetti <[email protected]> wrote:
> Hello,
>
> i've upgraded from 3.2.0-rc7 to post 3.3.0-rc3 git
> 4903062b5485f0e2c286a23b44c9b59d9b017d53, attached you can find dmesg
> with drm.debug=0xfff
>
> This started to appear in logs:
>
> [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
>
> X is getting a wrong resolution (log attached) and there's a lot of
> flickering, if i try to play a video the desktop turns black, the other
> ttys still works fine though.
>
> Please CC me since i'm not subscribed.
>
> 00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series
> Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA
> controller])
> Subsystem: Samsung Electronics Co Ltd Device c045
> Flags: bus master, fast devsel, latency 0, IRQ 45
> Memory at f8000000 (64-bit, non-prefetchable) [size=4M]
> Memory at d0000000 (64-bit, prefetchable) [size=256M]
> I/O ports at 1800 [size=8]
> Expansion ROM at <unassigned> [disabled]
> Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
> Capabilities: [d0] Power Management version 3
> Kernel driver in use: i915
>
> 00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset
> Integrated Graphics Controller (rev 07)
> Subsystem: Samsung Electronics Co Ltd Device c045
> Flags: bus master, fast devsel, latency 0
> Memory at f8400000 (64-bit, non-prefetchable) [size=1M]
> Capabilities: [d0] Power Management version 3
>
> Thanks
>
Can you check the drm-intel-fixes branch at
git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git?
It has a fix for laod detection that might help.
--
Jesse Barnes, Intel Open Source Technology Center
On 2012-02-23 17:41 +0100, Jesse Barnes wrote:
> On Fri, 17 Feb 2012 21:48:13 +0100
> Riccardo Magliocchetti <[email protected]> wrote:
>
>> Hello,
>>
>> i've upgraded from 3.2.0-rc7 to post 3.3.0-rc3 git
>> 4903062b5485f0e2c286a23b44c9b59d9b017d53, attached you can find dmesg
>> with drm.debug=0xfff
>>
>> This started to appear in logs:
>>
>> [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
>>
>> X is getting a wrong resolution (log attached) and there's a lot of
>> flickering, if i try to play a video the desktop turns black, the other
>> ttys still works fine though.
I noticed very similar problems when I upgraded from 3.2 to 3.3-rc4 on
my laptop. Same error message but the symptoms were worse, got a black
screen when the display manager started X.
> Can you check the drm-intel-fixes branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git?
> It has a fix for laod detection that might help.
Works great for me, thanks.
Cheers,
Sven
Hello,
Il 23/02/2012 17:41, Jesse Barnes ha scritto:
> On Fri, 17 Feb 2012 21:48:13 +0100
> Riccardo Magliocchetti<[email protected]> wrote:
>
>> Hello,
>>
>> i've upgraded from 3.2.0-rc7 to post 3.3.0-rc3 git
>> 4903062b5485f0e2c286a23b44c9b59d9b017d53, attached you can find dmesg
>> with drm.debug=0xfff
>>
>> This started to appear in logs:
>>
>> [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
>>
>> X is getting a wrong resolution (log attached) and there's a lot of
>> flickering, if i try to play a video the desktop turns black, the other
>> ttys still works fine though.
>>
>>
>
> Can you check the drm-intel-fixes branch at
> git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git?
> It has a fix for laod detection that might help.
3.3-rc4 plus these two patches from drm-intel-fixes works great.
4e9bb47bd29e02f2daaa7bdb2a8ddf977bf76f06 [PATCH 2/2] drm/i915: fix a
sprite watermark computation to avoid divide by zero if xpos<0
5ca0c34ae28344b6b4ca3036bc82f89c8db16a59 [PATCH 1/2] drm/i915: fix mode
set on load pipe. (v2)
Thanks!
riccardo
On Thu, 23 Feb 2012 19:48:59 +0100
Riccardo Magliocchetti <[email protected]> wrote:
> Hello,
>
> Il 23/02/2012 17:41, Jesse Barnes ha scritto:
> > On Fri, 17 Feb 2012 21:48:13 +0100
> > Riccardo Magliocchetti<[email protected]> wrote:
> >
> >> Hello,
> >>
> >> i've upgraded from 3.2.0-rc7 to post 3.3.0-rc3 git
> >> 4903062b5485f0e2c286a23b44c9b59d9b017d53, attached you can find dmesg
> >> with drm.debug=0xfff
> >>
> >> This started to appear in logs:
> >>
> >> [drm:intel_framebuffer_init] *ERROR* unsupported pixel format
> >>
> >> X is getting a wrong resolution (log attached) and there's a lot of
> >> flickering, if i try to play a video the desktop turns black, the other
> >> ttys still works fine though.
> >>
> >>
> >
> > Can you check the drm-intel-fixes branch at
> > git://git.kernel.org/pub/scm/linux/kernel/git/jbarnes/drm-intel.git?
> > It has a fix for laod detection that might help.
>
> 3.3-rc4 plus these two patches from drm-intel-fixes works great.
>
> 4e9bb47bd29e02f2daaa7bdb2a8ddf977bf76f06 [PATCH 2/2] drm/i915: fix a
> sprite watermark computation to avoid divide by zero if xpos<0
> 5ca0c34ae28344b6b4ca3036bc82f89c8db16a59 [PATCH 1/2] drm/i915: fix mode
> set on load pipe. (v2)
Great, thanks for confirming.
--
Jesse Barnes, Intel Open Source Technology Center