Openembedded Core Discussions
 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: Fri, 05 Aug 2011 10:33:16 -0700	[thread overview]
Message-ID: <4E3C295C.6060700@gmail.com> (raw)
In-Reply-To: <CAGiJk9eZgic_cL23CEJYq+++OW3233cdhpehwhsJkwo4=1yr9Q@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 08/04/2011 10:25 PM, Samuel Stirtzel wrote:
> 2011/8/4 Khem Raj <raj.khem@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
>> 
> After i updated my oe-core files the script still won't work for me. 
> The new output is:: - 
> samuel@S-Stirtzel-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: 
> Acquiring lockfile for tap0... Error: Unable to support this 
> combination of options

It means QEMUOPTIONS is empty in your case because you are sing ext2
image. It supports ext3 and btrfs

but it should be easy to add ext2 to mix. Can you try something like below

diff --git a/scripts/runqemu-internal b/scripts/runqemu-internal
index c15632d..64635df 100755
- --- a/scripts/runqemu-internal
+++ b/scripts/runqemu-internal
@@ -277,7 +277,7 @@ if [ "$MACHINE" = "qemuarm" -o "$MACHINE" =
"qemuarmv6" -o "$MACHINE" = "qemuarm
     MACHINE_SUBTYPE=versatilepb
     QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS"
     # QEMU_UI_OPTIONS="$QEMU_UI_OPTIONS -force-pointer"
- -    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" ]; then
+    if [ "$FSTYPE" = "ext3" -o "$FSTYPE" = "btrfs" -o "$FSTYPE" =
"ext2" ]; then
         KERNCMDLINE="root=/dev/sda rw console=ttyAMA0,115200
console=tty $KERNEL_NETWORK_CMD mem=$QEMU_MEMORY hi
         QEMUOPTIONS="$QEMU_NETWORK_CMD -M versatilepb -hda $ROOTFS
- -no-reboot $QEMU_UI_OPTIONS"
     fi


> Set 'tap0' nonpersistent Releasing lockfile of preconfigured tap 
> device 'tap0' -
> 
> This error was not created from the runqemu script itself. Maybe the
>  runqemu-initial script was expecting other options?
> 
> 
> Regards Samuel
> 
> _______________________________________________ Openembedded-core 
> mailing list Openembedded-core@lists.openembedded.org 
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


- --
>
>
>
>
>
>
> 
- -Khem
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iEYEARECAAYFAk48KVsACgkQuwUzVZGdMxSNaACffDYUHfK9qKdnYNdzCJCGr+3W
lqoAn2AFkMaezl4MLN7WbaE/zDjvu4vR
=pUFt
-----END PGP SIGNATURE-----



  reply	other threads:[~2011-08-05 17:37 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
2011-08-05  5:25         ` Samuel Stirtzel
2011-08-05 17:33           ` Khem Raj [this message]
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=4E3C295C.6060700@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