From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67359] No direct rendering with Radeon HD 7750
Date: Sat, 27 Jul 2013 12:59:55 +0000 [thread overview]
Message-ID: <bug-67359-502-WQAx1Bawkw@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-67359-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 854 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67359
--- Comment #4 from Jim Schutt <74.schutt@gmail.com> ---
(In reply to comment #3)
> (In reply to comment #2)
> > [ 11.109017] [drm:r600_uvd_init] *ERROR* UVD not responding, giving up!!!
> > [ 11.109588] [drm:si_startup] *ERROR* radeon: failed initializing UVD (-1).
> >
>
> I'm not sure why uvd fails to load, this should be filed as a separate bug.
> I don't think it's related to your direct rendering problems.
>
OK, thanks.
>
> >
> > So, please don't resolve this as fixed just yet.
>
> This looks to me like a gentoo packaging bug. llvmpipe is using LLVM 3.1
> and radeonsi in Mesa 9.1.* requires a patched LLVM 3.2.
I'll try to get the proper LLVM running, and see if that helps.
Thanks for your help.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1824 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:[~2013-07-27 12:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 16:17 [Bug 67359] New: No direct rendering with Radeon HD 7750 bugzilla-daemon
2013-07-26 16:35 ` [Bug 67359] " bugzilla-daemon
2013-07-27 0:16 ` bugzilla-daemon
2013-07-27 2:56 ` bugzilla-daemon
2013-07-27 12:59 ` bugzilla-daemon [this message]
2014-01-23 12:31 ` bugzilla-daemon
2019-11-19 8:36 ` 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-67359-502-WQAx1Bawkw@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