Sabayon Community

by **xipi** » Fri Aug 21, 2009 17:13

I've installed Sabayon 4.2 x86 on my laptop, and tried to update its kernel (2.6.29) to the latest available from linux sabayon (2.6.30). I did an "emerge linux-sabayon", and succesfully compiles.

But then, it complains about certain file collisions of files with .fw extension in the /lib folder in my system, so it stops and eventually does not merge the package.

I wonder what could have I done wrong, since I think the operation I'm trying to perform is pretty basic - and I'm reluctant to try "dirty" things that could break down my system (as for instance, deleting those files having collisions, unmerging the old kernel before merging the new one...).

I should also say that I've completely removed Entropy from my system (or at least I tried doing so, with emerge -C equo entropy sulfur). Might that have broken something out?

by **albfneto** » Fri Aug 21, 2009 23:00

removing all the entropy cannot break you system, put if you want to re-install it, usin emerge, this may break you system..., because python is in other version.
if you removed entropy, naturaly, you cannot more use it, only portage...

COllisions...

collisions are regularly a protection in Gentoo and Gentoo like systems.. are normal, they not indicates system breakage.

In general, they are two methods for solve collisions....

1) If the collident packages are few, remove the collident packages and after install the package that you want, re-install the collidents...
ex;;; emerge pack1 no works because colisions of pack 1 old version and pack 2...
remove pack 1 old, then remove pack 2, the re install pack1, and after re install pack 2, the pack 1 old cannot more necessary since is older!

