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.
Just installed Debian 3.1 on a Dell Inspiron 4150 laptop. Everything went well despite all the horror stores I had read while lurking the forums. Only problem I am having is that I have to run the "alsaconf" command in a terminal everytime I reboot for sound to work.
I think that I have read somewhere around here about there being a conflict with my modem sound. Not really sure though, I browse thru here so much I may be mistaking, and I just cant seem to find that post again.
Location: 1st hop-NYC/NewJersey shore,north....2nd hop-upstate....3rd hop-texas...4th hop-southdakota(sturgis)...5th hop-san diego.....6th hop-atlantic ocean! Final hop-resting in dreamland dreamwalking and meeting new people from past lives...gd' night.
Distribution: Siduction, the only way to do Debian Unstable
Posts: 506
Rep:
You mentioned that you can get sound to work after alsaconf on every boot.
Ok,get your sound working.
Set up the mixer to your likeing.
Once all is fine use the
alsactl store
command to save everything and have it there for next boot.
If it doesn't work you may need to be root...I dont remember.
Are u sure after alsaconf sound not working?after alsaconf alsactl store reboot.try right click xmms->preferences/options/alsa/oss/esd .try changing these three options and try playing any song.if not did u compiled custom kernel and forgot any modules?
Are u sure after alsaconf sound not working?after alsaconf alsactl store reboot.
Maybe I didnt ask the question properly. My sound works perfectly after I run alsaconf. But once I shutdown my machine and power it back up, I have to run alsaconf all over again. Running alsactl store after alsaconf does not save my settings, and again after I shutdown my machine and power it back up, I am going thru the same process to get my sound back up.
I loaded the default Kernel (2.4.27) from the Debian 3.1 Sarge Official DVD set, and have not recompliled my Kernel. I have googled this and searched this forumn but I have not found anyone with a similar problem. Anyone else have and suggestions?
Just wondering if you worked this out? DId a search here and found this thread.
I'm having the same problem, using Debian-testing, alsa and kernel 2.6.12.3. No sound on reboot, rerun alsaconf, alsactl store, and sound works, reboot, no sound, run alsaconf, alsactl store, sound works again... etc.
Negative. Nothing here has worked out. I have googled - searched - and pulled my hair out (next step is the Library of Congress) . But nothing has helped. Was just trying again actually when I saw your post. Maybe someone else will reply.
Anyone else have any suggestions. At least I am not the only one with a problem.
I just got it worked out...
I had a couple of OSS modules that conflicted with alsa, apparently. Removed them, rebooted, alsa works perfectly.
I compared the output of lsmod before and after running alsaconf, found the two modules in question and removed them in xconfig.
Xconfig is just an easy GUI for configuring a kernel... you can use 'make oldconfig' or 'make config' or whatever... It's pretty straightforward if you are familiar with compiling kernels. I compile kernels in /usr/src/ .
This is how I accomplish this, your mileage may vary:
As root, cd to /usr/src/linux, (a sym-link to the kernel, in my case /usr/src/linux-2.6.12.3), enter 'make xconfig', find the modules in question and remove them, exit and save xconfig, enter 'make modules', enter 'make modules_install' and reboot.
Hope that's not more info than you need, good luck.
netcrawl
I'll have to try this. It seems semi-related to a problem I'm having an posted in another thread. Sound only works for me in KDE, not any other Window Manager. It's pretty bizzare. I'll reply here if I get it to work.
I, too, have this problem (MEPIS 3.3.1). I think its due to my having two sound cards: an onboard and a PCI (which is the one I want to use).
I will try "alsactl store," but I am wondering if there is something else here? OSS causes some people problems, huh? (Will we ever be moving away from that?)
I just had the same problem as documented here. For me, though, it was not a case of OSS modules loaded.
In my case, the snd_sbawe driver was not loading. So, when alsa ran as part of init, it would immediately fail, as /proc/asound did not exist. The solution was easy:
add snd_sbawe to /etc/modules. Hopefully this tidbit will be useful to someone else.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.