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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
With your help, I've solved this problem. See below. I've also provided answers to your questions. Might be useful to someone else with the same problem.
The trick is to create the file /etc/modprobe.d/sound.conf containing the line:
options snd-hda-intel model=auto
This Slackware installation replaced an Arch install that I did when I built this machine in May. I never had any problems with sound. Before installing Slackware, I tar'ed /etc and just checked it -- nothing in /etc/modprobe.d. Why this is a problem in Slackware and not Arch on the same hardware is a bit of a mystery (yes, different kernel version, but the alsa package versions look to be the same in Arch and Slackware 14).
Anyway, thanks very much for your help in getting this resolved.
I built the machine myself. Motherboard is a GIGABYTE AM3+ NVIDIA GeForce 7025/nForce 630a Chipset DDR3 1600 Micro ATX AMD Motherboard GA-M68MT-S2. AMD Athlon II X2 250 processor. 4 GB DDR3 memory. 500 Gb 7200 rpm SATA drive. See lspci output in my original post for other hardware details.
Distribution: Slackware64 14.2 with AlienBob's KDE5
Posts: 270
Rep:
Quote:
Originally Posted by lee88abc
I have another audio problem.
I can play mpg123 myfile.mp3 on the black console.
But when I start up runmode 4 gui and kde starts. Then I get error saying audio device not work falling back to default.
Running as root, I can play audio in kde.
Make sure your user is in the audio group. Maybe plugdev too, I can't remember. If you chose the default groups when creating the user, those should have been added. Remember that you'll have to log in and then out again to get the new group list to take effect.
forgot to check back.
Thanks everyone.
In previous slackware versions I never had this problem.
In slack 14 for some reason I need to add user to audio group in passwd.
Is this a new requirement?
I've repeated the same process on physical machines and virtual machines. In each case I had to add user to audio group.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.