LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 02-20-2012, 02:14 PM   #1
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Rep: Reputation: 152Reputation: 152
Angry serial mouse "Device" ignored by xorg


I have this serial mouse that I have been using everyday on Linux 2.4. In a separate partition I am installing Linux 2.6. I first installed Slackware 13.1 with Linux 2.6.33 and after a long fight with HAL, managed to get my mouse and keyboard to work. I upgraded using Slackware 13.37 with Linux 2.6.37, and the new xorg, KDE 4.5.5 and Xfce4.6.2.

Linux 2.4 works with this same mouse using /dev/ttyS0.

I have changed back to nv video driver to simplify things (having problems with nVidia binary install too
(glex module wont load and nouveau driver detected)).

In the new system, the new Xorg will not recognize my mouse device. It blatantly ignores my "Device" line and switches to /dev/input/mice which connects to nothing.
GPM works with this mouse using /dev/ttyS0.

I have tried:
> ln -s /dev/ttyS0 /dev/mouse
> ln -s /dev/ttyS0 /dev/input/mouse_ser

I have tried mousedrv and evdev.
I have tried setting the device to /dev/ttyS0, /dev/mouse, and the /dev/input/mouse_ser soft link.

My xorg.conf contains

Section "InputDevice"
Identifier "Mouse1"
Driver "mouse"
# Driver "evdev"
Option "Protocol" "MouseSystems"
# Option "Device" "/dev/input/mouse_ser"
Option "Device" "/dev/ttyS0"
# Option "Device" "/dev/mouse"
# Option "CorePointer" changed to "SendCoreEvents"
Option "SendCoreEvents" "1"
Option "AccelerationProfile" "0"
# 0=classic, -1=none, 1=device-dependent 2=poly, 3=knee-linear, 4=simple, 5=power-func, 6=linear
Option "Buttons" "3"
EndSection


The response is consistent:
Xorg ignores the device line, tries to use /dev/input/mice
and uses the other settings.

[ 40945.719] (WW) Mouse1: No Device specified, looking for one...
[ 40945.719] (II) Mouse1: Setting Device option to "/dev/input/mice"
[ 40945.719] (--) Mouse1: Device: "/dev/input/mice"
[ 40945.719] (==) Mouse1: Protocol: "Auto"
[ 40945.719] (**) Option "SendCoreEvents" "1"
[ 40945.719] (**) Option "CorePointer"
[ 40945.719] (**) Mouse1: always reports core events
[ 40945.719] (**) Option "Device" "/dev/input/mice"
[ 40945.719] (**) Option "Buttons" "3"
[ 40945.719] (==) Mouse1: Emulate3Buttons, Emulate3Timeout: 50
[ 40945.719] (**) Mouse1: ZAxisMapping: buttons 4 and 5
[ 40945.719] (**) Mouse1: Buttons: 9
[ 40945.719] (II) XINPUT: Adding extended input device "Mouse1" (type: MOUSE)
[ 40945.719] (**) Mouse1: (accel) keeping acceleration scheme 1
[ 40945.720] (**) Option "AccelerationProfile" "0"
[ 40945.720] (**) Mouse1: (accel) acceleration profile 0
[ 40945.720] (**) Mouse1: (accel) acceleration factor: 2.000
[ 40945.720] (**) Mouse1: (accel) acceleration threshold: 4
[ 40945.720] (II) Mouse1: Setting mouse protocol to "ExplorerPS/2"
[ 40946.058] (II) Mouse1: ps2EnableDataReporting: succeeded
[ 40946.058] (**) Option "CoreKeyboard"


The one time I changed /dev/input/mice to a soft link to /dev/ttyS0,
the mouse worked somewhat, then xorg hung hard and inoperative such that console changes and ctrl-alt-del would not work (had to use reset button).

What is up with xorg that it cannot recognize any "Device" line for the mouse ???
The xorg with Slackware 13.1 and Linux 2.6.33 did not exhibit this behavior.

Has anyone else got a serial mouse working on a newer xorg ??
Can anyone report have the mouse "Device" line actually recognized (and testable) ??
 
Old 02-20-2012, 02:25 PM   #2
uhelp
Member
 
Registered: Nov 2011
Location: Germany, Bavaria, Nueremberg area
Distribution: openSUSE, Debian, LFS
Posts: 205

Rep: Reputation: 43
Most serial mice adhere to the microsoft protocol.
Try something like this:
Code:
"Device" "/dev/ttyS0"
"Protocol" "Microsoft"
I'm not sure whether a softlink would work...
Stay with /dev/ttyS0 or whatever the serial port might be.

There are some more serial protocols for mice.
If it doesn't work try googling "linux serial mouse protocol"

Last edited by uhelp; 02-20-2012 at 02:27 PM. Reason: typos corrected; Google search added
 
Old 02-20-2012, 02:46 PM   #3
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Original Poster
Rep: Reputation: 152Reputation: 152
Unhappy

Been using it for years on Linux 2.4 as Protocol "MouseSystems", and "MouseSystems" is recognized by GPM on Linux 2.6 too.
Being that the "MouseSystems" line is also ignored by Xorg, I do not know what it may be contributing to the problem.

There are a indefinite combination of things I could try.
I know someone will suggest a different mouse, and will suggest using a PS/2 mouse (abandoning any idea of getting serial mice to work).
This is a 3 button mouse, and I have not found a suitable replacement.
My trackball is a serial mouse too.

I have also searched the web for serial mouse problems with xorg.
The best I have found is a LinuxQuestions thread by GrapefruiTgirl.

It looks to me like the driver is so hung up on automatically detecting the mouse that it is ignoring the direct specification of "Device" and "Protocol".
They have had years to fix mouse and kbd recognition problems and seem to keep making it worse by trying to force autodetection.
From what I have read, serial mice cannot be autodetected, and probably when the driver fails to detect it, it then wanders off on some autodetection fantasy.

Tried the microsoft protocol, just to see what would happen.
Option "Protocol" "Microsoft"
It had no different effect, still the same log messages.

Last edited by selfprogrammed; 02-21-2012 at 06:30 PM.
 
Old 02-22-2012, 12:32 PM   #4
uhelp
Member
 
Registered: Nov 2011
Location: Germany, Bavaria, Nueremberg area
Distribution: openSUSE, Debian, LFS
Posts: 205

Rep: Reputation: 43
then have a look at /etc/X11/xorg.conf.d

New X-server does not use anymore xorg.conf.
Could be something like DD-mouse.conf (D=digit)
 
Old 02-22-2012, 04:22 PM   #5
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Original Poster
Rep: Reputation: 152Reputation: 152
I certainly does see my /etc/X11/xorg.conf.
From looking at the log, it is seeing all the other configure lines.
From the log in my first post it is seeing the line
Option "Buttons" "3"

It just ignores the lines
Option "Device" "/dev/ttyS0"
And I assume it is ignoring
Option "Protocol" "MouseSystems"

I have looked at /etc/X11/xorg.conf.d
I have looked at /usr/share/X11/xorg.conf.d
Did not see anything useful. They seem to be generic defaults to use when there is no /etc/X11/xorg.conf.
Certainly nothing that says "serial mouse".
There is nothing to say there that could not be put into /etc/X11/xorg.conf.
It all should be overridden if there is an explicit line in the xorg.conf.

The real problem is that X11 on my Linux 2.6 is completely unusable without a mouse. I won't be switching from Linux 2.4 anytime soon. My every experience with Linux 2.6 Xorg code is that it is broken goods. Over 18 months and 2 distributions, I have not managed to make it usable, and I have been using Linux for 10 years.

What are the chances of anyone using a serial mouse or trackball responding.
Where are the xorg developers on LQ when you need someone to yell at. Probably off deciding that no one uses Matrox anymore, lets bork the support for that (I have a Matrox card on another machine, that I cannot put into service because the email cannot handle attachments properly and the users prefer the old Win98 Outlook).
 
