From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1Ducba-0000Fw-Ir for garchives@archives.gentoo.org; Mon, 18 Jul 2005 20:52:50 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6IKnE5T024436; Mon, 18 Jul 2005 20:49:15 GMT Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.204]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6IKbsDa009035 for ; Mon, 18 Jul 2005 20:37:54 GMT Received: by rproxy.gmail.com with SMTP id i8so1381375rne for ; Mon, 18 Jul 2005 13:38:46 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=uscRZOvOWK+X8gPUB7WiCmbllIsQXk+qdCvNg2418jCck9iuEP0TVw8/UqDjTMvxDnMaPm4pPttuaygQ3hCy3g1tf5LmsC+zSoPnExL3u0XpqvBmkI5owa6hBE6xz32P6T0fro+qnAm7U8fXMu9ILuxzQGoAwPSW3fr89IlksLU= Received: by 10.39.3.25 with SMTP id f25mr2219588rni; Mon, 18 Jul 2005 13:38:46 -0700 (PDT) Received: by 10.38.78.42 with HTTP; Mon, 18 Jul 2005 13:38:45 -0700 (PDT) Message-ID: <342e109050718133816254405@mail.gmail.com> Date: Mon, 18 Jul 2005 17:38:45 -0300 From: Daniel da Veiga To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] alsa-driver emerge error In-Reply-To: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <342e109050718113217b45ff9@mail.gmail.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id j6IKbsDa009035 X-Archives-Salt: 5afe2dbf-c89a-42cd-a02d-3107ca907321 X-Archives-Hash: 38720ded91d00b289437175f8e0c7a55 Oh, I see... Well, since you have it builtin and everything is working, maybe its dependent on other app, do you have alsa-utils or anything that could pull alsa-drivers? If you have an old installation and (like me) don't remember exactly the steps for the initial configuration (I used alsa-driver, builtin, then removed it lots of times, recompiled the kernel lots, test purposes) then it can be a leftover from a previous config. Now, to determine if you can or can't remove it its up to you, you can always remove it and emerge it again if any problem appear. And if everything fails, you can always remove it from the kernel and emerge alsa-driver :) On 7/18/05, Stuart Howard wrote: > thx for the response > > I think we missed each other with the point though, currently my sound > works just fine and I am happy with it as it is [ie. built in] I am > not sure where the alsa driver in "world" came from unless it is a > hangover from my initial genkernel instalation. > I would like to remove this package from my system simply because I > "think" I dont need it, this being the bit I am not sure about. > I am afraid that there are two things on linux that I have never got > on well with, sound and optical drives. :) > > stu > > > > On 7/18/05, Daniel da Veiga wrote: > > In order to use alsa-driver, you must not have alsa compiled in the > > kernel, I dunno exactly how you got this error using alsa already if > > everything was working before (unless you changed any settings on your > > kernel config). Enable only the audio support, compile modules for > > your sound-cards and let alsa-driver do the rest. > > > > On 7/18/05, Stuart Howard wrote: > > > Hi > > > > > > I think I know why I have this error but I woul like another view > > > before I -aCv the package, the error from this mornings emerge -aDuv > > > world was :- > > > > > > checking for built-in ALSA... "yes" > > > configure: error: You have built-in ALSA in your kernel. > > > > > > !!! Please attach the config.log to your bug report: > > > !!! /var/tmp/portage/alsa-driver-1.0.9b/work/alsa-driver-1.0.9b/config.log > > > > > > !!! ERROR: media-sound/alsa-driver-1.0.9b failed. > > > !!! Function econf, Line 485, Exitcode 0 > > > !!! econf failed > > > !!! If you need support, post the topmost build error, NOT this status message. > > > > > > I skipped some of the less seemingly pertinent bits, my kernel is > > > currently 2.6.11.5 and ALSA is built into it whereas when I first > > > installed Gentoo [~6 months ago] I used genkernel which IIRC built > > > ALSA as modules which I think has led me to the above error. > > > I checked the changelog and this package > > > media-sound/alsa-driver-1.0.9b was last made x86 in febuary which may > > > have been before I installed gentoo hence I think why my world is > > > trying to install it even though I do not require it. > > > > > > Could someone confirm [or guide anyway ] for me that my "guess" is > > > right and that I will be safe to remove the package. > > > Alternatively I have got completly the wrong end of the stick and I am > > > about to kill my system :) > > > in which case a big NO!! dont do it will suffice . > > > > > > thanks stu > > > > > > > > > -- > > > "There are 10 types of people in this world: those who understand > > > binary, those who don't" > > > > > > --Unknown > > > > > > -- > > > gentoo-user@gentoo.org mailing list > > > > > > > > > > > > -- > > Daniel da Veiga > > Computer Operator - RS - Brazil > > > > -- > > gentoo-user@gentoo.org mailing list > > > > > > > -- > "There are 10 types of people in this world: those who understand > binary, those who don't" > > --Unknown > > -- > gentoo-user@gentoo.org mailing list > > -- Daniel da Veiga Computer Operator - RS - Brazil -- gentoo-user@gentoo.org mailing list