SlackwareThis Forum is for the discussion of Slackware Linux.
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.
For the sound when you log in as root do you get any sound?
if you do then change the permissions on the sound devices if it doesn't work even as root then can you post your lsmod here oh and one more thing have you recompiled a kernel yet? or are you running the default kernel slack ships with?
Last edited by ProtoformX; 06-13-2004 at 12:54 AM.
Originally posted by BajaNick I cant believe swaret updated so flawlessly, I thought I was gonna have to reinstall and jump through hoops for it to work. <snip> Except for a few minor glitches like my sound not working anymore:cry: and my login screen changing, but those are not much of a problem.
Sorry Baja, but frankly I like my sound - if I have to manually update by subscribing to the slackware security mailing list and running
about once every few weeks to keep my sound, I think it's worth it :)
Sure, swaret maybe good but I don't see anything wrong with manually updating, it may take that tincy bit more effort but ... sound is good.
Unless of course I'm completely wrong and the patches are actually screwing with slackware and swaret is actually doing nothing wrong...then swaret is amazing. :)
The reason sound is not working is probably because you updated alsa but not your kernel. Alsa are kernel modules, and somehow (I dont understand exactly) it seems not to work if you still use the stock 2.4.22 kernel (swaret has kernel in its excludes), but do upgrade alsa. I think that if you upgrade your kernel, it will all work fine
I ran in to this problem too, but it was no issue for me since I want everything kernel related handcompiled. IMO the kernel is the most important thing to optimize, with the rest I don't really bother
about once every few weeks to keep my sound, I think it's worth it
Well, realize that he probably used swaret to get up to date with -current, not just installing security updates for 9.1.
Tools like swaret, slackpkg, and slapt-get are very convenient for following the development of -current as long as you also keep an eye on the ChangeLog after each update to be sure there aren't any new packages you should add or old packages you should remove.
Also, to the original poster, if the kernel-ide package is excluded in swaret's config file (assuming that's what kernel you're using) you may want to add alsa-driver to the exclude list which should keep this problem from occuring in the future. Either that or allow the kernel-ide package to be updated (but be sure to run LILO after if it is!).
I've been using swaret for a long time and never never had troubles with it. But as it has been said, the sound will be a problem if you update alsa without upgrading the kernel. So earlier, i used to put alsa in the 'exclude list' in swaret.conf. But now, I run 2.6 and everything works fine. How I do my stuff is to install the basic system (without X, kde, gnome) from the slack cd and then do:
One thing you can do is edit your swaret.conf file and add the line "EXCLUDE=alsa" and it won't update the alsa files. Since it already excludes your kernel, I just exclude alsa since it seems to be dependent on the kernel version. I do the same thing with xfree.