The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
On 03/28/2017 05:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
I have similar issue with USB headphones. Worked fine in 7.2 but in 7.3 I frequently have to unplug and plug them back in before it finally is able to be selected from the menus as my output.
Once it is selected, it stays selected until next reboot.
On Tue, 28 Mar 2017, Alice Wonder wrote:
On 03/28/2017 05:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
I have similar issue with USB headphones. Worked fine in 7.2 but in 7.3 I frequently have to unplug and plug them back in before it finally is able to be selected from the menus as my output.
I notice that you have an HDA-Intel. I do as well. By any chance is the last kernel that worked reliably with sound is kernel-3.10.0-229.20.1.el7.x86_64. I find that with kernels newer than kernel-3.10.0-229.20.1.el7.x86_64 the sound card works, but the internal speaker is disabled, but I can plug in headphones and get sound that way. If I boot into kernel-3.10.0-229.20.1.el7.x86_64 with no other modifications to my system, my sound works fine.
Barry
On 03/29/2017 02:23 AM, Barry Brimer wrote:
On Tue, 28 Mar 2017, Alice Wonder wrote:
On 03/28/2017 05:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
I have similar issue with USB headphones. Worked fine in 7.2 but in 7.3 I frequently have to unplug and plug them back in before it finally is able to be selected from the menus as my output.
I notice that you have an HDA-Intel. I do as well. By any chance is the last kernel that worked reliably with sound is kernel-3.10.0-229.20.1.el7.x86_64. I find that with kernels newer than kernel-3.10.0-229.20.1.el7.x86_64 the sound card works, but the internal speaker is disabled, but I can plug in headphones and get sound that way. If I boot into kernel-3.10.0-229.20.1.el7.x86_64 with no other modifications to my system, my sound works fine.
Barry
Hey, Barry,
Thanks for the reply. Frankly I have no idea at all the last kernel version in which audio from non-DVD sources worked properly. But the sound for me, where it has worked, has always worked both from the onboard speakers and from the headphones... and I could easily switch back and forth, playing from the speakers, then plug in headphones and play from them... and back again. So your situation and mine are different... which isn't necessarily to say that a problem can't manifest itself in slightly different ways. I'm just saying that I'm not convinced the problem I have is/was caused by a kernel change. In any event, I wouldn't want to go back to an old kernel version. There were some major security patches in the more recent kernels and I wouldn't want to introduce those vulnerabilities back into my system. I think I'd rather go without the system's sound.
Thanks++, ken
On 03/28/2017 11:40 PM, Alice Wonder wrote:
On 03/28/2017 05:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
I have similar issue with USB headphones. Worked fine in 7.2 but in 7.3 I frequently have to unplug and plug them back in before it finally is able to be selected from the menus as my output.
Once it is selected, it stays selected until next reboot.
Alice,
Thanks for your reply. I believe you and I are looking at two separate problems. My system is capable of switching between the onboard speakers and the headphones with no problem at all (when the sound is working at all). That is, when there's sound out of the onboards, I can plug in the headphones and sound instantly comes out of them, and vice versa... even in the middle of one and the same video.
In your case the problem may have more to do with USB. USB is notoriously slow... at least it used to be. This is due to timing, i.e., after loading the USB sub-system, the system has to query the USB device to find out what it is (e.g., mouse, joystick, headphones, touchpad, etc.) and there are a bazillion different kinds of USB devices... a long list of things to query. Not only that, but a single query takes time: the system has to give the device time to respond-- it used to be a second or two. And there are ever more USB devices. Maybe too your headphones are near the bottom of the long list of USB devices.
I don't know that this is your situation. It could be something else (a half dozen other hang-ups). But you might want to test by plugging in your USB headphones and then leaving the plug in, waiting a couple minutes to see if they start to work.
Alice, could you please post the output of these three commands (for comparison purposes):
uname -r ps -ef|grep -i alsa aplayer -L
Thanks.
On 03/29/2017 04:05 AM, ken wrote:
On 03/28/2017 11:40 PM, Alice Wonder wrote:
On 03/28/2017 05:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
I have similar issue with USB headphones. Worked fine in 7.2 but in 7.3 I frequently have to unplug and plug them back in before it finally is able to be selected from the menus as my output.
Once it is selected, it stays selected until next reboot.
Alice,
Thanks for your reply. I believe you and I are looking at two separate problems. My system is capable of switching between the onboard speakers and the headphones with no problem at all (when the sound is working at all). That is, when there's sound out of the onboards, I can plug in the headphones and sound instantly comes out of them, and vice versa... even in the middle of one and the same video.
In your case the problem may have more to do with USB. USB is notoriously slow... at least it used to be. This is due to timing, i.e., after loading the USB sub-system, the system has to query the USB device to find out what it is (e.g., mouse, joystick, headphones, touchpad, etc.) and there are a bazillion different kinds of USB devices... a long list of things to query. Not only that, but a single query takes time: the system has to give the device time to respond-- it used to be a second or two. And there are ever more USB devices. Maybe too your headphones are near the bottom of the long list of USB devices.
I don't know that this is your situation. It could be something else (a half dozen other hang-ups). But you might want to test by plugging in your USB headphones and then leaving the plug in, waiting a couple minutes to see if they start to work.
Alice, could you please post the output of these three commands (for comparison purposes):
uname -r ps -ef|grep -i alsa aplayer -L
Thanks.
[alice@localhost ~]$ uname -r 3.10.0-514.6.2.el7.x86_64 [alice@localhost ~]$ ps -ef |grep -i alsa root 858 1 0 Feb27 ? 00:00:00 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main rdaemon alice 29238 29155 0 09:03 pts/19 00:00:00 grep --color=auto -i alsa [alice@localhost ~]$ aplayer -L bash: aplayer: command not found... [alice@localhost ~]$
-=-
Intel xeon on supermicro board
No onboard sound but unfortunately the video card has Intel HD audio associated with the HDMI out that for some reason the system always defaults to after boot even though there is no audio out on the video card (nvidia card) other than the HDMI which I only use for video.
I had blacklisted the Intel HD and that worked under CentOS 7.2 but I couldn't USB audio to work in 7.3 until I removed the blacklisted Intel HD driver, but I'm not sure if that was cause and effect or coincidence.
I really wish USB sound would "just work" and that the sound preferences would remember I prefer USB after a reboot. Linux use to be better about that sort of thing.
On 03/29/2017 12:08 PM, Alice Wonder wrote:
On 03/29/2017 04:05 AM, ken wrote:
On 03/28/2017 11:40 PM, Alice Wonder wrote:
On 03/28/2017 05:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
I have similar issue with USB headphones. Worked fine in 7.2 but in 7.3 I frequently have to unplug and plug them back in before it finally is able to be selected from the menus as my output.
Once it is selected, it stays selected until next reboot.
Alice,
Thanks for your reply. I believe you and I are looking at two separate problems. My system is capable of switching between the onboard speakers and the headphones with no problem at all (when the sound is working at all). That is, when there's sound out of the onboards, I can plug in the headphones and sound instantly comes out of them, and vice versa... even in the middle of one and the same video.
In your case the problem may have more to do with USB. USB is notoriously slow... at least it used to be. This is due to timing, i.e., after loading the USB sub-system, the system has to query the USB device to find out what it is (e.g., mouse, joystick, headphones, touchpad, etc.) and there are a bazillion different kinds of USB devices... a long list of things to query. Not only that, but a single query takes time: the system has to give the device time to respond-- it used to be a second or two. And there are ever more USB devices. Maybe too your headphones are near the bottom of the long list of USB devices.
I don't know that this is your situation. It could be something else (a half dozen other hang-ups). But you might want to test by plugging in your USB headphones and then leaving the plug in, waiting a couple minutes to see if they start to work.
Alice, could you please post the output of these three commands (for comparison purposes):
uname -r ps -ef|grep -i alsa aplayer -L
Thanks.
[alice@localhost ~]$ uname -r 3.10.0-514.6.2.el7.x86_64
It looks like either you need to do a kernel upgrade or you haven't rebooted since the most recent. I have 3.10.0-514.10.2.el7.x86_64.
[alice@localhost ~]$ ps -ef |grep -i alsa root 858 1 0 Feb27 ? 00:00:00 /usr/sbin/alsactl -s -n 19 -c -E ALSA_CONFIG_PATH=/etc/alsa/alsactl.conf --initfile=/lib/alsa/init/00main rdaemon
This is the same as what I have. So the same command is fired up to run alsa. I looked at the two files (both text files) and they're both, to me, inscrutable. The second one, is actually a program, code which programmatically configures alsactl. The programming language it uses is fairly normal and simple, but even with that, with all the variables and other files it uses and various operations it invokes, and then all the knowledge of internals of audio and the sound card it entails, it would take quite a bit of study to get a grip on it. Getting some human help there or a good doc or two (in addition to its man page) might even make it possible to fathom... :) then possibly happen onto the fix.
[alice@localhost ~]$ aplayer -L bash: aplayer: command not found...
Sorry, Alice. I shouldn't have trusted memory. The actual command is "aplay -L".
-=-
Intel xeon on supermicro board
Nice.
No onboard sound but unfortunately the video card has Intel HD audio associated with the HDMI out that for some reason the system always defaults to after boot even though there is no audio out on the video card (nvidia card) other than the HDMI which I only use for video.
Your system doesn't have a plug (typically a three- or four-connector (sub)mini-D) for analog sound?
I had blacklisted the Intel HD and that worked under CentOS 7.2 but I couldn't USB audio to work in 7.3 until I removed the blacklisted Intel HD driver, but I'm not sure if that was cause and effect or coincidence.
I really wish USB sound would "just work" and that the sound preferences would remember I prefer USB after a reboot. Linux use to be better about that sort of thing.
Well, it can't remember what it can't do properly in the first place. Have you compared lsmod output prior to plugging into USB to lsmod output when plugged in and functioning properly?
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an openSUSE version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
HI. OK. I had a bit more time to check things out. I have full pulseaudio installed on my setup under CentOS 6.8, including the hooks from alsa to pulseaudio and hooks to pulseaudio from X server. Additionally, I have PulseAudio Sound System in my startup applications from Centos 6.8, Gnome 2. That is what I had to manually cobble up on openSuSE.
Best of luck.
On Sun, Apr 2, 2017 at 10:31 AM, Kay Schenk kay.schenk@gmail.com wrote:
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768 a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and
they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an openSUSE
version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
--
MzK
"If evolution is outlawed, only outlaws will evolve."
-- Jello Biafra
On 04/02/2017 01:31 PM, Kay Schenk wrote:
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an openSUSE version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
Thanks for the thought. This is quite plausible. I did a little reading at the site you suggested and then at another which was linked off of that. I didn't find anything helpful at either place yet... well, except that in the audio stack alsa is just one layer; jack and pulseaudio ride on top of it. Apparently sound on linux can use all of them-- and others on both of the same layers-- all at the same time. This is probably what makes the configuration of them all so challenging.
In the middle of reading those sites I decided to see if audacity (a quite sophisticated and solid program) could somehow handle sound. I installed it and fired it up. Out of the box it didn't work. But I simply had to choose the correct device from audacity's drop-down menu and, viola, it would produce sound from a loaded file. Cool.
Right after that, I tried running "aplay /usr/share/sounds/alsa/Front_Right.wav" and that worked. Previously it didn't, although (as noted above) that same command when specifying the device did (i.e., "aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently installing and/or running audacity fixed something, but not everything.
Another trippy discovery: I used rpm to verify all the files installed with all the alsa* packages and there were absolutely no changes to any of them... they're all exactly as they were when first installed. Since sound worked exquisitely when I first installed 7.2 on this box and no alsa files have been changed since then, it's hard to find the fault with alsa.
Although aplay is back to working without having to specify the device, I still don't get sound out of youtube videos (even though I checked the settings and restarted Firefox), and gnome3's System Settings -> Sound still lists no devices at all. These are two major failures.
Does anyone know how to restart audio in systemd? That might still be worth looking into.
Before doing audacity, I tried gnome's mplayer. Geez, is that a stinky pile of code. Just selecting a directory where a file could be selected ended up locking up the app; I had to do a kill to get it off my screen. Does that actually work for anyone? If so, what kind of files or net locations does it work for?
Thanks once more for your thoughtful suggestions.
---see below --
On Mon, Apr 3, 2017 at 9:53 AM, ken gebser@mousecar.com wrote:
On 04/02/2017 01:31 PM, Kay Schenk wrote:
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768 a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and
they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an
openSUSE version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
Thanks for the thought. This is quite plausible. I did a little reading
at the site you suggested and then at another which was linked off of that. I didn't find anything helpful at either place yet... well, except that in the audio stack alsa is just one layer; jack and pulseaudio ride on top of it. Apparently sound on linux can use all of them-- and others on both of the same layers-- all at the same time. This is probably what makes the configuration of them all so challenging.
In the middle of reading those sites I decided to see if audacity (a quite sophisticated and solid program) could somehow handle sound. I installed it and fired it up. Out of the box it didn't work. But I simply had to choose the correct device from audacity's drop-down menu and, viola, it would produce sound from a loaded file. Cool.
Right after that, I tried running "aplay /usr/share/sounds/alsa/Front_Right.wav" and that worked. Previously it didn't, although (as noted above) that same command when specifying the device did (i.e., "aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently installing and/or running audacity fixed something, but not everything.
Another trippy discovery: I used rpm to verify all the files installed with all the alsa* packages and there were absolutely no changes to any of them... they're all exactly as they were when first installed. Since sound worked exquisitely when I first installed 7.2 on this box and no alsa files have been changed since then, it's hard to find the fault with alsa.
Although aplay is back to working without having to specify the device, I still don't get sound out of youtube videos (even though I checked the settings and restarted Firefox), and gnome3's System Settings -> Sound still lists no devices at all. These are two major failures.
Does anyone know how to restart audio in systemd? That might still be worth looking into.
Before doing audacity, I tried gnome's mplayer. Geez, is that a stinky pile of code. Just selecting a directory where a file could be selected ended up locking up the app; I had to do a kill to get it off my screen. Does that actually work for anyone? If so, what kind of files or net locations does it work for?
Thanks once more for your thoughtful suggestions.
Here ya go! A lovely sysvinit to systemd cheatsheet!
https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
Well assuming your sound is started at this level. It should be in your systemd scripts. (I can't help with this as I have not used systemd in a WHILE).
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 04/03/2017 06:34 PM, Kay Schenk wrote:
---see below --
On Mon, Apr 3, 2017 at 9:53 AM, ken gebser@mousecar.com wrote:
On 04/02/2017 01:31 PM, Kay Schenk wrote:
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768 a0f5b109947a48. Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and
they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an
openSUSE version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
Thanks for the thought. This is quite plausible. I did a little reading
at the site you suggested and then at another which was linked off of that. I didn't find anything helpful at either place yet... well, except that in the audio stack alsa is just one layer; jack and pulseaudio ride on top of it. Apparently sound on linux can use all of them-- and others on both of the same layers-- all at the same time. This is probably what makes the configuration of them all so challenging.
In the middle of reading those sites I decided to see if audacity (a quite sophisticated and solid program) could somehow handle sound. I installed it and fired it up. Out of the box it didn't work. But I simply had to choose the correct device from audacity's drop-down menu and, viola, it would produce sound from a loaded file. Cool.
Right after that, I tried running "aplay /usr/share/sounds/alsa/Front_Right.wav" and that worked. Previously it didn't, although (as noted above) that same command when specifying the device did (i.e., "aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently installing and/or running audacity fixed something, but not everything.
Another trippy discovery: I used rpm to verify all the files installed with all the alsa* packages and there were absolutely no changes to any of them... they're all exactly as they were when first installed. Since sound worked exquisitely when I first installed 7.2 on this box and no alsa files have been changed since then, it's hard to find the fault with alsa.
Although aplay is back to working without having to specify the device, I still don't get sound out of youtube videos (even though I checked the settings and restarted Firefox), and gnome3's System Settings -> Sound still lists no devices at all. These are two major failures.
Does anyone know how to restart audio in systemd? That might still be worth looking into.
Before doing audacity, I tried gnome's mplayer. Geez, is that a stinky pile of code. Just selecting a directory where a file could be selected ended up locking up the app; I had to do a kill to get it off my screen. Does that actually work for anyone? If so, what kind of files or net locations does it work for?
Thanks once more for your thoughtful suggestions.
Here ya go! A lovely sysvinit to systemd cheatsheet!
https://fedoraproject.org/wiki/SysVinit_to_Systemd_Cheatsheet
Well assuming your sound is started at this level. It should be in your systemd scripts. (I can't help with this as I have not used systemd in a WHILE).
Thanks much.
On Mon, Apr 03, 2017 at 12:53:54PM -0400, ken wrote:
On 04/02/2017 01:31 PM, Kay Schenk wrote:
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an openSUSE version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
Thanks for the thought. This is quite plausible. I did a little reading at the site you suggested and then at another which was linked off of that. I didn't find anything helpful at either place yet... well, except that in the audio stack alsa is just one layer; jack and pulseaudio ride on top of it. Apparently sound on linux can use all of them-- and others on both of the same layers-- all at the same time. This is probably what makes the configuration of them all so challenging.
In the middle of reading those sites I decided to see if audacity (a quite sophisticated and solid program) could somehow handle sound. I installed it and fired it up. Out of the box it didn't work. But I simply had to choose the correct device from audacity's drop-down menu and, viola, it would produce sound from a loaded file. Cool.
Right after that, I tried running "aplay /usr/share/sounds/alsa/Front_Right.wav" and that worked. Previously it didn't, although (as noted above) that same command when specifying the device did (i.e., "aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently installing and/or running audacity fixed something, but not everything.
Another trippy discovery: I used rpm to verify all the files installed with all the alsa* packages and there were absolutely no changes to any of them... they're all exactly as they were when first installed. Since sound worked exquisitely when I first installed 7.2 on this box and no alsa files have been changed since then, it's hard to find the fault with alsa.
Although aplay is back to working without having to specify the device, I still don't get sound out of youtube videos (even though I checked the settings and restarted Firefox), and gnome3's System Settings -> Sound still lists no devices at all. These are two major failures.
Are you, perchance, using Firefox-52? At version 52, they switched Firefox to use Pulse instead of Alsa. So you'll probably need to fire up pavucontrol and mess with its sliders to get firefox audio working.
I'm on Centos-7.3, and when I switched from 7.2 I found that some things now are controlled by pavucontrol, and not by the volume control in the top panel (I'm using Mate, not Gnome,... Gah, how can anyone stand Gnome 3.x??) It's kind of a pain, I haven't yet found a way to localize controls for all the various audio-producing tools in one place. Does anyone know how to do that?
Does anyone know how to restart audio in systemd? That might still be worth looking into.
Before doing audacity, I tried gnome's mplayer. Geez, is that a stinky pile of code. Just selecting a directory where a file could be selected ended up locking up the app; I had to do a kill to get it off my screen. Does that actually work for anyone? If so, what kind of files or net locations does it work for?
Thanks once more for your thoughtful suggestions.
CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
On 04/03/2017 07:47 PM, Fred Smith wrote:
On Mon, Apr 03, 2017 at 12:53:54PM -0400, ken wrote:
On 04/02/2017 01:31 PM, Kay Schenk wrote:
On 03/29/2017 06:43 AM, ken wrote:
On 03/28/2017 08:53 PM, ken wrote:
The www has failed me with this, so I'm trying you guys. Sound worked great out of the box when I installed 7.2... Yay! I could watch all kinds of videos, like on facebook and youtube. And I could listen to most podcasts too. But then something happened. It was either a kernel upgrade or that I installed vlc (for watching videos on DVD) and the whole stack of codecs for it... I don't know exactly when, but at some point I no longer had sound with youtube and other web videos. The videos played fine, just no sound. Note that using vlc, both video and the audio with it play just fine. I need to select the audio driver (from a list in a vlc menu), however, else the sound won't work in vlc either.
If I go into the Applications menu, then System Tools -> Settings -> Sound, under "Choose a device for sound output:" there are no devices listed. There used to be.
If I run "aplayer file.wav", nothing plays (no sound at all) and I get the error "main:786: audio open error: No such file or directory". If, on the other hand, I run "aplay file.wav -D plughw:0" (i.e., specify the/a device), I do get sound, the file does play.
I ran alsa-info.sh and it posted tons of info from it on my setup at http://www.alsa-project.org/db/?f=1dba91886be054df4816000768a0f5b109947a48.
Yet it still doesn't tell me what's missing.
Anyone here have an idea...? or thoughts about where to look next?
tia, ken
Still poking around my system for a solution, I found this comment at the top of /usr/lib/systemd/system/alsa-state.service and two other files in the same directory:
# Note that two different ALSA card state management schemes exist and they # can be switched using a file exist check - /etc/alsa/state-daemon.conf .
The /etc/alsa/state-daemon.conf file consists of one line:
# Remove this file to disable the alsactl daemon mode
I understand that a daemon continually runs, waiting for an event and then acts in some way in response, but it has to mean something more in this context. Anyone familiar with the internals of this?
I am not on systemd right now. I'm on CentOS 6.8. However, on an openSUSE version I was. Sound problems were the bane of my existence forever it seemed. So it maye take you a while to troubleshoot this. Using JUST alsa you should be able to play sound files at the command line. See: http://www.alsa-project.org/main/index.php/Main_Page
I think I may have installed pulse-audio to get things working under systemd with my GUI. What is your GUI? This may be a factor.
Thanks for the thought. This is quite plausible. I did a little reading at the site you suggested and then at another which was linked off of that. I didn't find anything helpful at either place yet... well, except that in the audio stack alsa is just one layer; jack and pulseaudio ride on top of it. Apparently sound on linux can use all of them-- and others on both of the same layers-- all at the same time. This is probably what makes the configuration of them all so challenging.
In the middle of reading those sites I decided to see if audacity (a quite sophisticated and solid program) could somehow handle sound. I installed it and fired it up. Out of the box it didn't work. But I simply had to choose the correct device from audacity's drop-down menu and, viola, it would produce sound from a loaded file. Cool.
Right after that, I tried running "aplay /usr/share/sounds/alsa/Front_Right.wav" and that worked. Previously it didn't, although (as noted above) that same command when specifying the device did (i.e., "aplay /usr/share/sounds/alsa/Front_Right.wav -D plughw:0"). So apparently installing and/or running audacity fixed something, but not everything.
Another trippy discovery: I used rpm to verify all the files installed with all the alsa* packages and there were absolutely no changes to any of them... they're all exactly as they were when first installed. Since sound worked exquisitely when I first installed 7.2 on this box and no alsa files have been changed since then, it's hard to find the fault with alsa.
Although aplay is back to working without having to specify the device, I still don't get sound out of youtube videos (even though I checked the settings and restarted Firefox), and gnome3's System Settings -> Sound still lists no devices at all. These are two major failures.
Are you, perchance, using Firefox-52? At version 52, they switched Firefox to use Pulse instead of Alsa. So you'll probably need to fire up pavucontrol and mess with its sliders to get firefox audio working.
Good call, Fred. Just today I got a message when, doing testing, a message came up in Firefox that I needed to install pulseaudio.* Well, I never installed pulseaudio, but it's already installed,** so it must have been installed when I first installed 7.2 on this machine. So then I tried, as you suggested, to start up pavucontrol and play around with it. However, pavucontrol was not installed. So yumd'd it down and installed, then clicked on it in the Applications -> Sound & Video menu, but I just got a window pop with the message, "Fatal Error: Unable to connect to PulseAudio: OK". Well, at least I finally have an explicit statement from the system that there's a problem.
*Okay, now we know you're a psychic. Along with that Firefox message was a button for more info. I clicked and it went to a webpage which basically said the same thing in more detail and with a link (allegedly) to more info, https://support.mozilla.org/t5/Videos-sound-pictures-and/Fix-common-audio-an....
**As I did a day or two ago with alsa packages, I used rpm to verify all the pulse* packages (rpm -qaVv pulseaudio*) and found that none of the files in any of the packages had been altered at all.
I'm on Centos-7.3, and when I switched from 7.2 I found that some things now are controlled by pavucontrol, and not by the volume control in the top panel (I'm using Mate, not Gnome,... Gah, how can anyone stand Gnome 3.x??) It's kind of a pain, I haven't yet found a way to localize controls for all the various audio-producing tools in one place. Does anyone know how to do that?
Sorry, I've never seen anything like that.
Does anyone know how to restart audio in systemd? That might still be worth looking into.
# systemctl list-unit-files --type=service ... alsa-restore.service static alsa-state.service static alsa-store.service static ...
The above command showed the three alsa services, but nothing for the other audio software I've been poking around in: pulseaudio, jack, oss. Nor did I see anything else listed which told me it had anything directly to do with the system's audio. Moreover, I don't have alsa running as a daemon. So unless I'm misunderstanding what systemd does, I don't think it's playing a role in my sound problems.
Before doing audacity, I tried gnome's mplayer. Geez, is that a stinky pile of code. Just selecting a directory where a file could be selected ended up locking up the app; I had to do a kill to get it off my screen. Does that actually work for anyone? If so, what kind of files or net locations does it work for?
Thanks once more for your thoughtful suggestions.
-
Alice Wonder -
Barry Brimer -
Fred Smith -
Kay Schenk -
ken