From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@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 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0069313640==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: nouveau-bounces-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org Sender: "Nouveau" To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org List-Id: nouveau.vger.kernel.org --===============0069313640== Content-Type: multipart/alternative; boundary="15599391342.2bBb.29286" Content-Transfer-Encoding: 7bit --15599391342.2bBb.29286 Date: Fri, 7 Jun 2019 20:25:34 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D110830 --- Comment #7 from Marcin Zajaczkowski --- (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) w= hen > > no external output is connected. And what I missed in my previous comme= nt - > > the external monitor works out-of-box, which is nice progress. >=20 > 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 (assumi= ng 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 >=20 > 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 yo= ur > 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 rig= ht here to test it organoleptically)? >=20 > grep . /sys/class/drm/card*-*/status >=20 > 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 --=20 You are receiving this mail because: You are the assignee for the bug.= --15599391342.2bBb.29286 Date: Fri, 7 Jun 2019 20:25:34 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 7 on bug 11083= 0 from <= span class=3D"fn">Marcin Zajaczkowski
(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 t=
urned 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 power=
top) 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.
>=20
> vgaswitcheroo explicit control is for hard muxes. These were popular 2=
005 to
> 2010 or so. You just have 2 GPUs. vgaswitcheroo reports whether they'r=
e 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 (assumi=
ng
the modern Intel can handle 3 displays enabled at the same time)?

> > There are also no reported providers in xra=
ndr:
> > > $ xrandr --listproviders
> > > Providers: number: 0
>=20
> This is incredibly odd -- there must always be at least 1! Are you run=
ning
> 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 Offl=
oad, Sink Offload crtcs: 3 outputs: 3 associated providers: 1 name:modesett=
ing
> Provider 1: id: 0x45 cap: 0x2, Sink Output crtcs: 4 outputs: 2 associa=
ted 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 rig=
ht
here to test it organoleptically)?

>=20
> grep . /sys/class/drm/card*-*/status
>=20
> 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.
= --15599391342.2bBb.29286-- --===============0069313640== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1 --===============0069313640==--