From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 43835] System crashes when radeon firmware blob (R520_cp.bin) is installed
Date: Wed, 25 Jan 2012 18:56:22 +0000 [thread overview]
Message-ID: <bug-43835-502-RORFpmJlKN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-43835-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=43835
--- Comment #41 from Camaleón <noelamac@gmail.com> 2012-01-25 10:56:22 PST ---
(In reply to comment #40)
> Mesa is libgl1-mesa-dri and libgl1-mesa-glx. The DDX driver is[1]
> xserver-xorg-video-radeon and libdrm-radeon1, I suppose. One can get
> fairly recent versions of most packages from sid or experimental.
>
> [1] http://www.x.org/wiki/Development/Documentation/Glossary
Okay, thanks... wheezy and sid share the same versions of the mentioned
packages:
libgl1-mesa-glx (7.11.2-1)
libgl1-mesa-glx (7.11.2-1 and others)
xserver-xorg-video-radeon (1:6.14.3-2)
xserver-xorg-video-radeon (1:6.14.3-2 and others)
And I can't tell the user to update from experimental, it's too dangerous.
Anyway, I understand bugzilla is not the best place to discuss this support
things (though I thank your efforts, Jonathan and Xorg people) :-)
I have finally to surrender. If anyone thinks on anything we can try, you can
contact directly to me or add the information here. I leave this bug status at
your (@xorg devels) consideration.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2012-01-25 18:56 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 9:06 [Bug 43835] New: System crashes when radeon firmware blob (R520_cp.bin) is installed bugzilla-daemon
2011-12-14 17:19 ` [Bug 43835] " bugzilla-daemon
2011-12-14 17:22 ` bugzilla-daemon
2011-12-14 17:56 ` bugzilla-daemon
2011-12-15 8:49 ` bugzilla-daemon
2011-12-15 15:29 ` bugzilla-daemon
2011-12-15 15:47 ` bugzilla-daemon
2011-12-15 16:43 ` bugzilla-daemon
2011-12-15 16:44 ` bugzilla-daemon
2011-12-15 21:25 ` bugzilla-daemon
2011-12-15 21:28 ` bugzilla-daemon
2011-12-15 21:37 ` bugzilla-daemon
2011-12-15 21:40 ` bugzilla-daemon
2011-12-16 8:01 ` bugzilla-daemon
2011-12-16 8:17 ` bugzilla-daemon
2011-12-16 9:05 ` bugzilla-daemon
2011-12-16 9:51 ` bugzilla-daemon
2011-12-16 21:23 ` bugzilla-daemon
2011-12-16 22:48 ` bugzilla-daemon
2011-12-17 9:44 ` bugzilla-daemon
2012-01-22 21:46 ` bugzilla-daemon
2012-01-22 21:47 ` bugzilla-daemon
2012-01-22 21:48 ` bugzilla-daemon
2012-01-22 21:49 ` bugzilla-daemon
2012-01-22 21:49 ` bugzilla-daemon
2012-01-22 22:24 ` bugzilla-daemon
2012-01-23 21:21 ` bugzilla-daemon
2012-01-23 21:22 ` bugzilla-daemon
2012-01-23 21:25 ` bugzilla-daemon
2012-01-23 21:25 ` bugzilla-daemon
2012-01-23 21:40 ` bugzilla-daemon
2012-01-24 7:58 ` bugzilla-daemon
2012-01-24 8:00 ` bugzilla-daemon
2012-01-24 9:16 ` bugzilla-daemon
2012-01-25 17:16 ` bugzilla-daemon
2012-01-25 17:17 ` bugzilla-daemon
2012-01-25 17:37 ` bugzilla-daemon
2012-01-25 17:54 ` bugzilla-daemon
2012-01-25 18:10 ` bugzilla-daemon
2012-01-25 18:17 ` bugzilla-daemon
2012-01-25 18:35 ` bugzilla-daemon
2012-01-25 18:41 ` bugzilla-daemon
2012-01-25 18:56 ` bugzilla-daemon [this message]
2012-01-25 18:57 ` bugzilla-daemon
2012-01-25 20:39 ` bugzilla-daemon
2012-01-26 7:41 ` bugzilla-daemon
2012-01-26 13:59 ` bugzilla-daemon
2012-01-26 18:18 ` bugzilla-daemon
2012-02-02 12:04 ` bugzilla-daemon
2012-02-02 14:23 ` bugzilla-daemon
2012-02-02 14:36 ` bugzilla-daemon
2012-02-02 14:36 ` bugzilla-daemon
2012-02-02 16:34 ` bugzilla-daemon
2012-02-02 16:57 ` bugzilla-daemon
2012-02-10 1:55 ` bugzilla-daemon
2012-02-12 11:24 ` bugzilla-daemon
2012-02-12 11:26 ` bugzilla-daemon
2012-02-12 11:27 ` bugzilla-daemon
2012-02-12 11:27 ` bugzilla-daemon
2019-11-19 8:24 ` 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-43835-502-RORFpmJlKN@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox