your mail

Peter Hutterer peter.hutterer at who-t.net
Mon Jan 5 17:42:10 PST 2009


On Mon, Jan 05, 2009 at 07:44:36PM -0500, - gw1500se wrote:
> Peter Hutterer wrote:
> 
>   On Thu, Jan 01, 2009 at 12:34:50PM -0500, - gw1500se wrote:
> 
>   I am having a problem with my Microsoft PS/2 optical wheel mouse when I
> switch between machines with a KVM switch. Specifically, my Mandriva machine
> no longer recognizes a mouse is attached (Windows does not have a problem
> with switching). Some research has come up with a suggestion that the mouse
> protocol be changed in xorg.conf to PS/2. However, it is currently
> ExplorerPS/2 and when I try to change it, it magically reverts so I don't
> know if that change will fix my problem or not.
> 
>   
>   watch the xorg.log when you switch to and fro the machine, it'll probably
> notice the mouse going away, but not coming back. In this case it could be
> either a problem with the kernel or with HAL.
> 
> 
> I think you are correct. Here is the log info switching away:
> 
> 
> 
> (II) evaluating device (Mouse1)
> (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
> (II) evaluating device (Keyboard1)
> (II) XINPUT: Adding extended input device "Keyboard1" (type: KEYBOARD)
> (II) Mouse1: ps2EnableDataReporting: succeeded
> (II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" removed.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" registered at address 0xA0.
> (II) intel(0): I2C device "CRTDDC_A:ddc2" removed.

all this is logs from the graphics card. is there anything related to input
devices?

>   
> try adding "AutoAddDevices" "false" to you ServerLayout section and restart
> the server. This forces the server to use the mouse driver (by default on
> /dev/input/mice) and leave all the hotplugging to the kernel.
> Does the mouse work then? If not - definitely a kernel problem.
> 
> 
> Is that the correct key word for my version? It doesn't like it. Here is that section:
> 
> Section "ServerLayout"
> 
>     Identifier "layout1"
> 
>     InputDevice "Keyboard1" "CoreKeyboard"
> 
>     InputDevice "Mouse1" "CorePointer"
> 
>     Screen "screen1"
> 
>     AutoAddDevices "false"

Option "AutoAddDevices" "false"
 
> EndSection
> 
> 
> 
> It told me AutoAddDevices was an invalid key word for that section.
>   
> 
>   Perhaps someone can tell me either why the mouse protocol will not stay the
> way I set it or, better yet, why the mouse goes away after using the KVM
> switch.
> 
>   
> most likely because your xorg.conf settings are ignored, as they usually are
> with servers 1.5 and above.
> http://who-t.blogspot.com/2008/12/evdev-xorgconf-hal-and-other-fud.html
> 
> 
> Since I am below 1.5, hopefully this doesn't apply. I don't know anything
> about HAL. I'm pretty sure my xorg.conf parameters are not being ignored as
> I have made changes that effect X. But then maybe it is ignoring some and
> not all.

1.4 uses hal already, so it applies to some extent.
 
Cheers,
  Peter



More information about the xorg mailing list