From owner-freebsd-current Sun Aug 6 21:47:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EB3E737BC9D; Sun, 6 Aug 2000 21:47:48 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id AAA93842; Mon, 7 Aug 2000 00:47:38 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Mon, 7 Aug 2000 00:47:38 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Ollivier Robert Cc: "FreeBSD Current Users' list" , cg@freebsd.org Subject: Re: [Neomagic] newpcm problems under current In-Reply-To: <20000806202735.A1224@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "me too" pcm0: mem 0xfda00000-0xfdafffff,0xfac00000-0xfaffffff irq 5 at device 0.1 on pci1 pcm0: play interrupt timeout, channel dead Then EBUSY until the cows come home. I chatted with Cam some this evening; this problem seems to have come about as a result of driver restructuring. This chipset used to "just work" on my Dell notebook under some earlier 4.0 revision. On Sun, 6 Aug 2000, Ollivier Robert wrote: > FreeBSD sidhe.freenix.org 5.0-CURRENT FreeBSD 5.0-CURRENT #19: Thu Aug 3 19:19:36 CEST 2000 roberto@sidhe:/src/src/sys/compile/nSIDHE i386 > > FreeBSD Audio Driver (newpcm) Aug 3 2000 17:03:04 > Installed devices: > pcm0: at memory 0xfe000000, 0xfea00000 irq 9 (1p/1r channels duplex) > > The first time I run mpg123, it does nothing (that is, no sound is emitted) > and afterwards, /dev/dsp can't be opened at all... Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message