From: Frans Pop <elendil@planet.nl>
To: Thomas Bleher <ThomasBleher@gmx.de>
Cc: linux-kernel@vger.kernel.org, dada1@cosmosbay.com
Subject: Re: ARM on qemu: running kernel 2.6.20 or newer?
Date: Thu, 5 Jun 2008 16:44:06 +0200 [thread overview]
Message-ID: <200806051644.07430.elendil@planet.nl> (raw)
In-Reply-To: <20080605135149.GA20870@j-crew.de>
Thomas Bleher wrote:
> I'm trying to run an ARM kernel on qemu (0.9.1-5) on a Debian AMD64
> system. 2.6.19 worked fine, but all newer kernel releases[1] result in
> qemu consuming 100% of the CPU without ever outputting anything to the
> console.
The daily built armel versatile D-I images [1] worked fine for me in qemu
just a few days ago. They use 2.6.24. There's one issue [2] related to
serial console, but graphics mode works fine.
Cheers,
FJP
[1] http://wiki.debian.org/ArmEabiHowto
[2] http://bugs.debian.org/484366
next prev parent reply other threads:[~2008-06-05 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-05 13:53 ARM on qemu: running kernel 2.6.20 or newer? Thomas Bleher
2008-06-05 14:44 ` Frans Pop [this message]
2008-06-12 7:35 ` Thomas Bleher
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=200806051644.07430.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=ThomasBleher@gmx.de \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.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