[Buildroot] Buildroot 2009.08 fails to build working rootfs

[Buildroot] Buildroot 2009.08 fails to build working rootfs

[Teemu Keskinarkaus]

First of all I'm using AT91-version of the buildroot-2009.08, but I'm
guessing (or more like hoping) that it has nothing to do with the
problem I'm having.

 

I finally got the buildroot build okay with external toolchain.
Toolchain is glibc eabi toolchain (Codesourcery) and kernel (2.6.30.4)
is configured for eabi too. Kernel boots up just fine and get's rootfs
mounted, but then panics because init is not found.

 

VFS: Mounted root (ubifs filesystem) readonly on device 253:1.

Freeing init memory: 100K

Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

 

I manually compiled busybox and made my own small rootfs. Then with the
same kernel as before, the system booted up nicely. 

 

I tried to be sneaky and replaced the busybox binary that buildroot was
compiled, with the one I had compiled and let buildroot regenerate
rootfs, but that didn't help. I still got the same error.

 

I programmed the rootfs image as a second partition to unit and booted
up with older buildroot and checked what was that new rootfs like and it
seemed to be just fine. I couldn't see anything that was causing the
problem. And the image was working just fine too.

 

Kernel command line on both working and non-working case is the same:

 

Kernel command line: mem=128M console=ttyS0,115200 ubi.mtd=1 ubi.mtd=2
root=ubi0:rootfs ro rootfstype=ubifs ubi.mtd=3

 

I'm guessing this must be some simple thing, but I just can't figure it
out. Has anyone else had similar problems and how did you solve it?

 

Teemu Keskinarkaus

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090918/82b6db5a/attachment-0001.htm>

[Buildroot] Buildroot 2009.08 fails to build working rootfs

[Teemu Keskinarkaus]

Found a reason why my rootfs wasn't working. The libraries were missing!

 

And now the cause. It seems that if I remove the
project_build_arm/projectname/root and
project_build_arm/projectname/.root and make the buildroot, the
buildroot won't copy the libraries to new root anymore. If I remove the
build_arm- directory too and let the buildroot compile more stuff the
root will be more complete although then there will be way too much
stuff. More than what is said in .config - file in buildroot
root-directory. Maybe that's because removing that build_arm - directory
like that.

 

It seems for me like buildroot bug, since the old buildroot generated
root always right after it was removed.

 

Teemu Keskinarkaus

 

________________________________

From: buildroot-bounces@busybox.net
[mailto:buildroot-bounces at busybox.net] On Behalf Of Teemu Keskinarkaus
Sent: 18. syyskuuta 2009 12:53
To: buildroot at busybox.net
Subject: [Buildroot] Buildroot 2009.08 fails to build working rootfs

 

First of all I'm using AT91-version of the buildroot-2009.08, but I'm
guessing (or more like hoping) that it has nothing to do with the
problem I'm having.

 

I finally got the buildroot build okay with external toolchain.
Toolchain is glibc eabi toolchain (Codesourcery) and kernel (2.6.30.4)
is configured for eabi too. Kernel boots up just fine and get's rootfs
mounted, but then panics because init is not found.

 

VFS: Mounted root (ubifs filesystem) readonly on device 253:1.

Freeing init memory: 100K

Kernel panic - not syncing: No init found.  Try passing init= option to
kernel.

 

I manually compiled busybox and made my own small rootfs. Then with the
same kernel as before, the system booted up nicely. 

 

I tried to be sneaky and replaced the busybox binary that buildroot was
compiled, with the one I had compiled and let buildroot regenerate
rootfs, but that didn't help. I still got the same error.

 

I programmed the rootfs image as a second partition to unit and booted
up with older buildroot and checked what was that new rootfs like and it
seemed to be just fine. I couldn't see anything that was causing the
problem. And the image was working just fine too.

 

Kernel command line on both working and non-working case is the same:

 

Kernel command line: mem=128M console=ttyS0,115200 ubi.mtd=1 ubi.mtd=2
root=ubi0:rootfs ro rootfstype=ubifs ubi.mtd=3

 

I'm guessing this must be some simple thing, but I just can't figure it
out. Has anyone else had similar problems and how did you solve it?

 

Teemu Keskinarkaus

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090921/9bde5f79/attachment.htm>

[Buildroot] Buildroot 2009.08 fails to build working rootfs

[Ulf Samuelsson]

