[Neither headphones nor speakers are displayed under "All Settings"->Sound, VIA VT1718S, Green Headphone Out, Front] No sound at all

[Vindicator]

The motherboard speakers and microphone aren't listed under "All Settings"->Sound UNLESS I unplug them and then plug them back in.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: pulseaudio 1:6.0-0ubuntu6
ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3
Uname: Linux 3.19.0-16-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: username 11102 F.... pulseaudio
 /dev/snd/pcmC1D0c: username 11102 F...m pulseaudio
 /dev/snd/controlC1: username 11102 F.... pulseaudio
 /dev/snd/timer: username 11102 f.... pulseaudio
CurrentDesktop: Unity
Date: Fri May 8 16:09:24 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-07 (1 days ago)
InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
SourcePackage: pulseaudio
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
Symptom_Card: Built-in Audio - HDA Intel MID
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test failed
Symptom_Type: No sound at all
Title: [To Be Filled By O.E.M., VIA VT1718S, Green Headphone Out, Front] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/06/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P2.20
dmi.board.name: H55M Pro
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP2.20:bd08/06/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55MPro:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Raymond (superquad-vortex2)]

Default sink name: alsa_output.pci-0000_00_1b.0.hdmi-stereo
Default source name: alsa_input.usb-Auvitek_Auvitek_000000000000001-01-U0x5e10x400.iec958-stereo

[Raymond (superquad-vortex2)]

Node 0x2d [Pin Complex] wcaps 0x400701: Stereo Digital
  Control: name="HDMI Phantom Jack", index=0, device=0
  Pincap 0x00000010: OUT
  Pin Default 0x185600f0: [Jack] Digital Out at Int HDMI
    Conn = Digital, Color = Unknown
    DefAssociation = 0xf, Sequence = 0x0
  Pin-ctls: 0x40: OUT
  Power states: D0 D1 D2 D3
  Power: setting=D0, actual=D0
  Connection: 1
     0x0e

is this internal spdif conecctor ?

[Vindicator (vindicator)]

I'm guessing it isn't spdif because it says it's audio for the HDMI.

Something I ended up finding I think is using alsamixer to make sure "auto-mute" is disabled, but that is only so I can have audio from the headphones in the front and back at the same time.

However what I just found is resuming from suspend, the audio listing is missing.

[Raymond (superquad-vortex2)]

http://www.asrock.com/mb/Intel/H55M%20Pro/

there is optical spdif at the rear panel and internal HDMI SPDIF connector

seem bios did not setup pin default correctly

Node 0x2e [Pin Complex] wcaps 0x400701: Stereo Digital
  Pincap 0x00000010: OUT
  Pin Default 0x474411f0: [N/A] SPDIF Out at Ext Rear Panel
    Conn = RCA, Color = Black
    DefAssociation = 0xf, Sequence = 0x0
    Misc = NO_PRESENCE
  Pin-ctls: 0x00:
  Power states: D0 D1 D2 D3
  Power: setting=D0, actual=D0
  Connection: 1
     0x0f

the should be red light at the optical spdif when iec958 playback switch is ON

try hdajackretask to change pin default from [N/A] to [Jack] , RCA to Optical

[Raymond (superquad-vortex2)]

APLAY

**** List of PLAYBACK Hardware Devices ****
card 0: MID [HDA Intel MID], device 0: VT1718S Analog [VT1718S Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 2: VT1718S Alt Analog [VT1718S Alt Analog]
  Subdevices: 1/1
  Subdevice #0: subdevice #0
card 0: MID [HDA Intel MID], device 3: VT1718S Digital [VT1718S Digital]
  Subdevices: 1/1
  Subdevice #0: subdevice #0

you neef to file upstream bug report if still no device 1 for optical spdif

https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers

[Raymond (superquad-vortex2)]

http://www.via.com.tw/en/products/audio/codecs/vt1718s/

2 independent 16/24-bit S/PDIF TX Outputs supporting 16/20/24-bit, 48K/96K/44.1K/88.2KHz sample rate

[Vindicator (vindicator)]

I think I should mention I'm not interested in the hdmi audio or motherboard spdif connections.

I have headphones plugged into the front green port, and a headset microphone connected to the green and pink in the rear ports.

I just ran a test for curiosity:
*****
Shutdown
Wait 30 seconds
Boot
front and back audio devices show in "Sound Settings"
Suspend
Wait 30 seconds
Resume
Only hdmi/displayport is listed for Output
Auvitek (tv tuner) and rear microphone are listed under input. Rear microphone is functioning.
*****
This is probably the reason I initiated the bug report, I probably had resumed from suspend instead of booted fresh.
In hopes to gain audio back from suspend, I had added that I found during a search:
*****
sudo gedit /etc/pm/sleep.d/50alsa
     case "$1" in
             hibernate|suspend)
                     # Stopping is not required
                     ;;
             thaw|resume)
                     /sbin/alsa force-reload
                     ;;
             *) exit $NA
                     ;;
     esac
