From owner-freebsd-questions@FreeBSD.ORG Mon Dec 13 01:16:13 2004 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 ABDDB16A4CE for ; Mon, 13 Dec 2004 01:16:13 +0000 (GMT) Received: from cedant2.abac.com (cedant2.abac.com [66.175.0.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8762843D49 for ; Mon, 13 Dec 2004 01:16:13 +0000 (GMT) (envelope-from bob@vesterman.com) Received: from [192.168.0.11] (ool-44c40513.dyn.optonline.net [68.196.5.19]) (authenticated bits=0) by cedant2.abac.com (8.13.1/8.13.1) with ESMTP id iBD1G9Pn085295 for ; Sun, 12 Dec 2004 17:16:12 -0800 (PST) (envelope-from bob@vesterman.com) Message-ID: <41BCF040.4090202@vesterman.com> Date: Sun, 12 Dec 2004 20:28:32 -0500 From: Robert William Vesterman User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.44 Subject: sound works with kldload, but not /boot/loader.conf? 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: Mon, 13 Dec 2004 01:16:13 -0000 Hi, I just tried playing a WAV file using xmms (this is the first time I've tried anything with sound on my installation). It issued a very generic error message, telling me things like "make sure your device is installed". I did some research (mostly in the FreeBSD handbook), and eventually got my sound working by doing a "kldload snd_driver". I then changed /boot/loader.conf to contain the line: snd_driver_load="YES" So that I wouldn't have to "kldload snd_driver" every time. After rebooting, xmms acted like it was playing the song - no error message, equalizer lights happily jumping around, et cetera - but no sound came out. If I try "kldload snd_driver" at this point, it says that snd_driver is already loaded. If I comment out the line from /boot/loader.conf, reboot and do a "kldload snd_driver", the sound works fine (as it did before). So, am I doing something wrong? Is there a way to get the /boot/loader.conf line to work? Is there anything else I could investigate? If it's just screwed up and that's all there is to it, could I just manually put "kldload snd_driver" into some automatic startup script? If so, what is the appropriate script? Thanks, Bob Vesterman.