Date: Sat, 4 Sep 1999 10:52:04 +0100 (BST) From: Doug Rabson <dfr@nlsystems.com> To: Chris Csanady <cc@137.org> Cc: Cameron Grant <gandalf@vilnya.demon.co.uk>, freebsd-multimedia@freebsd.org Subject: Re: newpcm Message-ID: <Pine.BSF.4.10.9909041049340.2081-100000@salmon.nlsystems.com> In-Reply-To: <37D04736.C57EE1DF@ameslab.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 3 Sep 1999, Chris Csanady wrote: > I recently updated my system, and it appears that newpcm is slightly > broken for me. It detects my audio hardware as: > > pcm0: <SoundBlaster Pro 3.2> at irq 5 drq 1 flags 0x10 on isa0 > > This is not what I have though. :) I have an intel pr440fx with an > onboard Crystal 4236. The funny thing is this actually mostly works. > The only noticeable problem is that the pcm volume control only affects > the left channel. > > I am not using pnp, and my kernel config has the line: > > device pcm0 at isa? port? irq 5 drq 1 flags 0x10 > > Any ideas? This is a known problem. Your hardware includes an SB compatibility mode and the soundblaster driver sees it first. I would like to be able to use the priority probing system to allow both drivers to take a look at the hardware but there is a bit more work to be done before that can happen. As a gross hack, you could put 'return ENXIO' at the start of sb_probe(). -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-multimedia" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9909041049340.2081-100000>