Re: [gentoo-user] alsa-driver emerge error
Stuart Howard schreef: 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. Well, there is a compromise solution: /etc/portage/profile/package.provided I don't have a clue what I tried to install that wanted alsa-driver, but I added media-sound/alsa-driver-1.0.6a (don't actually have to have a version, afaik, you can just put the package name) to the above-mentioned file, and it never bothered me again. Basically, you're telling Portage that you've handled this-- the package is installed, just not *by* Portage, so it should just trust you. And of course you have installed the package-- when you compiled the kernel, so it's not even like you're lying or anything. The upside of this should be that you can uninstall the alsa-driver package (if it is installed), or do an emerge (-p) --depclean to get rid of it, or remove it from your world file, and no program that depends on it should be disturbed (because you've informed Portage that the equivalent data is available, and Portage trusts you :-) )-- and no package that wants to depend on it in the future should try to install it. HTH, Holly -- gentoo-user@gentoo.org mailing list
Re: [gentoo-user] alsa-driver emerge error
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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
Re: [gentoo-user] alsa-driver emerge error
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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
Re: [gentoo-user] alsa-driver emerge error
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 [EMAIL PROTECTED] 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
Re: [gentoo-user] alsa-driver emerge error
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 In the gentoo alsa guide lists the pros and cons of alsa-driver vs. the alsa modules from kernel.org. If alsa already works then you don't need alsa-driver. Portage would certainly notify you of any dependency. After you prune the world file, you can use emerge -a depclean to remove unneeded packages. Of course, after a depclean (or any library changes), revdep-rebuild may be necessary. Zac -- gentoo-user@gentoo.org mailing list
[gentoo-user] alsa-driver emerge error
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
Re: [gentoo-user] alsa-driver emerge error
OK well it looks like I have been neglecting my admin duties I am going to proceed with removing the alsa-driver and then go from there, Holly thx for the workaround but I do not feel confident in me ;) I will trust the powers that be and make portage happy, my theory being that portage manages a safe secure stable system and why should I choose to break it. Anyway, on further investigation ie. a revdeprebuild and a emerge p --depclean [as suggested] it seems I have a fair few problems. Lots of nasty red messages saying eek!! [mmm I digress it seems, must return to topic] so revdep is complaining at firefox, probably due to my changing from compiled to bin and the depclean would like to remove 134 packages!! On further reading I think that adding -gnome to /etc/make.conf was hasty [I use xfce but still enjoy a few gnome packages] I will have to do some investigating. On the plus side my daily emerge world has just completed as I was writing this so that is good and sound appears to work though I have not yet rebooted --loathed to do it, reminds me of days on the dark side. well thx people, I will be back should all go horribly wrong :) stu On 7/18/05, Holly Bostick [EMAIL PROTECTED] wrote: Stuart Howard schreef: 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. Well, there is a compromise solution: /etc/portage/profile/package.provided I don't have a clue what I tried to install that wanted alsa-driver, but I added media-sound/alsa-driver-1.0.6a (don't actually have to have a version, afaik, you can just put the package name) to the above-mentioned file, and it never bothered me again. Basically, you're telling Portage that you've handled this-- the package is installed, just not *by* Portage, so it should just trust you. And of course you have installed the package-- when you compiled the kernel, so it's not even like you're lying or anything. The upside of this should be that you can uninstall the alsa-driver package (if it is installed), or do an emerge (-p) --depclean to get rid of it, or remove it from your world file, and no program that depends on it should be disturbed (because you've informed Portage that the equivalent data is available, and Portage trusts you :-) )-- and no package that wants to depend on it in the future should try to install it. HTH, Holly -- 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
