From owner-freebsd-current@FreeBSD.ORG Wed Jul 14 05:27:19 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 300C816A4CE for ; Wed, 14 Jul 2004 05:27:19 +0000 (GMT) Received: from sccrmhc12.comcast.net (sccrmhc12.comcast.net [204.127.202.56]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC8E043D5A for ; Wed, 14 Jul 2004 05:27:18 +0000 (GMT) (envelope-from vladimir@math.uic.edu) Received: from cat.math.uic.edu (c-67-162-104-112.client.comcast.net[67.162.104.112]) by comcast.net (sccrmhc12) with SMTP id <2004071405271701200fqh4je>; Wed, 14 Jul 2004 05:27:18 +0000 Received: (qmail 15549 invoked by uid 31415); 14 Jul 2004 05:27:17 -0000 Date: Wed, 14 Jul 2004 00:27:17 -0500 From: Vladimir Egorin To: freebsd-current@freebsd.org Message-ID: <20040714052717.GA15283@math.uic.edu> References: <20040714050225.12980.qmail@cat.math.uic.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040714050225.12980.qmail@cat.math.uic.edu> User-Agent: Mutt/1.5.6i Subject: Re: support for Asus P4P8X onboard audio X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Jul 2004 05:27:19 -0000 On Wed, Jul 14, 2004 at 05:02:25AM -0000, vladimir@math.uic.edu wrote: > > Does anyone know the state of support for that device? > The audio device is recognized: > > $ cat /dev/sndstat > FreeBSD Audio Driver (newpcm) > Installed devices: > pcm0: at io 0xfebff800, 0xfebff400 irq 10 bufsz 16384 (1p/1r/4v channels duplex default) > > $ dmesg|grep pcm > pcm0: port 0xee80-0xeebf,0xe800-0xe8ff mem 0xfebff400-0xfebff4ff,0xfebff800-0xfebff9ff irq 10 at device 31.5 on pci0 > pcm0: [GIANT-LOCKED] > pcm0: > > > ... however I cannot hear any sound during playback. I searched on the net and > saw a mention of some patches floating around, but could not > find anything definite. > > I believe users of P4B800 motherboard have the same problem. typo... this was supposed to be P4P800. Max Laier mentioned his P4P800 works, I guess the problem is local to my setup then. -- Vladimir