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, 07 Jun 2019 20:25:34 +0000	[thread overview]
Message-ID: <bug-110830-8800-tB5m8NXIXf@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-110830-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #7 from Marcin Zajaczkowski <mszpak-5tc4TXWwyLM@public.gmane.org> ---
(In reply to Ilia Mirkin from comment #6)
> (In reply to Marcin Zajaczkowski from comment #4)
> > Of course it didn't make sense to turn it on, as it was already turned on
> > (DynPwr) in my case :) ). I can switch it off with vgaswitcheroo (or at
> > least to be reported as DynOff - I will check it later with powertop) when
> > no external output is connected. And what I missed in my previous comment -
> > the external monitor works out-of-box, which is nice progress.
> 
> vgaswitcheroo explicit control is for hard muxes. These were popular 2005 to
> 2010 or so. You just have 2 GPUs. vgaswitcheroo reports whether they're on
> or off, but that control is performed dynamically by the driver based on
> usage.

You are right. Afew seconds after an external monitor is disconnected the
discrete card becomes DynOff.

I have a hard mux in my (quite) old Asus. I can use only the Intel card to save
energy and the Nvidia card is used only occasionally for CUDA and gaming. I
wonder why in multiple laptops nowadays the outputs are wired to one card
limiting the aforementioned use case? What are the benefits of that (assuming
the modern Intel can handle 3 displays enabled at the same time)?

> > There are also no reported providers in xrandr:
> > > $ xrandr --listproviders
> > > Providers: number: 0
> 
> This is incredibly odd -- there must always be at least 1! Are you running
> Xwayland or something? If so, the displays would be controlled through your
> wayland compositor. You can check that kms is working:

Yes, it was Wayland. With Xorg I see two providers:

> Providers: number : 2
> Provider 0: id: 0x6b cap: 0xf, Source Output, Sink Output, Source Offload, Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:modesetting
> Provider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 4 outputs: 2 associated providers: 1 name:modesetting

Hmm, why there are 3 and 4 outputs associated to them? Is it possible that DP
output is accessible with the Intel card only (I don't have a connector right
here to test it organoleptically)?

> 
> grep . /sys/class/drm/card*-*/status
> 
> You should see some card0-* and card1-* entries.

Yes, I see different outputs.
> /sys/class/drm/card0-DP-1/status:disconnected
> /sys/class/drm/card0-eDP-1/status:connected
> /sys/class/drm/card0-HDMI-A-1/status:disconnected
> /sys/class/drm/card1-DP-2/status:disconnected
> /sys/class/drm/card1-HDMI-A-2/status:disconnected

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

[-- Attachment #1.2: Type: text/html, Size: 3825 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-07 20:25 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 [this message]
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
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-tB5m8NXIXf@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