Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
No it's not weird. Sun keyboards are translated to i386 by the kernel in 2.6.xx. Use the i386 keyboard map for your locale and this annoyance will go away. --- Daniel E. Jonsen [EMAIL PROTECTED] wrote: I have an Ultra5 running a custom 2.6.8 kernel that I'm using as a LAMP server. I have a PCI USB 2.0 board installed so that I can use my PC104 USB keyboard mouse and put the Ultra5 on my 4-port USB KVM switch while I set everything up debug, then I'll yank the USB board and move the machine across the building to the server room, where there's plenty of space for the Sun type 5 keyboard mouse. The kernel I'm running now (USB kernel) has USB and full HID compiled-in and sun KB mouse as modules (not loaded). I also compiled the exact same kernel, but with Sun keyboard mouse compiled-in and all USB stuff as modules (Sun kernel). The whole time using the USB kernel, I had to have the Sun KB attached so that the machine wouldn't boot to a serial console, and to interact with the OpenFirmware prompt. I just tried booting with the Sun kernel after (using the USB kernel) running 'dpkg-reconfigure console-data' followed by 'dpkg-reconfigure console-common'. Using these two commands, I set the system keyboard map to sunkeymap, which is apparently correct for a Sun type 5 US keyboard. After rebooting, the system took no input from the USB keyboard and did take input from the Sun keyboard, as expected. However, what I didn't expect was this: the keys on the sun keyboard, even with the sunkeymap console mapping, generate exactly the same output as the keys on the USB keyboard when I run it with the Sun keyboard map. It's as though the Sun keyboard's firmware was reprogrammed to generate PC104 scan codes. No, I'm not on drugs. And the Sun keyboard works normally at the OpenFirmware prompt. Anyone have any clue what's causing this? Any idea how I can fix this? As a very slight aside, my keyboard actually has MODEL: TYPE 6 molded into the bottom, but it ran perfectly with the type 5 keymap before, and I've only ever read about type 6 keyboards in USB form. Thanks. Dan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
/dev/input/mice protocol ImPS/2 --- Daniel E. Jonsen [EMAIL PROTECTED] wrote: | So you're saying I should use the us (PC104) keyboard mapping even | with the Sun type 5 keyboard on a 2.6 kernel? Let me give it a shot... Any X keymap available ? This is what I used successfully in XF86Config-4 on a 2.4.27 kernel with the system (console) keyboard mapping set to sunkeymap: Section InputDevice Identifier Sun Keyboard Driver keyboard Option CoreKeyboard Option XkbRules sun Option XkbModel type5 Option XkbLayout us EndSection and this is what I'm using now, on a 2.6.8 kernel with the system (console) keyboard mapping set to us (pc104): Section InputDevice Identifier Sun Keyboard Driver keyboard Option CoreKeyboard Option Device/dev/input/event1 Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection I'm pretty sure that the 2.4 kernel didn't even need a Device entry like the 2.6 kernel does. Or maybe I accidentally deleted it. In any case, I tried the 2.6 kernel's block with sun and type5, but the key mappings were all wrong. AFAIK this might be the best one can do, but I'm the one with the questions in ths case, not the answers... The keyboard seems to be working OK now (except, as noted above by Vincent Pelletier, for a possible lack of special Sun key functionality), but I can't get the Sun serial mouse going. I tried /dev/sunmouse, which is what the 2.4 kernel liked, as well as /dev/input/mice (which is what the 2.6 kernel likes for the USB mouse) and /dev/input/mouse0 : Section InputDevice Identifier Sun Mouse Driver mouse Option CorePointer Option Device/dev/input/mouse0 Option Protocol BusMouse Option Emulate3Buttons true EndSection None of these work. /dev/sunmouse maps to no existing device, and apparently neither of the other two (existing) devices above correspond to the Sun mouse. If anybody out there with a Sun serial mouse working under XFree86 4.0 and a 2.6 kernel could send me their mouse section (as above), or if anyone could tell me what device a Sun serial mouse maps to under X, I'd be grateful. Actually, maybe the Protocol section might be wrong also (maybe ImPS/2 rather than BusMouse?), so please correct me there if that's the case. Thanks. Dan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Daniel E. Jonsen wrote: | So you're saying I should use the us (PC104) keyboard mapping even | with the Sun type 5 keyboard on a 2.6 kernel? Let me give it a shot... Afaik, there is no other way... But I'm interested in how to be able to use the sun keys, because some are detected as - for example - KP_ENTER. I'm not sure, but even some are detected as 2 different keys (they display 2 successive keycodes in xev, plus the release events). Any X keymap available ? Vincent Pelletier (PS: /me slaps thunderbird for always answering to the sender instead of the list. Sorry Daniel Jonsen...) -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCOW+oFEQoKRQyjtURAiIjAKCh6tbV3vT7KJVMvTEBZoDYwBzaUQCgi5Hq Z3zTA8YA+YFi+evHQ96d0Ps= =Tcar -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | /dev/input/mice | protocol ImPS/2 | | --- Daniel E. Jonsen [EMAIL PROTECTED] wrote: |If anybody out there with a Sun serial mouse working under XFree86 |4.0 and |a 2.6 kernel could send me their mouse section (as above), or if |anyone |could tell me what device a Sun serial mouse maps to under X, I'd be |grateful. Actually, maybe the Protocol section might be wrong also I have to unplug and replug the mouse once before getting it to work, but I only notice that on my home-built kernels... I find it really slow when it works. Vincent Pelletier -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCOXCPFEQoKRQyjtURAjxTAJ0f7yt+et0nJuC9LGqDdOBKQTK5YACZAXHL tra98TdTXyjBUwzEAI/9IkU= =eD68 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
On Thursday 17 March 2005 12:57, Vincent Pelletier wrote: I have to unplug and replug the mouse once before getting it to work, but I only notice that on my home-built kernels... I had to do the same when I set up X on my Ultra10 with type 5 kbd. pgp1qCvXeLqmT.pgp Description: PGP signature
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
Thanks, all! The mouse is working now. The config that works for me (custom 2.6.8 kernel on an Ultra5 with Type 5 (actually, type 6 on KB) serial keyboard Crossbow serial mouse), if anyone cares, is Section InputDevice Identifier Sun Mouse Driver mouse Option CorePointer Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons false EndSection When I had /dev/psaux as CorePointer, kdm caught Signal 11 refused to start up. No other discernable comments in kdm.log. I do have to unplug re-plug the mouse connector, though. Any thoughts on what's up with that? A minor annoyance, but since I'll be running this machine 24/7 anyway, it shouldn't be much of a problem for me. Thanks again. Dan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
As a very slight aside, my keyboard actually has MODEL: TYPE 6 molded into the bottom, but it ran perfectly with the type 5 keymap before, and I've only ever read about type 6 keyboards in USB form. Sun type 6 keyboards seem to be getting rarer (they mostly ship USB now) but they do exist. I'm writing this using one :-) Cheers, - Martin -- Martin [EMAIL PROTECTED] Seasons change, things come to pass -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
On Wednesday 16 March 2005 19:23, Daniel E. Jonsen wrote: It's as though the Sun keyboard's firmware was reprogrammed to generate PC104 scan codes. That's completely normal behavior with 2.6 kernels (where the input layer was redesigned). See the post-halloween-2.6.txt doc in kernel source Documentation dir. Cheers, FJP pgppuHwPAY3My.pgp Description: PGP signature
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
It's as though the Sun keyboard's firmware was reprogrammed to generate PC104 scan codes. That's completely normal behavior with 2.6 kernels (where the input layer was redesigned). So you're saying I should use the us (PC104) keyboard mapping even with the Sun type 5 keyboard on a 2.6 kernel? Let me give it a shot... See the post-halloween-2.6.txt doc in kernel source Documentation dir. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
| So you're saying I should use the us (PC104) keyboard mapping even | with the Sun type 5 keyboard on a 2.6 kernel? Let me give it a shot... Any X keymap available ? This is what I used successfully in XF86Config-4 on a 2.4.27 kernel with the system (console) keyboard mapping set to sunkeymap: Section InputDevice Identifier Sun Keyboard Driver keyboard Option CoreKeyboard Option XkbRules sun Option XkbModel type5 Option XkbLayout us EndSection and this is what I'm using now, on a 2.6.8 kernel with the system (console) keyboard mapping set to us (pc104): Section InputDevice Identifier Sun Keyboard Driver keyboard Option CoreKeyboard Option Device/dev/input/event1 Option XkbRules xfree86 Option XkbModel pc104 Option XkbLayout us EndSection I'm pretty sure that the 2.4 kernel didn't even need a Device entry like the 2.6 kernel does. Or maybe I accidentally deleted it. In any case, I tried the 2.6 kernel's block with sun and type5, but the key mappings were all wrong. AFAIK this might be the best one can do, but I'm the one with the questions in ths case, not the answers... The keyboard seems to be working OK now (except, as noted above by Vincent Pelletier, for a possible lack of special Sun key functionality), but I can't get the Sun serial mouse going. I tried /dev/sunmouse, which is what the 2.4 kernel liked, as well as /dev/input/mice (which is what the 2.6 kernel likes for the USB mouse) and /dev/input/mouse0 : Section InputDevice Identifier Sun Mouse Driver mouse Option CorePointer Option Device/dev/input/mouse0 Option Protocol BusMouse Option Emulate3Buttons true EndSection None of these work. /dev/sunmouse maps to no existing device, and apparently neither of the other two (existing) devices above correspond to the Sun mouse. If anybody out there with a Sun serial mouse working under XFree86 4.0 and a 2.6 kernel could send me their mouse section (as above), or if anyone could tell me what device a Sun serial mouse maps to under X, I'd be grateful. Actually, maybe the Protocol section might be wrong also (maybe ImPS/2 rather than BusMouse?), so please correct me there if that's the case. Thanks. Dan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: weird-o-rama: Type5 keyboard suddenly becomes PC104 keyboard...
In article [EMAIL PROTECTED] [EMAIL PROTECTED] writes: If anybody out there with a Sun serial mouse working under XFree86 4.0 and a 2.6 kernel could send me their mouse section (as above) Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/psaux Option Protocol ImPS/2 Option Emulate3Buttons false Option ZAxisMapping 4 5 EndSection Section InputDevice Identifier Generic Mouse Driver mouse Option SendCoreEventstrue Option Device/dev/input/mice Option Protocol ImPS/2 Option Emulate3Buttons true Option ZAxisMapping 4 5 EndSection Since /dev/input/mice doesn't exist, obviously the first one is being used. -- Blars Blarson [EMAIL PROTECTED] http://www.blars.org/blars.html With Microsoft, failure is not an option. It is a standard feature. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
