From owner-freebsd-questions@FreeBSD.ORG Fri Aug 8 10:58:50 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 10EB537B401 for ; Fri, 8 Aug 2003 10:58:50 -0700 (PDT) Received: from rwcrmhc13.comcast.net (rwcrmhc13.comcast.net [204.127.198.39]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6C6F943F75 for ; Fri, 8 Aug 2003 10:58:49 -0700 (PDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: from be-well.ilk.org (be-well.no-ip.com[66.30.200.37]) by comcast.net (rwcrmhc13) with ESMTP id <20030808175848015006i9bve>; Fri, 8 Aug 2003 17:58:48 +0000 Received: from be-well.ilk.org (lowellg.ne.client2.attbi.com [66.30.200.37] (may be forged)) by be-well.ilk.org (8.12.9/8.12.9) with ESMTP id h78HwfKS028081; Fri, 8 Aug 2003 13:58:41 -0400 (EDT) (envelope-from freebsd-questions-local@be-well.no-ip.com) Received: (from lowell@localhost) by be-well.ilk.org (8.12.9/8.12.6/Submit) id h78HweVw028078; Fri, 8 Aug 2003 13:58:40 -0400 (EDT) X-Authentication-Warning: be-well.ilk.org: lowell set sender to freebsd-questions-local@be-well.ilk.org using -f Sender: lowell@be-well.no-ip.com To: Andrew Thomson References: <1060263196.44321.2.camel@oblivion> From: Lowell Gilbert Date: 08 Aug 2003 13:58:40 -0400 In-Reply-To: <1060263196.44321.2.camel@oblivion> Message-ID: <44oez09gkv.fsf@be-well.ilk.org> Lines: 11 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: FreeBSD Questions Subject: Re: /dev/dsp disappearing X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2003 17:58:50 -0000 Andrew Thomson writes: > anyone else noticed /dev/dsp just disappearing.. > > i switched to esound in an effort to alleviate this problem.. however it > still pops up after a number of days of uptime.. only cured by reboot. There have been a number of changes in the device detection code since the version you're running; it's likely that this behaviour has changed. If not, you may need to go to the -CURRENT list.