All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 04 Aug 2011 08:27:20 -0700	[thread overview]
Message-ID: <4E3ABA58.9040408@gmail.com> (raw)
In-Reply-To: <CAGiJk9fsRGZiA92vpOcT8X95KscOg-vFxqdB7hcW16MOSk0PWQ@mail.gmail.com>

On 08/04/2011 01:08 AM, Samuel Stirtzel wrote:
> 2011/8/3 Khem Raj<raj.khem@gmail.com>:
>> 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
>>
> Already tried this one, but for some unknown reasons it doesn't work,
> I get the following output:
> -
> samuel@S-Linux:/var/oe-core/setup-scripts$ runqemu
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin
> /var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2
> Set MACHINE to [qemuarm] based on kernel
> [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
>
> Continuing with the following parameters:
> KERNEL: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/zImage-qemuarm.bin]
> ROOTFS: [/var/oe-core/tmp-eglibc/deploy/images/qemuarm/console-image-qemuarm.ext2]
> FSTYPE: [ext2]
> Setting up tap interface under sudo
> [sudo] password for samuel:
> sudo runqemu-ifup<gid>  <native-sysroot-basedir>
> samuel@S-Linux:/var/oe-core/setup-scripts$

A fix for this problem has been committed to oe-core already. Update and 
retry

> -
> This is all, no QEMU window appears or any other messages, or do I
> have run something else.

Nothing more. It should pop up a window where you will see the new 
machine booting

>
> For remote debugging purpose I wrote a generic script that will set up
> a tap and bridge interface and restores the network connection after
> qemu closes.
> This script can also run QEMU with standard network settings.
> Basically runqemu and my scripts should do the same thing(?), but
> since runqemu doesn't work for me I made my own scripts (also it won't
> need sudo if the standard network option is used).
>
> The scripts are attached in this mail, to run the script you could use
> "sh /somedir/generic_qemu_loader.sh --help".
> This script however may not work on other systems than ubuntu, I share
> it only for information exchange purpose.
> If you still want to use it, keep in thought that I am a beginner in
> shell coding!
>
> The difference between the standard network settings and the
> bridge/tap interfaces is, that the standard network only supports
> outgoing TCP and UDP connections while the bridge/tap interface can be
> used to host, for example, a gdbserver.
>
>
> Regards
> Samuel
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  parent reply	other threads:[~2011-08-04 15:31 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
2011-08-04  8:08     ` Samuel Stirtzel
2011-08-04 13:59       ` Samuel Stirtzel
2011-08-04 15:27       ` Khem Raj [this message]
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=4E3ABA58.9040408@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 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.