Actually, swaret doesn't over write anything, it just runs installpkg and upgradepkg for you. So, if anything like that would happen it would be a fault in the package, not swaret.

Now, I was just mentioning that I reconfigured X and recompiled my NVIDIA driver and kernel because not everything was compiled with the same version of gcc. This is because I am keeping up with -current, which is the unstable version. Thus the version disparity of gcc until the rest of the packages are updated.

The point being that, if X isn't starting to check these things. You probably don't need to reconfigure X but recompiling the kernel and the video driver with the same gcc may be the problem. That is, if 3rd party video drivers are in use here.

Things like this do happen from time to time with the development version, I'm pretty crazy about backing my system up before running swaret for anything that is major like X, glibc, gcc, etc etc because I've gotten bitten before and made my system into a brick. Once again, not the fault of swaret, or anything else. It's the chance one takes when installing development level versions.

I'm getting off topic for the thread now so I'll stop now but I think you all know what I mean.

Here are my thoughts on swaret for those interested.

One solution would be to head on over to The Alsa Project, look up your card, download the source, and follow the instructions to compile your module. The instructions are clear and easy to follow. Or I thought they were anyway and I'm far from an expert!

Another thing to do would be to fall back to the previous version of alsa that worked.

Or, you could E-mail Pat and let him know your module isn't installed. It may have been an oversight and you can request that it is put into future packages. Then wait for it to be released.

Personally, I go for the compiled myself way. Install checkinstall from the extra CD if you can, it builds slackware packages for you from compiled source so you can easily remove it if you want with removepkg.

Well, all's well except for alsa, how would I go back to the previous version, or better yet, how would I get my sound module back and working?

EDIT: rignes you beat me haha, I'll try that

Hmm...perhaps its time to recompile my kernel to 2.6?

If you know which version your previous alsa was you could see slackware.com for a package of that version.

Personally I would head over to asla and download the latest drivers, libs and utils and install those. May need a reboot or an insmod to get the right module loaded

All I know about the alsa before, was the fact that it was the version that came with slack 10.2, the stable default 10.2. I don't know the version name.

http://www.alsa-project.org/alsa-doc...&module=ca0106
^ is my sound card, the sb live! 24-bit 7.1. alsa's having a problem finding it, it says the module doesn't exist, but it did before

I'm not sure how comfortable you are with Slackware, so if I say stuff you already know I apologize.

First, assuming the kernel you have installed is the 2.4 that comes with Slack 10.2 then I'd go back to the slackware CD and find the package. A list of the installed packages is in /var/log/packages on your system. To remove your non-working package su to root, then 'removepkg /var/log/packages/nameofpackage'. Then I'd installpkg the alsa packages from the CD.

I hope that helps.

alright, what's the basic command for installing stuff from the cd?

The CD literally has the .tgz package files. You just have to cd to the directory containing the files you want then type 'installpkg nameofpackage.tgz' and it will install. To save you the time it looks like the alsa packages are on CD1 in the slackware/l directory.

If you ever wonder where to find a particular package you can search the package names at http://slackware.it/en/. There is a link for packages on the left.