Page 1 of 1

The default sound device cannot be opened

Posted: Sun Apr 05, 2020 9:19 am
by jan
Hello,
I am running 19.3 Mint with Cinnamon in a VMware workstation 12.
After logging in, there is a brief error message of the above.
Sound does work on the host (windows). It did stop working on a Mint 17.3 VM but I fixed that by changing the output (prefs - sound) from stereo duplex to stereo analogue.
Things I noticed. On the 19.3 VM, the sound prefs under the output tab only offered either mono or stereo analogue INPUT, not output.
I installed pavcontrol and later the prefs - sound app showed output but still only two options whereas 17.3 Mint shows many options.
The sound card (motherboard built in) is seen
~$ inxi -Fxz
......
Audio: Device-1: Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371 v: kernel bus ID: 02:02.0
Sound Server: ALSA v: k5.3.0-45-generic
.....
~$ aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: AudioPCI [Ensoniq AudioPCI], device 0: ES1371/1 [ES1371 DAC2/ADC]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: AudioPCI [Ensoniq AudioPCI], device 1: ES1371/2 [ES1371 DAC1]
Subdevices: 1/1
Subdevice #0: subdevice #0

The vmx file has the correct entries
sound.present = "TRUE"
sound.fileName = "-1"
sound.autodetect = "TRUE"

Any ideas?
Regards,
John

Re: The default sound device cannot be opened

Posted: Sun Apr 05, 2020 12:19 pm
by MrEen
Hi jan.

I haven't really worked with sound issue under this setup before, but let's see if we can get it sorted out.

Run pacmd list-cards in the terminal and paste that output. With luck, we just need a profile change that should be spotted with that command.

I don't know what to expect, but the output of dmesg | grep snd might help as well.

Re: The default sound device cannot be opened

Posted: Mon Apr 06, 2020 3:52 am
by jan
~$ pacmd list-cards
1 card(s) available.
index: 0
name: <alsa_card.pci-0000_02_02.0>
driver: <module-alsa-card.c>
owner module: 7
properties:
alsa.card = "0"
alsa.card_name = "Ensoniq AudioPCI"
alsa.long_card_name = "Ensoniq AudioPCI ENS1371 at 0x2040, irq 16"
alsa.driver_name = "snd_ens1371"
device.bus_path = "pci-0000:02:02.0"
sysfs.path = "/devices/pci0000:00/0000:00:11.0/0000:02:02.0/sound/card0"
device.bus = "pci"
device.vendor.id = "1274"
device.vendor.name = "Ensoniq"
device.product.id = "1371"
device.product.name = "ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI])"
device.string = "0"
device.description = "ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI])"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
profiles:
input:analog-mono: Analogue Mono Input (priority 2, available: unknown)
input:analog-stereo: Analogue Stereo Input (priority 60, available: unknown)
output:analog-mono: Analogue Mono Output (priority 200, available: unknown)
output:analog-mono+input:analog-mono: Analogue Mono Duplex (priority 202, available: unknown)
output:analog-mono+input:analog-stereo: Analogue Mono Output + Analogue Stereo Input (priority 260, available: unknown)
output:analog-stereo: Analogue Stereo Output (priority 6000, available: unknown)
output:analog-stereo+input:analog-mono: Analogue Stereo Output + Analogue Mono Input (priority 6002, available: unknown)
output:analog-stereo+input:analog-stereo: Analogue Stereo Duplex (priority 6060, available: unknown)
off: Off (priority 0, available: unknown)
active profile: <output:analog-stereo+input:analog-mono>
sinks:
alsa_output.pci-0000_02_02.0.analog-stereo/#0: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) Analogue Stereo
sources:
alsa_output.pci-0000_02_02.0.analog-stereo.monitor/#0: Monitor of ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) Analogue Stereo
alsa_input.pci-0000_02_02.0.analog-mono/#1: ES1371/ES1373 / Creative Labs CT2518 (Audio PCI 64V/128/5200 / Creative CT4810/CT5803/CT5806 [Sound Blaster PCI]) Analogue Mono
ports:
analog-input-mic: Microphone (priority 8700, latency offset 0 usec, available: unknown)
properties:
device.icon_name = "audio-input-microphone"
analog-input-linein: Line In (priority 8100, latency offset 0 usec, available: unknown)
properties:

analog-input-aux: Analogue Input (priority 8000, latency offset 0 usec, available: unknown)
properties:

analog-input-video: Video (priority 7000, latency offset 0 usec, available: unknown)
properties:

analog-output: Analogue Output (priority 9900, latency offset 0 usec, available: unknown)
properties:

:~$ dmesg | grep snd
~$

Re: The default sound device cannot be opened

Posted: Mon Apr 06, 2020 3:44 pm
by MrEen
Try running PulseAudio Volume Control (pavucontrol) and on the Configuration tab change the Profile to Analog Stereo Duplex and see if that jump starts the sound.

The other thing that might be causing your issue is permissions/ownership issues. But that's a little advanced for me in this scenario. Are you logging in to the system as a regular user? If not, that might be the issue.

Re: The default sound device cannot be opened

Posted: Tue Apr 07, 2020 4:12 am
by jan
Yes tried that. It was already set to stereo duplex. And changing ti to analogue made no difference either.
As I mentioned I did get this to work on older versions on mint (16). Perhaps this is a driver issue where the new versions of mint have drivers that are incompatible with my 10 year old motherboard with regard to the sound chip?

Re: The default sound device cannot be opened

Posted: Tue Apr 07, 2020 3:15 pm
by MrEen
I'd honestly suspect something between the Windows host and VMWare Workstation 12 myself, but I'm guessing here.

I just don't know enough about this use case to be able to offer much I'm afraid. The only thing that jumps out to me is to try deleting the files in /home/YourUserName/.config/pulse then run pulseaudio -k to see if that kicks it into gear.

Re: The default sound device cannot be opened

Posted: Fri Jul 10, 2020 3:44 am
by jan
Sorry for the delay in continuing this but I thought I would have another bash at trying to get this to work.
Here is the audio card output from inxi -Fxz
For mint 17.3
Audio: Card: Ensoniq ES1371 / Creative Labs CT2518/ES1373 driver: snd_ens1371 port: 2040 bus-ID: 02:02.0
Sound: Advanced Linux Sound Architecture ver: k3.13.0-24-generic

And here is the output for 19
Audio: Card Ensoniq ES1371/ES1373 / Creative Labs CT2518 driver: snd_ens1371 port: 2040 bus-ID: 02:02.0
Sound: Advanced Linux Sound Architecture v: k4.15.0-99-generic

So I am using a different version of the driver.
Could I revert to the older version? Would this be stable? And how would I do that?

Re: The default sound device cannot be opened

Posted: Fri Jul 10, 2020 7:15 pm
by MrEen
Those versions are the kernel versions, and you do not want to use a 3.x kernel on Mint 19. You might try going the other way and upgrading the kernel to the 5.4 version that should be available in the Update Manager.

I should note however that I have no Windows experience with VM's, and it's very possible this is a Windows issue, not Mint. Did you install whatever VMWare calls their version of Guest Additions?

Re: The default sound device cannot be opened

Posted: Sat Jul 11, 2020 12:21 am
by jan
Yes, vmtools has been installed. It allows bidirectional copy and paste between windows host and linux guest and that works.
The fact that sound works for a mint 16 VM that was subsequently upgraded to 17 does suggest that it is not a windows host problem.
I also tried using VirtualBox and sound does not work there. Which possibly suggests that it is the kernel / drivers that do not work with the on board sound chip though I can't imagine these things change.
Using the details in my previous post, does anyone have sound working with mint 18/19 and a Creative 128?

Re: The default sound device cannot be opened

Posted: Sat Jul 11, 2020 12:34 am
by MrEen
All I can say here is when I launch a VM, the sound driver doesn't reflect my built-in sound card at all, although sound does work in the VM. The VM uses virtualized stuff that is somewhat beyond my knowledge.

Hopefully someone else will have some ideas.