From: Nishanth Menon <nm@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: Elvis Dowson <elvis.dowson@mac.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: BeagleBoard stops at booting kernel with 2.6.37-rc5
Date: Thu, 16 Dec 2010 14:28:36 -0600 [thread overview]
Message-ID: <4D0A7674.40009@ti.com> (raw)
In-Reply-To: <AANLkTim1vzFpdOjBNDXT2cofUAS4=_G7+QtTKZdw0xDv@mail.gmail.com>
Robert Nelson had written, on 12/16/2010 02:25 PM, the following:
> On Thu, Dec 16, 2010 at 2:19 PM, Elvis Dowson <elvis.dowson@mac.com> wrote:
>> Hi,
>> I'm working with linux mainline 2.6.37-rc5 and my custom beagleboard based platform stops at booting the kernel. Is there a fix for this?
>>
>> reading uImage
>>
>> 2432692 bytes read
>> Booting from mmc ...
>> ## Booting kernel from Legacy Image at 82000000 ...
>> Image Name: Linux-2.6.37-rc5
>> Image Type: ARM Linux Kernel Image (uncompressed)
>> Data Size: 2432628 Bytes = 2.3 MB
>> Load Address: 80008000
>> Entry Point: 80008000
>> Verifying Checksum ... OK
>> Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing Linux... done, booting the kernel.
>>
>
> If it stops there, double check your bootarg's as with 2.6.37+ you
> might be using the omap-serial vs the old generic serial driver...
> "ttyO2" (O in Omap) vs "ttyS2"..
one more thing: in fs - getty dependency might exist - you could choose
something similar to what I did on my bare busybox install:
http://nishanthmenon.blogspot.com/2010/10/tired-of-ttysx-and-ttyox.html
--
Regards,
Nishanth Menon
next prev parent reply other threads:[~2010-12-16 20:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D76728EE-7818-4236-83E9-B32045714912@mac.com>
2010-12-16 20:25 ` BeagleBoard stops at booting kernel with 2.6.37-rc5 Robert Nelson
2010-12-16 20:28 ` Nishanth Menon [this message]
2010-12-16 20:32 ` David Anders
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=4D0A7674.40009@ti.com \
--to=nm@ti.com \
--cc=elvis.dowson@mac.com \
--cc=linux-omap@vger.kernel.org \
--cc=robertcnelson@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 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.