*BSD News Article 91659


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!blackbush.xlink.net!rz.uni-karlsruhe.de!not-for-mail
From: Philipp Mergenthaler <p@hadii609.hadiko.uni-karlsruhe.de>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: sound device probing fails
Date: 20 Mar 1997 09:44:15 GMT
Organization: University of Karlsruhe, Germany
Lines: 38
Message-ID: <5gr0tf$558$2@nz12.rz.uni-karlsruhe.de>
References: <332F555E.4E4A@harris.com>
Reply-To: un1i@rz.uni-karlsruhe.de
NNTP-Posting-Host: hadii609.hadiko.uni-karlsruhe.de
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Newsreader: TIN [UNIX 1.3 unoff BETA 970309; i386 FreeBSD 2.2-970225-GAMMA]
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:37484

Gregory James Cusick <gcusick@harris.com> wrote:
> I'm having difficulty getting my sb16 (pnp) working properly.

I have a (normal) soundbaster compatible, so I can't really help you :-( ,
just give some ideas:

> I configured a new kernel and compiled it successfully.  I have included
> in the kernel configuration file:

> controller sd0

I think sd0 is some SCSI device. The sound controller is
controller snd0  .

> device     sb0         at isa? port 0x220 irq 5 drq 1 vector sbintr

I have
device sb0      at isa? port 0x220 irq 5 conflicts drq 1 vector sbintr

[...]

> Also, I do have a snd0 device node in /dev.

I don't think the files in /dev influence the probing during boot, but
nonetheless:
I did a cd /dev; ./MAKEDEV sb  and got lots of devices (e.g. /dev/audio),
but no snd0 ...

> I read something in sound.doc about adding ALLOW_CONFLICT_IRQ,
> ALLOW_CONFLICT_IOADDR.  Where do you add these statements???  Do I need
> to?
You could enter -c during boot and look if there's somthing on the same
irq, drq or IO-adress as your soundcard, and if so, disable it. But I don't
think you need this, or you would've got a message like "device not probed
due to conflict" during boot.

Bye, Philipp