LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Upgraded to Slack 10, now sound card isn't found (http://www.linuxquestions.org/questions/slackware-14/upgraded-to-slack-10-now-sound-card-isnt-found-205787/)

Psyddicus 07-16-2004 08:10 AM

Upgraded to Slack 10, now sound card isn't found
 
Well, as the topic says, I recently (overnight) upgraded from Slack 9.1 to 10 using swaret. My sound card was working just fine in 9.1, but now when I try to use something like, let's say alsamixer, I get this...

alsamixer: function snd_ctl_open failed for default: No such device

I also ran alsaconf and it can't find any cards. I have no idea if this has anything to do with it, but I checked my hotplugs blacklist and my soundcard was still in there.

So...can someone help me help Slack find my soundcard?

vrln 07-16-2004 08:50 AM

What sound card are you using? You need to load the module before you run alsaconf/add the module to rc.modules. If itīs a creative soundblaster live/audigy 1-2 then your module is emu10k1

Psyddicus 07-16-2004 09:20 AM

Thanks for your reply.

I have 'via82cxxx_audio.' Did a modprobe for that, dmesg gives this...

Code:

Via 686a/8233/8235 audio driver 1.9.1-ac3
PCI: Found IRQ 11 for device 00:11.5
PCI: Sharing IRQ 11 with 00:0a.0
PCI: Sharing IRQ 11 with 00:0b.0
PCI: Sharing IRQ 11 with 00:10.2
via82cxxx: Six channel audio available
PCI: Setting latency timer of device 00:11.5 to 64
ac97_codec: AC97 Audio codec, id: ALG64 (Unknown)
via82cxxx: board #1 at 0xEC00, IRQ 11

I don't really know what some of this means, where do I go from here?

Crashbox 07-16-2004 10:14 AM

i had this problem when i upgraded a box from 9.1 to 10. the way i solved it (which, incidentally, is a solution i have found to work for most alsa problems) was to remove the 4 alsa packages (drivers, oss, lib, and utils) and then reinstall them. so, download those four slack packages from one of the mirrors, then fire up package tool, remove the four and then reinstall them. after that, run alsaconf, alsamixer and alsactl store...and you should be fine



***edit***

i know this seems like a rather window-ish solution, however it seems to be the most effective when dealing with alsa issues. every kernel upgrade and kernel recompile i've vere done has resulted in having to remove/reinstall alsa. i am assuming i am not the only one with these experiences, if however, i am, i would be interested in hearing how others deal with alsa...

***end edit***

friendly_guy 07-16-2004 01:54 PM

Crashbox - I am interested in this as, though Alsa works I get a broken pipe error message at boot & some inconsistent behaviour & want to give this a go.

I just wanted to ask why download the packages when they are on the slack CD? I am only on dial up so I would rather not download them without good reason.

marlor 07-16-2004 02:01 PM

simple solution,

i had the same problem ungrading from 9.1 to current.
what i did was to uninstall alsa with pkgtool, and then reinstall it with swaret, did alsaconf again and everything went back to smoth.


good luck

jong357 07-16-2004 03:21 PM

You would want to download them to get the new packages... If you'll be using your 9.1 cd, those are a little old.

Crashbox 07-16-2004 03:29 PM

friendly_guy - i suggested downloading the packages because i didn't (and still don't) know if Psyddicus has the Slack 10 cd's or not. he doesn't say if he did his swaret uprgade online or with the discs. either way, i agree with Jong, if all you have is the 9.1 cd's then you definitely want to get the new packages.

jong357 07-16-2004 03:58 PM

As for the "no sound" problem, this always happens after a kernel compile. There is no need to uninstall ALL of them either. All you need to do is uninstall the alsa-driver package and then reinstall. This has been covered so many times, it makes my head spin... :D But, yea, thats what I do after a new kernel compile as well... When you re-compile your kernel, you are deleting your /lib/modules/<uname -r> directory and starting fresh. Thats why your sound doesn't work anymore... All your sound modules and config files just got wiped clean.... The alsa-driver package replaces all those... I think the kernel and alsa teams aught to get together and decide to put these modules somewhere else or come up with a solution somehow. Ussually, after a kernel compile (version upgrade), the sound modules wont work anyway even if they did get left so it doesn't matter.....

keefaz 07-16-2004 04:17 PM

I found that just rm /etc/asound.state after a kernel compile will suffice to fix it no need to reinstall alsa.


All times are GMT -5. The time now is 03:11 AM.