This is output of alsa-info.sh: http://fm.no-ip.com/Tmp/Linux/Bobs/alsa-info.txt-os132-a88x-easyst Short form (aplay -l): **** List of PLAYBACK Hardware Devices **** card 0: HDMI [HDA ATI HDMI], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: HDMI [HDA ATI HDMI], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 0: ALC1150 Analog [ALC1150 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 1: Generic [HD-Audio Generic], device 3: ALC1150 Digital [ALC1150 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 (cat /proc/asound/cards) 0 [HDMI ]: HDA-Intel - HDA ATI HDMI HDA ATI HDMI at 0xfeb64000 irq 37 1 [Generic ]: HDA-Intel - HD-Audio Generic HD-Audio Generic at 0xfeb60000 irq 16 This is a multiboot system. Without out any manual intervention in /etc/modprobe.d/ or /etc/asound.conf, HDMI sounds (aplay, VLC, smplayer, desktop system sounds, and HTML5) are working on the following: openSUSE 13.1 (KDE3) openSUSE 42.1 (TDE) Debian Stretch (TDE) I was able to get Xorg sounds working on 13.1 only after upgrading alsa-firmware and kernel-firmware to newer than original versions, and kernel from 3.11 to 4.5. On openSUSE 13.2 (IceWM, KDE3, KDE4) even after upgrading its kernel to 4.5, and alsa-firmware and kernel-firmware to recent versions, I can't figure out how to get sound to work from anything except aplay. To make aplay put sound on HDMI requires either -Dhdmi:0 or -Dhdmi:0,0. Without any (other) option aplay produces this error: ALSA lib pcm_dmix.c:1022:(snd_pcm_dmix_open) unable to open slave aplay: main:722: audio open error: No such file or directory What file can't aplay find? Why is it looking for a "slave"? Why isn't card 0 used by default? Why isn't device 0 equal to card 0 instead of card 0 having devices 3 & 7, and card 1 having devices 0 and 1? Surely this must be related to why Xorg has no sound of any kind, but why, and how to fix? I don't really understand http://www.alsa-project.org/main/index.php/Asoundrc or other docs on such things WRT device specification. In particular on that page, why does the section following "The default plugin" even exist? What is it trying to make happen instead of what? Based on web searches, the following are various /etc/modprobe.d/ options I've tried with 13.2, all without success: options snd index=1,0 options snd_hda_intel index=1 options snd_hda_intel index=1,0 options snd_hda_intel index=1,1 options snd-hda-intel index=1 options snd-hda-intel index=1,0 options snd-hda-intel index=1,1 options snd-hda-intel index=0 model=ref enable_msi=1 enable=1,0 options snd-hda-intel index=1 model=ref enable_msi=1 enable=1,0 options snd-hda-intel index=0 model=ref enable=1,0 options snd-hda-intel single_cmd=1 options snd-hda-intel probe_mask=1 What man page or HOWTO should cover solving this kind of trouble? I'm having no luck finding a solution. There's no man page for /etc/asound.conf, alsa, alsa-utils or others I've tried. The man page for aplay is like most man pages, void of examples that might make it possible to relate its switch descriptions to needed configuration settings. This has been consuming an obscene amount of my time for nearly three weeks. :-( I would be really grateful for any suggestion that would quickly lead to a solution. The machine belongs to a virtually blind user who really needs reliable sound for his TTS, and who is extra handicapped by having no PC at all while I'm trying to figure this out for him. These mailing list threads show more that I've tried than I've written here: https://lists.opensuse.org/opensuse/2016-05/msg00356.html http://trinity-users.pearsoncomputing.net/?0::10228 Various logging I've done trying to get this working can be found on: http://fm.no-ip.com/Tmp/Linux/Bobs/ -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
