-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El 2005-10-24 a las 08:26 +0200, Pedro b escribió:
hola, aqui está el XF86Config
Te lo corto y dejo sólo lo que interesa:
Section "ServerFlags" Option "AllowMouseOpenFail" EndSection ...
Section "InputDevice" Driver "keyboard" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "es" Option "XkbModel" "pc102" Option "XkbRules" "xfree86" EndSection
Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "ButtonNumber" "2" Option "Device" "/dev/mouse" Option "Name" "Autodetection" Option "Protocol" "imps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection
Section "InputDevice" Driver "mouse" Identifier "Mouse[3]" Option "Device" "/dev/pointer1" Option "Name" "Autodetection" Option "Protocol" "imps/2" Option "Vendor" "Sysp" EndSection
...
Section "ServerLayout" Identifier "Layout[all]" InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" InputDevice "Mouse[3]" "SendCoreEvents" Option "Clone" "off" Option "Xinerama" "off" Screen "Screen[0]" EndSection
Tienes definidos dos ratones, uno en /dev/mouse (CorePointer, el primario), y otro en /dev/pointer1 (SendCoreEvents). Del manual: InputDevice "idev-id" "option" ... One of these entries should be given for each input device being used in a session. Normally at least two are required, one each for the core pointer and keyboard devices. If either of those is missing, suitable InputDevice entries are searched for using the method described above in the INPUTDEVICE sec- tion. The idev-id field is mandatory, and specifies the name of the InputDevice section being refer- enced. Multiple option fields may be specified, each in double quotes. The options permitted here are any that may also be given in the InputDevice sections. Normally only session-specific input device options would be used here. The most com- monly used options are: "CorePointer" "CoreKeyboard" "SendCoreEvents" and the first two should normally be used to indi- cate the core pointer and core keyboard devices respectively. ... Here is an example of a ServerLayout section for a dual headed configuration with two mice: Section "ServerLayout" Identifier "Layout 1" Screen "MGA 1" Screen "MGA 2" RightOf "MGA 1" InputDevice "Keyboard 1" "CoreKeyboard" InputDevice "Mouse 1" "CorePointer" InputDevice "Mouse 2" "SendCoreEvents" Option "BlankTime" "5" EndSection ...xx Option "CorePointer" When this is set, the input device is installed as the core (primary) pointer device. There must be exactly one core pointer. If this option is not set here, or in the ServerLayout section, or from the -pointer command line option, then the first input device that is capable of being used as a core pointer will be selected as the core pointer. This option is implicitly set when the obsolete Pointer section is used. ...xx Option "AlwaysCore" "boolean" Option "SendCoreEvents" "boolean" Both of these options are equivalent, and when enabled cause the input device to always report core events. This can be used, for example, to allow an additional pointer device to generate core pointer events (like moving the cursor, etc). Pero no puedo decirte porqué no va. Mira a ver si los dispositivos son correctos. - -- Saludos Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDXpFHtTMYHG2NR9URAi5EAJ94lTYEUqVnGe0fUz8Wcj7imqEPvQCeOXWp ceatxXzLyeR2UKuQrI143iE= =Adwc -----END PGP SIGNATURE-----