Indeed, and it could also be said that the willingness of people to follow the crowd without thinking about who they're following is quite astounding. How many people just use Ubuntu because their friends and family are using it, and not questioning its pros and cons? (Or maybe they're just not interested in computers enough to care to answer those questions). I think that's why I like Slackware so much; Pat V. puts out a simple, robust distro, but in order to administer it effectively, it forces me to think, read, and implement, not just blindly rely on others' efforts. Others may see it differently, but this is my philosophy of why I use Slackware.

Every time i reboot, my headphones are getting turned off in mixer. How to fix it? Thanks in advance for the fix.

PS: now i begin to understand, why people wanted Lennart Poettering dead. O_O

Perhaps we should not go there. Just my . Back on topic. I've been running Beta 1 on all of my machines and I'm impressed.
Slackware 14.2 is going to be a stellar release.

4 members found this post helpful.

Is /etc/rc.d/rc.alsa executable? If so, it may be loading the mixer defaults that replace your previous settings. I'm still not certain if that should be executable by default, and I'm suspecting that it should not.

So, try this:

Reboot and see if your settings are retained now. Please report back, thanks!

Udev appears to have rules for doing a "alsactl restore", but there's nothing I can see to deal with the initial configuration of the mixer (i.e. when there is no asound.state file) so perhaps rc.alsa still has a purpose, but only on first-boot or after the user deletes their state file. It probably doesn't need to do the alsactl restore any more though, so might be worth commenting that out or removing it and leaving udev to do that bit.

As for the card switches being changed, pulse may do that on startup depending on what "port" it selects when running through the various "paths" in its profile-set for the card. I had a brief play with the profile-set and path files while trying to learn the ins and outs of pulse over this last week, and man is it convoluted!


P.S.
Not sure whether an alsactl store on shutdown is a good idea anymore given that pulse has a tendency to run riot over the mixer controls. I think I'll comment that bit out too. edit: nevermind, when I went to comment it out, I found the scripts don't do that any more anyway. Should have checked.

No result. It's the same. It was executable, if it matters.

I've found a quick fix to this problem, if anyone interested:

for x in `amixer controls | grep layback` ; do amixer cset "${x}" on ; done
for x in `amixer controls | grep layback` ; do amixer cset "${x}" 70% ; done


It unmutes all devices and sets volume to 70. Kudos to the author here.

Go into the full editor and you can use % and other characters. They just aren't supported in the quick replies/edits.

1 members found this post helpful.

Thanks!

EDIT: i have found a way to fix problem with headphones being turned off after reboot. In XFCE i added a "PulseAudio Plugin" (it was added with recent updates along with PulseAudio i think). In it's settings you can control stuff related to PulseAudio. Did the trick for me.

I downloaded the DVD iso and burned it. I just couldn't wait to wipe my Slackware 14.1 and replace it with 14.2 Beta. It didn't work the first two times, of course, but if it were easy, old people would be doing it. So, I got my WiFi working with the Network Manager in KDE. Then I went for the AMD Drivers. Now X is just a blank screen. I need to reinstall the VESA Drivers, temporarily, while I figure out the AMD drivers. And I need to do it from the Command Line, since X is out until I get the Vesa drivers reinstalled. It's going to be a blast.

I'm old; I'm a Cretaceous Slacker. I hope you get your stuff sorted out. Slackware 14.2 is going to be grand.

1 members found this post helpful.

My friends call me "T-Rex", not because I am fast or have very many teeth left, it just sounds better than "Dino" and is easier to remember than "Pre-Cambrian Lifeform".

1 members found this post helpful.

Old??? We are Ancient!

A mild nod to all Kung Fu fans out there.

I'm so old I couldn't spare the time to download an iso, wipe my system, and reinstall a few times; to be certain I could finish before I got too old to do so, I just uncommented a -current mirror and updated.

Recall the poll here on LQ a few years ago regarding the age of poll repondents using Slackware? [1][2]

[1] http://www.linuxquestions.org/questi...re-4175473149/
[2] http://www.linuxquestions.org/questi...ts&pollid=2097

Unfortunately I am now getting speaker pops since PulseAudio has been introduced. It seems to only happen with system event sounds; emptying trash etc.

It didn't bother me so much at first but now it is just getting irritating and I am afraid that it is going to damage my speakers.

I have tried to delete the asound.conf and restart alsa but this has not helped. I had seen another post that had more info about how to revert back to alsa but I cannot find it now. I don't want to recompile a bunch of packages, I don't care if PA is in my PC, I just want to stop it from making my speakers pop.

This is what lspci is outputting as my audio device:

00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 02)

Any help would be appreciated.

I've run into this issue before. I'm not sure if I fixed it doing this, but it's worth the try.

As root, edit:
Look for:
and change it to:
Either restart pulseaudio or log out and log back in. See if that helps.

1 members found this post helpful.