All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] RTNETLINK error
Date: Thu, 10 Dec 2009 09:29:53 +0100	[thread overview]
Message-ID: <20091210092953.73963a39@surf> (raw)
In-Reply-To: <4B2CB099CF3D4F40B1B1442281CA94FFC4C929@EXCHANGEVS01.appsig.com>

Le Wed, 9 Dec 2009 11:20:12 -0800,
"NEAL, RYAN" <RYAN_NEAL@appsig.com> a ?crit :

> Starting network...
> 
> ip: RTNETLINK answers: File exists
> 
> And then it hangs.  I looked through the inittab -> rcS -> S40network
> to find that it is coming from the ifup call (on the loopback
> interface?).

Are you sure your /etc/inittab is properly configured to set-up a getty
or shell on whichever serial line you're using ?

This "ip: RTNETLINK" is something I also have, but the system is fully
functional. However, when I forget to adapt the /etc/inittab to the
board serial port configuration, I get the same behaviour as you do.

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

  parent reply	other threads:[~2009-12-10  8:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 19:20 [Buildroot] RTNETLINK error NEAL, RYAN
2009-12-09 20:04 ` Peter Korsgaard
2009-12-09 21:20   ` NEAL, RYAN
2009-12-09 22:05     ` Peter Korsgaard
2009-12-09 22:06       ` NEAL, RYAN
2009-12-09 22:10         ` Peter Korsgaard
2009-12-09 22:18           ` NEAL, RYAN
2009-12-10 10:21             ` Peter Korsgaard
2009-12-10 17:44               ` NEAL, RYAN
2009-12-10 18:21               ` NEAL, RYAN
2009-12-10  8:29 ` Thomas Petazzoni [this message]
2009-12-10 10:27   ` Peter Korsgaard
2009-12-10 20:13     ` NEAL, RYAN

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=20091210092953.73963a39@surf \
    --to=thomas.petazzoni@free-electrons.com \
    --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.