Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Cameron Hutchison <lists@xdna.net>
To: buildroot@busybox.net
Subject: [Buildroot] ip: RTNETLINK answers: File exists? uclibc login:??
Date: Wed, 03 Feb 2010 12:28:51 -0000	[thread overview]
Message-ID: <4e1d.4b696c03.c4fdb@getafix.xdna.net> (raw)
In-Reply-To: SNT129-W58972AB1A1E9CC737751EBB9560@phx.gbl

Tony Mozi <spooflinux@hotmail.fr> writes:

>When I start the board, I have 2 problems :

>1/ On minicom -s : 
>Starting network...
>ip: RTNETLINK answers: File exists 

This isn't a problem. It occurs (I think) because there are commands in
/etc/inittab to initialise the loopback interface, which get executed
again when "ifup -a" runs from the /etc/init.d/S40network initscript.
You can ignore this error.


>When I write a command, like ls, there is no effect.
>What does it mean?

It means there is nothing listening for your command because...


>2/ On the LCD of the board :
>Welcome to Buildroot
>uclibc login:

>Have you got an idea?

....it looks like you are not running a getty on ttyS0 (or whatever your
console is on).

In "make menuconfig", under Target Options --> Generic serial port
config, there is the option to set the serial port to run a getty on. If
you set this properly, you should end up with a line (uncommented) in
/etc/inittab that reads:

ttyS0::respawn:/sbin/getty -L ttyS0 115200 vt100 # GENERIC_SERIAL

This line will allow you to log into the system through minicom. You
should see the same prompt there you showed above that was on the LCD.

  reply	other threads:[~2010-02-03 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03  9:48 [Buildroot] ip: RTNETLINK answers: File exists? uclibc login:?? Tony Mozi
2010-02-03 12:28 ` Cameron Hutchison [this message]
2010-02-03 15:08   ` [Buildroot] ip: RTNETLINK answers: File exists? uclibc login:?? [RESOLVED] Tony Mozi

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=4e1d.4b696c03.c4fdb@getafix.xdna.net \
    --to=lists@xdna.net \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox