You are not logged in.
Hello,
I just installed arch in this machine and I cannot get sound to function properly.
I have tried using alsactl store but it does no good. After every reboot I need to turn the volume up on the speaker channel within alsa.
Another related note, alsaconf does not exist. A lot of the solutions that I have found involve running that command but it does not exist.
I have install both alsa-lib and asla-utils but alsaconf still does not exist.
Any help would be much appreciated, Thanks. ![]()
Offline
I'm not sure if I can be a lot of help here, but if you link to some of those suspected alsaconf solutions, I may be able to help convert them into what should go in your asoundrc. Alsaconf is just a tool to write asoundrc (I think)... a text editor is a better tool.
Last edited by Trilby (2013-06-05 22:43:19)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Hi,
alsaconf was removed from alsa-utils more than a year ago (see here). You can enable automatic storing/restoring of mixer levels by activating the systemd services
# systemctl enable alsa-store.service
# systemctl enable alsa-restore.serviceor issue alsactl store/restore manually.
Last edited by masutu (2013-06-07 01:27:08)
Offline
Ok so I gave that a shot here is the output:
[john@goldfish ~]$ sudo systemctl enable alsa-store.service
[sudo] password for john:
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, ...).
[john@goldfish ~]$ sudo systemctl enable alsa-restore.service
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, ...).
[john@goldfish ~]$ Offline
Yes, my fault, both services should be enabled by default (see here). For me this is true:
#systemctl list-unit-files --type=service | grep alsa
alsa-restore.service static
alsa-state.service static
alsa-store.service staticSorry for the noise...
Offline
For me it is also true.
[john@goldfish ~]$ systemctl list-unit-files --type=service | grep alsa
alsa-restore.service static
alsa-state.service static
alsa-store.service static As is stands, all I have to do to restore my sound when I boot up is "sudo alsactl restore"
I was thinking I could just throw it into startup script or something but I feel like there should be a less round-a-bout solution.
Offline
Ok so here is some more information:
When I bring up alsamixer, is displays on the master channel. I have to press f6 and select HDA Intel PCH.
The sound state of the master channel does get saved and restored but the sound state of the HDA Intel PCH channels are not getting saved and restored.
HDA Intel PCH is set to 0 which makes it the default sound card correct?
Offline
the card that is deplayed by default when I go into alsamixer is labeled as PulseAudio. Shouldn't it be defualting to HDA Intel PCH?
Offline