From alsa-user-owner@alsa.jcu.cz  Sat May  9 21:54:43 1998
Received: from entry.jcu.cz (perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.8.8/8.8.8) with SMTP id VAA17101;
	Sat, 9 May 1998 21:54:30 +0200
Date: Sat, 9 May 1998 21:54:30 +0200 (MET DST)
From: Jaroslav Kysela <perex@jcu.cz>
To: Juergen Kreileder <kreilede@guiness.informatik.uni-dortmund.de>
cc: alsa-user@alsa.jcu.cz
Subject: Re: SB16 PnP
In-Reply-To: <199805091820.UAA12554@tuborg.informatik.uni-dortmund.de>
Message-ID: <Pine.LNX.3.96.980509214159.16071E-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

On Sat, 9 May 1998, Juergen Kreileder wrote:

> Hi!
> 
> Is it possible to use the alsadriver with the isapnputils?
> If I do 'modprobe snd-sb16' I get this message:
> snd: SB16 [0x220]: unable to set DMA & IRQ (PnP device?)
> snd: SB16 [0x220]: irqreg=0xf4, dmareg=0x16, mpureg = 0xff
> snd: Sound Blaster 16 soundcard #1 not found at 0x220 or device busy
> snd: Sound Blaster 16 soundcard #2 not found or device busy
> 
> from conf.modules:
> options snd-sb16 snd_index=1 snd_port=0x220 snd_irq=7 snd_dma8=1 snd_dma16=5 snd_mpu_port=0x330
> 
> System is:
> Linux duke 2.1.101 #1 SMP Sat May 9 18:36:03 CEST 1998 i686 unknown

You have probably wrong configuration for isapnp program... If you have
PnP device - resource settings for ALSA driver must exactly match to
configuration which is activated with isapnp program. ALSA driver can't
change hardware settings for SB PnP soundcards...

If you have still trouble, please, send me your configuration file for
isapnp program. I'm testing ALSA driver with SB AWE 64 - this is PnP
soundcard and is activated with isapnp, too...

					Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic



