From owner-freebsd-multimedia Sat Sep 4 2:50:28 1999 Delivered-To: freebsd-multimedia@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 97F8615145 for ; Sat, 4 Sep 1999 02:50:24 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA98577; Sat, 4 Sep 1999 10:52:04 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sat, 4 Sep 1999 10:52:04 +0100 (BST) From: Doug Rabson To: Chris Csanady Cc: Cameron Grant , freebsd-multimedia@freebsd.org Subject: Re: newpcm In-Reply-To: <37D04736.C57EE1DF@ameslab.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-multimedia@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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: 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