Slackware 10.1 Kernel 2.6.10 sound problem.

landfill · 02-12-2005, 09:17 AM

Hi,
I'm having trouble getting my sound working after installing Slackware 10.1.
I upgraded the kernel to 2.6.10 (provided on the cd), but the sound didn't work with the original 2.4 either.
I have uninstalled and reinstalled alsa, and many other things.
My sound 'card' is an onboard device, which I believe is os the via82xx type.
My lspci output regarding the sound card is below:

Code:

0:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235/8237 AC97 Audio Controller (rev 50)

When I run alsaconf, It doesn't find any devices and when i run alsamixer it returns "alsamixer: function snd_ctl_open failed for
default: No such file or directory."

Help much appreciated!
L.

/bin/bash · 02-12-2005, 09:33 AM

Did you install the alsa-modules? They come separate from the other kernel modules, I don't know why.

Look in /lib/modules/2.6.10/kernel/sound and if all you have is soundcore then you don't have the alsa modules installed. Also you can do this:
lsmod|grep snd
Check for the module snd-via82xx. If you don't have it listed try to modprobe it. If that doesn't work then you probably need to install the alsa-driver package, you'll find it HERE

landfill · 02-12-2005, 09:44 AM

Aahh, yes, I only have soundcore.ko and modprobe doesn't find that module. I thouhg I already installed alsa-drivers but I'll try again. Cheers!

landfill · 02-12-2005, 10:03 AM

Ok, so I've instaled alsa-driver and now I have a lot more modules. Alsaconfig and alsamixer both work well now, and my card is detected. However, when I try to play an mp3 in xmms, I can't hear any sound. My sound isn't muted in alsamixer of anything. Any suggestions?

rhoyerboat · 02-12-2005, 05:13 PM

try hitting ctrl-p in XMMS and configuring the output plugin to libalsa*.so*.-whatever
check to see that rather then default, xmms has been using your soundcard as an output device

also i heard a rumor that mp3 support has been taken out of xmms and you need to install another plugin to make it work, but im having such serious soundcard issues myself right now that i cant sustain or dismiss this particular rumor

while were in the thread: i need to pass some arguments to modules being loaded, i also use slackware 10(.0 i think) and have one of those Neomagic 256audio/video units with 2 megs of ram

the modules are loading error free automatically but even short .wav files trigger a buffer overrun erro in snd_pcm_mmap_close .. .

i want to pass certain memory restrictions to my drivers but they are loading before i can do it manually. i cant find the autoload code in rc.d but maybe i just dont know where the rc scripts are getting their variable input from

landfill · 02-13-2005, 04:35 AM

Yep, I'd tried that before, but It didn't change anything.
Thanks anyway

/bin/bash · 02-14-2005, 04:29 AM

Does any sound work? Do you have a cd? If so can you play audio cd's.
Try just using aplay;
aplay song.mp3
aplay sound.wav

/bin/bash · 02-14-2005, 04:38 AM

rhoyerboat

You usually put module options in /etc/modules.conf or /etc/modprobe.conf files.

Try modinfo <module> this will tell you which options you can pass to the module. Then man modules.conf or man modprobe.conf But it is basically in this form:

options modulename option...

rhoyerboat · 02-15-2005, 04:22 AM

okey dokey thanks. ive been a monolythic type since day one. anyway: what i need now is a command line mp3 player(edited because i noticed i had one, though there -is- still some random noise in the output), getting the buffer_top in there seems to have enabled me to play and record, although 41k khz has a weird skip in it, ive decided that i do not need this rate. whats aggravating me is that xmms is crashing at the same address again. ive found some code in snd-nm256.c that interests me because a commented line comments that this code will crash a dell latittude laptop, a patch i found somewhere would delete the line, but it was already commented and replaced with something with a smaller address..

heres the code:

nm256_writePort8 (card, 2, 0x6c0, 1);
/* nm256_writePort8 (card, 2, 0x6cc, 0x87); crashes dell lattitude */
nm256_writePort8 (card, 2, 0x6cc, 0x80);
nm256_writePort8(card, 2, 0x6cc, 0x0);

its weird to me because its the same function called three times with different values.. im also wondering if there are implied integers after 0x, if there are then 0x80 would be a top address, if not, its the bottom.. i suppose this is important although this has become my first acrual debugging project.. anyway.. thanks for the modprobe stuff im gona go see if another X driven audio program crashes me too

pax

hmm second edit since i found mpg123:

lots of random noise in console mode, switch to X and it clarifies instantly, then alsa registers a few overruns as i swap windows within X ..