From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 35457] [rs690m] Graphics corruption with ati x1200 Date: Wed, 14 Oct 2015 12:48:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0996546838==" Return-path: Received: from culpepper.freedesktop.org (unknown [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id B1FC76E785 for ; Wed, 14 Oct 2015 05:48:23 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0996546838== Content-Type: multipart/alternative; boundary="1444826903.8b42862.14125"; charset="UTF-8" --1444826903.8b42862.14125 Date: Wed, 14 Oct 2015 12:48:23 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" https://bugs.freedesktop.org/show_bug.cgi?id=35457 --- Comment #102 from d4ddi0 --- (In reply to Micha from comment #101) > Another year with only a half working laptop :( > > Is there NOTHING I can do?!???!!!??! > > What causes the problems? The free radeon-driver? Mesa? > > PLEASE > HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > !!!!!!!!!!!!!!! I looked at your screenshots, Micha. Your problem looks like it has to do with the font and typeface. Both applications look like they use graphical tilesets to display fonts. I have no idea whether you are experiencing the same type of corruption described in this bug or something else. The problem with my system (which was fixed) was that the manufacturer (Gateway) put incorrect information about the amount of video ram. The manufacturer never supported Linux, and this type of graphics chip is relatively rare and odd compared to other radeon families. Open source radeon developers try to support us, but they don't have our same hardware. To be honest, I don't expect any remaining bugs with rs690 to get much attention. They are hard to find, and often problems with the firmware or hardware that radeon devs can't fix, only try to work around. Bottom line: No one is still looking at the driver for this hardware. You have access to the source code and can try looking at it yourself, but the pros haven't been able to figure it out; it might be hard or impossible to fix. -- You are receiving this mail because: You are the assignee for the bug. --1444826903.8b42862.14125 Date: Wed, 14 Oct 2015 12:48:23 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8"

Comment # 102 on bug 35457 from
(In reply to Micha from comment #101)
> Another year with only a half working laptop :(
> 
> Is there NOTHING I can do?!???!!!??!
> 
> What causes the problems? The free radeon-driver? Mesa?
> 
> PLEASE
> HELP!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
> !!!!!!!!!!!!!!!

I looked at your screenshots, Micha.
Your problem looks like it has to do with the font and typeface.
Both applications look like they use graphical tilesets to display fonts.
I have no idea whether you are experiencing the same type of corruption
described in this bug or something else.

The problem with my system (which was fixed) was that the manufacturer
(Gateway) put incorrect information about the amount of video ram. The
manufacturer never supported Linux, and this type of graphics chip is
relatively rare and odd compared to other radeon families.

Open source radeon developers try to support us, but they don't have our same
hardware. To be honest, I don't expect any remaining bugs with rs690 to get
much attention. They are hard to find, and often problems with the firmware or
hardware that radeon devs can't fix, only try to work around.

Bottom line: No one is still looking at the driver for this hardware.
You have access to the source code and can try looking at it yourself, but the
pros haven't been able to figure it out; it might be hard or impossible to fix.


You are receiving this mail because:
  • You are the assignee for the bug.
--1444826903.8b42862.14125-- --===============0996546838== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============0996546838==--