[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Compiling Linux kernel

Hi, Sven.

On Friday, 18 December 2009 17:34:22 +0100,
Sven Joachim wrote:

> > I was trying installing and booting 2.6.26-2-amd64 kernel and then
> > compiling 2.6.32 kernel of the traditional way:
> >
> > # cd /usr/src/linux-2.6.32
> > # cp /boot/config-`uname -r` ./.config
> > # make menuconfig
> > # make
> >
> > In this case I didn't use the ARCH=x86_64 variable and after to
> > execute 'make menuselect' to select the configuration parameters,
> > when invoking 'make', this worked without doing any type of
> > question. Could this be due to I booted previously with amd64
> > kernel?
> Not really, make menuconfig selects the defaults for options which did
> not exist in previous kernels.  Note that it will use the architecture
> of the running kernel if you do not specify ARCH.


> > I assume that it must have differences between both kernels
> > versions; for that reason, as I've mentioned in another mail of this
> > thread, after to have copied the file, I followed a similar
> > procedure to which mentioned above, but with the ARCH=x86_64
> > variable:
> >
> > # cd /usr/src/linux-2.6.32
> > # cp /boot/config-`uname -r` ./.config
> > # make ARCH=x86_64 menuconfig
> > # make
> >
> > But in spite of to have used 'make menuconfig', 'make' did 'restart
> > config' beginning to do questions to me.

> If you are not running a 64-bit kernel, you have to specify
> ARCH=x86_64 for _all_ make invocations.

Well. I didn't know that there was to do it with all. Using the
following steps I was not interrogated:

# cd /usr/src/linux-2.6.32
# cp /boot/config-`uname -r` ./.config

# make ARCH=x86_64 menuconfig
# make ARCH=x86_64
# make ARCH=x86_64 modules_install
# make ARCH=x86_64 install

But when boot, the process is interrupted with the following message:

request_module runaway loop modprobe binfmt-464c

It draws attention to me that this has not happened after compiling
after to have booted with amd64 kernel using the same environment (KVM
VM with host amd64). The unique difference in the process was the
aggregate of the ARCH=x86_64 variable with each invocation of make.

Thanks for your reply.

Fingerprint: BFB3 08D6 B4D1 31B2 72B9  29CE 6696 BF1B 14E6 1D37
Powered by Debian GNU/Linux Lenny - Linux user #188.598

Attachment: signature.asc
Description: Digital signature

Reply to: