Re: after alsaconf no sound

[Gerard Robin <g.robin3@free.fr>]

On Fri, Jun 08, 2007 at 05:09:59PM -0400, Ralph Katz wrote:
> From: Ralph Katz <ralph.katz@rcn.com>
> To: debian-user <debian-user@lists.debian.org>
> Subject: Re: after alsaconf no sound
> X-Spam-Checker-Version: SpamAssassin 3.1.4 (2006-07-26) on murphy.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-6.4 required=4.0 tests=AWL,BAYES_00,LDOSUBSCRIBER 
> 	autolearn=ham version=3.1.4
>
> On 06/08/2007 02:06 PM, Gerard Robin wrote:
> > Hello,
> > my sound worked fine in my box but after I ran alsaconf my system failed.
> >
> > I got:
> > sound blaster soundcard not found or device busy
> > can't grab irq 65535
> > can't grab irq 65535
> > can't grab irq 65535
> > snd_sb8 probe of snd_sb8.0 failed with error -16
> > .....
> > .....
> > I booted on my second hard drive (I have two hard drives in my box)
> > and I commented the line snd-sb8 in /etc/module (of the first hard
> > drive) and after that I can boot on the first hard drive without error
> > but the sound doesn't work.
> >
> > modprobe sb :
> > FATAL: Error inserting sb
> > (/lib/modules/2.6.18-3-486/kernel/sound/oss/sb.ko): No such device
> >
> > file /lib/modules/2.6.18-3-486/kernel/sound/oss/sb.ko  gives:
> >
> > /lib/modules/2.6.18-3-486/kernel/sound/oss/sb.ko: ELF 32-bit LSB
> > relocatable, Intel 80386, version 1 (SYSV), not stripped
> >
> > modprobe snd-sb8 gives the same result that alsaconf now.
> >
> > I am stuck with this problem. Can someone help me to restore the sound
> > in my box ? (Please don't ask me why I ran alsaconf ..... ;-)) tia
>
> I'm no expert, but sb is an oss driver, right?  snd-sb8 would be an alsa
> driver.  For this etch box, I had to /remove/ sb from /etc/modules and
> add the correct snd-____ module on 2.6.18-4-686 and an old isa sound card.
>
> Check the archives; we've discussed sound troubles with etch upgrades
> from sarge frequently.  Also, check your logs for hints.

Thanks for your help but finally I removed alsa-base, alsa-utils ... and I
reinstall them and I ran again alsaconf and the entire processus succeded.
Unstable is sometimes unstable :-)

--
Gérard