All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Chertov <rchertov@cs.ucsb.edu>
To: buildroot@busybox.net
Subject: [Buildroot] busybox question
Date: Wed, 28 Oct 2009 09:26:20 -0700	[thread overview]
Message-ID: <4AE870AC.6070601@cs.ucsb.edu> (raw)
In-Reply-To: <877hufddx5.fsf@macbook.be.48ers.dk>

Peter Korsgaard wrote:
>>>>>> "Roman" == Roman Chertov <rchertov@cs.ucsb.edu> writes:
> 
>  Roman> Hello,
>  Roman> I have an ARM920T board that I am trying to get going with buildroot and
>  Roman> uClibc.  I managed to compile the kernel, and it boots up to the point
>  Roman> where the login must happen.  Nothing happens at that point.  However,
>  Roman> the machine runs as I can ping it.  I have tried to init=/bin/sh
>  Roman> init=/bin/ethtool, but I did not get any output to indicate that
>  Roman> something started.
> 
> And you have set console= to something sensible? What is the last output
> you get from the kernel?

console=ttyAM0,115200 ip=dhcp noinitrd root=/dev/nfs init=/sbin/init
nfsroot=192.168.0.1:/proj/tools/buildroot-2009.08/project_build_arm/uclibc/root/
This is my argument list to the kernel.

This was my last message from the kernel

VFS: Mounted root (nfs filesystem).

Freeing init memory: 120K

Based on Francisco's private email, I made some nodes in the /dev
directory as by default, buildroot creates only files and not device
files with major/minor numbers.  I made the nodes by copying some of the
devices from the board's default disk while it was running.  Now, when I
boot, I get the following repeating sequence.

can't open /dev/~: No such file or directory

can't open /dev/tty1: No such file or directory

can't open /dev/tty2: No such file or directory


Looks like the culprit, is the improper device setup.

> 
> Do you have software floating point support enabled in buildroot?
> (toolchain->Use software floating point by default)

This is not set.

> 
>  Roman> I have the following question.  I can build the default image on the
>  Roman> board (Debian 2.4, glibc) and mount the buildroot root fs over NFS.
>  Roman> However, if I try to execute any program, I get the following errors:
> 
>  Roman> root at ts7000:bin# ./busybox
>  Roman> -bash: ./busybox: No such file or directory
> 
> You'll probably have to chroot into the nfs dir to get the dynamic
> linker to work.

I will give this a shot later on today.

Thanks.

Roman

> 
> 

  reply	other threads:[~2009-10-28 16:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27 21:12 [Buildroot] [git commit master] synergy: needs C++ support Peter Korsgaard
2009-10-28  4:25 ` [Buildroot] busybox question Roman Chertov
2009-10-28 10:13   ` Peter Korsgaard
2009-10-28 16:26     ` Roman Chertov [this message]
2009-10-28 16:46       ` Emmanuel Riou
2009-10-28 19:35         ` Roman Chertov
2009-10-28 20:37           ` Peter Korsgaard
2009-10-28 20:51             ` Roman Chertov
2009-10-28 21:00               ` Peter Korsgaard
2009-10-29 16:10                 ` Roman Chertov
2009-10-28 19:36       ` Peter Korsgaard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AE870AC.6070601@cs.ucsb.edu \
    --to=rchertov@cs.ucsb.edu \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.