Teemu Keskinarkaus skrev:
> Found a reason why my rootfs wasn?t working. The libraries were missing!
> 
>  
> 
> And now the cause. It seems that if I remove the 
> project_build_arm/projectname/root and 
> project_build_arm/projectname/.root and make the buildroot, the 
> buildroot won?t copy the libraries to new root anymore. If I remove the 
> build_arm- directory too and let the buildroot compile more stuff the 
> root will be more complete although then there will be way too much 
> stuff. More than what is said in .config ? file in buildroot 
> root-directory. Maybe that?s because removing that build_arm ? directory 
> like that.
> 
>  
> 
> It seems for me like buildroot bug, since the old buildroot generated 
> root always right after it was removed.
> 
>  

I dont think that the modifications in this tree touches that part.
What happens, if you change the project name?
Will everything be regenerated OK then?

BR
Ulf Samuelsson


> 
> *Teemu Keskinarkaus*
> 
>  
> 
> ------------------------------------------------------------------------
> 
> *From:* buildroot-bounces at busybox.net 
> [mailto:buildroot-bounces at busybox.net] *On Behalf Of *Teemu Keskinarkaus
> *Sent:* 18. syyskuuta 2009 12:53
> *To:* buildroot at busybox.net
> *Subject:* [Buildroot] Buildroot 2009.08 fails to build working rootfs
> 
>  
> 
> First of all I?m using AT91-version of the buildroot-2009.08, but I?m 
> guessing (or more like hoping) that it has nothing to do with the 
> problem I?m having.
> 
>  
> 
> I finally got the buildroot build okay with external toolchain. 
> Toolchain is glibc eabi toolchain (Codesourcery) and kernel (2.6.30.4) 
> is configured for eabi too. Kernel boots up just fine and get?s rootfs 
> mounted, but then panics because init is not found.
> 
>  
> 
> VFS: Mounted root (ubifs filesystem) readonly on device 253:1.
> 
> Freeing init memory: 100K
> 
> Kernel panic - not syncing: No init found.  Try passing init= option to 
> kernel.
> 
>  
> 
> I manually compiled busybox and made my own small rootfs. Then with the 
> same kernel as before, the system booted up nicely.
> 
>  
> 
> I tried to be sneaky and replaced the busybox binary that buildroot was 
> compiled, with the one I had compiled and let buildroot regenerate 
> rootfs, but that didn?t help. I still got the same error.
> 
>  
> 
> I programmed the rootfs image as a second partition to unit and booted 
> up with older buildroot and checked what was that new rootfs like and it 
> seemed to be just fine. I couldn?t see anything that was causing the 
> problem. And the image was working just fine too.
> 
>  
> 
> Kernel command line on both working and non-working case is the same:
> 
>  
> 
> Kernel command line: mem=128M console=ttyS0,115200 ubi.mtd=1 ubi.mtd=2 
> root=ubi0:rootfs ro rootfstype=ubifs ubi.mtd=3
> 
>  
> 
> I?m guessing this must be some simple thing, but I just can?t figure it 
> out. Has anyone else had similar problems and how did you solve it?
> 
>  
> 
> *Teemu Keskinarkaus*
> 
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

[Buildroot] Buildroot 2009.08 fails to build working rootfs

[Teemu Keskinarkaus]

> -----Original Message-----
> From: Ulf Samuelsson [mailto:ulf.samuelsson at atmel.com]
> Sent: 22. syyskuuta 2009 1:43
> To: Teemu Keskinarkaus
> Cc: buildroot at busybox.net
> Subject: Re: [Buildroot] Buildroot 2009.08 fails to build working
rootfs
> 
> Teemu Keskinarkaus skrev:
> > Found a reason why my rootfs wasn't working. The libraries were
missing!
> >
> >
> >
> > And now the cause. It seems that if I remove the
> > project_build_arm/projectname/root and
> > project_build_arm/projectname/.root and make the buildroot, the
> > buildroot won't copy the libraries to new root anymore. If I remove
the
> > build_arm- directory too and let the buildroot compile more stuff
the
> > root will be more complete although then there will be way too much
> > stuff. More than what is said in .config - file in buildroot
> > root-directory. Maybe that's because removing that build_arm -
directory
> > like that.
> >
> >
> >
> > It seems for me like buildroot bug, since the old buildroot
generated
> > root always right after it was removed.
> >
> >
> 
> I dont think that the modifications in this tree touches that part.
> What happens, if you change the project name?
> Will everything be regenerated OK then?

