Opened 14 years ago
Closed 13 years ago
#6335 closed defect (fixed)
(again) issues with Japanese keyboards (jp106)
| Reported by: | Kalin KOZHUHAROV | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 3.1.4 |
| Keywords: | jp106, keyboard | Cc: | |
| Guest type: | Linux | Host type: | Linux |
Description
Recently I started seeing issues (again) with Japanese keyboard support in some guest under all Gentoo hosts. The hosts have similar configuration.
I have hit this before and I am almost sure I have commented and/or submitted it here, but I cannot find it :-(
Tickets #6046 and #5543 seem related.
jp106 layout can be seen here: http://www.vultaire.net/software/dvorak_jp106/dv106jp_white.png
I'll try to reproduce it in a more controlled environment, but for now booting a SysRescueCD in a newly created VM and pressing the pipe key (with Shift), left of the BackSpace produces this log:
00:00:07.757 Guest Log: BIOS: KBD: int09h_handler(): unknown scancode read: 0x7d!
Another key, left of the RightShift produces this:
00:11:30.894 Guest Log: BIOS: KBD: int09h_handler(): unknown scancode read: 0x73!
On the host those keys (from xev) produce the following:
KeyPress event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588425178, (498,-25), root:(635,809), state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False
KeyPress event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588427401, (498,-25), root:(635,809), state 0x1, keycode 133 (keysym 0x7c, bar), same_screen YES, XLookupString gives 1 bytes: (7c) "|" XmbLookupString gives 1 bytes: (7c) "|" XFilterEvent returns: False
KeyRelease event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588427522, (498,-25), root:(635,809), state 0x1, keycode 133 (keysym 0x7c, bar), same_screen YES, XLookupString gives 1 bytes: (7c) "|" XFilterEvent returns: False
KeyRelease event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588430014, (498,-25), root:(635,809), state 0x1, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
KeyPress event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588712421, (567,-130), root:(704,704), state 0x0, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False
KeyPress event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588712657, (567,-130), root:(704,704), state 0x1, keycode 211 (keysym 0x5f, underscore), same_screen YES, XLookupString gives 1 bytes: (5f) "_" XmbLookupString gives 1 bytes: (5f) "_" XFilterEvent returns: False
KeyRelease event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588712814, (567,-130), root:(704,704), state 0x1, keycode 211 (keysym 0x5f, underscore), same_screen YES, XLookupString gives 1 bytes: (5f) "_" XFilterEvent returns: False
KeyRelease event, serial 30, synthetic NO, window 0x3800001,
root 0x253, subw 0x0, time 1588713206, (567,-130), root:(704,704), state 0x1, keycode 62 (keysym 0xffe2, Shift_R), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False
Those keys are known to have caused problems before, but they worked till recently (January 2010?). I'll try to go back in versions to see where it changed.
Are you sure that this isn't a problem with the way you set up your guest system? The keys that you described are meant to produce scan codes 0x7d and 0x73, respectively, as per the error messages that you included. See the labeling on the second picture on this page:
http://www.win.tue.nl/~aeb/linux/kbd/scancodes-8.html
Those error messages do suggest that our BIOS does not correctly handle those keys, so that they will not work in DOS or boot loaders. Is that something that would cause you problems?