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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
There is less than 24 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I installed Slackware and everything worked fine. I configured ALSA to make my sounds work fine as said in the post (this is I do it all by shilo).
following the advices in that post i installed swaret and did all the uploads and stuff...
controlled for the .new files and it all right...
when then i reboot my box a popup message came out:
Sound server informational message:
Error while initializing the sound driver:
device: default can't be opened for playback (No such device)
The sound server will continue, using the null output device.
in fact there is no sound card recognized by the system at all now...
and my sounds went off...
what can i do??? why Slack doesn't recognize my sound card anymore now?
(It is and integrated soundcard with Intel chips.)
The alsa drivers that you upgraded to are for the newest kernel. You probably need to remove kernel from the exclude list in swaret.conf then upgrade the kernel with swaret, or you could install the alsa drivers from source.
Last edited by Minderbinder; 05-16-2004 at 06:29 PM.
You can also compile a new kernel. I prefer to not let SWareT handle the kernel automatically. Maybe it's silly, but the three days that I ran Red Hat instead of Slackware, I had nothing but headaches letting automated programs handle the kernel.
Kernel is at 2.6.6 now. Great time to learn how to compile your own.
Also, there was a time I got a weird message like that in KDE. What window manager are you using? Also, is this a problem for root and users? Let me know.
Don't be scared of the kernel compiling. I recommend learning how to do it early. That way, if you totally hose your system, it's not near as much work to re-install. If you wait to learn it until after you've got everything else set up perfectly, you're gonna have a lot more work to get things set back up. In reality, though, if you follow the kernel compiling guide on my website, you'll never need to re-install everything, as you'll always have your old kernel as back up.
Sorry I can't be more help with KDE. If I remeber right, when I got that message before, it was a permissions problem, but I rarely use KDE, so I can't be sure.
The kernel is the heart of your Linux system. Recompiling your kernel is changing that "heart". You can recompile the kernel that you already have, but I recommend you upgrade your Kernel at the same time. ALSA is a part of the 2.6.xx kernel and works pretty well.
Check out the two stickies at the top of the forum. I also recommend my site, http://shilo.is-a-geek.com/slack/kernel14.html . If you have any questions after going through those, feel free to ask. Probably want to start a new thread for that, though, so this one stays on topic.
Originally posted by shilo You can also compile a new kernel. I prefer to not let SWareT handle the kernel automatically. Maybe it's silly, but the three days that I ran Red Hat instead of Slackware, I had nothing but headaches letting automated programs handle the kernel.
LOL, I don't let windows update Jr. ( err, swaret) handle anything............there are at least a few hundred threads pertaining
to swaret screwing up peoples system........(bad drivers, bad libraries,
incomplete libraries....etc) just don't use that windows update Jr. crap
and manually upgrade your Systems, that way "YOU" know its done
hey dude i had the same problem the kernel used in the slack 9.1 is a bit old so not all the new packages may work for it very well
i had the same problem with my sound card i compiled the 2.6.6 kernel and voila everything worked
Ps: about the sticky the makefile 2.6.0 differes from 2.6.x (2.6.1 , 2..6.2...)
so just open it in a x editor and find the export line
Originally posted by 320mb LOL, I don't let windows update Jr. ( err, swaret) handle anything............there are at least a few hundred threads pertaining
to swaret screwing up peoples system........(bad drivers, bad libraries,
A few hundred threads about swaret screwing up systems??? There are currently 363 total slackware threads, I seriously doubt that the vast majority are people bitching about swaret. I have never had any problems with swaret. I don't just blindly install everything swaret wants to, I look over the suggested packages and install the ones I think I need.
What is your problem with windows update? I wish all XP users would run it on a regular basis ao they would severely cut down on the number of worms on their systems. There are also security holes discovered in linux distros, including slackware. I keep them plugged by running swaret regularly. I could install them all manually, but that would be a major pain in the rear. If you are a noobie (or if you don't want to spend a lot of time updating manually) it's probably a good idea to keep security fixes up to date with swaret. Searching "+swaret +kernel" yielded 3 threads where swaret might have screwed up someone's system. Do you think a noobie's odds are better if they compile their own kernel?
Compiling your own kernel will give you a more optimized system. If you follow shilo's excellent how-to that he linked to in his post even noobies have a good chance of doing it correctly. However, if you can't get it to work, or you don't want to invest the time to get it working, using swaret to upgrade to the latest 2.4.X kernel will give you a more secure OS, which I think everyone will agree is a good thing.
minderbinder and 320mb well dudes both of u are right , after using slackware for 6 month now i guess about updates things are in the middle ,
swaret is good for updating (patching ur system) ,in fact it s a must even for power users , but u can't use to update all the packages cause we will loose the power and felxibilty of compiling from source like 320mb said
the kernel ,alsa ,xfree86 ,such things noone needs swaret to update them
it will not help as much and perhaps mess up the system .
about the windows update minder did u know that some patches are worthless ?
first i thought xp was a stable system till once i missed a dll , did anybody know how muchh a missng dynamic librarie will cost him in windows ? these idiots after knowing the advantages of linux,in linux u can even fetch ur libraries from the update manager , in windows u cannot fetch anything if u don't have the undated package
and for all people reading the thread the 2.4.22 has secrurity holes so if u r a newbie just let swaret to update it like minderbinder if u r not ready to compile ur kernel
Originally posted by GM Myrdin yes i do use kde... sorry, my experience was born with it and don't like to use some others (maybe sounds silly)...
so... i can try compiling a new kernel (terrorized---) first i'll look for alsa information...
thanks a lot
Don't be afraid of taking on that new kernel. I am new to slack also and followed the guide by shilo. After 1 week with Slackware I did my first ever kernel compile with failure and success. I have no programing background, have never done anything near this level before but Shilo's instructions about keeping a link to the old kernel are imho VERY IMPORTANT. You can also pull up your old kernel with the system tools and do a compare compile with the new kernel. If it was a module in 2.4 then I made it a module in 2.6.6. I found this to be a wonderful success and I learned a lot. So don't worry about making a mess because the best way to learn is to just do it. If you have done it since your post and got it working then Congrats to you man! Hope you learned as much as I did or more.
Back to the original problem of your sound card not being recognized anymore, the same thing happened to me after I used swaret to update KDE to 3.2.2. I just went to http://www.alsa-project.org and downloaded the newest alsa driver, lib file, util files for my sound card, compiled and installed all 3 of them and everything was fine again.
If you just click on the 'soundcards' link and find your soundcard, that one page will pretty much tell you how to do everything you need to do.