| View previous topic :: View next topic |
| Author |
Message |
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
 Posted: Thu Sep 28, 2006 5:07 am Post subject: |
 |
|
| Quote: | | P.S. The reason why I didn't use symlinks whas that the evdev X driver accept only /dev/input/event* names for the devices (man 4x evdev, one of the most obscure and frustrating man pages I've ever read, especially in the part regarding the capabilities bits). |
I read that before, but as I said, with xF86-input-evdev-1.0.0.5, symlinks were working, but now they no longer work. And for the man page, I've been really frustrated till I unmask xorg-7.1 and its corresponding drivers, because, there was no man page before!
| Quote: |
DON'T USE event0 or 1, as a rule. They might be already existing if you plug in your mouse before your keyboard os samething like that. Using a higher number (event20 and 21 or similar) as in my howto should prevent nasty, even if occasional, surprises. |
That won't happen since I've got a rule for my mouse, and two rules for the keyboard, but, one day I may plug an other input device and have some problem, I will change that, even if there are very few chances that I have this problem.
| talk: in the wiki wrote: | | Unfortunately the custom "One" key and the "Print" key are both managed by the same device so their codes inevitably overlap. |
Here is what I have:
I've made some tests and startx with input/event0 only (see my udev rules:ATTRS{modalias}=="usb:v045Ep00DBd0173dc00dsc00dp00ic03isc00ip00" ) and the evdevdriver:
result: none of the normal keys was working, but every multimedia keys were working. (notethat the print didn't work)
That 's why I kept this input device as the seconderary keyboard (SendCoreEvents ).
using my confiuration, here is the print key in xev, the "one" key ("XF86Launch1" from my settings)
| Quote: | KeyPress event, serial 29, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057567850, (1,62), root:(659,597),
state 0x10, keycode 111 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057567954, (1,62), root:(659,597),
state 0x10, keycode 111 (keysym 0xff61, Print), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057570891, (1,62), root:(659,597),
state 0x10, keycode 218 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057571003, (1,62), root:(659,597),
state 0x10, keycode 218 (keysym 0x1008ff41, XF86Launch1), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057573699, (1,62), root:(659,597),
state 0x10, keycode 116 (keysym 0xffec, Super_R), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057573843, (1,62), root:(659,597),
state 0x50, keycode 116 (keysym 0xffec, Super_R), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
KeyPress event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057575634, (1,62), root:(659,597),
state 0x10, keycode 104 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 32, synthetic NO, window 0x400001,
root 0x107, subw 0x0, time 4057575778, (1,62), root:(659,597),
state 0x10, keycode 104 (keysym 0xff54, Down), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
|
(super_R is the favorite key)
I don't seem to have the problem you were talking about?
| Quote: | | I've written to liyu |
I've also mailed him a week ago, but didn't get any answer, I hope you'll have more chances that I had 
(he must be fed up every one is writting him :/ )
_________________
The End of the Internet! |
|
| Back to top |
|
 |
trantorvega
n00b
Joined: 19 Sep 2005
Posts: 13
|
| Posted: Thu Sep 28, 2006 6:26 am Post subject: |
|
|
I believe we don't understand each other properly.
| trantorvega wrote: |
On the other hand the key number 1 and the Print key are both managed by the same evdev-driven InputDevice, so they still have the same keycode. |
If they are managed by the same device by logic I must refer to two additional keys, and therefore I cannot be referring to the good old Print key, which is not an additional key.
The only other possible match must be the non-F-locked version of F12, as i clearly stated in the howto. Of course if you have a french keyboard it won't be labelled Print, just like in my keyboard its label is "Stampa". What matters are KEYCODES.
Please read, if you've not already done so, the howto with attention, in order to avoid further misunderstandings or misinterpretations. I realize it's long, but that's for a reason.
About your tries with event0 again I explained in the howto why that cannot possibly work. The use of two InputDevices (evdev+evdev or kbd+evdev) follows from that explanation.
| truc wrote: |
I've also mailed him a week ago, but didn't get any answer, I hope you'll have more chances that I had
(he must be fed up every one is writting him :/ )
|
I've received more than one answer.
See this thread http://www.ubuntuforums.org/showthread.php?t=229559 .
P.S. An additional thread here. https://forums.gentoo.org/viewtopic-t-390636-highlight-.html
It's the thread where powerman posted about the patches that I subsequently linked into the howto. |
|
| Back to top |
|
|
gudok
n00b
Joined: 30 Sep 2006
Posts: 5
|
| Posted: Sat Sep 30, 2006 12:18 pm Post subject: |
|
|
I have a problem using HOWTO.
I recompiled the kernel and all multimedia buttons are working now in console mode.
But I can`t get XServer working with two logical keyboards - it says:
| Code: | (II) evdev brain: Rescanning devices (1).
(II) Keyboard2-usb-0000:00:02.1-1/input1: Found 1 absolute axes.
(II) Keyboard2-usb-0000:00:02.1-1/input1: Configuring as pointer.
(**) Keyboard2-usb-0000:00:02.1-1/input1: Configuring in Absolute mode.
(**) Keyboard2-usb-0000:00:02.1-1/input1: AbsoluteScreen: -1.
Backtrace:
0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4334]
1: [0xffffe420]
2: /usr/lib/xorg/modules/input/evdev_drv.so [0xa7f84638]
3: /usr/lib/xorg/modules/input/evdev_drv.so [0xa7f856eb]
4: /usr/lib/xorg/modules/input/evdev_drv.so(evdevNewDriver+0x4c) [0xa7f8584c]
5: /usr/lib/xorg/modules/input/evdev_drv.so [0xa7f843e8]
6: /usr/bin/X(InitInput+0x176) [0x809f7e6]
7: /usr/bin/X(main+0x35f) [0x806e56f]
8: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xa7d96ea8]
9: /usr/bin/X(FontFileCompleteXLFD+0xa9) [0x806d9d1]
Fatal server error:
Caught signal 11. Server aborting
|
As you can see evdev detects second keyboard as mouse.
I also tried using "keyboard" driver for the first logical keyboard and "evdev" for the second one - the same result. It seems that "evdev" can work only with core keyboard device.
Can you help?
P.S.: I use Xorg-7.1.0-1 and Xorg-input-evdev-1.1.2-3 - they seem to be the latest versions. |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sat Sep 30, 2006 12:21 pm Post subject: |
|
|
post your udev rules, ls -l /dev/input, the relevent section in xorg.conf (as I did before), if you've just modified your udev rules, don't forget to run udevstart.
_________________
The End of the Internet! |
|
| Back to top |
|
|
gudok
n00b
Joined: 30 Sep 2006
Posts: 5
|
| Posted: Sat Sep 30, 2006 2:30 pm Post subject: |
|
|
| truc wrote: | | post your udev rules, ls -l /dev/input, the relevent section in xorg.conf (as I did before), if you've just modified your udev rules, don't forget to run udevstart. |
I didn`t change my udev rules - I use information from /proc/bus/input/devices:
| Code: | I: Bus=0003 Vendor=046d Product=c01d Version=2100
N: Name="Logitech USB-PS/2 Optical Mouse"
P: Phys=usb-0000:00:02.0-1/input0
S: Sysfs=/class/input/input0
H: Handlers=event0 ts0 mouse0
B: EV=7
B: KEY=ff0000 0 0 0 0 0 0 0 0
B: REL=103
I: Bus=0003 Vendor=045e Product=00db Version=0173
N: Name="Microsoft Natural╝ Ergonomic Keyboard 4000"
P: Phys=usb-0000:00:02.1-1/input0
S: Sysfs=/class/input/input1
H: Handlers=kbd event1
B: EV=120003
B: KEY=10000 7 ff800000 7ff febeffdf f3cfffff ffffffff fffffffe
B: LED=7
I: Bus=0003 Vendor=045e Product=00db Version=0173
N: Name="Microsoft Natural╝ Ergonomic Keyboard 4000"
P: Phys=usb-0000:00:02.1-1/input1
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=10000f
B: KEY=7c0000 0 c0002 1400 0 0 1 10f80 287c407 ffff39fa d97157ff febeffdf ffefffff ffffffff fffffffe
B: REL=40
B: ABS=1 0
|
| Code: | fors:~% ls -lR /dev/input
/dev/input:
ØâÞÓÞ 0
drwxr-xr-x 2 root root 100 2006-09-30 16:34 by-id
drwxr-xr-x 2 root root 140 2006-09-30 16:34 by-path
crw-rw---- 1 root root 13, 64 2006-09-30 16:34 event0
crw-rw---- 1 root root 13, 65 2006-09-30 16:34 event1
crw-rw---- 1 root root 13, 66 2006-09-30 16:34 event2
crw-rw---- 1 root root 13, 67 2006-09-30 16:34 event3
crw-rw---- 1 root root 13, 63 2006-09-30 16:34 mice
crw-rw---- 1 root root 13, 32 2006-09-30 16:34 mouse0
crw-rw---- 1 root root 13, 128 2006-09-30 16:34 ts0
/dev/input/by-id:
ØâÞÓÞ 0
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 usb-Logitech_USB-PS.2_Optical_Mouse-event-mouse -> ../event0
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 usb-Logitech_USB-PS.2_Optical_Mouse-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 usb-Microsoft_Natural_Ergonomic_Keyboard_4000-event-kbd -> ../event1
/dev/input/by-path:
ØâÞÓÞ 0
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 pci-0000:00:02.0-usb-0:1:1.0-event-mouse -> ../event0
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 pci-0000:00:02.0-usb-0:1:1.0-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 pci-0000:00:02.1-usb-0:1:1.0-event-kbd -> ../event1
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 pci-0000:00:02.1-usb-0:1:1.1-event- -> ../event2
lrwxrwxrwx 1 root root 9 2006-09-30 16:34 platform-pcspkr-event-spkr -> ../event3
|
And here is my xorg.conf:
| Code: | ...
Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event1"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp:shift_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
Identifier "Keyboard2"
Driver "evdev"
Option "Device" "/dev/input/event2"
Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
Option "XkbModel" "microsoftnek4k"
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp:shift_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
# Logitech MX510 mouse
Identifier "Mouse1"
Driver "evdev"
Option "Device" "/dev/input/event0"
Option "Buttons" "10"
Option "ZAxisMapping" "9 10"
Option "Resolution" "800"
EndSection
...
InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Keyboard2"
InputDevice "Mouse1" "CorePointer"
...
|
Adding "SendCoreEvents" to Keyboard2 doesn`t help, too. (In this case Xorg, of course, reports that Keyboard2 always sends core events). |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sun Oct 01, 2006 11:41 am Post subject: |
|
|
| Quote: | | I didn`t change my udev rules |
why? just follow the howto..
_________________
The End of the Internet! |
|
| Back to top |
|
|
gudok
n00b
Joined: 30 Sep 2006
Posts: 5
|
| Posted: Sun Oct 01, 2006 3:22 pm Post subject: |
|
|
| truc wrote: | | Quote: | | I didn`t change my udev rules |
why? just follow the howto.. |
OK - I`ve done it. Now I have event7, event8 for two logical keyboards and event9 for usb mouse.
| Code: |
fors:~% cat /etc/udev/rules.d/010-udev-my.rules
KERNEL=="event*",ATTRS{modalias}=="usb:v045Ep00DBd0173dc00dsc00dp00ic03isc01ip01", MODE="0644", NAME="input/event7"
KERNEL=="event*",ATTRS{modalias}=="usb:v045Ep00DBd0173dc00dsc00dp00ic03isc00ip00", MODE="0644", NAME="input/event8"
KERNEL=="event*",ATTRS{modalias}=="usb:v046DpC01Dd2100dc00dsc00dp00ic03isc01ip02", MODE="0644", NAME="input/event9"
|
Here is my new xorg.conf:
| Code: | ...
Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event7"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp:shift_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
Identifier "Keyboard2"
Driver "evdev"
Option "Device" "/dev/input/event8"
Option "SendCoreEvents"
Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
Option "XkbLayout" "us,ru"
Option "XkbVariant" ",winkeys"
Option "XkbOptions" "grp:shift_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
# Logitech MX510 mouse
Identifier "Mouse1"
Driver "evdev"
Option "Device" "/dev/input/event9"
Option "Buttons" "10"
Option "ZAxisMapping" "9 10"
Option "Resolution" "800"
EndSection
...
InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Keyboard2"
InputDevice "Mouse1" "CorePointer"
...
|
Xorg message remains the same  |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sun Oct 01, 2006 4:12 pm Post subject: |
|
|
| Quote: | | Option "XkbVariant" ",winkeys" |
Is the coma normal?
Did you try without all your XKB options?
I mean something like this: | Code: | Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event7"
Option "XkbModel" "evdev"
EndSection |
and if it still doesn't work give us the result of and everything you can 
_________________
The End of the Internet! |
|
| Back to top |
|
|
gudok
n00b
Joined: 30 Sep 2006
Posts: 5
|
| Posted: Sun Oct 01, 2006 5:37 pm Post subject: |
|
|
| truc wrote: | | Quote: | | Option "XkbVariant" ",winkeys" |
Is the coma normal?
|
Yes, it`s the only way of enabling winkeys.
I`ve just tried Xorg without all those options and got the same result.
Now xorg.conf is as the same:
| Quote: | Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event7"
Option "Protocol" "evdev"
# Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
# Option "XkbLayout" "us,ru"
# Option "XkbVariant" ",winkeys"
# Option "XkbOptions" "grp:shift_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
Identifier "Keyboard2"
Driver "evdev"
Option "Device" "/dev/input/event8"
Option "Protocol" "evdev"
# Option "XkbRules" "xorg"
Option "XkbModel" "evdev"
# Option "XkbLayout" "us,ru"
# Option "XkbVariant" ",winkeys"
# Option "XkbOptions" "grp:shift_toggle,grp_led:scroll"
EndSection
Section "InputDevice"
# Logitech MX510 mouse
Identifier "Mouse1"
Driver "evdev"
Option "Device" "/dev/input/event9"
Option "Buttons" "10"
Option "ZAxisMapping" "9 10"
Option "Resolution" "800"
EndSection
...
InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Keyboard2" "SendCoreEvents"
InputDevice "Mouse1" "CorePointer"
|
And Xorg`s report:
| Code: | (II) evdev brain: Rescanning devices (1).
(**) Option "CoreKeyboard"
(**) Keyboard1-usb-0000:00:02.1-1/input0: Core Keyboard
(**) Option "XkbModel" "evdev"
(II) evdev brain: Rescanning devices (2).
(**) Option "SendCoreEvents"
(**) Keyboard2-usb-0000:00:02.1-1/input1: always reports core events
(II) Keyboard2-usb-0000:00:02.1-1/input1: Found 1 absolute axes.
(II) Keyboard2-usb-0000:00:02.1-1/input1: Configuring as pointer.
(**) Keyboard2-usb-0000:00:02.1-1/input1: Configuring in Absolute mode.
(**) Keyboard2-usb-0000:00:02.1-1/input1: AbsoluteScreen: -1.
Backtrace:
0: /usr/bin/X11/X(xf86SigHandler+0x84) [0x80c4344]
1: [0xffffe420]
2: /usr/lib/xorg/modules/input/evdev_drv.so [0xa7fa8638]
3: /usr/lib/xorg/modules/input/evdev_drv.so [0xa7fa96eb]
4: /usr/lib/xorg/modules/input/evdev_drv.so(evdevNewDriver+0x4c) [0xa7fa984c]
5: /usr/lib/xorg/modules/input/evdev_drv.so [0xa7fa83e8]
6: /usr/bin/X11/X(InitInput+0x176) [0x809f7e6]
7: /usr/bin/X11/X(main+0x35f) [0x806e56f]
8: /lib/tls/libc.so.6(__libc_start_main+0xc8) [0xa7db4ea8]
9: /usr/bin/X11/X(FontFileCompleteXLFD+0xa9) [0x806d9d1]
Fatal server error:
Caught signal 11. Server aborting
|
Xorg version:
| Code: | X Window System Version 7.1.1
Release Date: 12 May 2006
X Protocol Version 11, Revision 0, Release 7.1.1
Build Operating System: UNKNOWN
Current Operating System: Linux fors.fds 2.6.17 #1 SMP Sat Sep 16 16:35:21 MSD 2006 i686
Build Date: 07 July 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
|
Some more info:
| Code: | sh-3.1$ lsmod | grep evdev
evdev 9344 2
|
|
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Sun Oct 01, 2006 5:43 pm Post subject: |
|
|
just to be sure
| Code: | InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Keyboard2" "SendCoreEvents"
InputDevice "Mouse1" "CorePointer" |
is in the serverLayout section right?
did you run udevstart since you 've modified your udev rules? ls -l /dev/input
_________________
The End of the Internet! |
|
| Back to top |
|
|
gudok
n00b
Joined: 30 Sep 2006
Posts: 5
|
| Posted: Sun Oct 01, 2006 6:05 pm Post subject: |
|
|
| truc wrote: | just to be sure
| Code: | InputDevice "Keyboard1" "CoreKeyboard"
InputDevice "Keyboard2" "SendCoreEvents"
InputDevice "Mouse1" "CorePointer" |
is in the serverLayout section right?
did you run udevstart since you 've modified your udev rules? ls -l /dev/input |
1)
| Code: |
fors:~% ls -l /dev/input
ØâÞÓÞ 0
drwxr-xr-x 2 root root 100 2006-10-01 22:08 by-id
drwxr-xr-x 2 root root 140 2006-10-01 22:08 by-path
crw-rw---- 1 root root 13, 67 2006-10-01 22:08 event3
crw-r--r-- 1 root root 13, 65 2006-10-01 22:08 event7
crw-r--r-- 1 root root 13, 66 2006-10-01 22:08 event8
crw-r--r-- 1 root root 13, 64 2006-10-01 22:08 event9
crw-rw---- 1 root root 13, 63 2006-10-01 22:08 mice
crw-rw---- 1 root root 13, 32 2006-10-01 22:08 mouse0
crw-rw---- 1 root root 13, 128 2006-10-01 22:08 ts0
|
event3 is a "PC speaker"
2) I even rebooted PC - udev identifiers devices in a proper way |
|
| Back to top |
|
|
trantorvega
n00b
Joined: 19 Sep 2005
Posts: 13
|
| Posted: Sat Oct 07, 2006 8:00 am Post subject: |
|
|
Strangley enough the extended section reports to have two axes, one relative and one absolute, as well as a horizontal wheel. That might be adjusted with the bitmasks as reported in the evdev man page (If only they explained how to convert the bitmasks instead of just complaining about the annoying format they are avalaible in).
Nonetheless here is my Xorg log related output:
| Code: |
(II) evdev brain: Rescanning devices (2).
(**) Option "SendCoreEvents"
(**) Keyboard1-usb-0000:00:1d.7-3.2/input0: always reports core events
(**) Option "XkbRules" "xorg"
(**) Option "XkbModel" "microsoftnek4k"
(**) Option "XkbLayout" "it"
(II) evdev brain: Rescanning devices (3).
(**) Option "SendCoreEvents"
(**) Keyboard2-usb-0000:00:1d.7-3.2/input1: always reports core events
(II) Keyboard2-usb-0000:00:1d.7-3.2/input1: Found 1 absolute axes.
(II) Keyboard2-usb-0000:00:1d.7-3.2/input1: Configuring as pointer.
(**) Keyboard2-usb-0000:00:1d.7-3.2/input1: Configuring in Absolute mode.
(**) Keyboard2-usb-0000:00:1d.7-3.2/input1: AbsoluteScreen: -1 is not a valid screen.
(II) Keyboard2-usb-0000:00:1d.7-3.2/input1: Found 1 relative axes.
(II) Keyboard2-usb-0000:00:1d.7-3.2/input1: Configuring as pointer.
(**) Keyboard2-usb-0000:00:1d.7-3.2/input1: HWHEELRelativeAxisButtons: 6 7.
(II) Keyboard2-usb-0000:00:1d.7-3.2/input1: Found 17 mouse buttons
(II) Keyboard2-usb-0000:00:1d.7-3.2/input1: Configured 19 mouse buttons
(**) Option "XkbRules" "xorg"
(**) Option "XkbModel" "microsoftnek4k"
(**) Option "XkbLayout" "it"
|
I've the feeling your problem is unrelated to the details of your configuration. It might be a bug of X or the evdev driver. Question: did you compile X yourself or did you employ some kind of precompiled package? |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Mon Oct 09, 2006 9:18 am Post subject: |
|
|
I've just found that loading the module ehci-hcd, which is for usb2 support, prevents evdev devices from working properly. Actually the extra keys part of the keyboard is no longer working (and that's an other reason why I'm happy to use keyboard instead of evdev for the normal keys )
May be that's also your problem gudok try not loading this module (ehci-hcd) and startx, and see what happen
Does anybody has the same problem with evdev and ehci-hcd?
I've tried compiling ehci-hcd not as a module in the kernel, it looks like it's working for evdev, but I don't know if my usb external drive is usb1 or usb2 now, how can I know?
trantorvega, I recently understood that the print key you were talking about was the F12 key when function keys are disable. I though you were talking about the printkey ( one of the magic syskeys, just above insert).
That's not a problem for me since I don't plan using them at all (cause I already do an intensive use of the F1-F12 keys).
_________________
The End of the Internet! |
|
| Back to top |
|
|
wegrzyn
n00b
Joined: 27 Nov 2003
Posts: 22
Location: Boston, MA
|
| Posted: Thu Nov 09, 2006 8:07 pm Post subject: Don't get the same setxkbmap results |
|
|
I followed the instructions in the wiki regarding the 4000 keyboard and when I do setxkbmap -print I get totally different output. Here is what I get:
xkb_keymap {
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc(pc105)+latin+inet(microsoftpro)" };
xkb_geometry { include "microsoft(natural)" };
};
[I am using Xorg 1.1.1-r1]. I was wondering if anyone can point me in the right direction.
Thanks. |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Thu Nov 09, 2006 8:22 pm Post subject: |
|
|
I can't really help you on that, but, you can still try the other way I described above (there is also a note in the wiki about it), If you don't have that much time, it is really simpler
_________________
The End of the Internet! |
|
| Back to top |
|
|
wegrzyn
n00b
Joined: 27 Nov 2003
Posts: 22
Location: Boston, MA
|
| Posted: Tue Nov 14, 2006 1:45 pm Post subject: Wierdness in KDM login |
|
|
I did the mods as detailed by 'Truc' (see below) and proceeded to reboot my machine. When I tried to log back in I couldn't get the password to be accepted by the system! Has anyone seen this before?
Peace,
Chaz
What changes I made to xorg.conf per Truc...
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xorg"
Option "XkbModel" "pc105"
Option "XkbLayout" "fr"
EndSection
Section "InputDevice"
Identifier "Keyboard1"
Driver "evdev"
Option "Device" "/dev/input/event21"
Option "XkbModel" "evdev"
Option "XkbLayout" "fr"
EndSection |
|
| Back to top |
|
|
truc
Advocate
Joined: 25 Jul 2005
Posts: 3199
|
| Posted: Tue Nov 14, 2006 6:11 pm Post subject: |
|
|
you set my XKBLayout!
| Code: | | Option "XkbLayout" "fr" |
fr is for french:)
_________________
The End of the Internet! |
|
| Back to top |
|
|
ppurka
Advocate
Joined: 26 Dec 2004
Posts: 3256
|
| Posted: Sun Dec 31, 2006 10:13 pm Post subject: |
|
|
Hi,
Going by the feedback in this thread, I decided to purchase the MS Natural Ergonomic keyboard. I have almost everything working as I want now, after following the directions in the wiki. Thank you all for the nice instructions and tips.
However, I noticed that some of the settings in my case was not exactly what was present in the wiki. I just want to highlight those points.
1. First my | /etc/udev/rules.d/10-nek4k.rules wrote: | kernel=="event*",SYSFS{modalias}=="usb:v045Ep00DBd0173dc00dsc00dp00ic03isc00ip00", NAME="input/event20", MODE=0644
kernel=="event*",SYSFS{modalias}=="usb:v045Ep00DBd0173dc00dsc00dp00ic03isc01ip01", NAME="input/event21", MODE=0644 |
I am not quite conversant with the udev rules files. But, I noticed that udev would not create the input/event2* files unless I put the MODE part after the NAME part. Maybe this is a recent modification in udev (have udev-103 installed).
2. I had at first used the xorg config present in the wiki, and had associated the input/event20 device with the CoreKeyboard. I noticed that my NumLock/Capslock keys would work, but the corresponding leds would not turn on. After I switched the CoreKeyboard to input/event21, the leds started showing the correct status.
3. Later on, I used the "keyboard" driver as mentioned in this thread, and the evdev driver for input/event20 (as it was earlier). This got my keyboard working very nicely. As for the F-lock, I always have that turned on, so I guess duplicates between Fn-keys and Favourites is not something that bothers me. (As a bonus, my old PS/2 keyboard is also connected and it also works!)
Thank you again,
ppurka. |
|
| Back to top |
|
|
kos
n00b
Joined: 28 May 2003
Posts: 71
Location: Mountain View, CA
|
| Posted: Sat Jan 06, 2007 1:55 pm Post subject: |
|
|
bought ms4000 a couple of days ago and tried to configure it as written in the wiki, but using 0.4.1 patches. Everything works except a few items:
- F keys don't work in console. They seem to send correct codes, but F2 doesn't toggle splash verbose/silent mode.
- in X My Favorites and Down send the same keycode. Spent a day trying various solutions, nothing helps. As I see from usbnek4k.c, if ascii_keycode==1 it must send F16 instead of My Favorites, but it somehow doesn't work. I suspect that hid-input.c must also be hacked.
- F-keys always send F1-F12 codes, despite F-Lock state. Both in console and X.
I'm using a slightly different way to configure xkb, without changing any files in /usr/share/X11/xkb. I prefer to store my settings in ~/.xkb and load them from .xsession using
| Code: |
xkbcomp -R/home/kos/.xkb xkb :0 >/dev/null 2>&1
|
Here's what I have there:
| Code: |
-rw-r--r-- 1 kos users 9357 Jan 6 16:30 nek4k_geom
-rw-r--r-- 1 kos users 1007 Jan 6 16:30 nek4k_keycodes
-rw-r--r-- 1 kos users 1867 Jan 6 16:30 nek4k_sym
-rw-r--r-- 1 kos users 249 Jan 6 16:30 remap_menu_sym
-rw-r--r-- 1 kos users 344 Jan 6 16:32 xkb
|
xkb file:
| Code: |
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)+nek4k_keycodes(nek4k)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc105)+us+ru(winkeys):2+group(alt_shift_toggle)+nek4k_sym(microsoftnek4k)+remap_menu_sym(kos)" };
xkb_geometry { include "nek4k_geom(nek4k)" };
};
|
nek4k_geom is a snip directly from the wiki:
| Code: |
default xkb_geometry "nek4k" {
// Approximate layout for a Microsoft Natural Keyboard
description= "Microsoft Natural Ergonomic Keyboard 4000";
....
alias <AC00> = <CAPS>;
alias <AA00> = <LCTL>;
};
|
nek4k_keycodes is a slightly modified keycodes file from the wiki:
| Code: |
default xkb_keycodes "nek4k" {
<WEB> = 180;
<FIND> = 144;
<MAIL> = 163;
<ZMUP> = 168;
<ZMDN> = 169;
<PREV> = 166;
<SUCC> = 167;
<EQUL> = 125;
<PARO> = 187;
<PARC> = 188;
<MUTE> = 121;
<VOLD> = 122;
<VOLU> = 123;
<PLAY> = 172;
<CALC> = 148;
alias <BKMK> = <DOWN>;
<ONE> = 196;
<TWO> = 197;
<THRE> = 198;
<FOUR> = 199;
<FIVE> = 200;
<HELP> = 146;
<UNDO> = 139;
<REDO> = 190;
<NEW> = 189;
<OPEN> = 142;
<CLOS> = 214;
<REPL> = 240;
<FWD> = 241;
<SEND> = 239;
<SPLL> = 193;
<SAVE> = 242;
alias <PRNT> = <ONE>;
};
|
nek4k_sym:
| Code: |
// Microsoft Natural Ergonomic Keyboard 4000
partial alphanumeric_keys
xkb_symbols "microsoftnek4k" {
key <WEB> { [ XF86HomePage ] };
key <FIND> { [ XF86Search ] };
key <MAIL> { [ XF86Mail ] };
key <ZMUP> { [ XF86ScrollUp ] };
key <ZMDN> { [ XF86ScrollDown ] };
//back and forward buttons on the bottom. I want them be pgdown & pgup
// key <PREV> { [ XF86AudioPrev ] };
// key <SUCC> { [ XF86AudioNext ] };
key <PREV> { [ Prior ] };
key <SUCC> { [ Next ] };
// key <EQUL> { [ XF86Documents ] };
// key <PARO> { [ XF86Documents ] };
// key <PARC> { [ XF86Documents ] };
key <MUTE> { [ XF86AudioMute ] };
key <VOLU> { [ XF86AudioRaiseVolume ] };
key <VOLD> { [ XF86AudioLowerVolume ] };
key <PLAY> { [ XF86AudioPlay ] };
key <CALC> { [ XF86Calculator ] };
key <ONE> { [ XF86Documents ] };
key <TWO> { [ XF86AudioMedia ] };
key <THRE> { [ XF86AudioPrev ] };
key <FOUR> { [ XF86AudioNext ] };
key <FIVE> { [ XF86AudioStop ] };
key <HELP> { [ Help ] };
key <UNDO> { [ Undo ] };
key <REDO> { [ Redo ] };
key <NEW> { [ XF86New ] };
key <OPEN> { [ XF86Open ] };
key <CLOS> { [ XF86Close ] };
key <REPL> { [ XF86Reply ] };
key <FWD> { [ XF86MailForward ] };
key <SEND> { [ XF86Send ] };
key <SPLL> { [ XF86Spell ] };
key <SAVE> { [ XF86Save ] };
};
|
remap_menu_sym is my own addition which makes Menu key to be Esc, Esc to be Mod3 and Super_L to be Mod4. In case anyone is interested:
| Code: |
xkb_symbols "kos" {
//Make Menu to be Escape and
//Make Escape to be Mod3 :)
//Make left win key to be Mod4
key <MENU> { [ Escape ] };
key <ESC> { [ Hyper_L ] };
modifier_map Mod3 { Hyper_L };
modifier_map Mod4 { Super_L };
};
|
_________________
/KoS |
|
| Back to top |
|
|
ppurka
Advocate
Joined: 26 Dec 2004
Posts: 3256
|
| Posted: Sat Jan 06, 2007 5:24 pm Post subject: |
|
|
| kos wrote: | | F keys don't work in console. They seem to send correct codes, but F2 doesn't toggle splash verbose/silent mode. |
The keyboard does not work until the kernel loads the modules. So, you will not be able to even select a different kernel from grub too. | Quote: |
in X My Favorites and Down send the same keycode. Spent a day trying various solutions, nothing helps. As I see from usbnek4k.c, if ascii_keycode==1 it must send F16 instead of My Favorites, but it somehow doesn't work. I suspect that hid-input.c must also be hacked. |
As discussed in the wiki, and in this thread, you can set the CoreKeyboard to use keyboard instead of evdev. The other input device uses the evdev driver | Quote: |
F-keys always send F1-F12 codes, despite F-Lock state. Both in console and X.
I'm using a slightly different way to configure xkb, without changing any files in /usr/share/X11/xkb. I prefer to store my settings in ~/.xkb and load them from .xsession using
|
I don't know much about these configurations, but I followed the wiki exactly as written and used keyboard and evdev as driver and I do get different keycodes for different states of F-lock. |
|
| Back to top |
|
|
kos
n00b
Joined: 28 May 2003
Posts: 71
Location: Mountain View, CA
|
| Posted: Sat Jan 06, 2007 11:25 pm Post subject: |
|
|
| ppurka wrote: |
The keyboard does not work until the kernel loads the modules. So, you will not be able to even select a different kernel from grub too. |
I believe I have some different problem. Keyboard works in grub, and F2 doesn't work during shutdown as well, when the module is loaded.
Thanks.
update
I've tried to use "keyboard" driver for the core keyboard. "Protocol" option was commented out, XkbModel set to "pc105". As a result my keyboard went mad generating lots of garbage and eventually killed X after a few keystrokes.
_________________
/KoS |
|
| Back to top |
|
|
ppurka
Advocate
Joined: 26 Dec 2004
Posts: 3256
|
| Posted: Sun Jan 07, 2007 2:28 am Post subject: |
|
|
| kos wrote: | | I believe I have some different problem. Keyboard works in grub, and F2 doesn't work during shutdown as well, when the module is loaded. |
Very surprising. Exactly the opposite happens with me. Maybe it is because I still have my ps/2 keyboard connected  | Quote: | update
I've tried to use "keyboard" driver for the core keyboard. "Protocol" option was commented out, XkbModel set to "pc105". As a result my keyboard went mad generating lots of garbage and eventually killed X after a few keystrokes. |
Yes, maybe I should have mentioned this in my earlier post. Just comment out the line | Code: | | Option "Device" "/dev/input/event<num>" |
from your /etc/X11/xorg.conf, where this line corresponds to the driver keyboard. I faced this problem too. In particular, my keyboard driver portion is like this: | Code: | Section "InputDevice"
Identifier "Keyboard2"
Driver "keyboard"
Option "CoreKeyboard"
# Commenting out evdev, since we will use keyboard as driver, which will get rid of dupes {{{
# Option "Device" "/dev/input/event21"
# Option "Protocol" "evdev"
# Option "XkbModel" "evdev"
# Option "XkbModel" "microsoftnek4k"
# }}}
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Option "XkbRules" "xorg"
EndSection |
|
|
| Back to top |
|
|
kos
n00b
Joined: 28 May 2003
Posts: 71
Location: Mountain View, CA
|
| Posted: Tue Jan 09, 2007 4:22 pm Post subject: |
|
|
| ppurka wrote: | Yes, maybe I should have mentioned this in my earlier post. Just comment out the line | Code: | | Option "Device" "/dev/input/event<num>" |
from your /etc/X11/xorg.conf |
Thanks a lot, now "My Favorites" sends distinct keycode. Although I had to remap a couple dozens of buttons again, I was rewarded: now cursor keys work in vmware properly. With evdev they used to generate some weird scancodes there.
_________________
/KoS |
|
| Back to top |
|
|
jasn
Guru
Joined: 05 May 2005
Posts: 439
Location: Maryland, US
|
| Posted: Tue Jan 09, 2007 11:29 pm Post subject: |
|
|
| Sedrik wrote: | | masseya wrote: | | I know most of this thread has focused on larger keyboards, but if you're looking for a smaller ergonomic keyboard or interested in just trying out something new you might consider TypeMatrix. (http://www.typematrix.com/)[snip] |
But then again that is not an ergonomic keyboard, simply an ordinary keyboard with the keys moved around |
Actually it is an ergonomic keyboard. The faq on their website goes into their methodology around ergonomic keyboards at this URL. Linking to the press/reviews section of their website they have a review written by someone who regularly uses the Kinesis keyboard, and what they thought of the Typematrix. The review is here. |
|
| Back to top |
|
|
jasn
Guru
Joined: 05 May 2005
Posts: 439
Location: Maryland, US
|
| Posted: Tue Jan 09, 2007 11:32 pm Post subject: |
|
|
| masseya wrote: | | I know most of this thread has focused on larger keyboards, but if you're looking for a smaller ergonomic keyboard or interested in just trying out something new you might consider TypeMatrix. (http://www.typematrix.com/) |
I'm a longtime Microsoft ergonomic keyboard user, but always on the lookout for something else. These keyboards look pretty cool. Their website offers some interesting information on their take on ergonomic keyboards. I'd get one just to try, except it's a little frustrating that they don't have a USB version already.. If you have any other information you'd like to pass on about your experience using these keyboards, (like a mini-review), I'm all ears.. Thanks.. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
