From owner-freebsd-current@FreeBSD.ORG Mon May 26 02:53:10 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2D4A737B401 for ; Mon, 26 May 2003 02:53:10 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BC7843FCB for ; Mon, 26 May 2003 02:53:09 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from user-38lc19i.dialup.mindspring.com ([209.86.5.50] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19KEfC-00058o-00; Mon, 26 May 2003 02:53:07 -0700 Message-ID: <3ED1E2D2.AC5D07AE@mindspring.com> Date: Mon, 26 May 2003 02:48:02 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Fritz Heinrichmeyer References: <86vfvycc0x.fsf@jfh00.fernuni-hagen.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a429612c4ced2c28b150f2d4e2d168f02c548b785378294e88350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: CMedia CMI8738 works when setting pnp-os to no X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 09:53:10 -0000 Fritz Heinrichmeyer wrote: > as title says, now i have to set pnp-os to "no" in my bios setup for > sound playing to work. Usually this indicates that there is some initialization that's done by the BIOS that doesn't happen in the case of "pnp-os=yes" because the hardware expects the OS's driver to do the work. The main thing I've seen with motherboards that behave this way is power management: they expect the OS to turn the power on before it tries to use the device. Probably the chip itself is on, and the output amp is turned off. I mentioned this before in a similar thread; if you hack the driver to turn the power on, it should fix this for you. I've seen the same thing with a USB keyboard and mouse, on one motherboard... -- Terry