Can Buildroot 2.2.1 build a usable 2.6.27 kernel?

Go To Last Post
11 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I have tried several times to build a 2.6.27 kernel using different configurations of Buildroot 2.2.1.

Most makes seem to get tripped up with patches and trying to apply them more than once.

Apart from that, making only slight modifications to the atngw100_defconfig options and then choosing a 2.6.27 kernel does complete the build process successfully.

The problem is these 2.6.27 kernels I've built don't boot.

The first one dies when trying to load the root file system. VFS gets tripped and the boot hangs.

The second one got a bad magic number straight after uBoot.

When I fall back to one of my 2.6.25 custom kernels, all is well.

Should I move to using Buildroot 2.2.2? Or is there something I can do with 2.2.1 to get a 2.6.27 kernel working.

(I want a 2.6.27 kernel to use gpio-sys)

Thanks,

Nigel

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think your problem is having built a 2.6.25 kernel and then later on changed to 2.6.27 in the same buildroot environment.
Instead set up a completely fresh buildroot. You may want to "ln -s" the dl directory of your current buildroot to prevent duplicate source downloads.
Then run your "make xxx_defconfig" immediately followed by "make menuconfig" where you change the required kernel version.

Regards,

Werner

... the only thing you cannot unscramble is eggs...

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

What about the atmel patch, which is for kernel 2.6.25 ?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Is there a fitting patch available, do I have to rename the patch or will this workout just by changing the Kernel version in "make menuconfig"?

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

You do not need any patch for 2.6.25 or 2.6.27, the upstream source is fine. Although, the vendor releases usually have some extra features and drivers, not available upstream yet. 2.6.27 is a quite sane choice actually, should work fine without any patches :)

Hans-Christian

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Would anyone who has built a 2.6..27 kernel (hce, squidge? :)) be willing to upload their .config for me to use?

Thanks,

Nigel

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Dingo_aus wrote:
Would anyone who has built a 2.6..27 kernel (hce, squidge? :)) be willing to upload their .config for me to use?

 make atngw100_defconfig 

or look under arch/avr32/configs :-)

I generally customize configs for distribution but it's been a while since I ran in to a problem using the defconfigs for development work.

-S.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Unfortunately when I use atngw100_defconfig and make just the change to build a 2.6.27 kernel I get a kernel panic on a VFS sync during rootwait on boot.

I'll have another crack it tonight and see how I go.

Thanks.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Sure you're using the defconfig from 2.6.27?

FWIW I build my kernels all outside of buildroot to avoid exactly this kinda cruft. Buildroot's good for everything else but I've never had the patience to make it behave for my kernels.

-S.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Quote:
Unfortunately when I use atngw100_defconfig and make just the change to build a 2.6.27 kernel I get a kernel panic on a VFS sync during rootwait on boot.

The default config for atngw100 does not compile in ext2 and ext3 support by default, only enable them as modules. Try flipping them to be compiled into the kernel in menuconfig.

Hans-Christian

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Both good ideas. I'll start with hce's suggestion and then if that doesn't get me over the line I'll go down the non Buildroot path.

Cheers guys,

Nigel