2) if the collisions are many... edit the /etc/make.conf a comment (with #) the line:

Code: Select all: FEATURES="parallel-fetch collision-protect"

the save and install the packages, and after UNCOMMENT the line to reactivate collision protection

by **wolfden** » Sat Aug 22, 2009 4:46

if u are emerging sources you should be doing emerge sabayon-sources

viewtopic.php?f=54&t=17718

by **xipi** » Sat Aug 22, 2009 18:52

I currently have kernel 2.6.29, which is the one that came with SL 4.2 base installation.

I want to update to 2.6.30. Furthermore, I also want to have the sources for this kernel.

I assume that, using portage, following applies:

-To install the new available version in the kernel (which is compiled from sources, I guess as per its ebuild specification), I need to do:

Code: Select all: emerge linux-sabayon

-Afterwards, if I want to have the source code for this kernel into my /usr/src/ directory, I should do:

Code: Select all: emerge linux-sabayon-sources

(I assume the name of the package is no longer "sabayon-sources" but "linux-sabayon-sources" now).

If I understand it correctly, the first step compiles the kernel "behind the scenes" and installs the new kernel (initrd, bzImage, grub...). The second step just places the sources into the /usr/src without compiling them.

I want both. But I'm stuck in the first step.

The problem then is that there is a collision in the last stages of the first step. Not a package collision, but a file collision. It says that some .fw extension files in my /lib/firmware folder collide with the ones that the ebuild for 2.6.30 is trying to copy.

I assume that, if the ebuild is trying to copy these files, these files belong to the kernel package. If they are on my system, they should be for kernel 2.6.29 (the one installed in my box). So, if I follow your advice, I should unmerge the old kernel before installing the new one. Isn't that a bit awkward?

by **albfneto** » Mon Aug 24, 2009 2:33

for complete undestand the problem, please copy and paste the output of the commands that you used for try to install the kernel

by **xipi** » Mon Aug 24, 2009 21:57

Code: Select all: xipi640m josep # emerge linux-sabayon Calculating dependencies... done! >>> Verifying ebuild manifests >>> Emerging (1 of 1) sys-kernel/linux-sabayon-2.6.30 from sabayon * 2.6.30-3.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * linux-2.6.30.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * Preparing to build the kernel and its modules >>> Unpacking source... >>> Unpacking linux-2.6.30.tar.bz2 to /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work >>> Unpacking 2.6.30-3.tar.bz2 to /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/patches/000001 * Applying 2.6.30.5.patch (-p0+) ... [ ok ] * Applying current-tuxonice-for-2.6.30.patch-20090620-v1.patch (-p0+) ... [ ok ] * Applying linux-sabayon-2.6.30-aufs.patch (-p0+) ... [ ok ] * Applying 4100_dm-bbr.patch (-p0+) ... [ ok ] * Applying 4201_fbcondecor-0.9.6.patch (-p0+) ... [ ok ] * Applying 4400_alpha-sysctl-uac.patch (-p0+) ... [ ok ] >>> Source unpacked in /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work >>> Compiling source in /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/linux-2.6.30-sabayon ... * Starting to compile kernel... * Gentoo Linux Genkernel; Version 3.4.10 * Running with options: --splash=sabayon --dmraid --kerneldir=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/linux-2.6.30-sabayon --kernel-config=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/config --cachedir=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/cache --makeopts=-j3 --tempdir=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/linux-2.6.30-sabayon/temp --logfile=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/genkernel.log --bootdir=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/boot --mountboot --lvm --luks --disklabel --module-prefix=/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/lib all * Linux Kernel 2.6.30-sabayon for x86... * kernel: >> Running mrproper... * config: Using config from /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/config * Previous config backed up to .config.bak * >> Running oldconfig... * kernel: >> Cleaning... * kernel: >> Making dependencies... * >> Compiling 2.6.30-sabayon bzImage... * >> Compiling 2.6.30-sabayon modules... * Copying config for successful build to /etc/kernels/kernel-config-x86-2.6.30-sabayon * e2fsprogs: >> Configuring... * e2fsprogs: >> Compiling... * blkid: >> Copying to cache... * busybox: >> Applying patches... * busybox: >> Configuring... * busybox: >> Compiling... * busybox: >> Copying to cache... * initramfs: >> Initializing... * >> Appending base_layout cpio data... * >> Appending auxilary cpio data... * Including LUKS support * >> Appending busybox cpio data... * >> Appending lvm cpio data... * LVM: Adding support (using local static binaries)... * >> Appending dmraid cpio data... * DMRAID: Adding support (compiling binaries)... * device-mapper: >> Compiling... * >> Copying to cache... * dmraid: >> Configuring... * dmraid: >> Compiling... * >> Copying to bincache... * >> Appending modules cpio data... * >> Appending blkid cpio data... * >> Appending splash cpio data... * >> Installing splash [ using the sabayon theme ]... * * Kernel compiled successfully! * * Required Kernel Parameters: * real_root=/dev/$ROOT * * Where $ROOT is the device node for your root partition as the * one specified in /etc/fstab * * If you require Genkernel's hardware detection features; you MUST * tell your bootloader to use the provided INITRAMFS file. Otherwise; * substitute the root argument for the real_root argument if you are * not planning to use the initrd... * WARNING... WARNING... WARNING... * Additional kernel cmdline arguments that *may* be required to boot properly... * add "vga=791 splash=silent,theme:sabayon console=tty1 quiet" if you use a splash framebuffer ] * add "dolvm" for lvm support * add "dodmraid" for dmraid support * or "dodmraid=<additional options>" * Do NOT report kernel bugs as genkernel bugs unless your bug * is about the default genkernel configuration... * * Make sure you have the latest genkernel before reporting bugs. rm: no s’ha pogut eliminar el directori «/var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/work/linux-2.6.30-sabayon/temp/7291.27244.460.8340»: El directori no és buit >>> Source compiled. >>> Test phase [not enabled]: sys-kernel/linux-sabayon-2.6.30 >>> Install linux-sabayon-2.6.30 into /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/image/ category sys-kernel >>> Completed installing linux-sabayon-2.6.30 into /var/tmp/portage/sys-kernel/linux-sabayon-2.6.30/image/ strip: i686-pc-linux-gnu-strip --strip-unneeded -R .comment lib/modules/2.6.30-sabayon/kernel/fs/9p/9p.ko [...] lib/modules/2.6.30-sabayon/kernel/crypto/michael_mic.ko >>> Installing (1 of 1) sys-kernel/linux-sabayon-2.6.30 * This package will overwrite one or more files that may belong to other * packages (see list below). You can use a command such as `portageq * owners / <filename>` to identify the installed package that owns a * file. If portageq reports that only one package owns a file then do * NOT file a bug report. A bug report is only useful if it identifies at * least two or more packages that are known to install the same file(s). * If a collision occurs and you can not explain where the file came from * then you should simply ignore the collision since there is not enough * information to determine if a real problem exists. Please do NOT file * a bug report at http://bugs.gentoo.org unless you report exactly which * two packages install the same file(s). Once again, please do NOT file * a bug report unless you have completely understood the above message. * * package sys-kernel/linux-sabayon-2.6.30 NOT merged * * Detected file collision(s): * * /lib/firmware/ti_3410.fw * /lib/firmware/mts_cdma.fw * /lib/firmware/whiteheat.fw * /lib/firmware/tr_smctr.bin * /lib/firmware/ti_5052.fw * /lib/firmware/mts_edge.fw * /lib/firmware/intelliport2.bin * /lib/firmware/whiteheat_loader.fw * /lib/firmware/atmsar11.fw * /lib/firmware/mts_gsm.fw * /lib/firmware/ess/maestro3_assp_kernel.fw * /lib/firmware/ess/maestro3_assp_minisrc.fw * /lib/firmware/sun/cassini.bin * /lib/firmware/e100/d102e_ucode.bin * /lib/firmware/e100/d101s_ucode.bin * /lib/firmware/e100/d101m_ucode.bin * /lib/firmware/korg/k1212.dsp * /lib/firmware/cpia2/stv0672_vp4.bin * /lib/firmware/emi26/loader.fw * /lib/firmware/emi26/bitstream.fw * /lib/firmware/emi26/firmware.fw * /lib/firmware/emi62/spdif.fw * /lib/firmware/emi62/midi.fw * /lib/firmware/emi62/loader.fw * /lib/firmware/emi62/bitstream.fw * /lib/firmware/tigon/tg3_tso5.bin * /lib/firmware/tigon/tg3.bin * /lib/firmware/tigon/tg3_tso.bin * /lib/firmware/vicam/firmware.fw * /lib/firmware/keyspan_pda/keyspan_pda.fw * /lib/firmware/keyspan_pda/xircom_pgs.fw * /lib/firmware/acenic/tg1.bin * /lib/firmware/acenic/tg2.bin * /lib/firmware/kaweth/trigger_code.bin * /lib/firmware/kaweth/trigger_code_fix.bin * /lib/firmware/kaweth/new_code.bin * /lib/firmware/kaweth/new_code_fix.bin * /lib/firmware/adaptec/starfire_rx.bin * /lib/firmware/adaptec/starfire_tx.bin * /lib/firmware/ttusb-budget/dspbootcode.bin * /lib/firmware/yamaha/ds1_dsp.fw * /lib/firmware/yamaha/ds1_ctrl.fw * /lib/firmware/yamaha/ds1e_ctrl.fw * /lib/firmware/edgeport/down3.bin * /lib/firmware/edgeport/down2.fw * /lib/firmware/edgeport/down.fw * /lib/firmware/edgeport/boot.fw * /lib/firmware/edgeport/boot2.fw * * Searching all installed packages for file collisions... * * Press Ctrl-C to Stop * * sys-kernel/linux-sabayon-2.6.29 * /lib/firmware/acenic/tg1.bin * /lib/firmware/acenic/tg2.bin * /lib/firmware/adaptec/starfire_rx.bin * /lib/firmware/adaptec/starfire_tx.bin * /lib/firmware/atmsar11.fw * /lib/firmware/cpia2/stv0672_vp4.bin * /lib/firmware/e100/d101m_ucode.bin * /lib/firmware/e100/d101s_ucode.bin * /lib/firmware/e100/d102e_ucode.bin * /lib/firmware/edgeport/boot.fw * /lib/firmware/edgeport/boot2.fw * /lib/firmware/edgeport/down.fw * /lib/firmware/edgeport/down2.fw * /lib/firmware/edgeport/down3.bin * /lib/firmware/emi26/bitstream.fw * /lib/firmware/emi26/firmware.fw * /lib/firmware/emi26/loader.fw * /lib/firmware/emi62/bitstream.fw * /lib/firmware/emi62/loader.fw * /lib/firmware/emi62/midi.fw * /lib/firmware/emi62/spdif.fw * /lib/firmware/ess/maestro3_assp_kernel.fw * /lib/firmware/ess/maestro3_assp_minisrc.fw * /lib/firmware/intelliport2.bin * /lib/firmware/kaweth/new_code.bin * /lib/firmware/kaweth/new_code_fix.bin * /lib/firmware/kaweth/trigger_code.bin * /lib/firmware/kaweth/trigger_code_fix.bin * /lib/firmware/keyspan_pda/keyspan_pda.fw * /lib/firmware/keyspan_pda/xircom_pgs.fw * /lib/firmware/korg/k1212.dsp * /lib/firmware/mts_cdma.fw * /lib/firmware/mts_edge.fw * /lib/firmware/mts_gsm.fw * /lib/firmware/sun/cassini.bin * /lib/firmware/ti_3410.fw * /lib/firmware/ti_5052.fw * /lib/firmware/tigon/tg3.bin * /lib/firmware/tigon/tg3_tso.bin * /lib/firmware/tigon/tg3_tso5.bin * /lib/firmware/tr_smctr.bin * /lib/firmware/ttusb-budget/dspbootcode.bin * /lib/firmware/vicam/firmware.fw * /lib/firmware/whiteheat.fw * /lib/firmware/whiteheat_loader.fw * /lib/firmware/yamaha/ds1_ctrl.fw * /lib/firmware/yamaha/ds1_dsp.fw * /lib/firmware/yamaha/ds1e_ctrl.fw * * Package 'sys-kernel/linux-sabayon-2.6.30' NOT merged due to file * collisions. If necessary, refer to your elog messages for the whole * content of the above message. >>> Failed to install sys-kernel/linux-sabayon-2.6.30, Log file: >>> '/var/lib/entropy/logs/sys-kernel:linux-sabayon-2.6.30:20090824-203824.

by **wolfden** » Mon Aug 24, 2009 23:49

emerge sabayon-sources like the link I provided for u says

That will download the sources than follow the wiki on using genkernel to compile kernel.
http://wiki.sabayonlinux.org/index.php? ... _genkernel

linux-sabayon is the binary

by **xipi** » Tue Aug 25, 2009 9:13

Thanks. I will try that.

Anyway, I think that the way I tried should also work. Do you know why it doesn't?

Btw, what's the difference between sabayon-sources and linux-sabayon-soruces, aside of your level of happyness?

Code: Select all: * sys-kernel/linux-sabayon-sources [1] Available versions: (2.6.30) (~)2.6.30 {build symlink} Homepage: http://www.sabayonlinux.org Description: Official Sabayon Linux Standard kernel sources * sys-kernel/sabayon-sources [1] Available versions: (2.6.29) (~)2.6.29 (2.6.30) (~)2.6.30 {build symlink} Homepage: http://www.sabayon.org Description: Sabayon Linux kernel sources meta-package [b](makes wolfden happy)[/b] [1] "sabayon" /usr/local/portage/layman/sabayon Found 2 matches.

Greetings,

by **wolfden** » Tue Aug 25, 2009 22:32

The original name for our kernel was sabayon-sources, but it all got split up and name changed when binary came around, which is linux-sabayon, so the users kept trying to emerge linux-sabayon the binary package, which only gave mass problems. So I requested that sabayon-sources be brought back, which is a meta package for linux-sabayon-sources. The idea was to make it simple and easy for the users to understand that one is binary and one is source. The users are hung up with linux-sabayon, which is the binary package for entropy. sabayon-sources aka linux-sabayon-sources is for portage users to grab the source files and build the kernel with genkernel or other means.

So if we keep it simple with sabayon-sources, people will stop emerging linux-sabayon hopefully.

Sabayon Community

Problem emerging linux-sabayon 2.6.30 on SL4.2

Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Re: Problem emerging linux-sabayon 2.6.30 on SL4.2

Who is online