Slackware This Forum is for the discussion of Slackware Linux.
|
| Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
01-08-2006, 02:48 PM
|
#1
|
|
Member
Registered: Sep 2004
Location: Scotland
Posts: 41
Rep:
|
'Lost' sound after upgrade
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!
|
|
|
|
01-08-2006, 02:57 PM
|
#2
|
|
Senior Member
Registered: Oct 2003
Location: lost in the midwest...
Distribution: Slackware
Posts: 1,091
Rep:
|
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.
|
|
|
|
01-08-2006, 03:06 PM
|
#3
|
|
Member
Registered: Sep 2004
Location: Scotland
Posts: 41
Original Poster
Rep:
|
Thanks for that suggestion but, if you'll pardon my ignorance, how do I go about removing alsa and then re-installing it from the disk?
|
|
|
|
01-08-2006, 03:17 PM
|
#4
|
|
Member
Registered: Sep 2004
Location: Scotland
Posts: 41
Original Poster
Rep:
|
Hi again,
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?
Thanks.
|
|
|
|
01-08-2006, 03:25 PM
|
#5
|
|
Senior Member
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132
Rep:
|
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.
**EDIT***
You may want to use "upgradepkg --install-new package_name", just in case you didn't remove all the alsa packages.
Last edited by shilo; 01-08-2006 at 03:27 PM.
|
|
|
|
01-08-2006, 03:59 PM
|
#6
|
|
Member
Registered: Apr 2004
Location: new york
Distribution: win2k,ubuntu,sw13,arch,centos5.3
Posts: 815
Rep:
|
In swaret.conf file there is sexn that has
EXCLUDE=kernel and other exclusions wc shd include
EXCLUDE=aaa_
EXCLUDE=alsa kernel
according to download page.
God luck.
|
|
|
|
01-08-2006, 04:17 PM
|
#7
|
|
Member
Registered: Sep 2004
Location: Scotland
Posts: 41
Original Poster
Rep:
|
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!
|
|
|
|
01-08-2006, 04:23 PM
|
#8
|
|
Member
Registered: Sep 2004
Location: Scotland
Posts: 41
Original Poster
Rep:
|
shilo/lestoil - just a follow up so I get this right - to blacklist alsa I'm adding:
EXCLUDE=aaa_
EXCLUDE=alsa kernel
is that all I need?
My EXCLUDE list will look like this:
# Basic Exclude
#
EXCLUDE=kernel
EXCLUDE=lilo swaret
EXCLUDE=MANIFEST.bz2$
EXCLUDE=.*dl$ .*PACKAGER$ .*MYBUILD$
EXCLUDE=aaa_
EXCLUDE=alsa kernel
Thanks.
|
|
|
|
01-08-2006, 04:31 PM
|
#9
|
|
Senior Member
Registered: Nov 2002
Location: Stockton, CA
Distribution: Slackware 11 - kernel 2.6.19.1 - Dropline Gnome 2.16.2
Posts: 1,132
Rep:
|
Looks just like mine, now.
|
|
|
|
01-08-2006, 04:32 PM
|
#10
|
|
Member
Registered: Sep 2004
Location: Scotland
Posts: 41
Original Poster
Rep:
|
Shilo - appreciate that, thanks again.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 11:49 AM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|