All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 117131] vga_switcheroo does not switch IGP -> DIS ( IGP == i915 , DIS == radeon )
Date: Tue, 26 Apr 2016 18:37:02 +0000	[thread overview]
Message-ID: <bug-117131-2300-vN9Z8JQJuY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-117131-2300@https.bugzilla.kernel.org/>

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

--- Comment #21 from Jason Vas Dias <jason.vas.dias@gmail.com> ---
Aha! It was :

Section "Device"
  Identifier "Intel"
  Driver "intel"
  Option "Monitor-eDP-1" "eDP-1" 
  Option "Monitor-DisplayPort-0" "eDP-1"
EndSection

and also :

 Section "ServerLayout"
        Identifier     "X Intel"
        Screen         0  "Screen0" 0 0
        Inactive       "Radeon"
 ...
 EndSection

That did it! 

X-Server now initializes & xterm displays OK !
( with patch applied to latest xf86-video-intel driver, 
  see : https://bugs.freedesktop.org/show_bug.cgi?id=95140
) 

The Monitor-DisplayPort-0 xorg.conf Device section option
appears to only be documented in online blogs, eg:
 https://wiki.archlinux.org/index.php/multihead
It is not mentioned in any manual page installed by any Xorg package.
Let us eagerly anticipate the release of X11 7.8 and complete documentation ...




But still there are these dmesgs after successfully switching into 
graphics mode with the Intel driver:
[  173.684435] [drm] probing gen 2 caps for device 8086:c01 = 261ad03/e
[  173.684460] [drm] PCIE gen 3 link speeds already enabled
[  173.688244] [drm] PCIE GART of 2048M enabled (table at 0x00000000002E8000).
[  173.688390] radeon 0000:01:00.0: WB enabled
[  173.688405] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000100000c00 and cpu addr 0xffff880414fb6c00
[  173.688436] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
0x0000000100000c04 and cpu addr 0xffff880414fb6c04
[  173.688465] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
0x0000000100000c08 and cpu addr 0xffff880414fb6c08
[  173.688495] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000100000c0c and cpu addr 0xffff880414fb6c0c
[  173.689306] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
0x0000000100000c10 and cpu addr 0xffff880414fb6c10
[  173.690471] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000075a18 and cpu addr 0xffffc90000435a18
[  173.711357] radeon 0000:01:00.0: fence driver on ring 6 use gpu addr
0x0000000100000c18 and cpu addr 0xffff880414fb6c18
[  173.712128] radeon 0000:01:00.0: fence driver on ring 7 use gpu addr
0x0000000100000c1c and cpu addr 0xffff880414fb6c1c
[  173.860206] [drm] ring test on 0 succeeded in 2 usecs
[  173.860941] [drm] ring test on 1 succeeded in 1 usecs
[  173.861661] [drm] ring test on 2 succeeded in 1 usecs
[  173.862381] [drm] ring test on 3 succeeded in 1 usecs
[  173.863045] [drm] ring test on 4 succeeded in 3 usecs
[  174.040803] [drm] ring test on 5 succeeded in 2 usecs
[  174.041484] [drm] UVD initialized successfully.
[  174.152209] [drm] ring test on 6 succeeded in 15 usecs
[  174.152884] [drm] ring test on 7 succeeded in 4 usecs
[  174.153545] [drm] VCE initialized successfully.
[  174.154235] f 0#2: signaled from fence_wait
[  174.154923] [drm] ib test on ring 0 succeeded in 0 usecs
[  174.155606] f 1#2: signaled from fence_wait
[  174.156273] [drm] ib test on ring 1 succeeded in 0 usecs
[  174.156960] f 2#2: signaled from fence_wait
[  174.157611] [drm] ib test on ring 2 succeeded in 0 usecs
[  174.158282] f 3#2: signaled from fence_wait
[  174.158959] [drm] ib test on ring 3 succeeded in 0 usecs
[  174.159604] f 4#2: signaled from fence_wait
[  174.160242] [drm] ib test on ring 4 succeeded in 0 usecs
[  174.812851] f 5#4: signaled from fence_wait
[  174.813666] [drm] ib test on ring 5 succeeded
[  175.314798] f 6#4: signaled from fence_wait
[  175.315606] [drm] ib test on ring 6 succeeded
[  175.816796] f 7#4: signaled from fence_wait
[  175.817602] [drm] ib test on ring 7 succeeded
[  175.898550] device: 'vcs4': device_add
[  175.898567] PM: Adding info for No Bus:vcs4
[  175.898612] device: 'vcsa4': device_add
[  175.898621] PM: Adding info for No Bus:vcsa4
[  181.380548] ACPI Error: No handler for Region [EC81] (ffff88041d8d9bd0)
[EmbeddedControl] (20160108/evregion-166)
[  181.380553] ACPI Error: Region EmbeddedControl (ID=3) has no handler
(20160108/exfldio-299)
[  181.380557] ACPI Error: Method parse/execution failed
[\_SB.PCI0.PEG0.PEGP.SGOF] (Node ffff88041d8fca50), AE_NOT_EXIST
(20160108/psparse-542)
[  181.380561] ACPI Error: Method parse/execution failed
[\_SB.PCI0.PEG0.PEGP._OFF] (Node ffff88041d8fce88), AE_NOT_EXIST
(20160108/psparse-542)
[  181.380564] ACPI Error: Method parse/execution failed [\_SB.PCI0.GFX0.ATPX]
(Node ffff88041d9034b0), AE_NOT_EXIST (20160108/psparse-542)
[  181.380569] failed to evaluate ATPX got AE_NOT_EXIST
[  264.565810] i2c i2c-9: master_xfer[0] W, addr=0x50, len=1
[  264.565813] i2c i2c-9: master_xfer[1] R, addr=0x50, len=1


It looks like the Intel driver cannot execute that ATPX method either -
I definitely did specify 'radeon.runpm=0' , so this time it must be
something else invoking it .
Do I need to specify 'intel.runpm=0' ?

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

  parent reply	other threads:[~2016-04-26 18:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-24 19:17 [Bug 117131] New: vga_switcheroo does not switch IGP -> DIS ( IGP == i915 , DIS == radeon ) bugzilla-daemon
2016-04-24 19:28 ` [Bug 117131] " bugzilla-daemon
2016-04-24 19:46 ` bugzilla-daemon
2016-04-24 20:30 ` bugzilla-daemon
2016-04-24 20:44 ` bugzilla-daemon
2016-04-24 23:21 ` bugzilla-daemon
2016-04-25 13:58 ` bugzilla-daemon
2016-04-25 17:43 ` bugzilla-daemon
2016-04-25 17:49 ` bugzilla-daemon
2016-04-25 17:59 ` bugzilla-daemon
2016-04-25 18:49 ` bugzilla-daemon
2016-04-25 19:02 ` bugzilla-daemon
2016-04-25 19:25 ` bugzilla-daemon
2016-04-25 19:39 ` bugzilla-daemon
2016-04-25 20:19 ` bugzilla-daemon
2016-04-25 20:48 ` bugzilla-daemon
2016-04-25 20:51 ` bugzilla-daemon
2016-04-26  0:43 ` bugzilla-daemon
2016-04-26 15:26 ` bugzilla-daemon
2016-04-26 15:52 ` bugzilla-daemon
2016-04-26 16:55 ` bugzilla-daemon
2016-04-26 18:37 ` bugzilla-daemon [this message]
2016-04-26 18:38 ` bugzilla-daemon
2016-04-26 18:50 ` bugzilla-daemon
2016-04-26 22:11 ` bugzilla-daemon
2016-04-26 22:16 ` bugzilla-daemon
2016-04-26 22:20 ` 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-117131-2300-vN9Z8JQJuY@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.