You are not logged in.
Pages: 1
Hi,
I have no sound on my notebook speakers... I can solve this by plug the headphones, and unplug them (then the speakers will work).
Sound card: HDA Intel PCH (is the default one in alsamixer).
lspci | grep "Audio" output:
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
Any ideas?
Offline
Hmm, alsactl restore just did the trick...
Now, other ideas? Or I just run this at every startup?
Offline
There is a systemd service that comes with alsa-utils package called alsa-restore.service. You can enable that.
Offline
I can't...
Profile 'alsa-restore.service' does not exist or is not readable
Is already enabled.
Offline
Please post:
systemctl status alsa-restore -l
Run
sudo alsactl store
with sound working and the settings you wish to store, and then try alsa-restore service again.
Last edited by emeres (2014-05-20 20:34:36)
Offline
$ systemctl status alsa-restore -l
● alsa-restore.service - Restore Sound Card State
Loaded: loaded (/usr/lib/systemd/system/alsa-restore.service; static)
Active: inactive (dead) since Tue 2014-05-20 10:50:52 UTC; 1h 34min ago
Main PID: 1008 (code=exited, status=0/SUCCESS)
And after sudo alsactl store The: sudo netctl enable alsa-restore.service command gives me the same error: Profile 'alsa-restore.service' does not exist or is not readable
Offline
Why do you use netctl? You should use systemctl, like this:
sudo systemctl enable alsa-restore.service
sudo systemctl start alsa-restore.service
sudo systemctl status alsa-restore.service -l
You should be able to store settings using alsa-store.service:
sudo systemctl start alsa-store.service
Last edited by emeres (2014-05-20 21:45:58)
Offline
Yep, It was my mistake, sorry. Now this in the output:
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, ...).
Last edited by mariuss (2014-05-20 21:48:37)
Offline
Right, it does not have an [Install] section, but it is enabled by default, you should have symlinks in basic.target for both services.
ls -al /usr/lib/systemd/system/basic.target.wants
Run the rest of the code I suggested, then reboot see if it gets run and you have sound from speakers.
Offline
Pages: 1