Old 02-22-2012, 05:29 PM   #6
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
This can be a little tricky to get working. It has been a while since I set this up on an old box running Slackware (last upgraded to 13.1) and I am writing this from memory.
1. Check /etc/rc.d/rc.modules-$(uname -r) and uncomment the line that enables serial mouse support.
Code:
# Serial (RS-232, COM port) mouse support:
#/sbin/modprobe sermouse
2. Add the code to create the symlink in /etc/rc.d/rc.local.
Your line 'ln -s /dev/ttyS0 /dev/mouse' seems familiar.
3. You may also have to uncomment the line in /etc/modprobe.d/psmouse.conf to set a more basic mouse protocol.
Code:
#options psmouse proto=imps
Alternatively, invest in a USB optical mouse. Cleaning mouse balls and rollers is a pain.
 
Old 02-23-2012, 12:02 AM   #7
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
An update after checking an old backup from the Slackware box with a serial mouse running Slackware 13.37 with generic 2.6.37.6 single processor kernel.

From /etc/rc.d/rc.local
Code:
# Hack to get mouse to work
if [ -x /etc/rc.d/rc.serialmouse ]; then
  echo "Executing hack for serial mouse:  /etc/rc.d/rc.serialmouse"
  sh /etc/rc.d/rc.serialmouse
fi
From a custom file /etc/rc.d/rc.serialmouse
Code:
#!/bin/sh

# Hack to get serial mouse to work
 gpm -k # Could also use '/etc/rc.d/rc.gpm stop'
 rm /dev/mouse
 ln -s /dev/ttyS0 /dev/mouse
 gpm -m /dev/mouse -t bare # Could also use '/etc/rc.d/rc.gpm start'
From /etc/X11/xorg.conf
Code:
Section "InputDevice"
    Identifier  "Mouse0"
    Driver      "mouse"
#	Option	    "Protocol" "auto"
#	Option	    "Device" "/dev/mouse"
#	Option	    "ZAxisMapping" "4 5 6 7"
    Option "Protocol"    "Microsoft"
    Option "Device"      "/dev/ttyS0"
    Option "Emulate3Buttons"
EndSection
Ignore my previous post concerning /etc/modprobe.d/psmouse.conf as there were no changes from the defaults
Code:
# PS/2 mouse support:
# The default options when the psmouse module can cause problems with KVM
# switches.  If you experience this, you may want to uncomment the line
# below to use a more basic mouse protocol with the psmouse module:
#options psmouse proto=imps
Same for /etc/rc.d/rc.modules-2.6.37.6 as there were no changes from the defaults concerning the serial mouse.
Code:
# Serial (RS-232, COM port) mouse support:
#/sbin/modprobe sermouse

Last edited by allend; 02-23-2012 at 12:16 AM.
 
1 members found this post helpful.
Old 02-23-2012, 02:56 PM   #8
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Original Poster
Rep: Reputation: 152Reputation: 152
The mousedrv is at fault, it checks for "Device" and "Protocol" before it actually gets the options list from the xorg.conf. I put debug printf in the mouse driver, compiled, installed it in place of the Slackware binary. The call to get "Device" is returning NULL because it is placed 10 lines before the call to get the "Options" from the xorg.conf. The call to get the "Protocol" is right before it. This works if you want to ignore the xorg.conf and use HAL to get devices (but HAL and UDEV cannot find a serial mouse).
When I put another test for "Device" after the CollectOptions call, then it finds my "Device" line and a print stmt confirms that.

By reordering the calls in the mousedrv xorg module, I have got the serial mouse to work.
I have to use "Auto" for now because the "Protocol" is still not working, but that is another nights debugging to figure that out.

I got the source packages for the xorg from Slackware 13.37 and Slackware 13.1.
This occurs in both of them, and has been there since they got the idea to use HAL to find mouse devices (which is why I had so much trouble getting the mouse to work on Slackware 13.1). In the later mousedrv there have been code changes around that area, and another options test got moved from before the CollectOptions call to after it (to make that one work, probably).

The problem has been "Determined" but not quite "Solved".
Other serial mouse users have no chance of getting xorg mousedrv to work.
I will have to work up a patch. It will take a while to put together one that I can trust
to be released.