*****
But this doesn't appear to work for me (only microphone input listed).
Trying force-reload manually also didn't fix it, HOWEVER running "pulseaudio -k && sudo alsa force-reload" did, so I will test that in the script now.

[Vindicator (vindicator)]

Ugh, this isn't progressing well.
I tried adding "logger" statements to the script since my change wouldn't bring back the audio.
My logger statements didn't show in the log.
Then I added "touch" statements since I knew where those files would be created. Again, nothing created.

I had been using the "sleep" key on my keyboard, but also tried the "Suspend" menu item under power-cog at the top-right. Again, no files were touched.
I finally used "$ pm-suspend" and FINALLY the touched files showed as well as the log entries.
Now I have to figure out what is going on with the suspend menu item and sleep key.

But even then, the command "/usr/bin/pulseaudio -k && sudo /sbin/alsa force-reload" I used in the script didn't restore the audio devices like it did when I tried it manually before.
So, I'd think if I manually tried it again, it would work. No, it wouldn't. So then, I now copy/paste the command I pasted in my previous comment which did work. It now does not.

I am flummoxed and questioning my move from windows vista (not just from this experience).

[Raymond (superquad-vortex2)]

it is driver bug if all jack detect kctls return false

control.38 {
  iface CARD
  name 'Line Out Front Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.39 {
  iface CARD
  name 'Line Out Surround Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.40 {
  iface CARD
  name 'Line Out CLFE Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }
 control.41 {
  iface CARD
  name 'Front Headphone Jack'
  value false
  comment {
   access read
   type BOOLEAN
   count 1
  }
 }

[Raymond (superquad-vortex2)]

http://git.alsa-project.org/?p=alsa-tools.git;a=tree;f=hdajacksensetest;hb=HEAD

[Vindicator (vindicator)]

$ hdajacksensetest
Pin 0x24 (Green Line Out, Rear side): present = Yes
Pin 0x25 (Black Line Out, Rear side): present = No
Pin 0x26 (Orange Line Out, Rear side): present = No
Pin 0x28 (Green Headphone, Front side): present = Yes
Pin 0x29 (Pink Mic, Front side): present = No
Pin 0x2a (Blue Line In, Rear side): present = No
Pin 0x2b (Pink Mic, Rear side): present = Yes
Pin 0x2d ( Digital Out, HDMI): present = No

I also plugged in the front headphones so I could watch (hear) tv. The rear still isn't showing which is interesting that 0x24 says it's present.

[Vindicator (vindicator)]

Something else slightly interesting I found while searching was what I received from "$ acpi_listen" and then pressing my Sleep button:
button/sleep SBTN 00000080 00000000 K
jack/microphone MICROPHONE unplug
jack/headphone HEADPHONE unplug
jack/microphone MICROPHONE plug

I don't know if that is normal behavior. Makes me think to use the hda-jack tool to unset the "Present" detection value, but I'm not particularly big on making "hacks", but rather fixing problems.

[Raymond (superquad-vortex2)]

your system have many problems

[ 0.000000] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.19.0/drivers/iommu/dmar.c:829 warn_invalid_dmar+0x7c/0x90()
[ 0.000000] Your BIOS is broken; DMAR reported at address fed91000 returns all ones!
BIOS vendor: American Megatrends Inc.; Ver: P2.20; Product Version: To Be Filled By O.E.M.
[ 0.000000] Modules linked in:
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.19.0-16-generic #16-Ubuntu
[ 0.000000] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H55M Pro, BIOS P2.20 08/06/2010
[ 0.000000] ffffffff81b0d380 ffffffff81c03d18 ffffffff817c2235 00000000000008c8
[ 0.000000] ffffffff81c03d68 ffffffff81c03d58 ffffffff8107595a 0000000000001000
[ 0.000000] 00000000fed91000 ffffffff81ae8aab ffffffff81fe401c ffffffff81fe4060
[ 0.000000] Call Trace:
[ 0.000000] [<ffffffff817c2235>] dump_stack+0x45/0x57
[ 0.000000] [<ffffffff8107595a>] warn_slowpath_common+0x8a/0xc0
[ 0.000000] [<ffffffff81075a1f>] warn_slowpath_fmt_taint+0x3f/0x50
[ 0.000000] [<ffffffff81d7d8d6>] ? __early_ioremap.constprop.0+0x14b/0x1d3
[ 0.000000] [<ffffffff814f108c>] warn_invalid_dmar+0x7c/0x90
[ 0.000000] [<ffffffff81d7dae5>] ? early_iounmap+0x108/0x128
[ 0.000000] [<ffffffff817baa30>] dmar_validate_one_drhd+0xb0/0xf0
[ 0.000000] [<ffffffff814f1232>] dmar_walk_remapping_entries+0x92/0x1d0
[ 0.000000] [<ffffffff81d9cf7a>] detect_intel_iommu+0x52/0xd1
[ 0.000000] [<ffffffff817ba980>] ? xen_swiotlb_init+0x4b0/0x4b0
[ 0.000000] [<ffffffff81d57786>] pci_iommu_alloc+0x4b/0x6e
[ 0.000000] [<ffffffff81d67f22>] mem_init+0x17/0x9d
[ 0.000000] [<ffffffff81d4cd92>] start_kernel+0x246/0x48f
[ 0.000000] [<ffffffff81d4c120>] ? early_idt_handlers+0x120/0x120
[ 0.000000] [<ffffffff81d4c4d7>] x86_64_start_reservations+0x2a/0x2c
[ 0.000000] [<ffffffff81d4c61c>] x86_64_start_kernel+0x143/0x152

[Raymond (superquad-vortex2)]

   18.950222] ACPI Warning: SystemIO range 0x0000000000000828-0x000000000000082f conflicts with OpRegion 0x0000000000000800-0x000000000000084f (\PMRG) (20141107/utaddress-258)
