SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I managed to get Slackware -current to run on a very recent Acer Aspire E17 laptop. So far, things look good. Disabling Secure Boot and switching to Legacy Boot worked, the gdisk + LILO combination works, video works (see previous thread), wired and wireless networking works.
Now I'm trying to configure sound, since I don't have any. Here's what I have.
# aplay /usr/share/sounds/alsa/*.wav
ALSA lib pcm_dmix.c:1029:(snd_pcm_dmix_open) unable to open slave
aplay: main:722: audio open error: No such file or directory
I tried the "magic fix" by editing /etc/modprobe.d/snd-hda-intel.conf:
Glad that you found a solution already. If you like, however, you might also try another approach: Just start alsamixer as a normal user in a terminal, select your audio device (F6) and check, if the master channel is muted. In my system this is always the case after booting, so bumping up the volume in alsamixer is not a permanent solution, other than the one suggested by kkady32, but it still works (here, at least). Therefore I'll have to go through the above mentioned steps every time I boot my system. Not a big deal though, and certainly weighed up by the advantages of having PulseAudio in Slackware, now, IMHO.
In my system this is always the case after booting, so bumping up the volume in alsamixer is not a permanent solution, other than the one suggested by kkady32, but it still works (here, at least). Therefore I'll have to go through the above mentioned steps every time I boot my system.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.