From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 67283] New: VDPAU doesn't work on hybrid laptop through DRI_PRIME
Date: Thu, 25 Jul 2013 01:00:01 +0000 [thread overview]
Message-ID: <bug-67283-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2320 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=67283
Priority: medium
Bug ID: 67283
Assignee: dri-devel@lists.freedesktop.org
Summary: VDPAU doesn't work on hybrid laptop through DRI_PRIME
Severity: normal
Classification: Unclassified
OS: All
Reporter: rakothedin@gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: XOrg CVS
Component: DRM/Radeon
Product: DRI
Created attachment 82968
--> https://bugs.freedesktop.org/attachment.cgi?id=82968&action=edit
dmesg
I have a hybrid muxless laptop with intel+radeon:
#lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor
Graphics Controller (rev 09)
01:00.0 VGA compatible controller: Advanced Micro Devices [AMD] nee ATI Cape
Verde [Radeon HD 7700M Series]
I use openSUSE 12.3 x86_64 with
kernel 3.11-rc2
Xorg-x11-server 1.14.2
Mesa git20130723
libdrm2 git20130722
libdrm-radeon git20130722
xf86-video-ati git20130709
The kernel is booted with i915.i915_enable_rc6=7 i915.i915_enable_fbc=1
i915.lvds_downclock=1 drm.vblankoffdelay=1 radeon.dpm=1 modeset=1.
$xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x6e cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
3 outputs: 6 associated providers: 1 name:Intel
Provider 1: id: 0x45 cap: 0xd, Source Output, Source Offload, Sink Offload
crtcs: 6 outputs: 0 associated providers: 1 name:radeon
$xrandr --setprovideroffloadsink 0x45 0x6e
$DRI_PRIME=1 glxinfo | grep OpenGL
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD CAPE VERDE
OpenGL version string: 2.1 Mesa 9.2.0-devel
OpenGL shading language version string: 1.30
OpenGL extensions:
But if I try VDPAU I get:
$DRI_PRIME=1 vdpauinfo
display: :0 screen: 0
Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object
file: No such file or directory
Error creating VDPAU device: 1
or
$DRI_PRIME=1 VDPAU_DRIVER=radeonsi vdpauinfo
display: :0 screen: 0
do_winsys_init: DRM version is 1.6.0 but this driver is only compatible with
2.3.x (kernel 2.6.34) or later.
Error creating VDPAU device: 23
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3730 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 reply other threads:[~2013-07-25 1:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 1:00 bugzilla-daemon [this message]
2013-07-25 1:00 ` [Bug 67283] VDPAU doesn't work on hybrid laptop through DRI_PRIME bugzilla-daemon
2013-07-25 1:06 ` bugzilla-daemon
2013-07-25 1:44 ` bugzilla-daemon
2013-07-25 1:45 ` bugzilla-daemon
2013-07-25 1:46 ` bugzilla-daemon
2013-07-25 3:03 ` bugzilla-daemon
2013-07-25 5:05 ` bugzilla-daemon
2013-07-25 7:45 ` bugzilla-daemon
2013-07-26 5:06 ` bugzilla-daemon
2013-07-26 5:20 ` bugzilla-daemon
2013-07-26 23:33 ` bugzilla-daemon
2013-07-26 23:37 ` bugzilla-daemon
2013-08-05 14:34 ` 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-67283-502@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;
as well as URLs for NNTP newsgroup(s).