[arch-general] Sound problems
Good evening, I'm having troubles getting sound to work aftereach reboot. I've followed the instructions from the wiki. But after each reboot I need to run alsamixer -> selct the soundcard by pressing F6 -> and then have to increase the volume of the speaker. When invoking systemctl enable alsa-restore.service and systemctl enable alsa-store.service I do get the following error messsage: The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). ... and it starts from the beginning after the next reboot. BTW it doesn't help when I change the settings in /etc/asound.conf from pulseaudio to the hw device. Thanks for any help Frank
On Thu, Jan 31, 2013 at 6:35 PM, Frank Zimmermann < frank.zimmermann.berlin@freenet.de> wrote:
Good evening,
Hey!
I'm having troubles getting sound to work aftereach reboot. I've followed the instructions from the wiki. But after each reboot I need to run alsamixer -> selct the soundcard by pressing F6 -> and then have to increase the volume of the speaker. When invoking systemctl enable alsa-restore.service and systemctl enable alsa-store.service I do get the following error messsage:
The unit files have no [Install] section. They are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: 1) A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. 2) A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. 3) A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). ... and it starts from the beginning after the next reboot.
That's correct, these systemd's units provided by the alsa-util package aren't meant to be manually enabled or disabled; if I'm not mistaken, they are statically linked to sysinit.target - anyone who knows better how these ALSA units works is welcome to step in :) All that do the alsa-store.service is invoke the alsactl command to save your settings, try running it from console: # /usr/sbin/alsactl store
BTW it doesn't help when I change the settings in /etc/asound.conf from pulseaudio to the hw device.
So you've installed PulseAudio, may be the problem is related with PA then. Check carefully the PA wiki and if you can't find where the problem resides you will need to make some debug; the first step shall be uninstall PA and check that ALSA's systemd units are working right, then you can try reins- talling PA and looking carefully for any change you do to config files. Thanks for any help
Frank
Good luck :)
Am Donnerstag, den 31.01.2013, 21:23 -0300 schrieb Martín Cigorraga:
Hey!
Hi
All that do the alsa-store.service is invoke the alsactl command to save your settings, try running it from console: # /usr/sbin/alsactl store shouldn't this keep the settings for the speaker? In my case it doesn't
So you've installed PulseAudio, may be the problem is related with PA then. comes with Gnome Check carefully the PA wiki and if you can't find where the problem resides you will need to make some debug; the first step shall be uninstall PA and check that ALSA's systemd units are working right, then you can try reins- talling PA and looking carefully for any change you do to config files. I'll check Pulseaudio and see where it'll brings me.
KR Frank
On Fri, Feb 1, 2013 at 8:00 PM, Frank Zimmermann < frank.zimmermann.berlin@freenet.de> wrote:
Am Donnerstag, den 31.01.2013, 21:23 -0300 schrieb Martín Cigorraga:
# /usr/sbin/alsactl store shouldn't this keep the settings for the speaker? In my case it doesn't
Yes, of course, that's the purpose of that command.
So you've installed PulseAudio, may be the problem is related with PA
then. comes with Gnome
Check carefully the PA wiki and if you can't find where the problem resides you will need to make some debug; the first step shall be uninstall PA and check that ALSA's systemd units are working right, then you can try reins- talling PA and looking carefully for any change you do to config files. I'll check Pulseaudio and see where it'll brings me.
KR Frank
There are two things that come to my mind right now: 1) have present that some of the sound settings you can change with alsamixer depends on other settings. For example it is totally worthless to set the Master channel to it's maximum if PCM channel is muted. 2) because you use PA (well, you use GNOME but it triggers the PA installation) it may be worth to take a look at the various PA mixers found in the official repositories and in the AUR. I also found these threads related to your issue in the forums - it might be more to check: https://bbs.archlinux.org/viewtopic.php?id=69853 https://bbs.archlinux.org/viewtopic.php?id=37217 Cheers!
2013/2/2 Martín Cigorraga <msx@archlinux.us>
On Fri, Feb 1, 2013 at 8:00 PM, Frank Zimmermann < frank.zimmermann.berlin@freenet.de> wrote:
Am Donnerstag, den 31.01.2013, 21:23 -0300 schrieb Martín Cigorraga:
# /usr/sbin/alsactl store shouldn't this keep the settings for the speaker? In my case it doesn't
Yes, of course, that's the purpose of that command.
So you've installed PulseAudio, may be the problem is related with PA
then. comes with Gnome
Check carefully the PA wiki and if you can't find where the problem resides you will need to make some debug; the first step shall be uninstall PA and check that ALSA's systemd units are working right, then you can try reins- talling PA and looking carefully for any change you do to config files. I'll check Pulseaudio and see where it'll brings me.
KR Frank
There are two things that come to my mind right now: 1) have present that some of the sound settings you can change with alsamixer depends on other settings. For example it is totally worthless to set the Master channel to it's maximum if PCM channel is muted. 2) because you use PA (well, you use GNOME but it triggers the PA installation) it may be worth to take a look at the various PA mixers found in the official repositories and in the AUR.
I also found these threads related to your issue in the forums - it might be more to check: https://bbs.archlinux.org/viewtopic.php?id=69853 https://bbs.archlinux.org/viewtopic.php?id=37217
Cheers!
Try finding the program mentioned here[1], and change the default output device. [1]: http://ubuntuforums.org/showthread.php?t=772673#2 Regards, -- Leonardo Dagnino
Am Freitag, den 01.02.2013, 23:10 -0300 schrieb Martín Cigorraga:
# /usr/sbin/alsactl store shouldn't this keep the settings for the speaker? In my case it doesn't
Yes, of course, that's the purpose of that command.
We'lllooks like it doesn't. I've changed the settings in /etc/asound.conf from Pulseaudio tom my hw-device and still canot save settings.
There are two things that come to my mind right now: 1) have present that some of the sound settings you can change with alsamixer depends on other settings. For example it is totally worthless to set the Master channel to it's maximum if PCM channel is muted.
unmuted
2) because you use PA (well, you use GNOME but it triggers the PA installation) it may be worth to take a look at the various PA mixers found in the official repositories and in the AUR.
haven't tried em all, yet but will continue to do so. KR Frank
On Sun, Feb 3, 2013 at 6:26 PM, Frank Zimmermann < frank.zimmermann.berlin@freenet.de> wrote:
We'lllooks like it doesn't. I've changed the settings in /etc/asound.conf from Pulseaudio tom my hw-device and still canot save settings.
Have you tried running alsa-conf? (as root). What's your HW? $ lspci | grep -i audio
Am Sonntag, den 03.02.2013, 22:33 -0300 schrieb Martín Cigorraga:
Have you tried running alsa-conf? (as root). which package provides this? What's your HW? $ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) KR Frank
On 6 February 2013 16:33, Frank Zimmermann < frank.zimmermann.berlin@freenet.de> wrote:
Am Sonntag, den 03.02.2013, 22:33 -0300 schrieb Martín Cigorraga:
Have you tried running alsa-conf? (as root). which package provides this?
It was ditched: https://bugs.archlinux.org/task/28631 Chris
On Wed, Feb 6, 2013 at 8:09 AM, Chris Down <chris@chrisdown.name> wrote:
It was ditched: https://bugs.archlinux.org/task/28631
Chris
Oops, didn't had the slightest idea, thanks for pointing that out!
Am Sonntag, den 03.02.2013, 21:26 +0000 schrieb Frank Zimmermann:
Am Freitag, den 01.02.2013, 23:10 -0300 schrieb Martín Cigorraga:
# /usr/sbin/alsactl store shouldn't this keep the settings for the speaker? In my case it doesn't
Yes, of course, that's the purpose of that command.
We'lllooks like it doesn't. I've changed the settings in /etc/asound.conf from Pulseaudio tom my hw-device and still canot save settings.
There are two things that come to my mind right now: 1) have present that some of the sound settings you can change with alsamixer depends on other settings. For example it is totally worthless to set the Master channel to it's maximum if PCM channel is muted.
unmuted
2) because you use PA (well, you use GNOME but it triggers the PA installation) it may be worth to take a look at the various PA mixers found in the official repositories and in the AUR.
haven't tried em all, yet but will continue to do so. KR Frank
I think I got it:-) alsa-restore.service is not run at boot. When I set the sound in alsamixer, save it with alsactl store and reboot followed by manually executing sudo systemctl start alsa-restore.service the settings are correct. Now I need to figure out why it's not done automagicaly at boot. KR Frank
participants (4)
-
Chris Down
-
Frank Zimmermann
-
Leonardo Dagnino
-
Martín Cigorraga