From: Zoltan B. <zb...@fr...> - 2006-07-07 18:33:10
|
Hugo Vanwoerkom =EDrta: > --- Zoltan Boszormenyi <zb...@fr...> wrote: > > =20 >> Hugo Vanwoerkom =EF=BF=BDrta: >> =20 >>> */Zoltan Boszormenyi <zb...@fr...>/* >>> =20 >> wrote: >> =20 >>> Hi, >>> >>> I just noticed that faketty isn't needed with >>> =20 >> Xorg 7.x. >> =20 >>> The following section works like a charm for a >>> =20 >> keyboard, >> =20 >>> nothing else is needed. >>> >>> Section "InputDevice" >>> Identifier "Keyboard0" >>> Driver "evdev" >>> Option "Device" "/dev/input/eventX" >>> Option "XkbLayout" "hu" >>> EndSection >>> >>> The proper eventX device is registered in >>> =20 >> /proc/bus/input/devices >> =20 >>> and as with the kbd driver, multiple sections >>> =20 >> can be listed >> =20 >>> and assigned to the same server, e.g. the PS/2 >>> =20 >> keyboard >> =20 >>> and the BTTV remote is assigned to one X >>> =20 >> server, >> =20 >>> the USB keyboard's two devices (normal >>> =20 >> keyboard and >> =20 >>> the multimedia keys are separated) are >>> =20 >> assigned to the >> =20 >>> other server. >>> >>> And what is the vt set at then in gdm.conf for the >>> =20 >> other keyboards? >> =20 >>> Hugo >>> =20 >> Nothing, but "-sharevts" is needed. Same for faketty >> if I don't specify "vtX" on the parameter line and >> use >> Option "Device" "/dev/fttyN" instead. >> >> But some bug may still exist in the X evdev driver >> as hungarian layout doesn't work correctly. >> E.g. Option "XkbModel" "pc105" makes RightAlt >> behave as Enter and without it (e.g. working as >> pc104), >> my i-acute button doesn't work. >> >> So, XOrg is only starting to get there, I switched >> back to faketty for now. >> >> >> =20 > > I just tried this with good success. But I only have 2 > monitors/keybds/mice. > The keyboards are both IBM Model M's. Mine is now 13 > years old and the other I bought for $57 new. > Also I only need dead keys for us-intl config. > > So Faketty is gone and xorg.conf relevant parts > becomes: > > ... > Section "InputDevice" > Identifier "Keyboard0" > Driver "evdev" > Option "Device" =20 > "/dev/input/event0" > Option "XkbLayout" "us_intl" > EndSection > ... > Section "InputDevice" > Identifier "Keyboard1" > Driver "evdev" > Option "Device" =20 > "/dev/input/event1" > Option "XkbLayout" "us_intl" > EndSection > ... > =20 I replaced the 'Option "Device" ... ' lines with 'Option "Phys" "..."', it gives the same effect but with higher persistency. It turned out that modprobe processes race with each other and bttv and USB HID devices change their places (both /dev/fttyN and /dev/input/eventN) depending on the load order. Best regards, Zolt=E1n B=F6sz=F6rm=E9nyi |