From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory
Date: Wed, 03 Aug 2011 07:52:07 -0700 [thread overview]
Message-ID: <4E396097.1000207@gmail.com> (raw)
In-Reply-To: <CAGiJk9e01+q-P51iknAFut7jWgSP4NrzLoNDKAjM-wC+=7U+4w@mail.gmail.com>
On 08/02/2011 11:18 PM, Samuel Stirtzel wrote:
> Hi,
> well I never thought this would work out, but after adding "-o rw" to
> the -append parameters the system started and the login prompt
> appeared.
>
> So this problem is solved, for completenes I append my used command
> line to start qemu:
>
> qemu-system-arm -M versatilepb -m 128 -kernel
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin -hda
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
> -append "root=/dev/sda -o rw"
>
There is a smart script in scripts/ dir that you could use something
like this
runqemu /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
and it will setup everything (even networking) for you
make sure that its run in shell where you have sourced setup environment
of either oe-core or angstrom
Hope that helps
-Khem
next prev parent reply other threads:[~2011-08-03 14:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-02 13:19 Error running QEMU with oe-core / angstrom console-image, hwclock: can't open '/dev/misc/rtc' : No such file or directory Samuel Stirtzel
2011-08-03 6:18 ` Samuel Stirtzel
2011-08-03 6:21 ` Koen Kooi
2011-08-03 14:52 ` Khem Raj [this message]
2011-08-04 8:08 ` Samuel Stirtzel
2011-08-04 13:59 ` Samuel Stirtzel
2011-08-04 15:27 ` Khem Raj
2011-08-05 5:25 ` Samuel Stirtzel
2011-08-05 17:33 ` Khem Raj
2011-08-08 9:27 ` Samuel Stirtzel
2011-08-08 17:23 ` Khem Raj
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=4E396097.1000207@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@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