From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Gumstix Verdex builds hang on boot, any ideas?
Date: Sat, 11 Dec 2010 01:28:46 -0800 [thread overview]
Message-ID: <20101211092846.GF8894@gmail.com> (raw)
In-Reply-To: <201011272339.57718.afalls@qvxlabs.com>
On (27/11/10 23:39), Ardavon Falls wrote:
> When I try to run the image created, everything appears to boot normally,
> until halfway through the init/sysV boot process, it hangs printing the
> message...
>
> sa1100-rtc sa1100-rtc: rtc core: registered sa1100-rtc as rtc0
>
> I am using the following settings:
> distro: minimal
> machine: gumstix-verdex
> target_os: linux
>
> Any suggestions? has anyone else ran into this issue?
you need to enable more debug messages in kernel to see whats going on
>
> Thanks
> Ardy
>
> !DSPAM:4cf2074c16461704514828!
>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2010-12-11 9:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-28 7:39 Gumstix Verdex builds hang on boot, any ideas? Ardavon Falls
2010-12-11 9:28 ` Khem Raj [this message]
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=20101211092846.GF8894@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox