From: "john zhan" <r3587@sina.com>
To: "Kwansuk Kim" <kskim@neowave.co.kr>
Cc: <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: network tools don't work
Date: Sat, 1 Jul 2000 00:28:01 +0800 [thread overview]
Message-ID: <002b01bfe2b0$2a05ae00$57c809c0@nt4srv87> (raw)
In-Reply-To: NEBBKFENMLEDKDHMEHPJIEOOCAAA.kskim@neowave.co.kr
hi, kim
I experienced similar case.
That's your shared objs and your applications are not accordant.
Build apps and kernel with same version of glibc.
also,make sure you have same version libc.so.6 in /lib of your target rootfs .
regards.
john zhan.
----- Original Message -----
From: Kwansuk Kim <kskim@neowave.co.kr>
To: LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Sent: Tuesday, July 11, 2000 7:47 PM
Subject: network tools don't work
>
> After getting bash prompt, I determined wheather network is working, but it doesn't.
> It tells there is no protocol.
>
> ----------
>
> init-2.00# ./ifconfig lo 127.0.0.1
> 127.0.0.1: Resolver Error 0 (no error)
> Usage: ifconfig [-a] [-i] [-v] interface
> [inet address]
> [hw] [ax25 address]
> [metric NN] [mtu NN]
> [trailers] [-trailers]
> [arp] [-arp]
> [netmask aa.bb.cc.dd]
> [dstaddr aa.bb.cc.dd]
> [mem_start NN] [io_addr NN] [irq NN]
> [[-] broadcast [aa.bb.cc.dd]]
> [[-]pointopoint [aa.bb.cc.dd]]
> [up] [down] ...
> init-2.00# ping 210.105.51.96
> ping: unknown protocol icmp.
> init-2.00#
>
> ----------
>
> But I set configure file to support TCP/IP protocol.
> It's startup message.
>
> ---------------
>
> POSIX conformance testing by UNIFIX
> Linux NET4.0 for Linux 2.2
> Based upon Swansea University Computer Society NET3.039
> NET4: Unix domain sockets 1.0 for Linux NET4.0.
> NET4: Linux TCP/IP 1.0 for NET4.0
> IP Protocols: ICMP, UDP, TCP, IGMP
> TCP: Hash tables configured (ehash 32768 bhash 32768)
> Starting kswapd v 1.5
> Serial driver version 4.27 with no serial options enabled
> ttyS00 at 0x03f8 (irq = 4) is a 16450
> ttyS01 at 0x02f8 (irq = 3) is a 16450
> ttyS02 at 0x03e8 (irq = 4) is a 16450
> CPM UART driver version 0.02
>
> ttyS00 at 0x0380 is a SMC
> ttyS01 at 0x0100 is a SCC
> ttyS02 at 0x0200 is a SCC
> pty: 256 Unix98 ptys configured
>
> .....
>
> Is something wrong?
>
> I used ramdisk root file system, and ramdisk image was obtained from linuxppc.org. (about 4Meg, library version is 1.99)
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-06-30 16:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-11 11:47 network tools don't work Kwansuk Kim
2000-06-30 16:28 ` john zhan [this message]
2000-07-11 12:09 ` Dan A. Dickey
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='002b01bfe2b0$2a05ae00$57c809c0@nt4srv87' \
--to=r3587@sina.com \
--cc=kskim@neowave.co.kr \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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;
as well as URLs for NNTP newsgroup(s).