Thanks Allend:
That looks much like the config I have been messing with for 18 months now. I seriously doubt that worked for Slack 13.37 as that "Device" "/dev/ttyS0" is identical to the one that I use, and I just proved that the mousedrv does not see it. There has to be something else to get around that mousedrv problem, such as changing the defaults too, or using a mouse that happens to have the same protocol as the defaults, or linking /dev/input/mice to /dev/ttyS0 (which hung my system).

Last edited by selfprogrammed; 02-23-2012 at 03:07 PM.
 
Old 02-24-2012, 12:53 AM   #9
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
I am sure that I had the mouse working. This was an old print and file server box that has now been decommissioned, so the mouse in X was very rarely used.
Your mention of HAL reminded me.
From /etc/X11/xorg.conf
Code:
Section "ServerLayout"
	Identifier     "X.org Configured"
	Screen      0  "Screen0" 0 0
	InputDevice    "Mouse0" "CorePointer"
	InputDevice    "Keyboard0" "CoreKeyboard"
	Option         "AutoAddDevices" "off"
	Option         "AutoEnableDevices" "off"
	Option         "AllowEmptyInput" "off"
EndSection
Note the last three options.
 
Old 02-24-2012, 03:28 PM   #10
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Original Poster
Rep: Reputation: 152Reputation: 152
Got those too. Had to put them in Slack 13.1 because otherwise HAL would auto-load a second driver for the keyboard using evdev, while I was specifying the keyboard driver.
I ended up with two drivers on the keyboard, and that took a long time to figure out too.
I got the mouse working on that xorg too, in spite of the mousedrv being as bunged up like this one, ("Device" and "Protocol"). Don't know what I did that worked, but it must have been very sneaky, and it does not work on this xorg mousedrv (I upgraded in place so it should still be there, mostly). I can't remember what I did that time either, I was fighting with it for months trying everything imaginable.
If your "Device" line is ignored, then you must have did something in the /dev, or in HAL too,
or /etc/X11/xorg.conf.d or /usr/share/xorg/xorg.conf.d.
It is possible that you used a mousedrv patched by some distributor.
Too bad you do not have the last /var/log/Xorg.conf.log as the absence of the "Device" line during mouse config would confirm that you had the mousedrv bug too.

We really need to get xorg to fix the driver so that "Device" specs work.
I have submitted a bug report, but do not expect action.
I think that some additional voices supporting this fix would help, as I suspect some reluctance due to ideology (use HAL and evdev for everything). (No, evdev does not sense serial mouse either)
https://bugs.freedesktop.org/show_bug.cgi?id=46540

Last edited by selfprogrammed; 02-24-2012 at 03:52 PM.
 
Old 02-25-2012, 12:56 AM   #11
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware64-15.0
Posts: 6,357

Rep: Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739Reputation: 2739
Quote:
Too bad you do not have the last /var/log/Xorg.conf.log as the absence of the "Device" line during mouse config would confirm that you had the mousedrv bug too.
Actually I do have the last log. Taken from the image I took when decommissioning in case I wanted to look back at old settings :-)
Code:
[  6962.723] (WW) Mouse0: No Device specified, looking for one...
[  6962.724] (II) Mouse0: Setting Device option to "/dev/input/mice"
[  6962.724] (--) Mouse0: Device: "/dev/input/mice"
[  6962.725] (==) Mouse0: Protocol: "Auto"
[  6962.725] (**) Option "CorePointer"
[  6962.726] (**) Mouse0: always reports core events
[  6962.726] (**) Option "Device" "/dev/input/mice"
[  6962.727] (**) Option "Emulate3Buttons"
[  6962.728] (**) Mouse0: Emulate3Buttons, Emulate3Timeout: 50
[  6962.729] (**) Mouse0: ZAxisMapping: buttons 4 and 5
[  6962.730] (**) Mouse0: Buttons: 9
[  6962.730] (II) XINPUT: Adding extended input device "Mouse0" (type: 
MOUSE)
[  6962.731] (**) Mouse0: (accel) keeping acceleration scheme 1
[  6962.732] (**) Mouse0: (accel) acceleration profile 0
[  6962.733] (**) Mouse0: (accel) acceleration factor: 2.000
[  6962.733] (**) Mouse0: (accel) acceleration threshold: 4
[  6962.734] (II) Mouse0: Setting mouse protocol to "ExplorerPS/2"
[  6963.071] (II) Mouse0: ps2EnableDataReporting: succeeded
[  6963.072] (**) Option "CoreKeyboard"
[  6963.072] (**) Keyboard0: always reports core events
[  6963.073] (**) Option "Protocol" "standard"
[  6963.074] (**) Option "XkbRules" "base"
[  6963.075] (**) Option "XkbModel" "pc105"
[  6963.076] (**) Option "XkbLayout" "us"
[  6963.077] (II) XINPUT: Adding extended input device "Keyboard0" 
(type: KEYBOARD)
[  6963.349] (II) config/udev: Adding input device AT Translated Set 2 
keyboard (/dev/input/event0)
[  6963.350] (II) AutoAddDevices is off - not adding device.
[  7053.117] (II) Mouse0: ps2EnableDataReporting: succeeded
[1360033.471] (II) UnloadModule: "kbd"
[1360033.607] (II) UnloadModule: "mouse"
Your log excerpt does not extend to the section highlighted in blue

Last edited by allend; 02-25-2012 at 01:00 AM.
 
Old 02-26-2012, 09:21 PM   #12
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Original Poster
Rep: Reputation: 152Reputation: 152
First two lines of that log show the same problem, your xorg.conf "Device" line was not found, and it defaulted to "/dev/input/mice" instead. It did not see your "Protocol" "Microsoft" line either, and went to "Auto".
In your setup, somehow it was finding the mouse.
You have the advantage that your mouse is "Microsoft" which will match the defaults.
Somehow I got around it too in Slack 13.1, but it did not work in Slack 13.7.
The serial /dev/ttyS0 could be software directed to /dev/input/mouse, or gpm repeater could be involved.
Another way is to put the serial mouse on a PS/2 adaptor.

Really the driver needs to be fixed so that "Device" works and that is what I am working on.
Currently the "Device" line now works, I am working on why "MouseSystems" protocol works using "Protocol" "Auto" but is clearly wrong using "Protocol" "MouseSystems".
I already verified that it is not a "Microsoft" mode mouse and is in "MouseSystems" mode.
But have problems; something is hanging the system upon X-windows shutdown now.

[ 40946.058] (II) Mouse1: ps2EnableDataReporting: succeeded
Do not know the significance of this line. I will check next time I am on that system.

Last edited by selfprogrammed; 02-26-2012 at 09:24 PM.
 
Old 02-28-2012, 05:12 PM   #13
selfprogrammed
Member
 
Registered: Jan 2010
Location: Minnesota, USA
Distribution: Slackware 13.37, 14.2, 15.0
Posts: 632

Original Poster
Rep: Reputation: 152Reputation: 152
mousedrv device patch

This patch cures the "Device" and "Protocol" problem for mousedrv.
It mostly just moves around existing lines so that Collect is before usage.

Apply the patch to xf86-input-mouse package, directory source and then configure and compile.
>> cd xf86-input-mouse-1.7.0/src/
>> patch -p1 < mousedrv_device.patch

There are two patch files as attachments, one of which is the same as below.

********** PATCH FILE: mousedrv_device.patch *********
diff -U4 /usr/src/x37/orig_src/xf86-input-mouse-1.7.0/src/mouse.c src/mouse.c
--- /usr/src/x37/orig_src/xf86-input-mouse-1.7.0/src/mouse.c 2011-03-09 16:28:38.000000000 -0600
+++ src/mouse.c 2012-02-28 01:12:57.000000000 -0600
@@ -926,8 +926,40 @@
pMse->Ctrl = MouseCtrl;
pMse->PostEvent = MousePostEvent;
pMse->CommonOptions = MouseCommonOptions;

