linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Belisko Marek <marek.belisko@gmail.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: 2.6.38 not booting on sbc8100 (aka devkit8000)
Date: Thu, 24 Mar 2011 08:18:45 -0700	[thread overview]
Message-ID: <20110324151844.GT2811@atomide.com> (raw)
In-Reply-To: <AANLkTikAO+FA+0fCNiVj=9wVZ3t+vfx9tJX_SnJ7FGSd@mail.gmail.com>

* Belisko Marek <marek.belisko@gmail.com> [110324 02:50]:
> Hi,
> 
> Try to run 2.6.38 on my sbc8100
> (use mach-type for devkit8000 because boards are similar) board but
> when u-boot load it to ram I see just:
> ## Booting kernel from Legacy Image at 80300000 ...
>    Image Name:   Linux-2.6.38-06570-g79c21b4
>    Image Type:   ARM Linux Kernel Image (uncompressed)
>    Data Size:    2967164 Bytes =  2.8 MB
>    Load Address: 80008000
>    Entry Point:  80008000
>    Verifying Checksum ... OK
>    Loading Kernel Image ... OK
> OK
> Starting kernel ...
> 
> I have changed bootargs to: bootargs=console=ttyO2,115200n8 doesn't
> help. Any ideas what could be checked?

Can you enable DEBUG_LL and EARLY_PRINTK in your .config
and add earlyprintk to your cmdline? Then you should see
what goes wrong.

Tony

  reply	other threads:[~2011-03-24 15:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24  9:52 2.6.38 not booting on sbc8100 (aka devkit8000) Belisko Marek
2011-03-24 15:18 ` Tony Lindgren [this message]
     [not found]   ` <AANLkTik8PW4ad2_4=UxzvL-V7HcpH0=dg-Un5NLkj6Yi@mail.gmail.com>
2011-03-24 19:00     ` Tony Lindgren
2011-03-25  7:13       ` Jarkko Nikula
2011-03-25  7:53         ` Belisko Marek
2011-04-08  7:00           ` Thomas Weber
2011-04-08  8:03             ` Belisko Marek
2011-04-08  7:25               ` Thomas Weber
2011-03-25  7:57       ` Belisko Marek
2011-03-25  8:27         ` Jarkko Nikula
2011-03-25  9:32           ` Belisko Marek

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=20110324151844.GT2811@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=marek.belisko@gmail.com \
    /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).