Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Kagstrom <simon.kagstrom@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot with 2.4.27 kernel: Network problems
Date: Sun, 30 Jan 2011 08:44:25 +0100	[thread overview]
Message-ID: <20110130084425.5cc28ae3@x41> (raw)

Hi Buildrooters!

I have a bit of an odd problem. I have a ARM-based Linux stereo, which
I've rooted and want to add despotify support to and other things (see
here:

  http://simonkagstrom.livejournal.com/51909.html

if you are interested). I'm using buildroot to make my one rootfs for
it. The problem is that it uses a very old kernel, 2.4.27-vrs1, and
while the built buildroot filesystem works, I get problems with network
operations:

  g2 trunk 6869 Island:# ping 192.168.1.104
  PING 192.168.1.104 (192.168.1.104): 56 data bytes
  ping: can't create raw socket: Function not implemented

  g2 trunk 6869 Island:# ./busybox telnet localhost  
  telnet: socket: Function not implemented

and I presume this is because of the kernel version mismatch and
perhaps uClibc. Nslookup also doesn't work


I'm trying to trick buildroot into accepting my 2.4.27 kernel sources
by renaming it linux-2.6.tar.bz2 and hacking a bit, but is so far
unsuccessful. Have anyone else used buildroot with a 2.4 kernel
recently?

// Simon

             reply	other threads:[~2011-01-30  7:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  7:44 Simon Kagstrom [this message]
2011-01-30  9:36 ` [Buildroot] Buildroot with 2.4.27 kernel: Network problems Peter Korsgaard
2011-01-30 12:01   ` Simon Kagstrom
2011-01-30 12:43     ` Peter Korsgaard
2011-01-30 13:55       ` Simon Kagstrom
2011-01-30 15:11         ` Thomas Petazzoni

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=20110130084425.5cc28ae3@x41 \
    --to=simon.kagstrom@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox