From: Boszormenyi Zoltan <zboszor@pr.hu>
To: "Michel Dänzer" <michel@daenzer.net>
Cc: Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: AMD/AMD hybrid graphics
Date: Thu, 20 Feb 2014 06:09:54 +0100 [thread overview]
Message-ID: <53058E22.1060101@pr.hu> (raw)
In-Reply-To: <1392866428.12428.3.camel@thor.local>
[-- Attachment #1: Type: text/plain, Size: 992 bytes --]
2014-02-20 04:20 keltezéssel, Michel Dänzer írta:
> On Mit, 2014-02-19 at 11:56 +0100, Boszormenyi Zoltan wrote:
>> 2014-02-19 10:59 keltezéssel, Michel Dänzer írta:
>>> On Mit, 2014-02-19 at 09:11 +0100, Boszormenyi Zoltan wrote:
>>>
>>>> Can Mesa/Xorg use both r600g and radeonsi at the same time?
>>> Yes, that seems to work fine for others. You may need Mesa 10.1 or newer
>>> though.
>> Do you mean mean with Mesa 9.2.5 and Xorg server 1.14.4 in
>> Fedora 20 at this time, it's not possible unless I compile my own
>> llvm-3.5 SVN, Mesa 10.1 or 10.2 GIT and Xorg 1.15 GIT?
> I don't think Xorg 1.15 is necessary, but it shouldn't hurt either.
>
>
>> Attached is the log from both 1.14.4 (FC20) and 1.15.0 (rawhide), [...]
> The log files end abruptly, so we need to see the X server stderr
> output. Assuming you're using gdm, it should be captured
> in /var/log/gdm*/:0.log .
FC20 has lightdm by default, here's /var/log/lightdm/x-0.log
Thanks,
Zoltán
[-- Attachment #2: x-0.log --]
[-- Type: text/x-log, Size: 2438 bytes --]
X.Org X Server 1.15.0
Release Date: 2013-12-27
X Protocol Version 11, Revision 0
Build Operating System: 3.12.8-300.fc20.x86_64
Current Operating System: Linux localhost.localdomain 3.13.3-201.fc20.x86_64 #1 SMP Fri Feb 14 19:08:32 UTC 2014 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.13.3-201.fc20.x86_64 root=UUID=61edc6e4-5eb0-4ec6-869c-f80dd5bd1d93 ro vconsole.font=latarcyrheb-sun16 rhgb quiet LANG=hu_HU.UTF-8
Build Date: 04 February 2014 10:15:54PM
Build ID: xorg-x11-server 1.15.0-3.fc21
Current version of pixman: 0.30.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Feb 20 06:04:01 2014
(==) Using config directory: "/etc/X11/xorg.conf.d"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Initializing built-in extension Generic Event Extension
Initializing built-in extension SHAPE
Initializing built-in extension MIT-SHM
Initializing built-in extension XInputExtension
Initializing built-in extension XTEST
Initializing built-in extension BIG-REQUESTS
Initializing built-in extension SYNC
Initializing built-in extension XKEYBOARD
Initializing built-in extension XC-MISC
Initializing built-in extension XINERAMA
Initializing built-in extension XFIXES
Initializing built-in extension RENDER
Initializing built-in extension RANDR
Initializing built-in extension COMPOSITE
Initializing built-in extension DAMAGE
Initializing built-in extension MIT-SCREEN-SAVER
Initializing built-in extension DOUBLE-BUFFER
Initializing built-in extension RECORD
Initializing built-in extension DPMS
Initializing built-in extension Present
Initializing built-in extension DRI3
Initializing built-in extension X-Resource
Initializing built-in extension XVideo
Initializing built-in extension XVideo-MotionCompensation
Initializing built-in extension SELinux
Initializing built-in extension XFree86-VidModeExtension
Initializing built-in extension XFree86-DGA
Initializing built-in extension XFree86-DRI
Initializing built-in extension DRI2
Loading extension GLX
(II) [KMS] Kernel modesetting enabled.
(II) [KMS] Kernel modesetting enabled.
X: ../../../include/privates.h:122: dixGetPrivateAddr: Assertion `key->initialized' failed.
[-- Attachment #3: 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-02-20 5:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 8:11 AMD/AMD hybrid graphics Boszormenyi Zoltan
2014-02-19 9:59 ` Michel Dänzer
2014-02-19 10:56 ` Boszormenyi Zoltan
2014-02-20 3:20 ` Michel Dänzer
2014-02-20 5:09 ` Boszormenyi Zoltan [this message]
2014-02-20 5:47 ` Michel Dänzer
2014-02-20 7:44 ` Boszormenyi Zoltan
2014-02-20 8:17 ` Boszormenyi Zoltan
2014-02-21 2:25 ` Michel Dänzer
2014-02-21 2:37 ` Dave Airlie
2014-02-21 13:37 ` Alex Deucher
2014-02-21 14:32 ` Boszormenyi Zoltan
2014-02-21 14:58 ` Boszormenyi Zoltan
2014-02-21 15:12 ` Alex Deucher
2014-02-21 19:05 ` Boszormenyi Zoltan
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=53058E22.1060101@pr.hu \
--to=zboszor@pr.hu \
--cc=dri-devel@lists.freedesktop.org \
--cc=michel@daenzer.net \
/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