From alsa-user-owner@alsa.jcu.cz  Fri Jun 12 08:08:21 1998
Received: from indiana.edu (belize.ucs.indiana.edu [129.79.10.64])
	by marvin.jcu.cz (8.8.8/8.8.8) with ESMTP id IAA14788
	for <alsa-user@jcu.cz>; Fri, 12 Jun 1998 08:08:09 +0200
Received: from copper.ucs.indiana.edu (weg@copper.ucs.indiana.edu [129.79.1.4])
	by indiana.edu (8.8.8/8.8.8/1.16IUPO) with ESMTP id BAA07208
	for <alsa-user@jcu.cz>; Fri, 12 Jun 1998 01:08:07 -0500 (EST)
Received: (from weg@localhost)
	by copper.ucs.indiana.edu (8.8.5/8.8.5/1.4copper) id BAA03377;
	Fri, 12 Jun 1998 01:08:03 -0500 (EST)
To: alsa-user@jcu.cz
Subject: Re: pnp awe64 problems
References: <Pine.LNX.3.96.980611101435.9734C-100000@entry.jcu.cz>
Mime-Version: 1.0 (generated by tm-edit 7.106)
Content-Type: text/plain; charset=US-ASCII
From: weg@indiana.edu (Eythan M. Weg)
Date: 12 Jun 1998 01:08:02 -0500
In-Reply-To: Jaroslav Kysela's message of Thu, 11 Jun 1998 10:16:48 +0200 (MET DST)
Message-ID: <yrdubtrzup8d.fsf@copper.ucs.indiana.edu>
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list

Jaroslav Kysela <perex@jcu.cz> writes:

> On Wed, 10 Jun 1998, Eythan M. Weg wrote:
> 
> > I have PNP sb awe64, but cannot get it to operate.
> > 
> > This is my peeking into the card registers using isapnp:
> > 
> > Board 1 has Identity 00 1a 2d 90 9a e4 00 8c 0e:  CTL00e4 Serial No 439193754
> > [checksum 00]
> > Peek(CTL00e4/439193754)[0][0x70](INT 0) is 0x0502, (5,2)
> > Peek(CTL00e4/439193754)[0][0x74](DMA 0) is 0x01, (1)
> > Peek(CTL00e4/439193754)[0][0x75](DMA 1) is 0x05, (5)
> > Peek(CTL00e4/439193754)[0][0x60](IO  0) is 0x0220, (2,32)
> > Peek(CTL00e4/439193754)[0][0x62](IO  1) is 0x0330, (3,48)
> > Peek(CTL00e4/439193754)[0][0x64](IO  2) is 0x0388, (3,136)
> > Peek(CTL00e4/439193754)[1][0x60](IO  0) is 0x0200, (2,0)
> > Peek(CTL00e4/439193754)[2][0x60](IO  0) is 0x0620, (6,32)
> > 
.....
...........
> > 
> > Jun 10 14:20:18 aphrodite kernel: snd: sb_reset: failed!!! 
> > Jun 10 14:20:18 aphrodite kernel: snd: SB: [0x220] reset failed... 0xff 
> > Jun 10 14:20:18 aphrodite kernel: snd: Sound Blaster 16 soundcard #1 not found a
> > t 0x220 or device busy 
> > Jun 10 14:20:18 aphrodite kernel: snd: Sound Blaster 16 soundcard #2 not found o
> > r device busy 
> > Jun 10 14:20:18 aphrodite insmod: /lib/modules/2.0.34/misc/snd-sb16.o: init_modu
> > le: Device or resource busy
> > 
> > What could be wrong?
> 
> Have you activated devices in configuration file for isapnp (ACT Y) ?
> Value 0xff looks like no device is connected to ISA bus...

Yes.  The only way the PEEK command of
isapnptools can result in the reading
above is by an earlier use of
isapnp.conf, which contains exactly
these parameters.  I have no windows-95
on the computer.
Here is my configuration file:


(READPORT 0x0203)
(ISOLATE PRESERVE)
(IDENTIFY *)
(CONFIGURE CTL00e4/439193754 (LD 0
  (INT 0 (IRQ 5 (MODE +E)))
  (DMA 0 (CHANNEL 1))
  (DMA 1 (CHANNEL 5))
  (IO 0 (BASE 0x0220))
  (IO 1 (BASE 0x0330))
  (IO 2 (BASE 0x0388))
  (ACT Y)
))
(CONFIGURE CTL00e4/439193754 (LD 1
  (IO 0 (BASE 0x0200))
  (ACT Y)
))
(CONFIGURE CTL00e4/439193754 (LD 2
  (IO 0 (BASE 0x0620))
  (ACT Y)
))
(WAITFORKEY)


As for a device, what else could it be
except for what's on the card itself?
Could the failure be because of some
conflicts: interrupts, ports?  And if so,
how can I tell what resources are being
used which might collide with SB?


Thanks for the prompt response.

Eythan 

