From owner-freebsd-stable Thu Jun 15 12:22:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from firebat.Bushong.NET (c128625-a.frmt1.sfba.home.com [24.5.196.12]) by hub.freebsd.org (Postfix) with ESMTP id 3BCE137BC8B for ; Thu, 15 Jun 2000 12:22:30 -0700 (PDT) (envelope-from dbushong@firebat.Bushong.NET) Received: (from dbushong@localhost) by firebat.Bushong.NET (8.9.3/8.9.3) id MAA59927 for freebsd-stable@freebsd.org; Thu, 15 Jun 2000 12:22:28 -0700 (PDT) (envelope-from dbushong) Date: Thu, 15 Jun 2000 12:22:27 -0700 From: David Bushong To: freebsd-stable@freebsd.org Subject: crunchy sound with newpcm Message-ID: <20000615122227.T79778@bushong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My coworker had this problem about a month before I did, and now the same thing's happened to me: At some indeterminate point (for both of us, it was after a crash or a reboot or some other event, NOT immediately after a new -STABLE build), sound coming out (mp3s, regular wavs, anything going to /dev/dsp) comes out sounding crunchy and garbled. I just have device pcm in my config file, /dev/sndstat says: FreeBSD Audio Driver (newpcm) Jun 9 2000 12:35:40 Installed devices: pcm0: at io 0x530 irq 5 drq 0:1 (1p/1r channels duplex) and the dmesg says: pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 unknown0: at port 0x201 on isa0 (and all of those ranges, irq, and drqs check out in windows). It's actually an onboard sound chip on a Dell Dimension XPS D266, and (as always), it "used to work just fine". Anyone else seen this? Any thoughts? I've loved the newpcm driver for its simple one line, no options configuration, but now I feel helpless without settings to fiddle with ;) --David Bushong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message