Hallo, Laura Conrad hat gesagt: // Laura Conrad wrote: You're running the OSS drivers. You don't want to do this. Some ways out include: 1) You follow Tim's advice to install the AGNUlA kernel. 2) You install kernel 2.6 which includes ALSA. (It's what I do, although I always compile my own kernel.) 3) you build your own kernel as well. 4) You stay with Debian's packages and install the package "alsa-modules" which matches your installed kernel package. apt-get will take care that the right one gets installed. I would recommend to do 4) first, its the easiest way. "apt-cache search alsa-modules " shows the available packages, "dpkg -l kernel-image\* " will show what kernel package you are running. You can probably reuse your old alsa configuration with the new kernel. Ciao -- Frank Barknecht _ ______footils.org__

Thanks to everyone who wrote with helpful advice. I have tried most of the suggestions, and am still getting no sound. First I got the agnula kernel. I used the advice at <http://ccrma.stanford.edu/planetccrma/software/installkernelandsound.html#SECTION00023200000000000000> to configure the alsa implementation. When I ran that, i got no sound and no error message. I downloaded the 2.6 kernel, and got a kernel oops when I tried to reboot. I tried booting the knoppix CD, which has kernel 2.4.26 and oss, and it wouldn't play sound either. I tried booting back to 2.4.l8, and it doesn't play sound now either. I tried removing the alsa apps and going back to oss, which really used to work. It doesn't now, but it isn't clear that I really removed all the alsa stuff, although the loaded modules look like the oss ones to me. This version gives me an error message when I try to play a MIDI file: $ timidity score.midi Couldn't open output device I have some questions, none of which may be relevant, but I really need sound to work: I believe that via82cxxx_audio is the module for the soundcard that's on the motherboard, which I don't want to use. Why does it keep loading it, even though I have told the bios to turn it off? And how do I make it stop loading this module? /proc/interrupts reports that both the SB-Live and the onboard sound are sharing interrupt 9. Is this likely to be causing problems? Does anyone have any idea what changed between kernel 2.4.18, when OSS sound worked, and 2.4.25 when it doesn't? I believe the 2.6 kernel that I loaded was 2.6.7 -- is it likely that a less recent one would work better? i have checked the connections, and the speakers certainly work when I'm driving them from something other than my computer, and the computer seems to be seeing the SBLive soundcard in the normal ways, but is there any chance that something's wrong with the soundcard that just happened at the same time as I started playing kernel games? Is there anything else I should be trying? -- Laura (mailto:lconrad@laymusic.org , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139

Last Wednesday 04 August 2004 16:08, Laura Conrad was like: Oh dear :( ALSA drivers are all named snd-[something] - in your case snd-sb[something] look in /lib/modules/2.4.25-1-multimedia-686/alsa/ or any of the others, there's a directory for each kernel. This suggests that you haven't actually disabled the onboard via82cxxxx - It shouldn't be a problem if it's really not being used, but then it shouldn't show up in /proc/interrupts either in that case. I think the OSS modules were removed from the multimedia version of the kernel because they caused too much configuration confusion. They should be there in the other sets of modules. I don't know about 2.6.x kernels. Checklist: /etc/group - check you are in 'audio' group (may be 'sound' instead) /dev/dsp* /dev/mixer* /dev/cdrom* etc. - check these are set to the correct group also. [5] /etc/alsa/modutils/1.0 - check this has the right settings for the soundcard you want to use [4]. ~/.asoundrc - details at [4] again. Make sure the volume is turned up on your mixer and theoretically you should have sound. You may need to log out & back in again before these settings take effect. HTH tim hall Useful links: [0] http://www.debian.org/doc/manuals/reference/reference.en.html [1] http://www.agnula.org/download/demudi/1.2.0-FAQ [2] http://www.agnula.org/documentation/FAQ/ [3] http://d-i.alioth.debian.org/manual/en.i386/index.html [4] http://www.alsa-project.org/alsa-doc/ [5] http://kreiger.linuxgods.com/kiki/?linux+sound-permissions [6] http://www.togaware.com/linux/survivor/index.shtml

Last Thursday 05 August 2004 15:22, Laura Conrad was like: Uh, OK. That's beyond my understanding then. OK, that's a valid alsa config, but it should be in a file called '1.0', you could probably just copy this one across and run update-modules or just make a blank file and run alsaconf. Worth making one - you have to create it yourself following the instructions on the ALSA website. It's not supposed to be essential, but it probably is if you need to tell your box to use one of a choice of soundcards. I think your mixer settings are fine. No, these are harmless error messages due to the fact that you don't have pcmcia modules installed. Shouldn't make any difference AFAIK. Make a ~/.asoundrc and then reconfigure alsa and make sure it writes out to /etc/alsa/modutils/1.0 That _should_ do it. Let us know how you get on. cheers tim hall