From: Andrea <mariofutire@googlemail.com>
To: dri-devel@lists.freedesktop.org
Subject: 3.4.0 -> 3.5.0 bad rendering effects on radeon
Date: Sun, 12 Aug 2012 23:07:09 +0100 [thread overview]
Message-ID: <5028290D.2090306@googlemail.com> (raw)
Hi,
I use Fedora 17 and as soon as kernel 3.5 has been distributed, I get very bad
rendering artifacts on my laptop.
The laptop is a Thinkpad R50 with a radeon graphics card
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon RV250 [Mobility FireGL 9000] (rev 02)
It is not a new laptop, about 8 years old.
I've opened a bug at Fedora where you can see 2 pictures of what happens.
https://bugzilla.redhat.com/show_bug.cgi?id=845639
Reading the mailing list, I cannot understand if this problem has already been reported.
I've tried to bisect but I've hit a series of unbootable kernels.
"git bisect visualize" currently shows the log between
BAD: be122ab Merge tag 'spi-for-linus' of git://git.secretlab.ca/git/linux-2.6
GOOD: c10e408 i915: Add option to bypass vbt table.
where I can see a lot of drm related changes.
Regards
reply other threads:[~2012-08-12 22:07 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5028290D.2090306@googlemail.com \
--to=mariofutire@googlemail.com \
--cc=dri-devel@lists.freedesktop.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox