From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 35457] [rs690m] Graphics corruption with ati x1200
Date: Wed, 14 Oct 2015 12:48:23 +0000 [thread overview]
Message-ID: <bug-35457-502-RfcdorivTO@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-35457-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1737 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=35457
--- Comment #102 from d4ddi0 <stillcompiling@gmail.com> ---
(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.
[-- Attachment #1.2: Type: text/html, Size: 2593 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2015-10-14 12:48 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-35457-502@http.bugs.freedesktop.org/>
2013-11-27 15:13 ` [Bug 35457] [rs690m] Graphics corruption with ati x1200 bugzilla-daemon
2013-11-29 5:12 ` bugzilla-daemon
2013-11-29 6:12 ` bugzilla-daemon
2013-12-02 23:26 ` bugzilla-daemon
2013-12-02 23:27 ` bugzilla-daemon
2013-12-03 17:59 ` bugzilla-daemon
2013-12-11 16:48 ` bugzilla-daemon
2013-12-11 22:39 ` bugzilla-daemon
2013-12-12 6:38 ` bugzilla-daemon
2013-12-14 19:13 ` bugzilla-daemon
2013-12-17 12:00 ` bugzilla-daemon
2014-01-03 11:59 ` bugzilla-daemon
2014-01-03 16:33 ` bugzilla-daemon
2014-01-05 13:35 ` bugzilla-daemon
2014-01-05 13:36 ` bugzilla-daemon
2014-01-05 15:40 ` bugzilla-daemon
2014-01-05 18:29 ` bugzilla-daemon
2014-01-05 18:53 ` bugzilla-daemon
2014-09-11 5:36 ` bugzilla-daemon
2015-03-10 15:08 ` bugzilla-daemon
2015-03-10 15:11 ` bugzilla-daemon
2015-03-10 15:13 ` bugzilla-daemon
2015-03-30 14:03 ` bugzilla-daemon
2015-10-14 12:06 ` bugzilla-daemon
2015-10-14 12:48 ` bugzilla-daemon [this message]
2015-10-16 11:17 ` bugzilla-daemon
2016-02-10 12:44 ` bugzilla-daemon
2016-02-10 12:45 ` bugzilla-daemon
2016-02-10 14:07 ` bugzilla-daemon
2016-05-26 23:41 ` bugzilla-daemon
2016-05-26 23:44 ` bugzilla-daemon
2016-05-27 19:47 ` bugzilla-daemon
2016-05-27 19:51 ` bugzilla-daemon
2016-05-27 19:55 ` bugzilla-daemon
2016-06-06 4:54 ` bugzilla-daemon
2016-06-06 22:45 ` bugzilla-daemon
2016-09-09 9:21 ` bugzilla-daemon
2016-09-09 15:46 ` bugzilla-daemon
2017-02-19 0:16 ` bugzilla-daemon
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=bug-35457-502-RfcdorivTO@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--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 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.