Re: ALSA --> Problem solved by "rm /etc/modprobe.conf"
On Friday 17 September 2004 10:23, James Cummings wrote:
> On Fri, 17 Sep 2004 10:02:26 -0600, Justin Guerin <jguerin@cso.atmel.com>
wrote:
> > On Friday 17 September 2004 08:26, James Cummings wrote:
> > > So I've got various ac97* modules in my /etc/modules
> >
> > Which ones exactly?
>
> probably the wrong ones... but I was trying anything to get it to work:
> ac97_plugin_wm97xx 12800 0 (unused)
> ac97_plugin_ad1980 524 0 (unused)
> ac97 3232 0 (unused)
> ac97_codec 13300 0 [ac97_plugin_wm97xx ac97_plugin_ad1980]
>
These are OSS modules. All Alsa modules begin snd_*. There's no problem
with using the OSS modules, but you can't mix OSS and Alsa. Note that you
also need soundcore and sound. Those would have been loaded with modprobe
i810_audio, which failed, so that's probably not your problem. I confess I
don't know what the plugin modules are for, but I doubt they're causing
your problem.
> > > When I was running 2.4.26-686 kernel the package:
> > > alsa-modules-2.4.26-1-686
> > > made my soundcard be recognised by KDE.
> >
> > OK, so you were using Alsa? Did you upgrade the alsa-modules, too?
>
> Howso? There is no alsa-modules-2.4.27* package. Installing that
> is what made it work last time.
>
Yes, it seems that package hasn't made it into unstable or testing yet. You
have options, however. 1) you can do without sound and wait until that
package comes in, and then install it. 2) you can compile the Alsa modules
from source. 3) you can revert to 2.4.26 until the Alsa modules package
becomes available. 4) you can move to a 2.6 series kernel. Alsa is
included in those kernels by default, so there is no alsa-modules-2.6*
package.
> > > But now that I've upgraded to 2.4.27-686 KDE complains
> > > /dev/dsp no such device
> >
> > /dev/dsp won't exist if you're running devfs or udev, and the driver
> > isn't loaded (or you haven't told them to create the device node
> > automatically).
>
> I'm not sure I understand that. (sorry)
>
devfs and udev attempt to create device nodes only when the actual hardware
that uses them is present. That way, /dev isn't cluttered with a bunch of
useless device nodes. When devfs and udev are working properly, you won't
need to worry about this. Apparently, however, there's some sort of
problem. Read the MAKEDEV manual page, if you want to go this route.
> > > insmod i810_audio:
> >
> > What happens when you modprobe i810_audio?
>
> modprobe i810_audio
> /lib/modules/2.4.27-1-686/kernel/drivers/sound/i810_audio.o:
> init_module: No such device
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters.
> You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.27-1-686/kernel/drivers/sound/i810_audio.o: insmod
> /lib/modules/2.4.27-1-686/kernel/drivers/sound/i810_audio.o failed
> /lib/modules/2.4.27-1-686/kernel/drivers/sound/i810_audio.o: insmod
> i810_audio failed
>
It seems your sound card isn't being recognized. Have you tried any other
modules using modconf?
> > That won't work. Use the Alsa version of the 810 driver: snd-intel8x0.
>
> insmod: snd-intel8x0: no module by that name found
>
Yep, if you don't have the Alsa modules package installed, you won't have
this module to load. See above for your options.
> > Also, did you change from devfs to udev? And you're sure you're not
> > mixing Alsa and Oss modules?
>
> I have no idea. (again sorry) :-(
You are probably not mixing modules, because you don't have any Alsa
modules. :-) At least that's simple.
ps. please copy the list. I don't mind a CC, but you really want to make
sure everyone on debian-user has a chance to reply, because a lot of people
know a lot more about sound than I do.
Justin Guerin
Reply to: