All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joerg Platte <lists@naasa.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Sparc32 bash problem solved
Date: Sun, 28 May 2006 00:14:45 +0200	[thread overview]
Message-ID: <200605280014.45882.lists@naasa.net> (raw)
In-Reply-To: <200605272221.44155.lists@naasa.net>

Am Samstag, 27. Mai 2006 22:21 schrieb Joerg Platte:
> Yes, booting a small system with udev works! qemu in graphical mode boots
> up to the login prompt. But unfortunately each character i tried to type in
> is corrupt. Hence, its not possible to log in. In console mode getty causes
> a kernel oops. But it works now much better than before. Many thanks!

The oops and the corrupted characters are caused by the console-tools. After 
removing them everything works as expected! I was able to boot from the same 
image I used on a real 32 bit SPARC! I can log in and even log in again via 
ssh to localhost :-). Great work!

regards,
Jörg

  reply	other threads:[~2006-05-27 22:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-27 19:30 [Qemu-devel] Sparc32 bash problem solved Blue Swirl
2006-05-27 20:21 ` Joerg Platte
2006-05-27 22:14   ` Joerg Platte [this message]
2006-05-28  8:19   ` Blue Swirl

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=200605280014.45882.lists@naasa.net \
    --to=lists@naasa.net \
    --cc=jplatte@naasa.net \
    --cc=qemu-devel@nongnu.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.