[ 18.950228] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 18.950231] ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052f conflicts with OpRegion 0x0000000000000500-0x000000000000052f (\GPR2) (20141107/utaddress-258)
[ 18.950234] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 18.950254] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 19.217503] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
[ 19.375934] input: Logitech M510 as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.2/0003:046D:C52B.0003/0003:046D:1025.0004/input/input3
[ 19.376035] logitech-hidpp-device 0003:046D:1025.0004: input,hidraw1: USB HID v1.11 Mouse [Logitech M510] on usb-0000:00:1d.0-1.5:1
[ 19.409183] media: module verification failed: signature and/or required key missing - tainting kernel
[ 19.409517] media: Linux media interface: v0.10
[ 19.460019] Linux video capture interface: v2.00
[ 19.460023] WARNING: You are using an experimental version of the media stack.
 As the driver is backported to an older kernel, it doesn't offer
 enough quality for its usage in production.
 Use it with care.
Latest git patches (needed if you report a bug to <email address hidden>):
 1555f3bf5cc172e7d23c2b8db10d656d15bec13e [media] saa7164: fix compiler warning
 ebf984bb151e9952cccd060d3aba0b4d30a87e81 [media] v4l2: replace s_mbus_fmt by set_fmt in bridge drivers
 5eab4983777ba913efb42dd0f177b0dcdbd4f3d9 [media] v4l2: replace try_mbus_fmt by set_fmt in bridge drivers
[ 19.567660] Bluetooth: Core ver 2.20
[ 19.567675] NET: Registered protocol family 31
[ 19.567676] Bluetooth: HCI device and connection manager initialized
[ 19.567681] Bluetooth: HCI socket layer initialized
[ 19.567684] Bluetooth: L2CAP socket layer initialized
[ 19.567690] Bluetooth: SCO socket layer initialized
[ 19.609562] gpio_ich: GPIO from 436 to 511 on gpio_ich
[ 19.630985] usbcore: registered new interface driver btusb
[ 19.736937] bluetooth hci0: Direct firmware load for brcm/BCM20702A0-0a5c-21e8.hcd failed with error -2
[ 19.736947] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e8.hcd not found
[ 19.745898] WARNING: You are using an experimental version of the media stack.
 As the driver is backported to an older kernel, it doesn't offer
 enough quality for its usage in production.
 Use it with care.
