dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 69694] Xorg doesn't start on KABINi with radeonsi
Date: Sun, 16 Feb 2014 21:24:18 +0000	[thread overview]
Message-ID: <bug-69694-502-SQvyu4v1tE@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-69694-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1429 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=69694

--- Comment #22 from Marco <mpiazza@gmail.com> ---
Tried yesterday mesa git:
latest commit 1020d8937ef52725cc5adafc12465f6332815.

Now without xorg.conf and with xorg.conf.d with:
Section "Module"
    Load "dri2"
    Load "glamoregl"
EndSection

Xorg start without any problem.

marco@albireo:~/src/mesa.git$ glxinfo | grep -i opengl
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD KABINI
OpenGL core profile version string: 3.3 (Core Profile) Mesa 10.2.0-devel
(git-1020d89)
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 (git-1020d89)
OpenGL shading language version string: 1.30
OpenGL context flags: (none)
OpenGL extensions:

But... what about my second GPU? I was hoping to use it with DRI_PRIME but:
xrandr --listproviders 
shows only
Providers: number : 1
Provider 0: id: 0x54 cap: 0xf, Source Output, Sink Output, Source Offload, Sink
Offload crtcs: 2 outputs: 3 associated providers: 0 name:radeon

And what about render nodes? Will I be able to use second GPU as a render node?

Or this hybrid AMD GPU is considered as one and not two GPU?

For what concern this bug, You can now close it.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2214 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

  parent reply	other threads:[~2014-02-16 21:24 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23  7:53 [Bug 69694] New: Xorg doesn't start on KABINi with radeonsi bugzilla-daemon
2013-09-23  7:54 ` [Bug 69694] " bugzilla-daemon
2013-09-23  7:55 ` bugzilla-daemon
2013-09-23  7:55 ` bugzilla-daemon
2013-09-23 14:23 ` bugzilla-daemon
2013-09-23 21:05 ` bugzilla-daemon
2013-09-23 21:07 ` bugzilla-daemon
2013-09-23 21:10 ` bugzilla-daemon
2013-09-23 21:42 ` bugzilla-daemon
2013-09-23 22:19 ` bugzilla-daemon
2013-09-24  6:56 ` bugzilla-daemon
2013-09-24 20:44 ` bugzilla-daemon
2013-09-24 20:45 ` bugzilla-daemon
2013-09-24 20:45 ` bugzilla-daemon
2013-09-25 21:45 ` bugzilla-daemon
2013-09-25 21:46 ` bugzilla-daemon
2013-09-25 22:02 ` bugzilla-daemon
2013-09-26  5:53 ` bugzilla-daemon
2014-02-13  3:07 ` bugzilla-daemon
2014-02-13 22:30 ` bugzilla-daemon
2014-02-13 22:33 ` bugzilla-daemon
2014-02-13 22:34 ` bugzilla-daemon
2014-02-16 21:24 ` bugzilla-daemon [this message]
2014-02-16 21:25 ` bugzilla-daemon
2014-02-17  7:54 ` 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-69694-502-SQvyu4v1tE@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