Re: Kernel Compilation Error
[Still top posting.] On Wed, 2014-08-20 at 09:33 +0530, Niamathullah sharief wrote: i TRIED TO SOLVE THIS AND I AM UNABLE TO DO IT. Totally confused. I'm afraid we need more details. You don't want that error during make modules_install, that's clear. But would you like to sign your modules during install (see config MODULE_SIG_ALL in init/Kconfig) or not, etc. And how did you actually try to solve this? Paul Bolle ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel Compilation Error
[Send this to the correct list. Does kernelnewb...@nl.linux.org even exist?] On Tue, 2014-08-19 at 09:48 +0200, Paul Bolle wrote: [fixed top posting.] On Tue, 2014-08-19 at 12:51 +0530, Pramod Gurav wrote: On Tue, Aug 19, 2014 at 12:03 PM, Niamathullah sharief newbie...@gmail.com wrote: when i give make modules_install command i am getting the following error [root@localhost linux-3.15.1]# make modules_install INSTALL arch/x86/crypto/crc32-pclmul.ko Can't read private key make[1]: *** [arch/x86/crypto/crc32-pclmul.ko] Error 2 make: *** [_modinst_] Error 2 It would always be better if you can provide the details of things you are doing and steps you have carried out until it failed. But if I can guess it right you are trying to upgrade kernel on local machine which is x86 based. The failure seems while trying to install newly compiled modules from new kernel(3.15). I am not sure if your compilation has gone well but I think you should be root to install kernel and modules. Try to install the kernel and moudules as root as it installs them in path which is not accessible to user(under /). In Niamathullah Sharief's message I see [root@localhost linux-3.15.1]# make modules_install So it appears make modules_install was run as root (sudo is not installed on that box?). By the way, I've never ran into this error. So I did $ git grep -n Can't read private key scripts/sign-file:38:die Can't read private key\n if (!$signature_file !-r $private_key); If I'd ran into this error myself I'd start with looking at scripts/sign-file and the place(s) where that script is called. Hope this helps. Paul Bolle ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel Compilation Error
[Send this to the correct list again. What a mess...] On Tue, 2014-08-19 at 11:23 +0200, Paul Bolle wrote: [Have you've been lectured on top posting already?] On Tue, 2014-08-19 at 14:30 +0530, Niamathullah sharief wrote: I didnt find the place to enable CONFIG_MODULE_SIG_ALL Its like ifdef CONFIG_MODULE_SIG_ALL MODSECKEY = ./signing_key.priv MODPUBKEY = ./signing_key.x509 export MODPUBKEY mod_sign_cmd = perl $(srctree)/scripts/sign-file $(CONFIG_MODULE_SIG_HASH) $(MODSECKEY) $(MODPUBKEY) else mod_sign_cmd = true endif export mod_sign_cmd Personally I do $ git grep -nw MODULE_SIG_ALL init/Kconfig:1857:config MODULE_SIG_ALL init/Kconfig:1866: depends on MODULE_SIG_FORCE !MODULE_SIG_ALL But you can search for CONFIG_MODULE_SIG_ALL in the interface of make menuconfig too. (I noticed I have both signing_key.priv and signing_key.x509 in the root of my kernel tree. They appear to be, well, faux: grep for slartibartfast@magrathea.h2g2 to see what I mean. These keys are months old, and survived numerous invocations of make clean. I don't remember which command generated them, sorry.) Paul Bolle ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel Compilation Error
i TRIED TO SOLVE THIS AND I AM UNABLE TO DO IT. Totally confused. On Tue, Aug 19, 2014 at 2:54 PM, Paul Bolle pebo...@tiscali.nl wrote: [Send this to the correct list again. What a mess...] On Tue, 2014-08-19 at 11:23 +0200, Paul Bolle wrote: [Have you've been lectured on top posting already?] On Tue, 2014-08-19 at 14:30 +0530, Niamathullah sharief wrote: I didnt find the place to enable CONFIG_MODULE_SIG_ALL Its like ifdef CONFIG_MODULE_SIG_ALL MODSECKEY = ./signing_key.priv MODPUBKEY = ./signing_key.x509 export MODPUBKEY mod_sign_cmd = perl $(srctree)/scripts/sign-file $(CONFIG_MODULE_SIG_HASH) $(MODSECKEY) $(MODPUBKEY) else mod_sign_cmd = true endif export mod_sign_cmd Personally I do $ git grep -nw MODULE_SIG_ALL init/Kconfig:1857:config MODULE_SIG_ALL init/Kconfig:1866: depends on MODULE_SIG_FORCE !MODULE_SIG_ALL But you can search for CONFIG_MODULE_SIG_ALL in the interface of make menuconfig too. (I noticed I have both signing_key.priv and signing_key.x509 in the root of my kernel tree. They appear to be, well, faux: grep for slartibartfast@magrathea.h2g2 to see what I mean. These keys are months old, and survived numerous invocations of make clean. I don't remember which command generated them, sorry.) Paul Bolle ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel compilation
[Forgot to cc list] 2011/5/2 Ezequiel García elezegar...@yahoo.com.ar Greetings, After reading Linux Kernel in a Nutshell (by the way, great book), I now have my own kernel configured for my hardware needs. However, I have some really strange behavior. On tty1, the same tty that launches X11, I have to press twice each keyboard key. Anyone has any idea what's going on? I am using a customized Debian Squeeze + OpenBox. Thanks in advance, and thanks Greg for writing the book. Ezequiel. Hi Ezequiel I'm new on this list as well but I don't think anyone will be able to help you with the limited info that you have provided. When you say you have a kernel configured for your hardware, did you: A) Download the kernel from http://www.kernel.org/ ? In that case you need to tell us which version you're using. B) Get the kernel from git a git tree http://git.kernel.org/? We still need to know exactly which version C) Recompile your debian kernel? (2.6.32?) If this bug is present with only a change in kernel config, it would be interesting to see the difference between the working and broken config. I hope that helps, Pico ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel compilation
Hi Scott :) On Wed, Jan 5, 2011 at 12:34, scott redhowlingwol...@nc.rr.com wrote: I'm new to the list and would like to say hello to everyone. Now on to the meat. I have tried to compile a kernel with a grsec patch 5 times now using a couple of different methods and I keep getting a No init found and Couldn't support optional features errors every time at bootup. I'm trying to use a vanilla 2.6.32.27 kernel on 10.04 Ubuntu and it compiles fine, just will not boot. My first question is: did the patching go successfully? were you applying the correct grsec version against a matching vanilla kernel version? And last, maybe you can attach your kernel .config content...and one of fine people here will try to decipher what's wrong with it :) -- regards, Mulyadi Santosa Freelance Linux trainer and consultant blog: the-hydra.blogspot.com training: mulyaditraining.blogspot.com ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel compilation
On 01/05/2011 01:46 AM, Mulyadi Santosa wrote: Hi Scott :) On Wed, Jan 5, 2011 at 12:34, scottredhowlingwol...@nc.rr.com wrote: I'm new to the list and would like to say hello to everyone. Now on to the meat. I have tried to compile a kernel with a grsec patch 5 times now using a couple of different methods and I keep getting a No init found and Couldn't support optional features errors every time at bootup. I'm trying to use a vanilla 2.6.32.27 kernel on 10.04 Ubuntu and it compiles fine, just will not boot. My first question is: did the patching go successfully? were you applying the correct grsec version against a matching vanilla kernel version? And last, maybe you can attach your kernel .config content...and one of fine people here will try to decipher what's wrong with it :) The patch was matched and was successful. It compiled with no errors. Just the 'no init' at boot. I'll post my .config later today as it's late here and have to work. I'm beginning to think it may have something to do with the limits on file size as I got a few warnings about out-of-range sizes. I have it set to 1024. Thanks for your reply, Scott Thanks for your reply. ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: Kernel compilation
On Wed, 5 Jan 2011, scott wrote: I'm new to the list and would like to say hello to everyone. Now on to the meat. I have tried to compile a kernel with a grsec patch 5 times now using a couple of different methods and I keep getting a No init found and Couldn't support optional features errors every time at bootup. I'm trying to use a vanilla 2.6.32.27 kernel on 10.04 Ubuntu and it compiles fine, just will not boot. I've tried CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers, CONCURRENCY_LEVEL=3 make-kpkg --initrd --append-to-version=-586 kernel_image kernel_headers modules_image. I have all the reqs for building kernels such as build-essentials, fakeroot, kernel-package, kernel-wedge, nurces-dev and qt for xconfig. These are the steps I've taken. DL the kernel image from kernels.org, get the patch from grsec.net, untar the kernel, cd into the directory created, do a 'cp /boot/config-`uname -r` .config', 'make oldconfig', apply the patch, then either 'make menuconfig' or 'make xconfig'. Then I do a 'make-kpkg clean' and run one of the commands in the first paragraph above. I get the debs built and can install them just fine, but I keep getting the same errors. I've cut out as many Experimental options I thought might cause a problem and still get a kernel panic at boot. Anyone have a clue what I'm doing wrong? you are clearly using ubuntu, so here's a simpler recipe i've used successfully. 1) configure and build your kernel from the source 2) sudo make modules_install 3) sudo make install 4) sudo update-initramfs -c -k kernel version goes here 5) sudo update-grub the drawback to the above is that your kernel is not built as an official *package* but for testing purposes, it should do. you'll get your kernel installed under /boot, your modules installed, a new initramfs image, and your grub file updated. can you try it this way and see if it makes a difference? rday -- Robert P. J. Day Waterloo, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
