Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
* [Buildroot] Problems with custom config of kernel 2.6.34.1
@ 2010-07-12 20:52 Ossy
  2010-07-13  6:55 ` Thomas Petazzoni
  0 siblings, 1 reply; 4+ messages in thread
From: Ossy @ 2010-07-12 20:52 UTC (permalink / raw)
  To: buildroot

Hi mailinglist,

I use the kernel version 2.6.33.6 without any problems. But since I 
updated to the newer version 2.6.34.1 I'm not able to use a custom 
config anymore.

I loaded the old config into the kernel menuconfig and stored it as new 
file linux-2.6.34.1.config. When I launched the overall make process the 
kernel patches were applied fine, but the process runs into text mode 
configuration:

...
 >>>   Configuring kernel
cp 
"target/device/sheevaplug/SeagateDockStar/SeagateDockStar-linux-2.6.34.1.config" 
/home/ossy/buildroot/buildroot-dev/output/build/linux-2.
6.34.1/.config
/home/ossy/buildroot/buildroot-dev/output/toolchain/bin/sed -i -e 
"/CONFIG_AEABI/d" /home/ossy/buildroot/buildroot-dev/output/build/linux-2.
6.34.1/.config
echo "CONFIG_AEABI=y" >> 
/home/ossy/buildroot/buildroot-dev/output/build/linux-2.6.34.1/.config
/home/ossy/buildroot/buildroot-dev/output/toolchain/bin/sed -i -e 
"/CONFIG_IPV6/d" /home/ossy/buildroot/buildroot-dev/output/build/linux-2.6
.34.1/.config
echo "# CONFIG_IPV6 is not set" >> 
/home/ossy/buildroot/buildroot-dev/output/build/linux-2.6.34.1/.config
/home/ossy/buildroot/buildroot-dev/output/toolchain/bin/sed -i -e 
"/CONFIG_BLK_DEV_INITRD/d" /home/ossy/buildroot/buildroot-dev/output/build
/linux-2.6.34.1/.config
echo "# CONFIG_BLK_DEV_INITRD is not set" >> 
/home/ossy/buildroot/buildroot-dev/output/build/linux-2.6.34.1/.config
/home/ossy/buildroot/buildroot-dev/output/toolchain/bin/sed -i -e 
"/CONFIG_INITRAMFS_SOURCE/d" /home/ossy/buildroot/buildroot-dev/output/bui
ld/linux-2.6.34.1/.config
echo "CONFIG_INITRAMFS_SOURCE=\"\"" >> 
/home/ossy/buildroot/buildroot-dev/output/build/linux-2.6.34.1/.config
PATH="/home/ossy/buildroot/buildroot-dev/output/host/bin:/home/ossy/buildroot/buildroot-dev/output/host/usr/bin:/home/ossy/buildroot/buildro
ot-dev/output/host/usr/sbin/:/usr/local/bin:/usr/bin:/bin:/usr/games" 
PERLLIB="/home/ossy/buildroot/buildroot-dev/output/host/usr/lib/perl"
/usr/bin/make -j2 HOSTCC="/usr/bin/gcc" HOSTCFLAGS="" ARCH=arm 
INSTALL_MOD_PATH=/home/ossy/buildroot/buildroot-dev/output/target 
CROSS_COMPI
LE=/home/ossy/buildroot/buildroot-dev/output/staging/usr/bin/arm-unknown-linux-uclibcgnueabi- 
LDFLAGS="-L/home/ossy/buildroot/buildroot-dev/
output/staging/lib 
-L/home/ossy/buildroot/buildroot-dev/output/staging/usr/lib" 
LZMA="/home/ossy/buildroot/buildroot-dev/output/host/usr/bin
/lzma" -C /home/ossy/buildroot/buildroot-dev/output/build/linux-2.6.34.1 
oldconfig
make[1]: Entering directory 
`/home/ossy/buildroot/buildroot-dev/output/build/linux-2.6.34.1'
scripts/kconfig/conf -o arch/arm/Kconfig
*
* Restart config...
*
*
* Enable the block layer
*
Enable the block layer (BLOCK) [Y/?] y
   Support for large (2TB+) block devices and files (LBDAF) [Y/n/?] (NEW)


Why is the configuration restarted? The config file was well copied from 
custom directory to output/build/linuxsrc/.config.
So why should I restart configuration in textmode?

Thanks for your help.

Regards,
Marcus

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Problems with custom config of kernel 2.6.34.1
  2010-07-12 20:52 [Buildroot] Problems with custom config of kernel 2.6.34.1 Ossy
