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.
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.
Installed Slackware 10.2 and, after running alsaconf - which detected my Via Tech VT8233 (AC97 audio controller) PCI soundard, I had sound.
Then, downloaded, installed and ran SWareT, upgraded several packages including Alsa and now no sound at all - alsaconf cannot detect PCI or legacy sound cards.
I get the following error message at boot up:
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.
I've searched the forum for any reports of similar happenings but can't find any. I'm assuming the upgrade screwed up something but, as I'm new to Slackware and command-line configs, I'm not sure what to do.
Help would be appreciated!
i'm pretty sure it was just the upgrade of alsa...i did this once, too. i fixed it by removing alsa, then reinstalling it from the installation disk. the only time i upgrade alsa is when i upgrade the kernel.
I've done the removing bit without any problems (I think!) using SWareT - now how do I install from the installation disk? If I'm using SWareT again, presumably I have to 'point' it at the disk, and if so, how?
1) Alsa should be blacklisted in swaret.conf (also kernel*, aaa*, *dl)
2) No need to use swaret to install packages fro mthe install disk. Mount the install disk. find the packages. Use "installpkg package_name". Note this is for installing only (which is what you want if you already removed the alsa packages).
The asla packages can be found in /l and /ap. There are 4.
You may want to use "upgradepkg --install-new package_name", just in case you didn't remove all the alsa packages.
shilo - installed the new alsa files from CD - worked a treat! Now I'm going to try blacklisting alsa in swaret.conf to avoid future problems. Really appreciate the guidance guys - every day in every way I'm getting less baffled!