Re: X starts when mouse is not connected (AllowMouseOpenFail = false)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 24 Nov 2005, Lance Duivenbode wrote:
Lance Duivenbode wrote:
Marc Aurele La France wrote:
On Fri, 23 Sep 2005, Marc Aurele La France wrote:
On Fri, 23 Sep 2005, Lance Duivenbode wrote:
Marc Aurele La France wrote:
On Tue, 13 Sep 2005, Lance Duivenbode wrote:
Marc Aurele La France wrote:
On Thu, 8 Sep 2005, Lance Duivenbode wrote:
I work for uses Linux (a custom version) running the 2.4.24 kernel and we've just upgraded to XFree86 4.5.0. Previously, when X was started without a mouse it would exit back to the shell complaining that it couldn't find the core pointer. However, since we've upgraded to 4.5.0 this behaviour no longer occurs - even with the "AllowMouseOpenFail" server flag explicitly set to "false".

Given the fact that my company remotely manages internet kiosks, we want to be able to detect if a mouse is not connected since this usually indicates faulty hardware. Is it still possible to prevent X from starting if there is no mouse attached or has this option been removed? I would appreciate any help since I've not been able to find anything in the docs or via searching the internet.

This is likely a consequence of auto-configuration. I'll have a look. You wouldn't happen to have a mouse-less log, would you?

Thanks for you reply. I've included a mouse-less log as requested as well as the configuration file.

You say you upgraded to 4.5.0.  From what version?

Sorry about the delay but it took some time to find out (I'm pretty new to the company). It appears we were running version 4.2 before.

OK.  Does it make any difference to add O_EXCL back into
xf86OpenSerial()'s open(2) call on line 143 of xc/programs/Xserver/hw/xfree86/os-support/shared/posix_tty.c?

Anything more on this?

Sorry Marc, I've been a little bit busy with other things lately.

In regards to the change, I could only find it on line 150 of posix_tty.c where the code is:

   SYSCALL (fd = open (dev, O_RDWR | O_NONBLOCK));
   if (fd == -1)
   {
       xf86Msg (X_ERROR,
            "xf86OpenSerial: Cannot open device %s\n\t%s.\n",
            dev, strerror (errno));
       xfree(dev);
       return (-1);
   }

I've made the change and as I write this it's building. I'll let you know what happens when I've tested it (hopefully today or tomorrow),

I finally managed to get around to testing the change you suggested (I replaced the XFree86 binary with the new one - hope that's the right thing to do!). Unfortunately it made no difference. Even if 'AllowMouseOpenFail' is explicitly set to 'false' it still fails. Any other ideas?

The only thing I can think of is that the kernel now thinks there is a mouse regardless.

Marc.

+----------------------------------+-----------------------------------+
|  Marc Aurele La France           |  work:   1-780-492-9310           |
|  Academic Information and        |  fax:    1-780-492-1729           |
|    Communications Technologies   |  email:  tsi@xxxxxxxxxxx          |
|  352 General Services Building   +-----------------------------------+
|  University of Alberta           |                                   |
|  Edmonton, Alberta               |     Standard disclaimers apply    |
|  T6G 2H1                         |                                   |
|  CANADA                          |                                   |
+----------------------------------+-----------------------------------+
XFree86 developer and VP.  ATI driver and X server internals.
_______________________________________________
XFree86 mailing list
XFree86@xxxxxxxxxxx
http://XFree86.Org/mailman/listinfo/xfree86

[Index of Archives]     [X Forum]     [Xorg]     [XFree86 Newbie]     [IETF Announce]     [Security]     [Font Config]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux Kernel]

  Powered by Linux