All of lore.kernel.org
 help / color / mirror / Atom feed
From: chatchai@allit.info
To: openembedded-devel@openembedded.org
Subject: openomap
Date: Wed, 08 Nov 2006 08:38:13 +0000	[thread overview]
Message-ID: <W74093306724411162975093@webmail21> (raw)

Hi list

I have built both linux-omap-2.6.18-omap1.bb and linux-omap-2.8.28+git.bb. Both of them build successfully, but when I start a kernel, it said 
Uncompressing Kernel Image ... Error: inflate() returned -3
GUNZIP ERROR - must RESET board to recover
So, I compiled a kernel from source using available in source directory (of openembedded), and using toolcain from openembedded, compile 
is successd,build image using git version of uboot, and booting is also work.

Another ploblem is, dorpbear isn't work. I start dropbear (/etc/init.d/dropbear start) and check it using ps, nothing about dropbear. I connect to 
omap (osk) using putty, it said connection refused.

Anybody experienced these kind of ploblem please tell me what is the ploblem.

Tanks and regard

Chatchai
All Infomation Technologies, Thailand








                 reply	other threads:[~2006-11-08  8:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=W74093306724411162975093@webmail21 \
    --to=chatchai@allit.info \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.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.