qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Bochnig, Martin" <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Keyboard problem in qemu 0.6.0-2
Date: Fri, 03 Sep 2004 19:13:42 +0200	[thread overview]
Message-ID: <4138A646.3000500@gmx.com> (raw)
In-Reply-To: <413943E6.1000901@bigpond.net.au>

Kim Adil wrote:
> I seem to have a default keymap to the french keyboard layout. I thought 
> it must be defined in the guest os images that I downloaded, however, I 
> tried booting a windows XP setup disk and the same key layout was 
> experienced. Is there a way to alter this?

Hi,

I have similar problems with a Solaris10_x86 host running QEMU 0.6.0 
when displaying to the default Xsun X-Server at ':0.0' or forwarding to 
my SPARC machines running several Solaris versions.

These problems make QEMU (any Guest OS's command line, any input fields) 
completely unusable.

Almost exactly the same DISmapping appeared, when running the prebuilt 
0.6.0 LinUX binary on the JDS1_Live Demo CD (while the mapping itself 
was different).
Since no one else complained about it, my HOST and my machines 
displaying QEMU's window over the network appeared to be the cause.

Both the physical Keyboards itself (different vendors, different 
interfaces [ps/2 and usb]) as well as all guest and host OS's use 
US-English / POSIX C 7bit as default locale.

I had the same problem at University when running 0.6.0 on a Debian 
system installed in 2001.

On most of these systems
"qwertyui"
  is interpreted by the guest as
"rp6tu]i0".
Many keys do nothing at all. Others give strange control seqences with 
their ascii hex id printed to the guest console.

I posted to the ml around a week ago but didn't get reports of others 
confirming my experiences.
Am I the only one worldwide (your problem description still sounds quite 
moderate, as your keys are still in a usual sequential order - just 
shifted by a few keys) ?

WORKAROUND: First ensure that you have installed the very latest SDL 
release (unfortunately doing so didn't solve above problems in any way - 
however).
***The solution was to upgrade the HOST to the latest XFree86 4.x (that 
is to replace Xsun)***
***Alternatively it may help to use VNC4.x (which actually uses/includes 
a minimal - XFree86 4.x server)***.
So the misbehavior seems to be Host-X11_Server dependent.
The key mappings between SDL<<--->>X11 seem to be the root of these errors.
A bug in qemu, as it doesn's support forwarding to proprietary or even 
free X11 servers, when too old.
(maybe an XFree86_4.x--only specific option not supported by anything else?)

Another alternative is: Go to http://www.dad-answers.com/qemu , download 
the NOsdl-patch, copy 'nosdl.c' over 'sdl.c' , type
"make distclean;./configure;make" then switch user to root and do a make 
install.

Worked for me.


--

Martin

  reply	other threads:[~2004-09-03 17:21 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <ksadil@bigpond.net.au>
2004-09-04  1:07 ` [Qemu-devel] Keyboard problem in qemu 0.6.0-2 Kim Adil
2004-09-03 11:54   ` Mark Williamson
2004-09-04  2:07     ` Kim Adil
2004-09-03 12:28       ` Mark Williamson
2004-09-04  2:34         ` Kim Adil
2004-09-04  2:38           ` Kim Adil
2004-09-04  4:26             ` Kim Adil
2004-09-03 17:13               ` Bochnig, Martin [this message]
2004-09-03 17:33                 ` Bochnig, Martin
2004-09-04  1:53                 ` Kim Adil
2004-09-04  7:18                   ` Bochnig, Martin
2004-09-04  7:55                     ` Bochnig, Martin
     [not found] <200409032051.i83KpOLj027201@tiger2.tools.intra>
2004-09-03 21:11 ` Bochnig, Martin
2004-09-03 17:38 Juergen Keil
2004-09-03 20:06 ` Bochnig, Martin
2004-09-03 20:22   ` Bochnig, Martin
2004-09-03 20:44 ` Fabrice Bellard
2004-09-06 14:16   ` Johannes Schindelin
2004-09-07 13:27   ` Johannes Schindelin

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=4138A646.3000500@gmx.com \
    --to=mb1x@gmx.com \
    --cc=bochnig@pool.math.tu-berlin.de \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).