Opened 17 years ago
Closed 17 years ago
#1682 closed defect (fixed)
Japanese Keyboard does not work on Opensuse 10.3 x64
Reported by: | Georges | Owned by: | |
---|---|---|---|
Component: | other | Version: | VirtualBox 1.6.2 |
Keywords: | keyboard japanese | Cc: | |
Guest type: | other | Host type: | other |
Description
On Opensuse 10.3 x64, Virtualbox 1.6.2, the 106 keys japanese keyboard has missing keys (in fact it seems to be recognised as an US keyboard). => Typically, no: "@"... which makes typing email address more complex -:)
The guest OS is XP English, but the same issue appears on Ubuntu Hardy.
[By the way the keyboard works perfectly on the host -:) , I had the same issue with 1.6.0 version and I hoped it would be solved on the 1.6.2 release. I tried (without success) the tricks of the preivous ticket on the same subject .]
Thanks for your help!!
Attachments (7)
Change History (22)
comment:1 by , 17 years ago
comment:2 by , 17 years ago
Hi, sorry for the delay in answering, I was out of town.
So, nothing special on this keyboard (apart from being Japanese, the standard one you can see at wikipedia: http://en.wikipedia.org/wiki/Image:KB_Japanese.svg)
No ssh or other way either. => Just simple keyboard usb connected on an intel PC x64
I put the VBox.log for reference (in attachment). You are right there is a warning from VirtualBox: What do you advise?
Thx
by , 17 years ago
Attachment: | VBoxKeyboard.so added |
---|
Updated VirtualBox keyboard library (Linux 64bit, version 1.6.2 ONLY)
by , 17 years ago
Attachment: | VBoxKeyboard.tar.gz added |
---|
Updated VirtualBox keyboard library (source code)
comment:3 by , 17 years ago
Try the updated keyboard handler library I have attached (back up your old one first!) and see if it helps.
comment:4 by , 17 years ago
Hi,
... I tried... here is the new log ...
I suppose I changed the right file (the older one was rename .ORG not to interfere).
[Under /usr/lib64 ?]
The good news: no major issue. The bad one: still an US Keyboard... I attached the log.
Next try? thx!
comment:5 by , 17 years ago
Just to be sure, you did select the right keyboard layout in the guest, didn't you?
comment:6 by , 17 years ago
Yes, in Windows I searched for the 106 keyboard.
But the Vbox log (the newest one), even if I had "botched" it, would not show this error would it?
Thx!
comment:7 by , 17 years ago
It could show that error for other reasons. I just meant that if you had selected Japanese layout in the host system but US in the guest, you would obviously have the symptoms you described.
I will prepare a version of the library which produces more debug information.
comment:8 by , 17 years ago
OK thx, I will try it (it is now 21:40 here in Japan), so I guess the try will be for to-morrow -:)
comment:9 by , 17 years ago
Hi Michael,
I rechecked this morning using "Ubuntu Hardy" as Guest (instead of XP English): It works.
I retried on XP English, unistall the Japanese keyboard 106/109... reinstall in case of... with no success.
So with Ubuntu check, it concludes that your patch works (though I have still the same error message in the log)... For XP I guess there is another issue.
The automatic updater installed a new kernel.. so now I cannot /etc/init.d/vboxdrv setup ... so that will restrict my tests -:).
by , 17 years ago
Attachment: | VBox_Ubuntu.log added |
---|
Works with Ubuntu now, though the error message is still there.
comment:10 by , 17 years ago
An update:
- The Kernel issue is solved (just downloaded the kernel sources...)
- I installed XP Japanese, and yes it did recognize the Japanese keyboard (with your patch)!
- Then I re-installed XP English... and it works now...
The Error on the log still remains though... but it is no longer a concern for me -:) => Thanks for your help and efficiency!
comment:11 by , 17 years ago
Hello georges,
I took slightly longer to respond than I meant. Could you try executing a virtual machine from the command line as follows:
$ LOG_KB_SECONDARY=1 VirtualBox -startvm <VM name>
and capture the output on the console in a file and post that here? I would like to find the reason for that log error, the more so since everything seems to be working now (printing errors when there are none doesn't help anyone :) ).
Thanks!
comment:12 by , 17 years ago
Hi Michael,
I would tend to agree...
I tried but I always get an error message:
Could not find a registered machine named '/opt/VirtualBox/Ubuntu 8.02/UbuntuHardDisk.vdi'.
Result Code: 0x80070057 Component: VirtualBox Interface: IVirtualBox {2d3b9ea7-25f5-4f07-a8e1-7dd7e0dcf667}
I tried direct name (from the right directory)... to no avail...
I checked that: VBoxManage showvdiinfo /opt/VirtualBox/Ubuntu\ 8.02/UbuntuHardDisk.vdi ... works fine: (C) 2005-2008 Sun Microsystems, Inc. All rights reserved.
UUID: 34f55696-7737-4ace-94a8-2a8daa8e2b4a Registered: yes Accessible: yes Size: 3905 MBytes Current size on disk: 3905 MBytes Type: standard Storage type: Virtual Disk Image (VDI) In use by VM: cb235fee-a477-4fcb-3ba7-0040083b8483 Path: /opt/VirtualBox/Ubuntu 8.02/UbuntuHardDisk.vdi
... so ready to help... provided I can do it. [for info I did it on ubuntu to avoid any side XP issues, and the error log does show], by the way vboxmanage does not like much cdi bigger than 4GB...?
Ready to help
comment:13 by , 17 years ago
Sorry for the delay. <VM Name> means the name you have given to the virtual machine, not the hard disk file name. At a guess, from the output you supplied above, your VM name is "Ubuntu 8.02".
comment:14 by , 17 years ago
Thx, now it works much better... I added a small modification to give you more information: LOG_KB_SECONDARY=1 VirtualBox -startvm "Ubuntu 8.04" > output.log
I attached both files
Enjoy.
comment:15 by , 17 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
The warning messages should be gone in the next version. Thanks for your help!
Is there any keyboard related stuff at the top of the log file for the machine? (Normally under ~/.VirtualBox/Machines/<machine name>/Logs/VBox.log). Are you using a standard PC locally (i.e. no ssh), or is there anything "non-standard" about your keyboard setup that you can think of?