From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on finch.gentoo.org X-Spam-Level: X-Spam-Status: No, score=-0.1 required=5.0 tests=DMARC_NONE, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=unavailable autolearn_force=no version=4.0.0 Received: from bashful.cdf.toronto.edu (bashful.cdf.toronto.edu [128.100.31.157]) by chiba.3jane.net (Postfix) with ESMTP id 3F9F0ABD51 for ; Wed, 1 May 2002 23:37:47 -0500 (CDT) Received: by bashful.cdf.toronto.edu (Postfix, from userid 191) id C5BA04005CF; Thu, 2 May 2002 00:37:14 -0400 (EDT) To: gentoo-dev@gentoo.org From: Arcady Genkin Subject: Re: [gentoo-dev] Unmasking latest ALSA modules References: <878z777m09.fsf@tea.thpoon.com> <20020429141457.7bbc0e07.spider@gentoo.org> <20020430054215.5c48eb7f.spider@gentoo.org> <20020430121554.236b05f3.spider@gentoo.org> X-Face: 0=A/O5-+sE[Tf%X>rYr?Y5LD4,:^'jaJ!4jC&UR*ZrrK2>^`g22Qeb]!:d;}2YJ|Hq"LHdF OX`jWX|AT-WVFQ(TPhFVak)0nt$aEdlOq=1~D,:\z5QlVOrZ2(H,mKg=Xr|'VlHA="r Date: Thu, 02 May 2002 00:37:14 -0400 Message-ID: User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Common Lisp, i686-pc-linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: gentoo-dev-admin@gentoo.org Errors-To: gentoo-dev-admin@gentoo.org X-BeenThere: gentoo-dev@gentoo.org X-Mailman-Version: 2.0.6 Precedence: bulk Reply-To: gentoo-dev@gentoo.org List-Help: List-Post: List-Subscribe: , List-Id: Gentoo Linux developer list List-Unsubscribe: , List-Archive: X-Archives-Salt: 2e199e9f-ecda-4260-acaf-075cb62bdb23 X-Archives-Hash: c3c5a5ef7f8c7fd6d6a7a22b705a4e05 Spider writes: >> Maybe we should modprobe them from alsasound startup script? >> Or, perhaps, start alsasound before modules are autoloaded? > > to load alsasound before modules would very well be possible. I just tried doing the former, and neither adding "before modules" to the alsasound init script, nor adding "use alsa-modules" to the modules init script ensured that alsasound init script is executed *before* modules... Am I missing something obvious? > or register them as /dev/dsp and /dev/mixer and make them autoload > by means of kernel/devfsd? I have only rudimentary knowledge of the devfs workings/config... If anyone thiks that this is a better way than ordering the init scripts, and knows how to do the above, I'd be much obliged for a pointer on this. I'm going to unmask alsa 0.9 in the meanwhile. -- Arcady Genkin