+ /* Default Mapping: 1 2 3 8 9 10 11 ... */
+ for (i = 0; i < MSE_MAXBUTTONS; i++)
+ pMse->buttonMap[i] = 1 << (i > 2 && i < MSE_MAXBUTTONS-4 ? i+4 : i);
+
+ pMse->autoProbe = FALSE;
+
+ protocolFrom = X_DEFAULT;
+ protocol = (osInfo->DefaultProtocol)? osInfo->DefaultProtocol() : "Auto";
+ protocolID = ProtocolNameToID(protocol);
+ if (!(pProto = GetProtocol(protocolID)))
+ {
+ rc = BadValue;
+ goto out;
+ }
+ pMse->protocolID = protocolID;
+ pMse->oldProtocolID = protocolID; /* hack */
+
+ /* Collect the options, and process the common options. */
+#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) < 12
+ /* need some special handling here. xf86CollectInputOptions will reset
+ * pInfo->options if the second argument is not-null. To re-merge the
+ * previously set arguments, pass the original pInfo->options in.
+ */
+ xf86CollectInputOptions(pInfo, pProto->defaults, pInfo->options);
+#else
+ COLLECT_INPUT_OPTIONS(pInfo, pProto->defaults);
+#endif
+ xf86ProcessCommonOptions(pInfo, pInfo->options);
+
+ /* [WDJ] Check Device and Protocol options. Serial mice depend on getting
+ these from xorg.conf, there is no HAL/UDEV work-around. */
+
/* Find the protocol type. */
protocol = xf86SetStrOption(pInfo->options, "Protocol", NULL);
if (protocol) {
protocolFrom = X_CONFIG;
@@ -942,12 +974,9 @@
}

device = xf86SetStrOption(pInfo->options, "Device", NULL);

- /* Default Mapping: 1 2 3 8 9 10 11 ... */
- for (i = 0; i < MSE_MAXBUTTONS; i++)
- pMse->buttonMap[i] = 1 << (i > 2 && i < MSE_MAXBUTTONS-4 ? i+4 : i);
-
+ /* handles PROT_AUTO, PROT_UNKNOWN, PROT_UNSUP, sets protocolID too */
protocol = MousePickProtocol(pInfo, device, protocol, &protocolID);

if (!device)
MouseFindDevice(pInfo, protocol);
@@ -959,22 +988,8 @@
goto out;
}

pMse->protocolID = protocolID;
- pMse->oldProtocolID = protocolID; /* hack */
-
- pMse->autoProbe = FALSE;
- /* Collect the options, and process the common options. */
-#if GET_ABI_MAJOR(ABI_XINPUT_VERSION) < 12
- /* need some special handling here. xf86CollectInputOptions will reset
- * pInfo->options if the second argument is not-null. To re-merge the
- * previously set arguments, pass the original pInfo->options in.
- */
- xf86CollectInputOptions(pInfo, pProto->defaults, pInfo->options);
-#else
- COLLECT_INPUT_OPTIONS(pInfo, pProto->defaults);
-#endif
- xf86ProcessCommonOptions(pInfo, pInfo->options);

/* Check if the device can be opened. */
pInfo->fd = xf86OpenSerial(pInfo->options);
if (pInfo->fd == -1) {
@@ -1606,9 +1621,9 @@
);
xf86InitValuatorDefaults(device, 1);

#ifdef EXTMOUSEDEBUG
- ErrorF("assigning %p atom=%d name=%s\n", device, pInfo->atom,
+ ErrorF("assigning %p atom=%ld name=%s\n", device, pInfo->atom,
pInfo->name);
#endif
break;
Attached Files
File Type: txt WJ_mousedrv_device.patch.txt (3.3 KB, 9 views)
File Type: txt WJ_mousedrv_debug.patch.txt (6.1 KB, 10 views)
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
evdev/xorg help? USB mouse/kbd: 2.6.24="just works">2.6.25="unplug/replug to work". GrapefruiTgirl Linux - Hardware 4 12-13-2012 02:23 PM
There is no "Input Device" section in xorg.conf MooseMagnet Linux - Newbie 3 01-03-2009 05:35 PM
pl2303 attached to ttyUSB0 but driver attached to device is "serial" sheeluh Linux - Software 4 03-12-2007 04:27 AM
Problems configuring "xorg.conf" with "ATI FGLRX" BlueSpirit Slackware 3 09-16-2006 02:01 PM
what are the other "config's" like "mouse/xorg/xwmconfig ??? b0nd Slackware 2 01-10-2006 01:51 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:25 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration