1 |
Fernando Rodriguez <cyklonite@×××××.com> [17-02-25 14:36]: |
2 |
> On 02/25/2017 07:23 AM, Meino.Cramer@×××.de wrote: |
3 |
> > hi, |
4 |
> > |
5 |
> > I am trying to build a linux kernel (vanilla from ftp.kernel.org) |
6 |
> > in my chrooted new root. |
7 |
> > |
8 |
> > make modules install |
9 |
> > |
10 |
> > failed |
11 |
> > |
12 |
> > with: |
13 |
> > |
14 |
> > CHK include/config/kernel.release |
15 |
> > CHK include/generated/uapi/linux/version.h |
16 |
> > CHK include/generated/utsrelease.h |
17 |
> > CHK include/generated/bounds.h |
18 |
> > CHK include/generated/timeconst.h |
19 |
> > CHK include/generated/asm-offsets.h |
20 |
> > CALL scripts/checksyscalls.sh |
21 |
> > CHK include/generated/compile.h |
22 |
> > ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs' |
23 |
> > make[1]: *** [usr/Makefile:73: usr/initramfs_data.cpio.gz] Error 1 |
24 |
> > make: *** [Makefile:988: usr] Error 2 |
25 |
> > |
26 |
> > |
27 |
> > make bImage fails with |
28 |
> > |
29 |
> > (chroot) make bzImage |
30 |
> > CHK include/config/kernel.release |
31 |
> > CHK include/generated/uapi/linux/version.h |
32 |
> > CHK include/generated/utsrelease.h |
33 |
> > CHK include/generated/bounds.h |
34 |
> > CHK include/generated/timeconst.h |
35 |
> > CHK include/generated/asm-offsets.h |
36 |
> > CALL scripts/checksyscalls.sh |
37 |
> > CHK include/generated/compile.h |
38 |
> > ./scripts/gen_initramfs_list.sh: Cannot open '/usr/share/v86d/initramfs' |
39 |
> > make[1]: *** [usr/Makefile:73: usr/initramfs_data.cpio.gz] Error 1 |
40 |
> > make: *** [Makefile:988: usr] Error 2 |
41 |
> > |
42 |
> > |
43 |
> > I look for the magic v83d and found (being at my old root) |
44 |
> > |
45 |
> > [I] sys-apps/v86d |
46 |
> > Available versions: 0.1.10 {debug x86emu} |
47 |
> > Installed versions: 0.1.10(02:34:27 02/28/11)(x86emu -debug) |
48 |
> > Homepage: https://dev.gentoo.org/~spock/projects/uvesafb/ |
49 |
> > Description: A daemon to run x86 code in an emulated environment |
50 |
> > |
51 |
> > Is this "quite normal" or does the make process of the kernel make |
52 |
> > false conclusion while being chrooted? |
53 |
> > |
54 |
> > Do I really need initram? ... For years I though my grub had |
55 |
> > booted the kernel which runs my linux directlu... |
56 |
> > |
57 |
> > My commandline to build the kernel at my old root was: |
58 |
> > |
59 |
> > 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 |
60 |
> > |
61 |
> > whjch had. |
62 |
> > |
63 |
> > v86d is not installed yet and of course I will install it if needed. |
64 |
> > But I want to get shure, that the chrooted environment has not |
65 |
> > confused the kernel build process... |
66 |
> > |
67 |
> > Thanks for any help in advance! |
68 |
> > Cheers |
69 |
> > Meino |
70 |
> |
71 |
> Check the CONFIG_INITRAMFS_SOURCE option. |
72 |
> |
73 |
> How did you configure the kernel? Did you used the .config file from |
74 |
> your root system or perhaps ran make oldconfig (I think it tries to use |
75 |
> /proc/config.gz if it can't find it in /boot)? |
76 |
> |
77 |
> |
78 |
> |
79 |
> -- |
80 |
> |
81 |
> Fernando Rodriguez |
82 |
> |
83 |
|
84 |
Hi Fernando, |
85 |
|
86 |
I used the config I used for building the kernel of the 'old' root. |
87 |
The new root is intended to replace the old root on the same machine. |
88 |
Its even the same kernel source... |
89 |
So everything should fine. |
90 |
Even if it will use /proc/config.gz it will find the config of |
91 |
the current kernel running the old root (and that way the chrooted |
92 |
rooot). |
93 |
|
94 |
....scratching my head... |
95 |
|
96 |
I will check the configs...may be there is something not readable |
97 |
(permissions) ... I had copied a lot back and forth (I bought one |
98 |
of those crappy harddiscs, which became full after a while...;) |
99 |
|
100 |
Cheers |
101 |
Meino |