LinuxQuestions.org
Did you know LQ has a Linux Hardware Compatibility List?
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices

Reply
 
Search this Thread
Old 05-12-2006, 01:03 AM   #1
Zaskar
Member
 
Registered: Feb 2004
Location: NY
Distribution: Debian (Testing)
Posts: 219

Rep: Reputation: 30
Slack "Current" Alsa Sound Config


Ok i got Slack 10.2 running and updates with the "Current" repos and it got the new Alsa also.

i had alsa configured before (on 10.2 standard) and it found the onboard sound and it worked fine. then i reformatted to play around with a clean slate and updated to "current" and now the new Alsa doesnt even find the device, any ideas?
 
Old 05-12-2006, 10:40 AM   #2
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Rep: Reputation: 45
Is sound support and your device compiled as a modules in the kernel? If you are running 2.6.x kernel, did you install the alsa-driver from the testing/linux-2.6* directory? If you still can not get it working, please post the output of 'lsusb' and any text reported by 'alsaconf'.

regards,
...drkstr
 
Old 05-12-2006, 10:49 AM   #3
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,562

Rep: Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394
ALSA only works if you're running the kernel that it's built against. If you've installed ALSA from "current" then you also need to switch to the kernel from "current".
 
Old 05-12-2006, 10:53 AM   #4
theoffset
Member
 
Registered: Aug 2005
Location: Guadalajara, Jal, Mexico
Distribution: Slackware Linux
Posts: 211

Rep: Reputation: 30
Alsa (the modules), along with the kernel is one of those things which you should avoid to upgrade. It's usually recomended to make a custom kernel and stick with that.

The Alsa libs/tools should also be kept the same that what your kernel is using. That means that, unless you do upgrade your Kernel to the one in current, and the alsa modules, you'd have to upgrade alsa from source.

The ways to deal with this is:

If you want to use Slackware's
Do download the -current Kernel package (and its modules package) and alsa modules, libs, utils.
Do a manual install of the Kernel (move the image to /boot, edit /etc/lilo.conf, run lilo) install the kernel modules and the alsa modules
Restart the system and run the new kernel, to make sure it'll work on your system.
Do install the alsa libs, and utils.

If you want to use a custom kernel (which is recomended anyway):
You Could download the kernel-source package instead (or download the lastest from www.kernel.org)
You Should then configure the kernel, make the kernel and modules, and install the kernel. If it's a 2.6.x you Could enable Alsa from there and forget the Alsa-modules packages.
If you're using the kernel-source package, you could then install Alsa related stuff, otherwize you either compiled alsa with the kernel or go to www.alsa-project.com and download all of Alsa and compile it by your self (make sure to remove the packages before).

Both metods usually work (I've done them, both). The last one is IMO better, because you use a custom compiled kernel, and you could enable the alsa within the kernel and forget about keeping the alsa-modules package (which may end up breaking stuff).

Also, the lastest -current, because of changes to udev and hotplug, runs better using a 2.6.16.x kernel (or a 2.4.x).
 
Old 05-12-2006, 11:55 AM   #5
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Rep: Reputation: 45
Yes, you need to enable alsa support in the kernel as a module (should be enabled by default). In addition, you need the packages alsa-driver, alsa-lib, and alsa-utils. The alsa-driver package is different for the 2.4.x and 2.6.x kernel, you will need to pick the right one (does not matter what 'x' is). alsa-lib and alsa-utils are not kernel specific.

regards,
...drkstr

**edit**
FYI, for alsaconf to work, your sound device must be enable in the kernel as a module. The main "sound support" or 'soundcore' must also be enabled as a module instead of hard coded to prevent confilcts with the sound device module. I belive it is not set as a module by default so you will need to change this.
**edit**

Last edited by drkstr; 05-12-2006 at 12:00 PM.
 
Old 05-12-2006, 12:34 PM   #6
dugan
Senior Member
 
Registered: Nov 2003
Location: Canada
Distribution: distro hopper
Posts: 4,562

Rep: Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394Reputation: 1394
You don't install alsa-driver if you've enabled ALSA in the kernel!

If you're building a custom kernel, then you have two options:

a) leave ALSA disabled in the kernel and then install the alsa-driver tarball that you download from alsa-project.org. Slackware provides SlackBuild scripts (in the source directory) to automate this.

This is how ALSA is set up by default in Slackware.

OR

b) Enable ALSA in the kernel.

You don't do both.
 
Old 05-12-2006, 01:03 PM   #7
drkstr
Senior Member
 
Registered: Feb 2006
Location: Seattle, WA: USA
Distribution: Slackware 11.0
Posts: 1,191

Rep: Reputation: 45
I'm sorry, I should have been more specific. The alsa driver will install modules as well as some useful headers in /usr/include/sound which I don't belive are provided by the kernel. The actual alsa modules that get loaded are the ones from the kernel compile. If you are short on disk space, you can delete the modules that alsa-driver installs at /lib/modules/<alsa-driver version> but it makes no difference since they are not actually loaded.

regards,
...drkstr

Last edited by drkstr; 05-12-2006 at 01:07 PM.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
ALSA "locks" sound only one program at a time slackwarefan Linux - Software 13 12-27-2006 11:34 AM
[B]"wireless network" config from "system" hangs[/B] dauphinfay Ubuntu 0 03-04-2006 03:16 PM
Getting error: "ALSA device "default" is already in use by another program." brynjarh Debian 7 02-04-2005 11:45 AM
"make config" with current kernel arimus25 Linux - Software 1 03-08-2004 06:26 PM
Does "ac97 & RH8" imply "buy a Sound Blaster Live"? nicktoop Linux - Hardware 3 02-13-2004 08:53 AM


All times are GMT -5. The time now is 08:53 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration