From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 76840] HybridGraphics: Kernel driver in use: radeon but adapter not listed
Date: Fri, 04 Apr 2014 19:15:26 +0000 [thread overview]
Message-ID: <bug-76840-502-S0fwxekahL@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-76840-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 4190 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=76840
--- Comment #8 from Michael Eagle <xanto@egaming.ro> ---
Hello,
I upgraded my kernel with latest ubuntu mainline
Linux mike-g337 3.14.0-999-generic #201404040227 SMP Fri Apr 4 06:28:24 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
and also webstack from oibaf-ppa:
Upgrade: libg3dvl-mesa:amd64 (10.2~git1404021931.0f641b~gd~s,
10.2~git1404040730.4fa58a~gd~s), xserver-xorg-video-intel:amd64
(2.99.911+git1404021930.baef22~gd~s, 2.99.911+git1404031930.f05658~gd~s),
xserver-xorg-video-ati:amd64 (7.3.99+git1404021930.ed0cfb~gd~s,
7.3.99+git1404022026.ed0cfb~gd~s), xserver-xorg-video-radeon:amd64
(7.3.99+git1404021930.ed0cfb~gd~s, 7.3.99+git1404022026.ed0cfb~gd~s),
mesa-common-dev:amd64 (10.2~git1404021931.0f641b~gd~s,
10.2~git1404040730.4fa58a~gd~s)
and now, xrandr --listproviders shows the desired output:
Providers: number : 3
Provider 0: id: 0x68 cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
4 outputs: 5 associated providers: 2 name:Intel
Provider 1: id: 0x3f cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 0 outputs: 0 associated providers: 2 name:radeon
Provider 2: id: 0x3f cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 0 outputs: 0 associated providers: 2 name:radeon
DRI_PRIME, also works
mike-g337 mike # DRI_PRIME=0 glxinfo | grep 'OpenGL'
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) Haswell Mobile
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.0-devel
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.2.0-devel
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:
mike-g337 mike # DRI_PRIME=1 glxinfo | grep 'OpenGL'
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD HAINAN
OpenGL core profile version string: 3.1 (Core Profile) Mesa 10.2.0-devel
OpenGL core profile shading language version string: 1.40
OpenGL core profile context flags: (none)
OpenGL core profile extensions:
OpenGL version string: 3.0 Mesa 10.2.0-devel
OpenGL shading languagew, version string: 1.30
OpenGL context flags: (none)
OpenGL extensions
Now because radeon is active, I can not remove the module from within X
anymore:
rmmod radeon
Error: Module radeon is in use
DRI_PRIME=1 glxgears also works, I don't have any game to test now, But,
everything is fine in your opinion ?
And also, perhaps I shouldn't do this, but if I run:
DRI_PRIME=2 glxinfo | grep 'OpenGL'
X server crashes with the following backtrace (it wasn't crashing before):
[ 913.503] (EE)
[ 913.503] (EE) Backtrace:
[ 913.503] (EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x7fae2101cfdd]
[ 913.503] (EE) 1: /usr/bin/X (0x7fae20e7a000+0x1a6d49) [0x7fae21020d49]
[ 913.503] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0
(0x7fae1ff7a000+0xfbb0) [0x7fae1ff89bb0]
[ 913.503] (EE) 3: /usr/bin/X (DRI2Connect+0x5f) [0x7fae20ff0a7f]
[ 913.503] (EE) 4: /usr/bin/X (0x7fae20e7a000+0x1776dc) [0x7fae20ff16dc]
[ 913.503] (EE) 5: /usr/bin/X (0x7fae20e7a000+0x5525e) [0x7fae20ecf25e]
[ 913.503] (EE) 6: /usr/bin/X (0x7fae20e7a000+0x447ba) [0x7fae20ebe7ba]
[ 913.503] (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5)
[0x7fae1ebb5de5]
[ 913.503] (EE) 8: /usr/bin/X (0x7fae20e7a000+0x44aff) [0x7fae20ebeaff]
[ 913.503] (EE)
[ 913.503] (EE) Segmentation fault at address 0x0
[ 913.503] (EE)
Fatal server error:
[ 913.503] (EE) Caught signal 11 (Segmentation fault). Server aborting
[ 913.503] (EE)
[ 913.503] (EE)
Please consult the The X.Org Foundation support
at http://wiki.x.org
for help.
[ 913.503] (EE) Please also check the log file at "/var/log/Xorg.0.log" for
additional information.
[ 913.503] (EE)
[ 913.503] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 913.521] (EE) Server terminated with error (1). Closing log file.
Thank you,
Cheers Mike.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 5039 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:[~2014-04-04 19:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-31 14:40 [Bug 76840] New: HybridGraphics: Kernel driver in use: radeon but adapter not listed bugzilla-daemon
2014-03-31 14:51 ` [Bug 76840] " bugzilla-daemon
2014-03-31 14:58 ` bugzilla-daemon
2014-03-31 15:00 ` bugzilla-daemon
2014-03-31 15:27 ` bugzilla-daemon
2014-03-31 15:28 ` bugzilla-daemon
2014-03-31 15:28 ` bugzilla-daemon
2014-03-31 15:32 ` bugzilla-daemon
2014-04-04 19:15 ` bugzilla-daemon [this message]
2015-11-20 16:09 ` 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-76840-502-S0fwxekahL@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