Poof! alsaconf is gone... So what should we bear in mind now?
Well it's only been sixteen days now so I don't feel too bad about discovering the hard way that alsaconf was removed.
While performing a post install config of a fresh Slackware -current on my daughter's new laptop, I was taken aback when it came time to activate/config her sound. No probs, just did an alsamixer and an alsactl store after consulting 10 Sep's changelog on my personal mirror here. But then I thought, well what should I be considering, or paying attention to moving forward, now that alsaconf has been removed. Your thoughts? Suggestions? Kindest regards, . |
Code:
alsactl init |
Without your post I wouldn't even have noticed, I never had to use it. From the changelog when it was removed:
Quote:
|
From what I've seen alsaconf is useless in 13.37, so I am not surprised that it was removed. I just did what you did, 'alsamixer' then 'alsactl store'.
|
Alsaconf creates the default sound.conf file in /etc/modprobe.d to ensure modules are loaded correctly so that alsactl doesn't have hiccups restoring proper audio volume levels and that modules for the OSS emulation portion work properly and are loaded.
You can easily create the file yourself if alsactl has trouble restoring audio levels at boot. Example using an SBLive with the SFXLoad and the Creative SoundFont package: Code:
# ALSA portion |
All times are GMT -5. The time now is 10:05 AM. |