From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org Subject: [Bug 75985] [NVC1] HDMI audio device only visible after rescan Date: Sun, 15 Oct 2017 04:14:11 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1353396921==" 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 --===============1353396921== Content-Type: multipart/alternative; boundary="15080408514.bf9AFf1.28369"; charset="UTF-8" --15080408514.bf9AFf1.28369 Date: Sun, 15 Oct 2017 04:14:11 +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=3D75985 --- Comment #18 from Fede --- (In reply to Maik Freudenberg from comment #17) > (In reply to Ilia Mirkin from comment #16) > > So an interesting thought here is that GRUB also supports the setpci > > command > Really smart thinking but users trying it had no success. Register always > returning value 0xFFFFFFFF. Which would normally(?) mean, no device there. > Which led me to dig a bit into setpci and it seems to me that without the > kernel and its mmio, setpci is only able to work on the standard 256 pci > registers but not the extended config space. So out of luck there? I can confirm this. It does not work from GRUB. The best work-around so far= is to have a service do the setpci step before the nvidia drivers are loaded a= nd display-manager.service starts (for those on systemd). --=20 You are receiving this mail because: You are the assignee for the bug.= --15080408514.bf9AFf1.28369 Date: Sun, 15 Oct 2017 04:14:11 +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 # 18 on bug 75985<= /a> from Fede 
(In reply to Maik Freudenberg from comment #17)
> (In reply to Ilia Mirkin from comment #16)
> > So an interesting thought here is that GRUB also supports the set=
pci
> > command
> Really smart thinking but users trying it had no success. Register alw=
ays
> returning value 0xFFFFFFFF. Which would normally(?) mean, no device th=
ere.
> Which led me to dig a bit into setpci and it seems to me that without =
the
> kernel and its mmio, setpci is only able to work on the standard 256 p=
ci
> registers but not the extended config space. So out of luck there?


I can confirm this. It does not work from GRUB. The best work-around so far=
 is
to have a service do the setpci step before the nvidia drivers are loaded a=
nd
display-manager.service starts (for those on systemd).

You are receiving this mail because:
  • You are the assignee for the bug.
= --15080408514.bf9AFf1.28369-- --===============1353396921== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTm91dmVhdSBt YWlsaW5nIGxpc3QKTm91dmVhdUBsaXN0cy5mcmVlZGVza3RvcC5vcmcKaHR0cHM6Ly9saXN0cy5m cmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9ub3V2ZWF1Cg== --===============1353396921==--