[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-11-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #19 from Denis Lisov  ---
Having the same bug.

Thinkpad P50, Quadro M1000M.

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GM107GLM [Quadro
M1000M] [10de:13b1] (rev a2)

Ready to test patches.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-10-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- 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 0x. 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 and
display-manager.service starts (for those on systemd).

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-10-14 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #17 from Maik Freudenberg  ---
(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 0x. 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?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-10-12 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #16 from Ilia Mirkin  ---
So an interesting thought here is that GRUB also supports the setpci command,
and runs early enough for it to matter. This would be the functional equivalent
of an early pci quirk. If someone having the issue could try adding

setpci -s 01:00.0 0x488.l=0x200:0x200

to be run by grub, and reporting back whether that helped or not, with `lspci
-nn -d 10de:` output, that'd be interesting to see. [Not everyone can use
01:00.0 -- double-check where your GPU is at. But that'll be right for most
people.]

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-10-04 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #15 from Peter Wu  ---
The AER capability was the closest one I could see just before the magic value
of 0x488, it likely has nothing to do with 0x488. I haven't tried
writing/reading it yet.

You might also be interested in this document:
https://github.com/envytools/envytools/blob/master/rnndb/bus/pci.xml

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-09-29 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #14 from Maik Freudenberg  ---
(In reply to Peter Wu from comment #12)
> AER capability
Red herring?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-09-28 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

Maik Freudenberg  changed:

   What|Removed |Added

 CC||hhfe...@gmx.de

--- Comment #13 from Maik Freudenberg  ---
(In reply to Peter Wu from comment #12)
> On my laptop that area is somewhere after the AER
> capability and is all zeroes, it does not seem to make sense.

Why do you mention AER capability in this context? Are associated registers
normally the highest used in PCI config space? Could you give a hint on that?
Seen from a hardware perspective, this could make sense. Since the audio is
another PCI function not always needed, it sure has some enable pin on the chip
so it can be toggled or disabled by some external circuitry, vendor specific.
And some (reserved) gpio pin is used to make it switchable through software. So
maybe the config space >=0x400 being gpio space?
Wild guess, of course.
Interesting would be if after write, this can be read or returns zero again? 
What about desktop cards, do they also have this register? Is this always set
then?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-09-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #12 from Peter Wu  ---
(In reply to Maik Freudenberg from comment #11)
> Some interesting information from Aaron Plattner of Nvidia:
> https://devtalk.nvidia.com/default/topic/1024022/linux/gtx-1060-no-audio-
> over-hdmi-only-hda-intel-detected-azalia/post/5211273/#5211273

Interesting bit about the PCI configuration space. Essentially this is the
command that Aaron posted. On my laptop that area is somewhere after the AER
capability and is all zeroes, it does not seem to make sense.

Aarons command is essentially the above remove/rescan, but including:
setpci -s 01:00.0 0x488.l=0x200:0x200

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2017-09-26 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #11 from Maik Freudenberg  ---
Some interesting information from Aaron Plattner of Nvidia:
https://devtalk.nvidia.com/default/topic/1024022/linux/gtx-1060-no-audio-over-hdmi-only-hda-intel-detected-azalia/post/5211273/#5211273

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2016-12-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #10 from zigar...@gmail.com ---
Any updates?

I can confirm this bug on my Lenovo Thinkpad T520 (4242-PT2). For testing I
used a FHD TV connected via a DP to HDMI connector. The hardware setup was
tested and confirmed to work as expected with Windows 7 so a hardware cause can
be ruled out.

uname -a
Linux t520 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64
GNU/Linux

I am using the optimus implementation provided by nouveau together with the
intel graphics driver.

xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x8c cap: 0xb, Source Output, Sink Output, Sink Offload crtcs:
3 outputs: 3 associated providers: 0 name:Intel
Provider 1: id: 0x66 cap: 0x7, Source Output, Sink Output, Source Offload
crtcs: 2 outputs: 5 associated providers: 0 name:nouveau

'lspci' doesn't show the audio device but 'lspci -H1' does:
01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [Quadro NVS 4200M]
(rev a1)
01:00.1 Audio device: NVIDIA Corporation GF119 HDMI Audio Controller (rev a1)

Even 'lspci -H1' shows the audio device only when the discrete GPU is powered
up (e.g. by doing 'lspci; lspci -H1').

I am not using a DM or a DE but bspwm launched via startx from the tty.

The procedure I used:
1) boot and login (x not yet started)
2) modprobe nouveau
3) echo 1 > /sys/bus/pci/devices/:01:00.0/remove
4) echo 1 > /sys/bus/pci/rescan
5) lspci now shows the audio device
6) startx
7) open pavucontrol (to trigger launch of pulseaudio via rtkit)

It made no difference when, or even if a device is connected to the DP Port.
The output wasn't usable even with this workaround as pulseaudio showed it
always as unplugged. On one single attempt it did show as connected and worked
ok but even though following procedure exactly and trying many times I was not
able to reproduce this.

After starting pulseaudio multiple errors of the form 'kernel:
snd_hda_codec_hdmi hdaudioC2D0: out of range cmd 0:5:707:' showed up.

The usage of this workaround also lead to a very unstable system till the next
boot. I experienced cpu soft locks multiple times (though found no way to
reliably reproduce them) from which no recovery except hard resetting the
computer was possible.

Attached is a dmesg log where I follow the above procedure (connecting the
display between steps 3 and 4) and activating/deactivating the display with
xrandr once in the end.
I could also provide a syslog from boot till shutdown recorded with journald if
required.

If I can help fixing this by providing more information or testing things let
me know.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2016-12-22 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #9 from zigar...@gmail.com ---
Created attachment 128640
  --> https://bugs.freedesktop.org/attachment.cgi?id=128640=edit
dmesg recording from a t520 trying the workaround

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2016-11-05 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #8 from Peter Wu  ---
Following these steps I always see an audio function (01:00.1):

1. Power off laptop
2. Insert miniDP cable (HDMI probably works as well, did not test)
3. Power on laptop
4. Check lspci -s1:

When booting the laptop without cable there is some other weird behavior:
1. Power on laptop
2. Run "lspci -s1: ; lspci -H1 -s:"
   (first command also resumes the dGPU as side-effect)
   Expected: 2x 01:00:0
3. Wait 5 seconds for the card to runtime suspend (important, verify that this
is actually the case, e.g. by watching "dmesg -w").
4. Insert cable
5. Run the above two lspci commands again. Now I also see the audio function
(01:00.1).
6. Repeat step 3, remove audio cable, repeat step 5 (now the audio function is
gone again!)

This was tested on a Clevo P651RA (GTX 965M). Weird!

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2016-07-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

Peter Wu  changed:

   What|Removed |Added

 CC||pe...@lekensteyn.nl

--- Comment #7 from Peter Wu  ---
Possibly interesting information from
https://devtalk.nvidia.com/default/topic/609790/no-hdmi-sound-w-optimus-in-linux/

On Windows, the audio device is not visible normally, but when a HDMI audio
cable is inserted, suddenly the audio device appears. Perhaps the Windows
driver is doing some rescanning automatically?


Related: 20/111 Nvidia devices report an audio device. AFAIK newer machines
have their HDMI port connected to the Nvidia card, so something is probably
missing there. See
https://lists.freedesktop.org/archives/nouveau/2016-July/025619.html

-- 
You are receiving this mail because:
You are the assignee for the bug.___
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2014-09-16 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #6 from Jethro Beekman freedesktop-b...@jbeekman.nl ---
Nevermind, the workaround lists the device, and ALSA/Pulse seem to recognize
the device, but no audio gets through. I need to do more debugging.

I found this patch, it seems relevant:
http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?h=linux-3.18id=cc2a9071458254cb0db6153811734750da0233ea

FYI the nouveau driver doesn't actually output any graphics on my machine (see
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1292036
), I'm just here to get audio working ;)

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2014-09-15 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #5 from Jethro Beekman freedesktop-b...@jbeekman.nl ---
I've been having a similar issue for a while, see this thread:
https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg45935.html

The workaround you propose (loading nouveau, removing the device, rescanning
the bus) works.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2014-03-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

Ilia Mirkin imir...@alum.mit.edu changed:

   What|Removed |Added

Summary|HDMI audio device only  |[NVC1] HDMI audio device
   |visible after rescan|only visible after rescan

--- Comment #1 from Ilia Mirkin imir...@alum.mit.edu ---
I assume that somewhere in that list of steps you had to plug the HDMI cable
in? Is it the case, at least on windows, that the PCI device appears and
disappears at the same time that the HDMI cable is plugged/unplugged?

What happens if you boot with the HDMI cable plugged in?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2014-03-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #2 from Jean-Louis Dupond jean-lo...@dupond.be ---
Tested this out.

On Windows:
Both devices not visible in lspci. When you then start a game for example, the
NVIDIA VGA device becomes visible. The audio device not.

Now if you plugin a HDMI cable, both devices (VGA  Audio) becomes visible.

If we now remove the HDMI cable, both devices stay there for a while, and then
get deactivated together.

On Linux:
If we boot with HDMI cable in, same issue.

Now if I do the pci remove/rescan without HDMI cable, same result.
The Audio device becomes visible, even without having a HDMI cable in!

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2014-03-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #3 from Jean-Louis Dupond jean-lo...@dupond.be ---
Created attachment 95562
  -- https://bugs.freedesktop.org/attachment.cgi?id=95562action=edit
acpidump

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


[Nouveau] [Bug 75985] [NVC1] HDMI audio device only visible after rescan

2014-03-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=75985

--- Comment #4 from Jean-Louis Dupond jean-lo...@dupond.be ---
All hotplug options enabled in kernel:
CONFIG_MEMORY_HOTPLUG=y
CONFIG_MEMORY_HOTPLUG_SPARSE=y
CONFIG_HOTPLUG_CPU=y
# CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set
# CONFIG_DEBUG_HOTPLUG_CPU0 is not set
CONFIG_ARCH_ENABLE_MEMORY_HOTPLUG=y
CONFIG_ACPI_HOTPLUG_CPU=y
CONFIG_ACPI_HOTPLUG_MEMORY=y
CONFIG_HOTPLUG_PCI_PCIE=y
CONFIG_HOTPLUG_PCI=y
CONFIG_HOTPLUG_PCI_ACPI=y
CONFIG_HOTPLUG_PCI_ACPI_IBM=m
CONFIG_HOTPLUG_PCI_CPCI=y
CONFIG_HOTPLUG_PCI_CPCI_ZT5550=m
CONFIG_HOTPLUG_PCI_CPCI_GENERIC=m
CONFIG_HOTPLUG_PCI_SHPC=m
CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau


<    1   2