From owner-freebsd-current Sun Jun 20 6:33:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id E377514F55 for ; Sun, 20 Jun 1999 06:33:01 -0700 (PDT) (envelope-from naddy@mips.rhein-neckar.de) Received: from mips.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id PAA13042 for freebsd-current@freebsd.org; Sun, 20 Jun 1999 15:33:00 +0200 (CEST) (envelope-from naddy@mips.rhein-neckar.de) Received: by mips.rhein-neckar.de id m10vhXN-000WyUC (Debian Smail-3.2.0.101 1997-Dec-17 #2); Sun, 20 Jun 1999 15:21:29 +0200 (CEST) Message-ID: <19990620152129.Z180@mips.rhein-neckar.de> Date: Sun, 20 Jun 1999 15:21:29 +0200 From: Christian Weisgerber To: freebsd-current@freebsd.org Subject: audio-Device gone mute Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My audio-Device just seems to have gone mute. (I was fiddling around with "tosha -o - | pcmplay -" at the time.) Various attempts to produce sounds with pcmplay, mpg123, and cat >/dev/audio now remain silent. According to aumix, the mixer state is okay. Conf: 4.0-CURRENT (May 29), ES1370 (Soundblaster PCI 64) with pcm(4). mpg123 always reports "[0:00]", so apparently writes block somewhere. Any idea what has happened, and, more importantly, how can I reset the sound driver other than rebooting? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de 100+ SF Book Reviews: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message