Fernando Rodriguez <cyklon...@gmail.com> [17-02-25 14:36]:
> On 02/25/2017 07:23 AM, meino.cra...@gmx.de wrote:
> > hi,
> >
> > I am trying to build a linux kernel (vanilla from ftp.kernel.org)
> > in my chrooted new root.
> >
> > make modules install
> >
> > failed
> >
> > with:
> >
> > CHK include/config/kernel.release
> > CHK include/generated/uapi/linux/version.h
> > CHK include/generated/utsrelease.h
> > CHK include/generated/bounds.h
> > CHK include/generated/timeconst.h
> > CHK include/generated/asm-offsets.h
> > CALL scripts/checksyscalls.sh
> > CHK include/generated/compile.h
> > ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs'
> > make[1]: *** [usr/Makefile:73: usr/initramfs_data.cpio.gz] Error 1
> > make: *** [Makefile:988: usr] Error 2
> >
> >
> > make bImage fails with
> >
> > (chroot) make bzImage
> > CHK include/config/kernel.release
> > CHK include/generated/uapi/linux/version.h
> > CHK include/generated/utsrelease.h
> > CHK include/generated/bounds.h
> > CHK include/generated/timeconst.h
> > CHK include/generated/asm-offsets.h
> > CALL scripts/checksyscalls.sh
> > CHK include/generated/compile.h
> > ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs'
> > make[1]: *** [usr/Makefile:73: usr/initramfs_data.cpio.gz] Error 1
> > make: *** [Makefile:988: usr] Error 2
> >
> >
> > I look for the magic v83d and found (being at my old root)
> >
> > [I] sys-apps/v86d
> > Available versions: 0.1.10 {debug x86emu}
> > Installed versions: 0.1.10(02:34:27 02/28/11)(x86emu -debug)
> > Homepage: https://dev.gentoo.org/~spock/projects/uvesafb/
> > Description: A daemon to run x86 code in an emulated
> > environment
> >
> > Is this "quite normal" or does the make process of the kernel make
> > false conclusion while being chrooted?
> >
> > Do I really need initram? ... For years I though my grub had
> > booted the kernel which runs my linux directlu...
> >
> > My commandline to build the kernel at my old root was:
> >
> > kernel=/boot/vmlinuz-4091200-64-RT && make -j7 all && make -j7
> > modules_install && /bin/cp -f ./arch/x86_64/boot/bzImage* $kernel; emerge
> > nvidia-drivers ;emerge app-emulation/virtualbox-modules ;grub-mkconfig -o
> > /boot/grub/grub.cfg
> >
> > whjch had.
> >
> > v86d is not installed yet and of course I will install it if needed.
> > But I want to get shure, that the chrooted environment has not
> > confused the kernel build process...
> >
> > Thanks for any help in advance!
> > Cheers
> > Meino
>
> Check the CONFIG_INITRAMFS_SOURCE option.
>
> How did you configure the kernel? Did you used the .config file from
> your root system or perhaps ran make oldconfig (I think it tries to use
> /proc/config.gz if it can't find it in /boot)?
>
>
>
> --
>
> Fernando Rodriguez
>
Hi Fernando,
I used the config I used for building the kernel of the 'old' root.
The new root is intended to replace the old root on the same machine.
Its even the same kernel source...
So everything should fine.
Even if it will use /proc/config.gz it will find the config of
the current kernel running the old root (and that way the chrooted
rooot).
....scratching my head...
I will check the configs...may be there is something not readable
(permissions) ... I had copied a lot back and forth (I bought one
of those crappy harddiscs, which became full after a while...;)
Cheers
Meino
