At Fri, 31 Oct 2003 14:39:27 +0200,
Andrei Boros wrote:
>
>
> Takashi Iwai wrote:
>
> > > > > gate:~# modprobe snd-opti92x-ad1848
> > > > > /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or
> > > > > resource busy
> > > > > snd: Device or resource busy
>
> > could you check
Takashi Iwai wrote:
> > > > gate:~# modprobe snd-opti92x-ad1848
> > > > /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or
> > > > resource busy
> > > > snd: Device or resource busy
> could you check at which point the error happens, e.g. by putting
> printk()'s ?
Ok, here it
At Wed, 29 Oct 2003 09:06:14 +0200,
Andrei Boros wrote:
>
> Takashi Iwai wrote:
>
> > > gate:~# modprobe snd-opti92x-ad1848
> > > /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or
> > > resource busy
> > > snd: Device or resource busy
> >
> > the devices are activated by the
Takashi Iwai wrote:
> > gate:~# modprobe snd-opti92x-ad1848
> > /lib/modules/2.2.24/misc/snd-opti92x-ad1848.o: init_module: Device or
> > resource busy
> > snd: Device or resource busy
>
> the devices are activated by the alsa driver. so it's ok.
> the problem is that the detection of device fai
On a Slackware 7.0 system, kernel 2.2.23, alsa-0.9-rc7:
I have 2 sound cards: a Hercules Gamesurround Fortissimo II and an old
Opti924 ISA card.
The Hercules works.
The Opti924 is another story. After reading on the ALSA site that 924
chipset is supported by the snd-opti92x-ad1848 driver, I ran
