Typing "|" (pipe) in console with keyboard layout jp106 does not work with any 2.6 (or any of the later 2.5) kernels. Currently using: sys-apps/kbd-1.08-r4 sys-kernel/development-sources-2.6.1-rc1 sys-libs/glibc-2.3.3_pre20031222
Also #~ on some GB keyboards... http://marc.theaimsgroup.com/?l=linux-kernel&m=107363687730772&w=2
Same here, but the problem was solved on my ~x86 box after I emerged linux-headers-2.6.0, remerged kbd-1.08-r4 and changed the keycode for backslash bar to 182 in /usr/share/keymaps/i386/qwerty/jp106.map.gz. (keycode 182 = backslash bar control keycode 182 = Control_backslash)
additionally with my current kernel, i've found that two keys return the same scancode. the keys are "\"-"|" key (corresponding to keycode 182 as explained by usata) and the "katakana/hiragana"-"romaji" key with the scancode returned for both being 0x7d for keydown and 0xfd for keyup.
maybe /var/tmp not world writable?
have confirmed that usata's solution works. however, the romaji key is still of course duplicating the behaviour of the \| key. Other keys that aren't working properly are the hankaku-zenkaku/kanji key (which is duplicating the tab key in console when pressed twice!?), the muhenkou key (no real problem) and the \_ key (which i'll try and find an appropriate keycode for). will also confirm whether kbd built against 2.6 headers will work correctly under 2.4.
the rebuild kbd works flawlessly under 2.4 except for the remapped keycode.
Please apply the following patch, it should fix this. ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.1/2.6.1-mm4/broken-out/keyboard-scancode-fixes.patch This patch (or a slight variation on it) will almost certainly be included in 2.6.2, but if anyone's bumping d-s or g-d-s revisions it's probably worth adding this in.
John, can you please add this to gentoo-dev-sources? As for development-sources we'd like to keep that ``as vanilla as it gets'' so we'll carry this over when it's added to 2.6.2. Thanks for the patch reference, Ciaran.
hopefully this has now been solved in the newer 2.6.2 sources. please bump and retry
