From: Sven Joachim <svenjoac@gmx.de>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keith Packard <keithp@keithp.com>
Subject: Re: i915 regression with 3.3-rc3+git
Date: Thu, 23 Feb 2012 19:16:54 +0100 [thread overview]
Message-ID: <8739a12z55.fsf@turtle.gmx.de> (raw)
In-Reply-To: <20120223084106.4b132532@jbarnes-desktop> (Jesse Barnes's message of "Thu, 23 Feb 2012 08:41:06 -0800")
On 2012-02-23 17:41 +0100, Jesse Barnes wrote:
> On Fri, 17 Feb 2012 21:48:13 +0100
> Riccardo Magliocchetti <riccardo.magliocchetti@gmail.com> 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
next prev parent reply other threads:[~2012-02-23 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 20:48 i915 regression with 3.3-rc3+git Riccardo Magliocchetti
2012-02-23 16:41 ` Jesse Barnes
2012-02-23 18:16 ` Sven Joachim [this message]
2012-02-23 18:48 ` Riccardo Magliocchetti
2012-02-23 18:55 ` Jesse Barnes
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8739a12z55.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=jbarnes@virtuousgeek.org \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riccardo.magliocchetti@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.