Problem generated emerge alsa Kernel Broken No boot [Solved]

[albfneto]

In one of my sabayon installed:

i was using amarok for reproduce radio stream... working well...
i updated cairo and cairo-dock, and during this updating... Amarok no more works, message mms plugin no found!
trying to solve this, i closed amarok and tried to update it.....
it was updated, but with no more sound... Comp general sound,also lost!
try to reconfigure alsa........ message that sound server broken....
finally,i tried to update or re-install alsa:

# emerge -C alsa
# emerge -av alsa

The portage recognized Kernel as main dependence.....! and removed sabayon 26 and 25 kernel!
this installation,no more boots!
Is there something that lies Cairo, cairo Dock, alsa, amarok and the kernels?
is a command "emerge alsa" dangerous?

[albfneto]

seeing in the net, i have in mind that this is related with two anitque reports in Gentoo Bugzilla:

http://bugs.gentoo.org/65781
http://bugs.gentoo.org/40311


When i tried to update ALSA, since ALSA is compiled with the kernel (after kernei 2.6), remove alsa, also removed the kernels, 2.6.25 and 2.6.26....

[albfneto]

Kernel damaged, removed, both 2.6.26 and 2.6.25...
Grub not restored due to broken kernels..
solved with the rescue disc of the 3.5.1.
some application should be re-installed,but working.
the question is open...
Why the kernels were broken bu a emerge -C alsa?, because this command removed my kernels?
this is a testing Sabayon ( i have four installations,in four comps)
i mix the installers, because i had mixed prior, in these installation....
in fact, no problems in an Sabayon that i use only Entropy, and other when i use only Portage.
in fact all the problems occurs when the installers were mixed...
Solved!

[wolfden]

well this is confusing,

there is no package alsa
alsa won't compile if it is built into the kernel

if you do emerge alsa - you pull kernel
if you do emerge -C alsa - you pull kernel

That is why your kernels went bye bye

use the --ask or --pretend in portage when you are not familiar with things first. emerge -a << get in the habit of it.

So you never installed alsa as there is no alsa package nor would of built with kernel as it's built it, so there was no alsa to uninstall in the first place.

Understand your kernel and how it is built and also understand the package managers you are using, a simple --ask would of saved a pile of frustration. As far as why it's this way - check with gentoo devs. It all comes together over time with usage.

You can recompile your kernel without alsa built in and emerge alsa-drivers if you want to go that route.

Regardless --ask is your friend

[albfneto]

This (when i write this) is a sabayon installation in wich i use only Entropy.
i said,i have other, in which i use only Portage.
as soon i will log in other comp,i n one of my "mixed" installers Sabayons, and i will try the command emerge -C alsa with options --ask --pretend, and post the result. the output of the command....
yes do, i have in mind that the problem is connected with the two reports in the Gentoo Bugzilla that i post...
Only after the commands,i see that the ALSA is enclosed in the kernel!
strange because the commands, deleted both (2.6.25 and 2.6.26) kernel packs!

See that is strange.... I booted to another comp, in which i had the problem...i said to you, in this i used the two installers, because months ago i mixed, and had these problems of Entropy-Portage Confusion" between versions of packages... see the ouput of the commands:

Code: Select all

localhost / # emerge -C -p alsa

>>> These are the packages that would be unmerged:

 sys-kernel/linux-sabayon
    selected: 2.6.25-r1 2.6.26
   protected: none
     omitted: none

>>> 'Selected' packages are slated for removal.
>>> 'Protected' and 'omitted' packages will not be removed.


localhost / # emerge --ask alsa

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R   ] sys-kernel/linux-sabayon-2.6.26

Would you like to merge these packages? [Yes/No]             



[wolfden]

but the package is alsa-drivers, not alsa

[albfneto]

yes but i'm still curious! strange that the command remove kernel
the expected for emerge is that, "alsa was not found, these packages have alsa in the name:
alsa-drivers
alsa-mixer.... etc...!
not remove the Kernel;;;;;;!

The evidence is: at least in my comp, "emerge -C alsa is a dangerous command!!!!

[wolfden]

well running any command can be dangerous when not issueing it correctly