From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot with 2.4.27 kernel: Network problems
Date: Sun, 30 Jan 2011 10:36:39 +0100 [thread overview]
Message-ID: <87bp2yybq0.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110130084425.5cc28ae3@x41> (Simon Kagstrom's message of "Sun, 30 Jan 2011 08:44:25 +0100")
>>>>> "Simon" == Simon Kagstrom <simon.kagstrom@gmail.com> writes:
Simon> Hi Buildrooters!
Simon> I have a bit of an odd problem. I have a ARM-based Linux stereo, which
Simon> I've rooted and want to add despotify support to and other things (see
Simon> here:
Simon> http://simonkagstrom.livejournal.com/51909.html
Simon> if you are interested). I'm using buildroot to make my one rootfs for
Simon> it. The problem is that it uses a very old kernel, 2.4.27-vrs1, and
Simon> while the built buildroot filesystem works, I get problems with network
Simon> operations:
Simon> g2 trunk 6869 Island:# ping 192.168.1.104
Simon> PING 192.168.1.104 (192.168.1.104): 56 data bytes
Simon> ping: can't create raw socket: Function not implemented
Simon> g2 trunk 6869 Island:# ./busybox telnet localhost
Simon> telnet: socket: Function not implemented
Is this with a complete rootfs built by buildroot, or just with the
busybox binary copied over to an existing system? If the last, don't
forget that uClibc doesn't have a stable ABI, so you need to link
busybox statically if you want to run it in a rootfs with another uClibc
version.
Simon> I'm trying to trick buildroot into accepting my 2.4.27 kernel
Simon> sources by renaming it linux-2.6.tar.bz2 and hacking a bit, but
Simon> is so far unsuccessful. Have anyone else used buildroot with a
Simon> 2.4 kernel recently?
No, not as far as I know. 2.4.x is ancient.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-30 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 7:44 [Buildroot] Buildroot with 2.4.27 kernel: Network problems Simon Kagstrom
2011-01-30 9:36 ` Peter Korsgaard [this message]
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=87bp2yybq0.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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