From owner-freebsd-questions@FreeBSD.ORG Wed Jun 23 19:21:30 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 5202916A4CE for ; Wed, 23 Jun 2004 19:21:30 +0000 (GMT) Received: from geofront.co.uk (port-179.dolphin.c4l.co.uk [80.253.114.179]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA3B343D41 for ; Wed, 23 Jun 2004 19:21:29 +0000 (GMT) (envelope-from Mike@the-rubber-chicken-network.co.uk) Received: from [132.147.16.8] ([195.194.75.70]) by geofront.co.uk (8.12.9/8.12.6) with ESMTP id i5NJLlYQ045164; Wed, 23 Jun 2004 20:21:47 +0100 (BST) (envelope-from Mike@the-rubber-chicken-network.co.uk) Message-ID: <40D9D814.6080803@the-rubber-chicken-network.co.uk> Date: Wed, 23 Jun 2004 20:20:52 +0100 From: Mike Woods User-Agent: Mozilla Thunderbird 0.6 (X11/20040607) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Damon Butler References: <40D9B90A.3020509@hddesign.com> <40D9BFDF.2030203@the-rubber-chicken-network.co.uk> <40D9D174.4010107@hddesign.com> In-Reply-To: <40D9D174.4010107@hddesign.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new cc: freebsd-questions@freebsd.org Subject: Re: Sound issues on dual-boot machine 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: Wed, 23 Jun 2004 19:21:30 -0000 Damon Butler wrote: > Hurm. That's all well and good, I guess, but *why* is Linux > initializing the on-board sound while FreeBSD is/can not? I admit my > understanding of PC hardware to be limited, but I had thought that the > purpose of the BIOS was to "initialize" the hardware for the OS to > recognize. Doesn't it hand out IRQs and so forth? The bios is more like a wakeup call, it tells things that need to be told to wake up and say hello, anything after that is up to the hardware, more than likley it's a quirk in the particular peice of hardware, something about the way it works that differes just enough from the norm to need special attention to get it going. > Is my problem indicative of a general driver deficiency in FreeBSD? > Is there some module I'm not aware of that, were I to load it, take > care of this mysterious "initialization" ? No, this looks like a device specific quirk, like how the 3com 905c will always try and share irq's with my soundcard in my home machine regardless of anything i do yet in other machines it behaves itself :) With the sheer amount of hardware and variations on hardware available these things are to be occasionaly expected :) ----------------- Mike Woods IT Technician