Latest git patches (needed if you report a bug to <email address hidden>):
 1555f3bf5cc172e7d23c2b8db10d656d15bec13e [media] saa7164: fix compiler warning
 ebf984bb151e9952cccd060d3aba0b4d30a87e81 [media] v4l2: replace s_mbus_fmt by set_fmt in bridge drivers
 5eab4983777ba913efb42dd0f177b0dcdbd4f3d9 [media] v4l2: replace try_mbus_fmt by set_fmt in bridge drivers
[ 19.803467] WARNING: You are using an experimental version of the media stack.
 As the driver is backported to an older kernel, it doesn't offer
 en...

[Vindicator (vindicator)]

<sigh>So do you think the BIOS is the root cause? It is ~5 years old and I've flashed the latest firmware some years back and I'm sure they won't be supporting any more changes.

I haven't really had issues in Vista but knew in time I'd likely shift to Linux.

Is there a way to find out what hardware is surely compatible prior to purchasing it (no bios, acpi, usb, ... flaws)?
I am aware of "Desktop Hardware Compatibility List" (http://ubuntuforums.org/showthread.php?t=361236), but can't trust any of it.
I could have posted that mine was compatible since everything would (seem to) work using Ubuntu Live or even right after the install, but there would be issues below the surface that could only be found in the log or by putting the system to sleep/resume, and logs aren't posted on that thread.

"When" I upgrade my hardware, I'd like to know the logs will be clean of any errors due to hardware misprogramming.

[Raymond (superquad-vortex2)]

try ubuntu 14.10 or 14.04 LTS LiveCD and check whether those iommu oops occur or not

[Vindicator (vindicator)]

LiveCD
Linux ubuntu 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
*****
May 15 16:54:14 ubuntu kernel: [ 0.000000] WARNING: CPU: 0 PID: 0 at /build/buildd/linux-3.13.0/drivers/iommu/dmar.c:488 warn_invalid_dmar+0x7e/0x90()
May 15 16:54:14 ubuntu kernel: [ 0.000000] Your BIOS is broken; DMAR reported at address fed91000 returns all ones!
May 15 16:54:14 ubuntu kernel: [ 0.000000] BIOS vendor: American Megatrends Inc.; Ver: P2.20; Product Version: To Be Filled By O.E.M.
May 15 16:54:14 ubuntu kernel: [ 0.000000] Modules linked in:
May 15 16:54:14 ubuntu kernel: [ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 3.13.0-24-generic #46-Ubuntu
May 15 16:54:14 ubuntu kernel: [ 0.000000] Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./H55M Pro, BIOS P2.20 08/06/2010
May 15 16:54:14 ubuntu kernel: [ 0.000000] 000000000000000b ffffffff81c01de8 ffffffff81715a64 ffffffff81c01e30
May 15 16:54:14 ubuntu kernel: [ 0.000000] ffffffff81c01e20 ffffffff810676bd ffffffff81fdc01c ffffffff81fdc060
May 15 16:54:14 ubuntu kernel: [ 0.000000] 00000000fed91000 0000000000000000 ffffffff81c01fb0 ffffffff81c01e80
May 15 16:54:14 ubuntu kernel: [ 0.000000] Call Trace:
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81715a64>] dump_stack+0x45/0x56
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff810676bd>] warn_slowpath_common+0x7d/0xa0
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81067774>] warn_slowpath_fmt_taint+0x44/0x50
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d4eef4>] ? __early_set_fixmap+0xa0/0xa5
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff815ed65e>] warn_invalid_dmar+0x7e/0x90
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d89765>] check_zero_address+0xd6/0xf4
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d89798>] detect_intel_iommu+0x15/0xae
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d3ef9d>] pci_iommu_alloc+0x4a/0x6c
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d4ec4a>] mem_init+0x17/0x9c
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d34d3a>] start_kernel+0x202/0x443
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d34941>] ? repair_env_string+0x5c/0x5c
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d34120>] ? early_idt_handlers+0x120/0x120
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d345ee>] x86_64_start_reservations+0x2a/0x2c
May 15 16:54:14 ubuntu kernel: [ 0.000000] [<ffffffff81d34733>] x86_64_start_kernel+0x143/0x152
*****
Looks to be the same stuff...
I posted on another forum that I think it would be great if Linux had a testing tool that manufacturers could run against their hardware and if it came back perfectly clean, they can claim full compatibility.
Otherwise, it's just playing russian-roulette to see what will work or not.
I read on another forum about MSI only having a firmware flashing tool for windows, so that's something I need to keep in mind.