@ 2010-07-13  6:55 ` Thomas Petazzoni
  2010-07-13  9:11   ` Paul Jones
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Petazzoni @ 2010-07-13  6:55 UTC (permalink / raw)
  To: buildroot

Hello Marcus,

On Mon, 12 Jul 2010 22:52:55 +0200
Ossy <ossy1980@gmx.net> wrote:

> Hi mailinglist,
> 
> I use the kernel version 2.6.33.6 without any problems. But since I 
> updated to the newer version 2.6.34.1 I'm not able to use a custom 
> config anymore.
> 
> I loaded the old config into the kernel menuconfig and stored it as
> new file linux-2.6.34.1.config. When I launched the overall make
> process the kernel patches were applied fine, but the process runs
> into text mode configuration:

Thanks for your report. Could you provide a step-by-step procedure to
reproduce the problem from scratch ?

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Problems with custom config of kernel 2.6.34.1
  2010-07-13  6:55 ` Thomas Petazzoni
@ 2010-07-13  9:11   ` Paul Jones
  2010-07-13 19:27     ` Ossy
  0 siblings, 1 reply; 4+ messages in thread
From: Paul Jones @ 2010-07-13  9:11 UTC (permalink / raw)
  To: buildroot

> -----Original Message-----
> From: buildroot-bounces at busybox.net [mailto:buildroot-
> bounces at busybox.net] On Behalf Of Thomas Petazzoni
> Sent: Tuesday, 13 July 2010 4:55 PM
> To: buildroot at busybox.net
> Subject: Re: [Buildroot] Problems with custom config of kernel 2.6.34.1
> 
> Hello Marcus,
> 
> On Mon, 12 Jul 2010 22:52:55 +0200
> Ossy <ossy1980@gmx.net> wrote:
> 
> > Hi mailinglist,
> >
> > I use the kernel version 2.6.33.6 without any problems. But since I
> > updated to the newer version 2.6.34.1 I'm not able to use a custom
> > config anymore.
> >
> > I loaded the old config into the kernel menuconfig and stored it as
> > new file linux-2.6.34.1.config. When I launched the overall make
> > process the kernel patches were applied fine, but the process runs
> > into text mode configuration:
> 
> Thanks for your report. Could you provide a step-by-step procedure to
> reproduce the problem from scratch ?

Isn't that just make oldconfig running? What happens if you press enter to
give the default answer to every question?


Paul.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* [Buildroot] Problems with custom config of kernel 2.6.34.1
  2010-07-13  9:11   ` Paul Jones
@ 2010-07-13 19:27     ` Ossy
  0 siblings, 0 replies; 4+ messages in thread
From: Ossy @ 2010-07-13 19:27 UTC (permalink / raw)
  To: buildroot

Am 13.07.2010 11:11, schrieb Paul Jones:
>>> I use the kernel version 2.6.33.6 without any problems. But since I
>>> updated to the newer version 2.6.34.1 I'm not able to use a custom
>>> config anymore.
>>>
>>> I loaded the old config into the kernel menuconfig and stored it as
>>> new file linux-2.6.34.1.config. When I launched the overall make
>>> process the kernel patches were applied fine, but the process runs
>>> into text mode configuration:
>>
>> Thanks for your report. Could you provide a step-by-step procedure to
>> reproduce the problem from scratch ?
I changed the brconfig from kernel 2.6.33.x to 2.6.34.x. I loaded my 
custom kernel configuration into the linux menuconfig and stored it as 
new file. Obviously this not sufficient to migrate from one config 
version to another (I remember once in time it was, maybe 2.4.x days?).

>
> Isn't that just make oldconfig running? What happens if you press enter to
> give the default answer to every question?
Paul is absolutly right. I gave the default answer to every question 
(only a few...) and wrote this config back to 
mycustomlinuxconf-2.6.34.x.config.

The next time I do not expect to answer questions on the commandline 
during overall make process.

Thanks both for your help.

Regards,
Marcus

@Thomas: Please note my patch for making u-boot (correcting two typos) 
from 7.7.2010 . The fix is very straight forward (only two changed lines).

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2010-07-13 19:27 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-07-12 20:52 [Buildroot] Problems with custom config of kernel 2.6.34.1 Ossy
2010-07-13  6:55 ` Thomas Petazzoni
2010-07-13  9:11   ` Paul Jones
2010-07-13 19:27     ` Ossy

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox