Nouveau Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 110830] [nouveau] GeForce GTX 1660 Ti (mobile) not supported (NV168/TU116)
Date: Fri, 14 Jun 2019 15:56:36 +0000	[thread overview]
Message-ID: <bug-110830-8800-u4wFnFIFJD@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110830-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 2205 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=110830

--- Comment #11 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to Marcin Zajaczkowski from comment #10)
> (In reply to Ilia Mirkin from comment #9)
> > xrandr --setprovideroutputsource 1 0
> > 
> > which should allow you to drive on your NVIDIA GPU's outputs by configuring
> > them in xrandr.
> 
> In lxqt (with Openbox) after that command and "xrandr --output HDMI-1-2
> --auto --right-of eDP-1" the external monitor is turned on and I see a mouse
> cursor there, but no window is rendered.
> 
> In Gnome 3 (with xorg) the external monitor is detected automatically, but
> the effect is the same - black screen with a mouse cursor.

I've seen a bunch of reports of this recently. It's not any issue with nouveau
kernel component itself, I think it's an Xorg issue. Try using a redirecting
compositor. Or not using one. Or using modesetting ddx. Or using nouveau ddx.

The lack of acceleration on TU* might also be playing into this. Not sure.

> 
> Can it be related to the fact that NVidia providers reports only "Sink
> Output", but not offloading?
> 
> > This should also be possible with a Wayland compositor, however the
> > specifics will vary by compositor. Xwayland has no ability to control screen
> > setup.
> 
> In Wayland the external monitor works out-of-box in Gnome 3. However, I have
> problem with bringing it to live with Xorg server (some tools I use don't
> like Wayland). Is it possible to force LXQT or Gnome 3 (on xorg) to render
> also on the external screen?
> 
> I've read about some issues with Windows Manager and "offloading", but
> though it only applies to OpenGL-based output with PRIME=1.

Offloading is usually meant as "perform rendering on secondary GPU, display on
primary GPU". This is what something like DRI_PRIME controls (i.e. which GPU
performs rendering for a particular application).

You want the inverse -- you want your primary GPU to generate images to be
displayed on a secondary GPUs outputs. In Xorg this is referred to as "reverse
PRIME".

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3285 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2019-06-14 15:56 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-03 13:30 [Bug 110830] New: [nouveau] GeForce GTX 1660 Ti (mobile) not supported (NV168/TU116) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-110830-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2019-06-03 13:32   ` [Bug 110830] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-03 18:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07  9:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 10:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 10:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 13:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 20:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 20:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-07 21:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 15:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 15:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-06-14 21:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-06-14 21:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-09 18:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-07-09 18:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-110830-8800-u4wFnFIFJD@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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