Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
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 recently upgraded my Slackware installation from 9.1 to 10.0, everything went smooth. I then decided to take it a step further and try out the packaged 2.6.7 kernel. That install also went smooth, however, I noticed I lost my sound. I installed the new alsa driver package that came with the kernel, ran alsoconf, detected my sound card, etc, etc. Still no sound. I removed and reinstalled the package, ran alsaconf again. Again, it found and installed my sound card. Still no sound. I've researched this a bit and did not find any information regarding this issue with any kernels newer than 2.4.6. Any help/suggestions/comments would be greatly appreciated.
If it won't work for root then there is something fundamentally wrong. In this case I would start with the basics...is everything cabled properly? Don't laugh or just shrug it off...look, because it even happens to experts every once in a while. Is the soundcard seated properly in the pci slot? Check all the physical connections.
Can't, it's a laptop, onboard sound, etc. But, the sound worked basically up until kernel upgrade, so I'm not sure what happened. I'm in the process of backing up my home directory so I can blow the install away. I've noticed some other issues going on that I didn't before, so I think there is something else going on. Thanks for all of your replies.
That's alright dude, I'm starting over fresh. I was running Slackware 9.1 with 2.4.26, I then upgraded to Slackware 10.0 with 2.4.26. Then went up to 2.6.7. I'm going to do a fresh install of 10.0 with 2.6.7 and see if I can get it to work.
if you wish try recrateing the device files and check the drivers loaded, may be you have to update some scripts I did in modules.conf to have the alsa architecture to work properly ... at least I did it and it worked...
did you use alsa before or oss.
I use debian and there is script that recreates teh files under /dev if necessary at boot time, very handy thing
After all you can try recompile and install your own kernel ... it should save you more time as installing and configuring a hole system again
Yes, I ran alsa prior. I've already checked all the scripts and triple checked everything was loading properly. And as I stated earlier, I have since run into more issues than just the sound not working, so there is something else going on.
What do you mean "ms-windows mentality", it's only a laptop I use to mess around and test things on.
sorry about the ms mentality -it means reisntall everything again
If I want to test a new distro I do install it on different partition, I do check it and after I am sure it works I replace my distro, though I made this just one time, because I did upgrade from stable to testing and than I tried to downgrade, what was obiously too brave. Since than (more than 2 years) I use only woody stable and compile the few apps I need, the kernel and alsa too with regular upgrades from the distro itself.
I tried the 2.6 , but it's not stable enough to satisfy my expectations and I use only 2.4 the latest patches appplied - no problems. I tried on my other partition few other distros, but I still have one where I'm sure I can boot on and work.
This way I can really enjoy 100% the power of my machine and really spend time working and not configuring all the time and posting questions to LinuxQuestions.org
Another windows symptom is "upgrade now" and "new version available" and so on.
Why should I upgrade if somthing works already to something I don't know if it works.
Next time copy your system to a free partition
boot from this partition
make the upgrade there
reboot and test the upgrade
IF ITS OK
replace your old system with the new one
Mostly if you have customly installed apps (compiled and so), keep a track of them and test them (usually you should recompile and reinstall them
Anyway you seem to be smart and I'm sure wou'll find your own way to manage linux.