Gentoo Archives: gentoo-user

From: Fernando Rodriguez <cyklonite@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Strange hickups while trying to compile a kernel in a chroot
Date: Sat, 25 Feb 2017 13:31:26
Message-Id: e8399950-6a34-0edc-15ff-533a6aa3c97f@gmail.com
In Reply to: [gentoo-user] Strange hickups while trying to compile a kernel in a chroot by Meino.Cramer@gmx.de
1 On 02/25/2017 07:23 AM, Meino.Cramer@×××.de wrote:
2 > hi,
3 >
4 > I am trying to build a linux kernel (vanilla from ftp.kernel.org)
5 > in my chrooted new root.
6 >
7 > make modules install
8 >
9 > failed
10 >
11 > with:
12 >
13 > CHK include/config/kernel.release
14 > CHK include/generated/uapi/linux/version.h
15 > CHK include/generated/utsrelease.h
16 > CHK include/generated/bounds.h
17 > CHK include/generated/timeconst.h
18 > CHK include/generated/asm-offsets.h
19 > CALL scripts/checksyscalls.sh
20 > CHK include/generated/compile.h
21 > ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs'
22 > make[1]: *** [usr/Makefile:73: usr/initramfs_data.cpio.gz] Error 1
23 > make: *** [Makefile:988: usr] Error 2
24 >
25 >
26 > make bImage fails with
27 >
28 > (chroot) make bzImage
29 > CHK include/config/kernel.release
30 > CHK include/generated/uapi/linux/version.h
31 > CHK include/generated/utsrelease.h
32 > CHK include/generated/bounds.h
33 > CHK include/generated/timeconst.h
34 > CHK include/generated/asm-offsets.h
35 > CALL scripts/checksyscalls.sh
36 > CHK include/generated/compile.h
37 > ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs'
38 > make[1]: *** [usr/Makefile:73: usr/initramfs_data.cpio.gz] Error 1
39 > make: *** [Makefile:988: usr] Error 2
40 >
41 >
42 > I look for the magic v83d and found (being at my old root)
43 >
44 > [I] sys-apps/v86d
45 > Available versions: 0.1.10 {debug x86emu}
46 > Installed versions: 0.1.10(02:34:27 02/28/11)(x86emu -debug)
47 > Homepage: https://dev.gentoo.org/~spock/projects/uvesafb/
48 > Description: A daemon to run x86 code in an emulated environment
49 >
50 > Is this "quite normal" or does the make process of the kernel make
51 > false conclusion while being chrooted?
52 >
53 > Do I really need initram? ... For years I though my grub had
54 > booted the kernel which runs my linux directlu...
55 >
56 > My commandline to build the kernel at my old root was:
57 >
58 > 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
59 >
60 > whjch had.
61 >
62 > v86d is not installed yet and of course I will install it if needed.
63 > But I want to get shure, that the chrooted environment has not
64 > confused the kernel build process...
65 >
66 > Thanks for any help in advance!
67 > Cheers
68 > Meino
69
70 Check the CONFIG_INITRAMFS_SOURCE option.
71
72 How did you configure the kernel? Did you used the .config file from
73 your root system or perhaps ran make oldconfig (I think it tries to use
74 /proc/config.gz if it can't find it in /boot)?
75
76
77
78 --
79
80 Fernando Rodriguez

Replies