From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106271] Switch between AMD hybrid graphics (HD 8650G / HD 8970M) makes hardware reset.
Date: Tue, 27 Oct 2015 15:47:57 +0000 [thread overview]
Message-ID: <bug-106271-2300-VI4ThGvMY1@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-106271-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=106271
--- Comment #6 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Aneroid from comment #5)
> Yes, I try to do that.
>
> xrandr --listproviders
> Providers: number : 2
> Provider 0: id: 0x7e cap: 0xf, Source Output, Sink Output, Source Offload,
> Sink Offload crtcs: 4 outputs: 4 associated providers: 0 name:radeon
> Provider 1: id: 0x46 cap: 0xf, Source Output, Sink Output, Source Offload,
> Sink Offload crtcs: 6 outputs: 1 associated providers: 0 name:radeon
>
> xrandr --setprovideroffloadsink 0x7e 0x46
You've got the arguments reversed; the first is the offload device, the second
is the display device. Try:
xrandr --setprovideroffloadsink 0x46 0x7e
>
> And it ruined my xorg completely. X fall out in to the shell without any
> errors.
Can you attach your dmesg output and xorg log when you do that?
Does adding amdgpu.runpm=0 to the kernel command line in grub help?
--
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
next prev parent reply other threads:[~2015-10-27 15:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 17:40 [Bug 106271] New: Switch between AMD hybrid graphics (HD 8650G / HD 8970M) makes hardware reset bugzilla-daemon
2015-10-19 17:41 ` [Bug 106271] " bugzilla-daemon
2015-10-19 17:42 ` bugzilla-daemon
2015-10-20 19:01 ` bugzilla-daemon
2015-10-20 19:08 ` bugzilla-daemon
2015-10-27 15:27 ` bugzilla-daemon
2015-10-27 15:47 ` bugzilla-daemon [this message]
2015-10-30 14:33 ` bugzilla-daemon
2015-10-30 14:35 ` bugzilla-daemon
2015-10-30 14:36 ` bugzilla-daemon
2015-11-01 6:06 ` bugzilla-daemon
2015-11-12 14:44 ` bugzilla-daemon
2015-11-12 15:34 ` bugzilla-daemon
2015-11-15 8:39 ` bugzilla-daemon
2015-11-15 20:08 ` 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-106271-2300-VI4ThGvMY1@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