All of lore.kernel.org
 help / color / mirror / Atom feed
From: "machael" <dony.he@huawei.com.cn>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Strange problem after shell appears...
Date: Wed, 21 Mar 2001 19:29:40 +0800	[thread overview]
Message-ID: <000901c0b1fa$38134060$8021690a@huawei.com> (raw)


Hello,all:

Now I can boot linux on my 8260-based custom board. But I have a strange
problem:

#############################
.....................
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 48k init
Sash shell (version 1.0)
sash# hel^@
###############################

After shell appears, I cannot run any built-in commands such as "ls" , "cp"
etc...
As you can see above, when  I type 2 or 3 characters(for example, "hel"),
then it appends "^@" automatically at once(So you see "hel^@" above). Then
it stops there. It has no any response  when I try to type any more
characters. But I can ping it from my host computer.
This means the target board is not crashed...

Of course I am sure the root NFS is OK. I have tried cross-compile sash
statically or dynamically, but both have the same result as above:

###########################################
    powerpc-linux-gcc -O2 -c -o sash.o sash.c
    powerpc-linux-gcc -O2 -c -o cmds.o cmds.c
    .....................
then:
    powerpc-linux-ld -O2 -static -s -o sash sash.o cmds.o ......
or
   powerpc-linux-ld  -O2 -Wl,--rpath,/lib -o sash sash.o cmds.o ...
################################################

Any ideas?
Thank you very much.

machael


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2001-03-21 11:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-21 11:29 machael [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-22  2:37 Strange problem after shell appears machael

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='000901c0b1fa$38134060$8021690a@huawei.com' \
    --to=dony.he@huawei.com.cn \
    --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 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.