[Raymond (superquad-vortex2)]

diff -u alsa_info_before_suspend alsa_info_after_resume

[Vindicator (vindicator)]

I'll post the diff, but also want you to know I've started the upgrade process with the purchase of the ASRock H97M.
The reason for the definitive decision to upgrade is my secondary drive which is 4TB ended up failing big-time.

Switching back and forth between ubuntu and vista (primary 1.5TB), I'd get a notice about the 4TB partition size being less, so I'd let ubuntu change it. Then the other day when I did the diff test from live cd, I thought I'd switch to my ubuntu partition to run the same test except I got emergency mode and saw the drive was the issue. I went back to vista and it wasn't there anymore.
Testdisk got "the?" partition back (many found), but no files with both MFTs being corrupt.

So hopefully going from BIOS to UEFI will make all the difference. I think I read that ASRock can update it's firmware via USB, so I'm not limited to windows in order to flash.

diff:
*****
--- ./suspendBefore/alsa-info.txt.IBQ3iv1Byh 2015-05-16 17:00:02.996456000 +0000
+++ ./suspendAfter/alsa-info.txt.t07g81UwFs 2015-05-16 17:02:06.197731000 +0000
@@ -3,7 +3,7 @@
 !!ALSA Information Script v 0.4.64
 !!################################

-!!Script ran on: Sat May 16 17:00:01 UTC 2015
+!!Script ran on: Sat May 16 17:02:04 UTC 2015

 !!Linux Distribution
@@ -161,7 +161,7 @@
   Device: name="VT1718S Analog", type="Audio", device=0
   Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
   Amp-Out vals: [0x1d 0x1d]
- Converter: stream=8, channel=0
+ Converter: stream=0, channel=0
   PCM:
     rates [0x5e0]: 44100 48000 88200 96000 192000
     bits [0xe]: 16 20 24
@@ -173,7 +173,7 @@
     ControlAmp: chs=3, dir=Out, idx=0, ofs=0
   Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
   Amp-Out vals: [0x1d 0x1d]
- Converter: stream=8, channel=0
+ Converter: stream=0, channel=0
   PCM:
     rates [0x5e0]: 44100 48000 88200 96000 192000
     bits [0xe]: 16 20 24
@@ -187,7 +187,7 @@
     ControlAmp: chs=2, dir=Out, idx=0, ofs=0
   Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
   Amp-Out vals: [0x1d 0x1d]
- Converter: stream=8, channel=0
+ Converter: stream=0, channel=0
   PCM:
     rates [0x5e0]: 44100 48000 88200 96000 192000
     bits [0xe]: 16 20 24
@@ -200,7 +200,7 @@
   Device: name="VT1718S Alt Analog", type="Audio", device=2
   Amp-Out caps: ofs=0x2a, nsteps=0x2a, stepsize=0x05, mute=0
   Amp-Out vals: [0x1d 0x1d]
- Converter: stream=8, channel=0
+ Converter: stream=0, channel=0
   PCM:
     rates [0x5e0]: 44100 48000 88200 96000 192000
     bits [0xe]: 16 20 24
@@ -225,7 +225,7 @@
   Control: name="IEC958 Playback Switch", index=0, device=0
   Control: name="IEC958 Default PCM Playback Switch", index=0, device=0
   Device: name="VT1718S Digital", type="HDMI", device=3
- Converter: stream=8, channel=0
+ Converter: stream=0, channel=0
   Digital:
   Digital category: 0x0
   IEC Coding Type: 0x0
@@ -577,7 +577,7 @@
 crw-rw----+ 1 root audio 116, 10 May 16 11:56 /dev/snd/controlC0
 crw-rw----+ 1 root audio 116, 3 May 16 11:56 /dev/snd/controlC1
 crw-rw----+ 1 root audio 116, 9 May 16 11:56 /dev/snd/hwC0D0
-crw-rw----+ 1 root audio 116, 8 May 16 16:59 /dev/snd/pcmC0D0c
+crw-rw----+ 1 root audio 116, 8 May ...

[Launchpad Janitor (janitor)]

[Expired for pulseaudio (Ubuntu) because there has been no activity for 60 days.]