DebianThis forum is for the discussion of Debian 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.
Distribution: debian sarge, 2.6.6, and ALSA finally works!!
Posts: 18
Rep:
Hi One ManArmy
I've been trying to get Alsa to work on my Debian set-up for ages. I recently updated to sarge and installed the 2.6.6 kernel, expecting Alsa to work, but nothing!!
I have gone through similar situation to yourself, run alsaconf etc. Becuase I am running 2.6 kernel I know the drivers are there. My modprobe.conf is full of Alsa settings, and still nothing.
But then....... I read this thread and followed the link recommened by zajelo3.
I thought that all my OSS drivers were removed, they weren't.
My /etc/modules file needed modifying to remove the 'sound' entry and the entry for my spoundcard 'in my case ens1371' : Here is my /etc/modules file
Code:
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.
usb-ohci
input
usbkbd
keybdev
#es1371 to remove the oss driver soundcard
#sound to remove the oss drivers
parport
mousedev
psmouse
ne2k-pci
I rebooted and hey presto, alsa is working straight away. Just type alsamixer to get a mixer up, unmute the channels and I have sound-sweet-sound piping from my computer.
So, there is hope, and zajelo3 - thank you very much, I've been scratching my head on this for ages.
Guess what gaffel?
It was the same exact problem as yours and solved exactly as you said.
Actually,I knew I had to comment the sound modules in the /etc/modules
file to avoid loading them on bootin. But The problem is that the trident
module was surounded with commented stuff which gave me the
illusion that it was commented as well .
I commented the trident module,rebooted and ......off u go
The trident module didn't show up when booting and it said like
it was black listed or something.
Anywayz.........thanx 4 u all for your help.
This forum rocks
Last edited by OneManArmy; 07-26-2004 at 06:12 PM.
1) Removed *all* sound related modules
2) Used modconf to add soundcore module
3) Ran alsaconf
Here;s what happened
1) alsaconf detected my ens1371 sound card
2) alsaconf said it had configured my soundcard properly
3) alsa said this:
Running update-modules...
Loading driver...
Restoring ALSA mixer settings ... failed:
You may want to run 'alsactl restore' manually to view any errors.
Setting default volumes...
I've tried *everything* but I *always* get this error message (for months now).
root@370[kdewebdev]# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a `#', and everything on the line after them are ignored.
apm
apm
soundcore
root@370[kdewebdev]#
looks quite empty ! Anyway, I think you need to install (using modconf)
the "snd" and "snd-pcm-oss" which you can find under /kernel/sound/core.
As far as I remember, ALSA uses some OSS emulation stuff so it needs
that "snd-pcm-oss" module.
Hope this helps.
The weird thing is, those modules are already installed -- I think running alsaconf did that. So does anyone know why these things don't appear in my /etc/modules? While we're at it, how come I've got 'apm' listed twice?
I'm still no closer to getting alsa working though :-(
Good to see you have sound now. I totally missed the sound card module not being loaded. Next time I'll look at my set up closer. But don't feel bad, there's a lot of talk on the alsa-user mailing list about how hard it is to get alsa going on the 2.6 kernel, and most of those guys are professionals. Most of them are still using the 2.4 kernel, as the 2.6 kernel is just now getting up to the specifications that they need for professional audio work.
I used to be a sound engineer back in NYC and as much as I love using Linux for my day to day desktop, I frankly can't imagine using anything other than a Mac in the recording studio simply because these kinds of issues *practically never* happen on a Mac and every minute of studio downtime is insanely expensive.
I can just imagine telling the producer, the asst. engineers, the band -- "hey y'all? uhh... this might take a while. I think I'm gonna have to recompile my kernel for alsa... tick-tock... tick-tock..." :-)
Anyway, I'm really curious... are there any pro audio guys out there really using Linux in the studio?
Yes there are pro's using Linux for pro-audio. But your concerns are well founded, because Linux as a pro-audio tool, be it at a live gig or in the recording studio, is still in its infancy. Most of the apps are still beta, and the coders that write the programs are so busy, that they really don't have time to keep the documentation up to date. If your serious about use Linux in pro audio the best thing to do is to subscribe to the "linux-audio-users@music.columbia.edu" list and just jump in and get your feet wet. There is a thread going right now about the sad state of documentation for Linux audio apps and one thought was, just as you said, that you really can't ask professional's to wait while you get something working (or read the doc's) that should already be working. Another question linux pro audio users are asking is "Are Linux pro audio applications always going to be by geeks for geeks?", in other words "What will it take to get to the point where a regular pro-audio person can just use a app and not have to be a computer programmer?" Alot of the people on the list use Linux in conjunction with other OS'es because they realize that the Linux pro audio scene is just starting. It is fun to watch it as it progresses, but it's not ready to replace your mac just yet.
Hi all,
I have been having problems with ALSA too. Everything worked fine until a few weeks ago my sound stopped working.
I have checked most fora but couldn't find a solution.
The problem seems to be that alsa only loads the 'snd' module, but not all the others up to snd_cmipci. When I load snd_cmipci manually everything works fine and a workaround is to put it in /etc/modules. I never had to do this though and I think the loading of snd should in turn load other modules too.
Before I posted here, I had modutils and module-init-tools both, but now I only have module-init-tools.
Any ideas?
Regards, Matthijs.
PS. Oddly /etc/modprobe.conf is empty, is this right?
beast:~# cat /etc/modprobe.d/sound
alias snd-card-0 snd-cmipci
alias sound-slot-0 snd-cmipci
beast:~# cat /etc/modprobe.conf
beast:~# cat /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file should contain the names of kernel modules that are
# to be loaded at boot time, one per line. Comments begin with
# a "#", and everything on the line after them are ignored.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.