[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 Michel Dänzer changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #15 from Parker Reed --- Ahh thanks. Wasn't aware of that. This can be closed out in that case. I'll bug the software I was using about not setting the DRI_PRIME in certain cases. -- You are receiving this mail because: You are the

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #14 from Michel Dänzer --- (In reply to Parker Reed from comment #13) > But the Intel card isn't enabled in the conf. That doesn't matter with DRI3. With it, libGL can use an alternative GPU without any explicit support for it in Xo

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #13 from Parker Reed --- But the Intel card isn't enabled in the conf. Why is it trying to init it if it's not there? i915 is loaded kernel side but it's just dead displaying a TTY. I agree the DRI_PRIME shouldn't be called in this

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #12 from Michel Dänzer --- In other words, the only thing preventing the Intel GPU from being used in this case is the i965 driver missing the blitImage functionality. -- You are receiving this mail because: You are the assignee fo

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #11 from Michel Dänzer --- (In reply to Parker Reed from comment #10) > So would DRI_PRIME=1 acting like 0 if only one GPU is present, be a > possibility? The fact it's trying to load the non-existent GPU It's not really "non-existe

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #10 from Parker Reed --- So would DRI_PRIME=1 acting like 0 if only one GPU is present, be a possibility? The fact it's trying to load the non-existent GPU in the first place seems to be the root issue. -- You are receiving this ma

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #9 from Parker Reed --- I need to wakeup and read the comment. So it's because DRI2. Thanks for the reply. -- You are receiving this mail because: You are the assignee for the bug. You are the QA Contact for the bug.___

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 --- Comment #8 from Parker Reed --- Aye, I was more intrigued by the vsync bypass. It even uncapped games with a forced 60 (regardless of vsync being on or off) Just a consequence of that DRI fallback? -- You are receiving this mail because:

[Mesa-dev] [Bug 111272] [DRI_PRIME] Error on multi GPU with only one enabled

2019-08-02 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=111272 Michel Dänzer changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop |mesa-dev@lists.freedesktop.