Re: [Qemu-devel] unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
On Thu, Jan 24, 2019 at 08:34:50AM +, Burgess, Alison E wrote: > I am running Ubuntu 18.04 and I am sending this email because when > I try to run these series of commands in an executable file in > > > arm-none-eabi-as -mcpu=arm926ej-s -g ts.s -o ts.o > arm-none-eabi-gcc -c -mcpu=arm926ej-s -g t.c -o t.o > arm-none-eabi-ld -T t.ld ts.o t.o -o t.elf > arm-none-eabi-objcopy -O binary t.elf t.bin > arm-none-eabi-readelf -a t.elf > > rm *.o *.elf > > echo ready to go? > read dummy > > qemu-system-arm -M realview-pbx-a9 -m 128M -kernel t.bin \ > -serial mon:stdio -serial /dev/pts/0 -serial /dev/pts/0 -serial /dev/pts/0 > > (where the number in /dev/pts/# is the number I get when I run ps in the > terminal) > > The qemu terminal appears, but once I press 'Enter' again so that > my code runs, I am faced with the unknown keycodes `(unnamed)', > please report to qemu-devel@nongnu.org error message. After a couple > of hours searching online I have not been able to find a solution > and I have download and reinstalled qemu a couple of times. Can you tell us what version of QEMU you are using ? In addition what environment are you running it under ? X11 or Wayland or something else ? Finally, what keyboard layout is your environment setup to use ? Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
Re: [Qemu-devel] unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
On Thu, 24 Jan 2019 at 13:30, Burgess, Alison E wrote: > I am running Ubuntu 18.04 and I am sending this email because when I try to > run these series of commands in an executable file in > > > arm-none-eabi-as -mcpu=arm926ej-s -g ts.s -o ts.o > arm-none-eabi-gcc -c -mcpu=arm926ej-s -g t.c -o t.o > arm-none-eabi-ld -T t.ld ts.o t.o -o t.elf > arm-none-eabi-objcopy -O binary t.elf t.bin > arm-none-eabi-readelf -a t.elf > > rm *.o *.elf > > echo ready to go? > read dummy > > qemu-system-arm -M realview-pbx-a9 -m 128M -kernel t.bin \ > -serial mon:stdio -serial /dev/pts/0 -serial /dev/pts/0 -serial /dev/pts/0 > > (where the number in /dev/pts/# is the number I get when I run ps in the > terminal) > > The qemu terminal appears, but once I press 'Enter' again so that my code > runs, I am faced with the unknown keycodes `(unnamed)', please report to > qemu-devel@nongnu.org error message. After a couple of hours searching online > I have not been able to find a solution and I have download and reinstalled > qemu a couple of times. Hi; this warning message (a) can usually be ignored and (b) doesn't exist any more in new versions of QEMU. The chances are very high that your problem is not related to the warning message. You might also try using the latest version of QEMU (3.1). Those -serial options look very weird. My guess is your problem is either in those, or your guest binary simply is crashing without sending anything to the terminal. Is the guest binary known to work (eg on real hardware)? thanks -- PMM
[Qemu-devel] unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org
I am running Ubuntu 18.04 and I am sending this email because when I try to run these series of commands in an executable file in arm-none-eabi-as -mcpu=arm926ej-s -g ts.s -o ts.o arm-none-eabi-gcc -c -mcpu=arm926ej-s -g t.c -o t.o arm-none-eabi-ld -T t.ld ts.o t.o -o t.elf arm-none-eabi-objcopy -O binary t.elf t.bin arm-none-eabi-readelf -a t.elf rm *.o *.elf echo ready to go? read dummy qemu-system-arm -M realview-pbx-a9 -m 128M -kernel t.bin \ -serial mon:stdio -serial /dev/pts/0 -serial /dev/pts/0 -serial /dev/pts/0 (where the number in /dev/pts/# is the number I get when I run ps in the terminal) The qemu terminal appears, but once I press 'Enter' again so that my code runs, I am faced with the unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org error message. After a couple of hours searching online I have not been able to find a solution and I have download and reinstalled qemu a couple of times. Thanks, Alison Burgess
Re: [Qemu-devel] unknown keycodes
On Mon, Apr 23, 2018 at 05:31:28AM +0200, Thomas Huth wrote: > On 21.04.2018 11:27, Mike R wrote: > > (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to > > qemu-devel@nongnu.org > > > > reported. > > Well, please also report: > > - Which version of QEMU are you using? > > - Which keyboard layout do you have on your physical keyboard? > > - Which key did you press to get that message? > > - Which user interface of QEMU are you using (GTK, SDL1.2, SDL2 or VNC)? FYI, offlist we determined that it was QEMU 2.10 displaying over ssh on XQuartz display server. This is known to be broken because QEMU historically only understands the Linux evdev & kbd keycode mappings. QEMU 2.12 is much improved with explicit support for XQuartz and XWin, so hopefully the problem will be solved for this particular case. Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
Re: [Qemu-devel] unknown keycodes
On Mon, Apr 23, 2018 at 10:10:47AM +0100, Peter Maydell wrote: > On 23 April 2018 at 04:31, Thomas Huthwrote: > > On 21.04.2018 11:27, Mike R wrote: > >> (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to > >> qemu-devel@nongnu.org > >> > >> reported. > > > > Well, please also report: > > It's kind of our own fault that we didn't ask for those > sorts of details in that error message. I think that a lot > of the time it was reported without necessarily meaning that > any interesting keys weren't being handled correctly. > > In any case, as of commit 2ec78706d188 that message has > been removed, so the 2.12 release should fix this, or > at least not produce unhelpful warnings :-) Yes, if you get the same situation in 2.12, it will now print a much better mesage: g_warning("Unknown X11 keycode mapping '%s'.\n" "Please report to qemu-devel@nongnu.org\n" "including the following information:\n" "\n" " - Operating system\n" " - X11 Server\n" " - xprop -root\n" " - xdpyinfo\n", keycodes ? keycodes : ""); Regards, Daniel -- |: https://berrange.com -o-https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o-https://fstop138.berrange.com :| |: https://entangle-photo.org-o-https://www.instagram.com/dberrange :|
Re: [Qemu-devel] unknown keycodes
On 23 April 2018 at 04:31, Thomas Huthwrote: > On 21.04.2018 11:27, Mike R wrote: >> (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to >> qemu-devel@nongnu.org >> >> reported. > > Well, please also report: It's kind of our own fault that we didn't ask for those sorts of details in that error message. I think that a lot of the time it was reported without necessarily meaning that any interesting keys weren't being handled correctly. In any case, as of commit 2ec78706d188 that message has been removed, so the 2.12 release should fix this, or at least not produce unhelpful warnings :-) thanks -- PMM
Re: [Qemu-devel] unknown keycodes
On 21.04.2018 11:27, Mike R wrote: > (qemu) unknown keycodes `empty+aliases(qwerty)’, please report to > qemu-devel@nongnu.org > > reported. Well, please also report: - Which version of QEMU are you using? - Which keyboard layout do you have on your physical keyboard? - Which key did you press to get that message? - Which user interface of QEMU are you using (GTK, SDL1.2, SDL2 or VNC)? Thanks, Thomas signature.asc Description: OpenPGP digital signature
[Qemu-devel] unknown keycodes
(qemu) unknown keycodes `empty+aliases(qwerty)’, please report to qemu-devel@nongnu.org reported. signature.asc Description: Message signed with OpenPGP using GPGMail
Re: [Qemu-devel] unknown keycodes `(unnamed)'
On 19.10.2017 21:23, Spaceboy Ross wrote: > unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org > > uname -a returns: > > Linux spaceboyross-Latitude-D630 4.13.0-16-generic #19-Ubuntu SMP Wed > Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > Please be more specific: Which key did you press to get that output? Which keyboard layout (language) are you using? Which version of QEMU is this? What kind of user interface are you using (GTK? SDL? VNC?). Thomas
[Qemu-devel] unknown keycodes `(unnamed)'
unknown keycodes `(unnamed)', please report to qemu-devel@nongnu.org uname -a returns: Linux spaceboyross-Latitude-D630 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
[Qemu-devel] unknown keycodes
Hello, I’m running OS X 10.5.10 running the X11 server XQuartz 2.7.7 (xorg-server 1.15.2). Qemu is running on freeBSD being transmitted to the local machine over SSH. Qemu version: QEMU PC emulator version 0.11.1, Copyright (c) 2003-2008 Fabrice Bellard. All keypresses seem to send the incorrect keys to the VM. I got this error message on the command line: dan@core: % ./9cpu-start.sh [2] 62405 dan@core: % unknown keycodes `empty_aliases(qwerty)', please report to qemu-devel@nongnu.org Here is the startup command: # Run the instance qemu-system-x86_64 \ -net nic,model=virtio,macaddr=52:54:00:00:EE:03 \ -net tap,name=tap0,script=no \ -cdrom 9front-4308.4e3f4e43246e.iso -boot d \ -hda ./sda.img ; Regards Daniel
Re: [Qemu-devel] unknown keycodes
Daniel P. Berrange berrange at redhat.com writes: Good, those are the interesting bits I wanted to see _XKB_RULES_NAMES(STRING) = base, empty, empty, , I'll prepare a patch to test out which ought to fix OS-X Regards, Daniel Any luck with this patch? I'm having the same issue: Mac OS X, XQuartz - Ubuntu X11/XAuth server - QEMU
Re: [Qemu-devel] unknown keycodes
Matt Brennan matty.bren...@gmail.com writes: Hi - I am running on an OS X 10.8.2 (Mountain Lion) laptop, with XQuartz installed, using SSH -X in to a ubuntu machine where qemu is attempting to run Raspberry Pi. $ qemu-system-arm -kernel kernel-qemu -cpu arm1176 -m 512 -M versatilepb -no-reboot -serial stdio -append root=/dev/sda2 panic=1 -hda 2012-08-08-wheezy-armel.img Uncompressing Linux... done, booting the kernel. unknown keycodes `empty_aliases(qwerty)', please report to qemu-devel@nongnu.org Just wanted to pass that error along as directed. This is from ui/sdl.c; cc'ing maintainer.
[Qemu-devel] unknown keycodes 'macintosh_aliases(qwertz)'
Hi, as requested by the qemu software, here's my report that qemu says unknown keycodes `macintosh_aliases(qwertz)', please report to qemu-devel@nongnu.org % qemu-system-ppc --version QEMU emulator version 1.0 (Debian 1.0+dfsg-3), Copyright (c) 2003-2008 Fabrice Bellard % uname -a Linux ibook 3.3.0-rc3-04608-ge9badff4-dirty #78 Thu Mar 1 02:23:27 CET 2012 ppc GNU/Linux % cat /proc/cpuinfo processor : 0 cpu : 7455, altivec supported clock : 606.00MHz revision: 3.3 (pvr 8001 0303) bogomips: 36.86 timebase: 18432000 platform: PowerMac model : PowerBook6,3 machine : PowerBook6,3 motherboard : PowerBook6,3 MacRISC3 Power Macintosh detected as : 287 (iBook G4) pmac flags : 001b L2 cache: 256K unified pmac-generation : NewWorld Memory : 640 MB % Xorg -version X.Org X Server 1.11.3.901 (1.11.4 RC 1) Release Date: 2012-01-06 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32-5-powerpc64 ppc Debian Current Operating System: Linux ibook 3.3.0-rc3-04608-ge9badff4-dirty #78 Thu Mar 1 02:23:27 CET 2012 ppc Kernel command line: BOOT_IMAGE=(first-boot,apple4)/boot/vmlinuz-3.3.0-rc3-04608-ge9badff4-dirty root=/dev/sda4 ro nosmp radeon.agpmode=1 netconsole=@192.168.0.5/eth0,@192.16.0.1/ Build Date: 19 January 2012 10:30:00AM xorg-server 2:1.11.3.901-2 (Cyril Brulebois k...@debian.org) Current version of pixman: 0.24.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. % xdpyinfo name of display::0 version number:11.0 vendor string:The X.Org Foundation vendor release number:11103901 X.Org version: 1.11.3.901 maximum request size: 16777212 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, MSBFirst, 32 image byte order:MSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x204, revert to None number of extensions:28 BIG-REQUESTS Composite DAMAGE DOUBLE-BUFFER DPMS DRI2 GLX Generic Event Extension MIT-SCREEN-SAVER MIT-SHM RANDR RECORD RENDER SECURITY SGI-GLX SHAPE SYNC X-Resource XC-MISC XFIXES XFree86-DGA XFree86-VidModeExtension XINERAMA XInputExtension XKEYBOARD XTEST XVideo XVideo-MotionCompensation default screen number:0 number of screens:1 screen #0: dimensions:1920x1080 pixels (477x268 millimeters) resolution:102x102 dots per inch depths (7):16, 1, 4, 8, 15, 24, 32 root window id:0x106 depth of root window:16 planes number of colormaps:minimum 1, maximum 1 default colormap:0x20 default number of colormap cells:64 preallocated pixels:black 0, white 65535 options:backing-store NO, save-unders NO largest cursor:64x64 current input event mask:0xfa200c ButtonPressMask ButtonReleaseMaskButtonMotionMask StructureNotifyMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask ColormapChangeMask number of visuals:33 default visual id: 0x21 visual: visual id:0x21 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0x22 class:DirectColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0xe7 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0xe8 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0xe9 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0xea class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:
Re: [Qemu-devel] unknown keycodes 'macintosh_aliases(qwertz)'
On Fri, Mar 02, 2012 at 12:21:49PM +0100, Jörg Sommer wrote: Hi, as requested by the qemu software, here's my report that qemu says unknown keycodes `macintosh_aliases(qwertz)', please report to qemu-devel@nongnu.org Thanks for the information, I have posted patches a few weeks back which should fix this problem: https://lists.gnu.org/archive/html/qemu-devel/2012-01/msg02210.html I will be posted a second version of the patches soon, with a view to getting this fixed in the next QEMU release Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
Re: [Qemu-devel] unknown keycodes
On Mon, Jan 16, 2012 at 08:04:32AM +0100, Daniel Espling wrote: Hi Daniel, please find the output of xdpyinfo and xprop attached, I checked the output from both the linux server side and the OSX client, but the only difference is the name of display parameter so I included only that of the linux server. Regards, Daniel number of extensions:23 Apple-DRI Apple-WM Good, those are the interesting bits I wanted to see _XKB_RULES_NAMES(STRING) = base, empty, empty, , I'll prepare a patch to test out which ought to fix OS-X Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
[Qemu-devel] unknown keycodes
Hi! getting the following message: unknown keycodes `empty_aliases(qwerty)', please report to qemu-devel@nongnu.org I'm connecting to a ubuntu 10.04 server running qemu 1.0.50 forwarding X11. Locally I'm on a Macbook pro with Swedish keyboard layout. When I run qemu my keyboard is totally messed up (Enter becomes j, j becomes 7 etc.). Running with -k en-us works but restricts me to english characters (swedish characters generates keysym errors, which is expected) my locale is: LANG=en_US.UTF-8 LC_CTYPE=sv_SE.UTF-8 LC_NUMERIC=en_US.UTF-8 LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8 LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8 LC_PAPER=en_US.UTF-8 LC_NAME=en_US.UTF-8 LC_ADDRESS=en_US.UTF-8 LC_TELEPHONE=en_US.UTF-8 LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=en_US.UTF-8 LC_ALL= Regards, Daniel
Re: [Qemu-devel] unknown keycodes
On Thu, Jan 12, 2012 at 09:56:46AM +0100, Daniel Espling wrote: Hi! getting the following message: unknown keycodes `empty_aliases(qwerty)', please report to qemu-devel@nongnu.org I'm connecting to a ubuntu 10.04 server running qemu 1.0.50 forwarding X11. Locally I'm on a Macbook pro with Swedish keyboard layout. When I run qemu my keyboard is totally messed up (Enter becomes j, j becomes 7 etc.). Running with -k en-us works but restricts me to english characters (swedish characters generates keysym errors, which is expected) Unfortunately, the SDL code as written pretty much only copes with an XFree86 server running on a Linux host. Running any kind of X server on OS-X or Windows and forwarding to an app running Linux will result in fubar keyboard mappings as you see. The problem is that keymapping code assumes that it is getting either a'xt' or 'evdev' based keycodes from the X server. On OS-X you instead get a variant on Mac OS keycodes which are completely different. I've solved this problem in GTK-VNC by adding checks for the OS-X and Win32 X servers: http://git.gnome.org/browse/gtk-vnc/tree/src/vncdisplaykeymap.c Can you provide the output of 'xdpyinfo' and 'xprop -root | grep XKB' just so I can confirm my code will work. If so, I'll port the GTK-VNC code to QEMU's SDL display to fix this. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
[Qemu-devel] unknown keycodes error
Hello, I created a vm with ubuntu-vm-creator: sudo ubuntu-vm-builder kvm oneiric --user user --pass test When I execute ./run.sh I get the following errors: kvm: pci_add_option_rom: failed to find romfile pxe-rtl8139.bin unknown keycodes `empty_aliases(qwerty)', please report to qemu-devel@nongnu.org When I try to type in the vm my keyboard is basically scrambled; for example, q is now -, w is now =, e is now backspace, etc. If you want any info from me let me know! Thanks. Jordan Fix
[Qemu-devel] unknown keycodes
qemu -cdrom /dev/acd1 -hda kwinxp.img -m 512 -boot d -localtime unknown keycodes `sun(type6_usb)_aliases(qwerty)', please report to qemu-devel@nongnu.org uname -a FreeBSD freew.t-s-f.com.au 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 If you need any more, please contact me. Cheers, Henry
Re: [Qemu-devel] unknown keycodes
On 01/18/2011 07:22 PM, Henry Grebler wrote: qemu -cdrom /dev/acd1 -hda kwinxp.img -m 512 -boot d -localtime unknown keycodes `sun(type6_usb)_aliases(qwerty)', please report to qemu-devel@nongnu.org Thanks, you can work around this by using -k en-us. Regards, Anthony Liguori uname -a FreeBSD freew.t-s-f.com.au 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009 r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 If you need any more, please contact me. Cheers, Henry