??What??
I didn't upgrade to 10.1, I installed it from a CD.
The problem isn't with an up<i>grade</i>, it's with an up<i>date</i>. In other words, I didn't upgrade to a newer Slackware version (i don't think they even have one yet), I just installed some updated packages for the one I already had installed.

quote
Also, "alsaconf" said that I should stop the sound driver. . .
how do I do this?
endquote

huh ?
are you using a selfmade kernel , or a precompiled from a Slackware package ?

egag

Some suggestion to a primitive solution:[list=1][*]check installed versions of kernel & alsa packages
[*]hope there is only one version of each, then reinstall them for sure by
[*]run [/list=1]
But as egag said, make sure you didn't installed your custom kernel. If you did, make sure alsa-driver package is not installed and then reinstall your custom kernel including modules.

dunric...only the modules should be reinstalled
( if they are not compiled in the kernel ...)

egag

I just suggested to do these simple steps to ensure all required packages are installed in proper versions and I'm not sure whether NetRaven somehow don't messed up kernel too. Kernel modules need to correspond to proper kernel version.
I had to add after installing of kernel package, lilo must be rerun and system rebooted.

dunric...i was only meaning the last line about the custom kernel.
but i think i jumped to conclusions too fast in my earlier posts
because there is still the Q.: is it a selfmade kernel and is sound compiled in ?

we'll see...

egag

Dunric - I got this:

root@darkstar:~# ls /var/log/packages/alsa-*
/var/log/packages/alsa-driver-1.0.9b_2.4.31-i486-1
/var/log/packages/alsa-lib-1.0.9-i486-1
/var/log/packages/alsa-oss-1.0.9-i486-1
/var/log/packages/alsa-utils-1.0.9a-i486-1
root@darkstar:~# ls /var/log/packages/kernel-generic*
/var/log/packages/kernel-generic-2.6.10-i486-1
root@darkstar:~# ls /var/log/packages/kernel-modules*
/var/log/packages/kernel-modules-2.4.29-i486-1
/var/log/packages/kernel-modules-2.6.10-i486-1

Well, looks like the two different versions of kernel-modules just might be it. . . but how do I uninstall only the 2.4.29 one?

And no, it's not a self-made kernel, it's the 2.6.10 from the CD.

you need to remove the alsa driver package :

#removepkg alsa-driver-1.0.9b_2.4.31-i486-1

then get and install the ones for your kernel .
get it from a slackware mirror ( alsa-driver-1.0.9b_2.6.10-i486-1.tgz )
and install with :
#installpkg alsa-driver-1.0.9b_2.6.10-i486-1.tgz

that should do it ...
( then run alsaconf and rc.alsa and it should work )

egag

i'm sorry again, you need to get the alsa-1.0.8 from the cd.
there's no such on the mirror i use...

egag

Taking this back to post #6, I believe that is all that's required. I have one box I recently did a swaert update on where I had forgot to add alsa to the blacklist. SAme thing as this.

egage's solution in post six is exactly what I had done to fix it. It was a self compiled kernel, so I just:

When ALSA was upgraded, modules got mixed up because the upgradepkg which took place removed your working ALSA drivers and put in ALSA drivers for a different kernel. There is no need to remove any packages with this solution.

The above solution makes the assumptions that:

A) /usr/src/linux is a symlink to the kernel you run (adjust accordingly if not)

b) as egag pointed out, if you ran a "make clean" you will need to run "make modules" first. If you did a "make mrproper", you will need to set up a .config file first

c) ALSA is compiled as modules in your working kernel. I would assume that it is, since it would not have broken otherwise.

This will then hose any added drivers (like NVIDIA or MadWiFi), so if you have some, you'll need to re-install them.

Then, either reboot, or run rc.alsa, which will now work because the drivers are present.

Exactly as egag already posted, you have ALSA modules for kernel 2.4.31 and you need to replace it with version for kernel 2.6.10.
Did it the job ?

Sorry for the delay, I had to sleep because it was too late for me

shilo-
Thank you, I'm trying your suggestion right now! I never realized you were supposed to blacklist "alsa" - and your warning came none too soon, as I'm also setting up an older box with Slackware for MythTV (it's a program that basically turns your PC into a TiVo).

Well, I'll let you guys know if it works!

It's a recommendation on there site in the forums somewhere, I believe. If not, it's a good idea anyway. Also, I recommend blacklisting aaa* and glibc*. Some things shouldn't be upgraded, others I believe should be upgraded by hand.

I've done that very thing. I decided not to use SWareT for updating that install, though. To much chance for messing up when you are installing so much custom software.

To totally threadjack, when you set up MythTV, you should install LiRC if you want remote control. Then, use the Slackbuild script for xine to rebuild it. If you have already installed LiRC, the new xine build will see that LiRC is installed and make xine LiRC-"aware". Then, you ditch your DVD player and use MythTV for everything. This stumped me for a bit, until I realized that the stock Slackware xine does not have LiRC support.

I just so this posting. I had the same scenario 3 weeks ago when I decide to upgrade all my Slack packages to the latest available.
Everything was just fine, except my sound was gone.
My solution was:
1. use swaret to remove alsa.
2. go to http://www.alsa-project.org/ and get the latest sources
3. install the sources
4. run alsaconf and configure the outputs.
5. alsactl store to save my config
and I was back in business.

Hope this helps

Rick

yeah it helps ...rofl
you're sure you didn't compile the thing ?

egag