dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 90451] Dedicated gpu on HP 355 G2 not working correctly (slower than integrated+corrupt display in es2gears)
Date: Thu, 08 Jan 2015 09:21:47 +0000	[thread overview]
Message-ID: <bug-90451-2300-WYpauQWgVm@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-90451-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=90451

--- Comment #3 from l55@anonymousspeech.com ---
Created attachment 162821
  --> https://bugzilla.kernel.org/attachment.cgi?id=162821&action=edit
dmesg output

I noticed that unigine tropics benchmark reports the same video memory for
running without DRI_PRIME=1 and with DRI_PRIME=1, so it seems it doesn't switch
gpus at all, although with DRI_PRIME=1 it takes longer to launch and display of
the benchmark window is corrupt. 

I also tried fglrx: Differences are:
- unigine reports 512MB gpu memory, with opensource driver it reports 256MB
- it reports that it's running on the dedicated gpu (aticonfig --pxl), but
unigine still reports 512MB(should be 2048)

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-01-08  9:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-29 12:11 [Bug 90451] New: Dedicated gpu on HP 355 G2 not working correctly (slower than integrated+corrupt display in es2gears) bugzilla-daemon
2015-01-02 22:47 ` [Bug 90451] " bugzilla-daemon
2015-01-08  9:14 ` bugzilla-daemon
2015-01-08  9:21 ` bugzilla-daemon [this message]
2015-01-08 14:25 ` bugzilla-daemon
2015-01-09  9:36 ` bugzilla-daemon
2015-01-11 13:04 ` bugzilla-daemon
2015-01-11 15:12 ` bugzilla-daemon
2015-01-11 15:46 ` 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-90451-2300-WYpauQWgVm@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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