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: Sat, 03 Mar 2018 17:54:23 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0216696826==" 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 --===============0216696826== Content-Type: multipart/alternative; boundary="15200996621.EfFA0.9405" Content-Transfer-Encoding: 7bit --15200996621.EfFA0.9405 Date: Sat, 3 Mar 2018 17:54:22 +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 #44 from Ilia Mirkin --- (In reply to Maik Freudenberg from comment #42) > The hda devices on 3D controller are existing but not completely configur= ed > by vendors leading to errors like > [ 4790.121207] pci 0000:07:00.1: [10de:0e0f] type 00 class 0x040300 > [ 4790.121253] pci 0000:07:00.1: reg 0x10: [mem 0x00000000-0x00003fff] > [ 4790.121610] pci 0000:07:00.1: BAR 0: no space for [mem size 0x00004000] > [ 4790.121613] pci 0000:07:00.1: BAR 0: failed to assign [mem size > 0x00004000] > [ 4790.121900] snd_hda_intel 0000:07:00.1: Disabling MSI > [ 4790.122493] snd_hda_intel 0000:07:00.1: can't ioremap BAR 0: [??? > 0x00000000 flags 0x0] > [ 5661.858112] snd_hda_intel 0000:07:00.1: ioremap error >=20 > AFAIK, 3D class is used by nvidia to specifically mark the adapters witho= ut > display engines, like Teslas or some Optimus dGPUs. So excluding them sho= uld > be safe. Sadly no. This was true for a time, but is unfortunately not accurate across all devices. One can check if the DCB table has any outputs, and only do st= uff if there are none.This tends to be representative of whether there are actu= al outputs on a laptop connected to the GPU. (The DISPLAY block can also be fu= sed off, which can also be checked.) --=20 You are receiving this mail because: You are the assignee for the bug.= --15200996621.EfFA0.9405 Date: Sat, 3 Mar 2018 17:54:22 +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 # 44 on bug 75985<= /a> from Ilia Mirkin 
(In reply to Maik Freudenberg from comment #42)
> The hda devices on 3D controller are existing bu=
t not completely configured
> by vendors leading to errors like
> [ 4790.121207] pci 0000:07:00.1: [10de:0e0f] type 00 class 0x040300
> [ 4790.121253] pci 0000:07:00.1: reg 0x10: [mem 0x00000000-0x00003fff]
> [ 4790.121610] pci 0000:07:00.1: BAR 0: no space for [mem size 0x00004=
000]
> [ 4790.121613] pci 0000:07:00.1: BAR 0: failed to assign [mem size
> 0x00004000]
> [ 4790.121900] snd_hda_intel 0000:07:00.1: Disabling MSI
> [ 4790.122493] snd_hda_intel 0000:07:00.1: can't ioremap BAR 0: [???
> 0x00000000 flags 0x0]
> [ 5661.858112] snd_hda_intel 0000:07:00.1: ioremap error
>=20
> AFAIK, 3D class is used by nvidia to specifically mark the adapters wi=
thout
> display engines, like Teslas or some Optimus dGPUs. So excluding them =
should
> be safe.

Sadly no. This was true for a time, but is unfortunately not accurate across
all devices. One can check if the DCB table has any outputs, and only do st=
uff
if there are none.This tends to be representative of whether there are actu=
al
outputs on a laptop connected to the GPU. (The DISPLAY block can also be fu=
sed
off, which can also be checked.)

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