I changed the project name and also the kernel version. Those two are
not related together. Then I make the buildroot and sure enough, the
libraries are missing from the new root-directory. After 'make clean'
the make generated rootfs that has all needed libraries too. Earlier I
couldn't done 'make clean' since the project name had changed and 'make
clean' failed. 

So it seems that 'make clean' is needed to be able to regenerate
root-directory. This might be related to external toolchain. Not that I
mind, but it takes way longer to use 'make clean' and 'make' rather than
just removing the old root-directory and say 'make'. Also other
modifications might be lost. 

Teemu Keskinarkaus

> 
> BR
> Ulf Samuelsson
> 
> 
> >
> > *Teemu Keskinarkaus*
> >
> >
> >
> >
------------------------------------------------------------------------
> >
> > *From:* buildroot-bounces at busybox.net
> > [mailto:buildroot-bounces at busybox.net] *On Behalf Of *Teemu
Keskinarkaus
> > *Sent:* 18. syyskuuta 2009 12:53
> > *To:* buildroot at busybox.net
> > *Subject:* [Buildroot] Buildroot 2009.08 fails to build working
rootfs
> >
> >
> >
> > First of all I'm using AT91-version of the buildroot-2009.08, but
I'm
> > guessing (or more like hoping) that it has nothing to do with the
> > problem I'm having.
> >
> >
> >
> > I finally got the buildroot build okay with external toolchain.
> > Toolchain is glibc eabi toolchain (Codesourcery) and kernel
(2.6.30.4)
> > is configured for eabi too. Kernel boots up just fine and get's
rootfs
> > mounted, but then panics because init is not found.
> >
> >
> >
> > VFS: Mounted root (ubifs filesystem) readonly on device 253:1.
> >
> > Freeing init memory: 100K
> >
> > Kernel panic - not syncing: No init found.  Try passing init= option
to
> > kernel.
> >
> >
> >
> > I manually compiled busybox and made my own small rootfs. Then with
the
> > same kernel as before, the system booted up nicely.
> >
> >
> >
> > I tried to be sneaky and replaced the busybox binary that buildroot
was
> > compiled, with the one I had compiled and let buildroot regenerate
> > rootfs, but that didn't help. I still got the same error.
> >
> >
> >
> > I programmed the rootfs image as a second partition to unit and
booted
> > up with older buildroot and checked what was that new rootfs like
and it
> > seemed to be just fine. I couldn't see anything that was causing the
> > problem. And the image was working just fine too.
> >
> >
> >
> > Kernel command line on both working and non-working case is the
same:
> >
> >
> >
> > Kernel command line: mem=128M console=ttyS0,115200 ubi.mtd=1
ubi.mtd=2
> > root=ubi0:rootfs ro rootfstype=ubifs ubi.mtd=3
> >
> >
> >
> > I'm guessing this must be some simple thing, but I just can't figure
it
> > out. Has anyone else had similar problems and how did you solve it?
> >
> >
> >
> > *Teemu Keskinarkaus*
> >
> >
> >
> >
> >
------------------------------------------------------------------------
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> 

[Buildroot] Buildroot 2009.08 fails to build working rootfs

[Anders Darander]

On Tue, Sep 22, 2009 at 07:50, Teemu Keskinarkaus
<Teemu.Keskinarkaus@cc-systems.com> wrote:
> I changed the project name and also the kernel version. Those two are
> not related together. Then I make the buildroot and sure enough, the
> libraries are missing from the new root-directory. After 'make clean'
> the make generated rootfs that has all needed libraries too. Earlier I
> couldn't done 'make clean' since the project name had changed and 'make
> clean' failed.

If the missing libraries comes from the external toolchain, then it is
quite likely that they aren't going to be copied to the rootfs again,
if you remove the rootfs (or renamed the project). As long as the
stamp-file in build_*/stamps/ext-toolchain-installed is left, the
external toolchain is not reinstalled. If you remove this file, the
toolchain will get reinstalled, together with all libraries to the
rootfs.

> So it seems that 'make clean' is needed to be able to regenerate
> root-directory. This might be related to external toolchain. Not that I
> mind, but it takes way longer to use 'make clean' and 'make' rather than
> just removing the old root-directory and say 'make'. Also other
> modifications might be lost.

So yes, it's quite likely related to the external toolchain.

Regards,
Anders

-- 
Anders Darander