Hi!
I'm using thinkpad x60 with external USB mouse. On first boot, both
mice stopped working after minute-or-so in X. Lets see if it breaks on
the next boot, too..
USB keyboard still works, and dmesg seems to contain repeated
detections of USB mouse. But unplugging USB mouse does not bring
internal trackpoint to work, so...
Any ideas?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Thu, 15 Nov 2012, Pavel Machek wrote:
> I'm using thinkpad x60 with external USB mouse. On first boot, both
> mice stopped working after minute-or-so in X. Lets see if it breaks on
> the next boot, too..
>
> USB keyboard still works, and dmesg seems to contain repeated
> detections of USB mouse. But unplugging USB mouse does not bring
> internal trackpoint to work, so...
>
> Any ideas?
Does the dmesg also contain information regarding disconnection of the
mouse before it stopped working?
--
Jiri Kosina
SUSE Labs
Hi!
> I'm using thinkpad x60 with external USB mouse. On first boot, both
> mice stopped working after minute-or-so in X. Lets see if it breaks on
> the next boot, too..
Aha, happens on next boot, and mice are broken from the start.
Hmm. And even on console, gpm is not there, and if I try to start it
manually, it finds that /dev/input/mice: "no such device or
address". Manual "cat" gives same result.
/dev/input/mice is c 13, 63 device.
Looks like real regression here.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Thu 2012-11-15 14:30:04, Jiri Kosina wrote:
> On Thu, 15 Nov 2012, Pavel Machek wrote:
>
> > I'm using thinkpad x60 with external USB mouse. On first boot, both
> > mice stopped working after minute-or-so in X. Lets see if it breaks on
> > the next boot, too..
> >
> > USB keyboard still works, and dmesg seems to contain repeated
> > detections of USB mouse. But unplugging USB mouse does not bring
> > internal trackpoint to work, so...
> >
> > Any ideas?
>
> Does the dmesg also contain information regarding disconnection of the
> mouse before it stopped working?
See the other mail, /dev/input/mice is not working.
And yes, mouse seems to be detected multiple times; it may have
happened before, with /dev/input/mice I would not notice.
dmesg attached.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Thu, 15 Nov 2012, Pavel Machek wrote:
> > > I'm using thinkpad x60 with external USB mouse. On first boot, both
> > > mice stopped working after minute-or-so in X. Lets see if it breaks on
> > > the next boot, too..
> > >
> > > USB keyboard still works, and dmesg seems to contain repeated
> > > detections of USB mouse. But unplugging USB mouse does not bring
> > > internal trackpoint to work, so...
> > >
> > > Any ideas?
> >
> > Does the dmesg also contain information regarding disconnection of the
> > mouse before it stopped working?
>
> See the other mail, /dev/input/mice is not working.
>
> And yes, mouse seems to be detected multiple times; it may have
> happened before, with /dev/input/mice I would not notice.
>
> dmesg attached.
If you have mouse that is buggy and periodically
disconnecting/reconnecting itself, you need commit df0cfd6990347c, which
went into 3.7-rc5 (it's a regression fix from -rc1).
--
Jiri Kosina
SUSE Labs
On Thu 2012-11-15 15:10:03, Jiri Kosina wrote:
> On Thu, 15 Nov 2012, Pavel Machek wrote:
>
> > > > I'm using thinkpad x60 with external USB mouse. On first boot, both
> > > > mice stopped working after minute-or-so in X. Lets see if it breaks on
> > > > the next boot, too..
> > > >
> > > > USB keyboard still works, and dmesg seems to contain repeated
> > > > detections of USB mouse. But unplugging USB mouse does not bring
> > > > internal trackpoint to work, so...
> > > >
> > > > Any ideas?
> > >
> > > Does the dmesg also contain information regarding disconnection of the
> > > mouse before it stopped working?
> >
> > See the other mail, /dev/input/mice is not working.
> >
> > And yes, mouse seems to be detected multiple times; it may have
> > happened before, with /dev/input/mice I would not notice.
> >
> > dmesg attached.
>
> If you have mouse that is buggy and periodically
> disconnecting/reconnecting itself, you need commit df0cfd6990347c, which
> went into 3.7-rc5 (it's a regression fix from -rc1).
I have -rc5 now, and still no mice for me.
root@amd:/tmp# uname -a
Linux amd 3.7.0-rc5+ #236 SMP Thu Nov 15 20:07:26 CET 2012 i686 GNU/Linux
root@amd:/tmp# cat /dev/input/mice
cat: /dev/input/mice: No such device or address
root@amd:/tmp# ls -al /dev/input/mice
crw-rw---- 1 root root 13, 63 Apr 25 2010 /dev/input/mice
root@amd:/tmp#
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Fri, 16 Nov 2012, Pavel Machek wrote:
> > If you have mouse that is buggy and periodically
> > disconnecting/reconnecting itself, you need commit df0cfd6990347c, which
> > went into 3.7-rc5 (it's a regression fix from -rc1).
>
> I have -rc5 now, and still no mice for me.
>
> root@amd:/tmp# uname -a
> Linux amd 3.7.0-rc5+ #236 SMP Thu Nov 15 20:07:26 CET 2012 i686 GNU/Linux
> root@amd:/tmp# cat /dev/input/mice
> cat: /dev/input/mice: No such device or address
> root@amd:/tmp# ls -al /dev/input/mice
> crw-rw---- 1 root root 13, 63 Apr 25 2010 /dev/input/mice
> root@amd:/tmp#
Let's see whether this is /dev/input/mice issue or something else first.
Is anything coming out of corresponding /dev/input/eventX node?
And /dev/hidrawX?
Thanks,
--
Jiri Kosina
SUSE Labs
On Fri 2012-11-16 11:54:26, Jiri Kosina wrote:
> On Fri, 16 Nov 2012, Pavel Machek wrote:
>
> > > If you have mouse that is buggy and periodically
> > > disconnecting/reconnecting itself, you need commit df0cfd6990347c, which
> > > went into 3.7-rc5 (it's a regression fix from -rc1).
> >
> > I have -rc5 now, and still no mice for me.
> >
> > root@amd:/tmp# uname -a
> > Linux amd 3.7.0-rc5+ #236 SMP Thu Nov 15 20:07:26 CET 2012 i686 GNU/Linux
> > root@amd:/tmp# cat /dev/input/mice
> > cat: /dev/input/mice: No such device or address
> > root@amd:/tmp# ls -al /dev/input/mice
> > crw-rw---- 1 root root 13, 63 Apr 25 2010 /dev/input/mice
> > root@amd:/tmp#
>
> Let's see whether this is /dev/input/mice issue or something else first.
>
> Is anything coming out of corresponding /dev/input/eventX node?
/dev/input/mouse0 and /dev/input/mouse1 generate events when I move
internal/USB mouse.
ls -al /dev/input/mouse0
crw-rw---- 1 root root 13, 32 Apr 25 2010 /dev/input/mouse0
pavel@amd:/tmp$ ls -al /dev/input/mouse1
crw------T 1 root root 13, 33 Aug 30 16:41 /dev/input/mouse1
pavel@amd:/tmp$
> And /dev/hidrawX?
/dev/hidraw0 seems to correspond to USB mouse and generates
events. Could not find hidraw corresponding to PS/2 mouse.
So it seems to be "/dev/input/mice" issue. Does it work for you?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
On Fri, 16 Nov 2012, Pavel Machek wrote:
> > > root@amd:/tmp# uname -a
> > > Linux amd 3.7.0-rc5+ #236 SMP Thu Nov 15 20:07:26 CET 2012 i686 GNU/Linux
> > > root@amd:/tmp# cat /dev/input/mice
> > > cat: /dev/input/mice: No such device or address
> > > root@amd:/tmp# ls -al /dev/input/mice
> > > crw-rw---- 1 root root 13, 63 Apr 25 2010 /dev/input/mice
> > > root@amd:/tmp#
> >
> > Let's see whether this is /dev/input/mice issue or something else first.
> >
> > Is anything coming out of corresponding /dev/input/eventX node?
>
> /dev/input/mouse0 and /dev/input/mouse1 generate events when I move
> internal/USB mouse.
>
> ls -al /dev/input/mouse0
> crw-rw---- 1 root root 13, 32 Apr 25 2010 /dev/input/mouse0
> pavel@amd:/tmp$ ls -al /dev/input/mouse1
> crw------T 1 root root 13, 33 Aug 30 16:41 /dev/input/mouse1
> pavel@amd:/tmp$
>
> > And /dev/hidrawX?
>
> /dev/hidraw0 seems to correspond to USB mouse and generates
> events. Could not find hidraw corresponding to PS/2 mouse.
That is correct and expected behavior.
> So it seems to be "/dev/input/mice" issue. Does it work for you?
Yes, it works for me properly (testing with rc4+, 1b42fc4 more precisely).
Even after disconnect/reconnect cycle of USB mouse, I am getting events
properly from /dev/input/mice (frankly I am surprised that you noticed ...
Xorg has been using evdev driver for ages already by default, right?)
What was the last kernel version that worked for you in this respect?
Adding Dmitry and linux-input.
--
Jiri Kosina
SUSE Labs
On Fri, Nov 16, 2012 at 01:37:31PM +0100, Jiri Kosina wrote:
> On Fri, 16 Nov 2012, Pavel Machek wrote:
>
> > > > root@amd:/tmp# uname -a
> > > > Linux amd 3.7.0-rc5+ #236 SMP Thu Nov 15 20:07:26 CET 2012 i686 GNU/Linux
> > > > root@amd:/tmp# cat /dev/input/mice
> > > > cat: /dev/input/mice: No such device or address
> > > > root@amd:/tmp# ls -al /dev/input/mice
> > > > crw-rw---- 1 root root 13, 63 Apr 25 2010 /dev/input/mice
> > > > root@amd:/tmp#
> > >
> > > Let's see whether this is /dev/input/mice issue or something else first.
> > >
> > > Is anything coming out of corresponding /dev/input/eventX node?
> >
> > /dev/input/mouse0 and /dev/input/mouse1 generate events when I move
> > internal/USB mouse.
> >
> > ls -al /dev/input/mouse0
> > crw-rw---- 1 root root 13, 32 Apr 25 2010 /dev/input/mouse0
> > pavel@amd:/tmp$ ls -al /dev/input/mouse1
> > crw------T 1 root root 13, 33 Aug 30 16:41 /dev/input/mouse1
> > pavel@amd:/tmp$
> >
> > > And /dev/hidrawX?
> >
> > /dev/hidraw0 seems to correspond to USB mouse and generates
> > events. Could not find hidraw corresponding to PS/2 mouse.
>
> That is correct and expected behavior.
>
> > So it seems to be "/dev/input/mice" issue. Does it work for you?
>
> Yes, it works for me properly (testing with rc4+, 1b42fc4 more precisely).
> Even after disconnect/reconnect cycle of USB mouse, I am getting events
> properly from /dev/input/mice (frankly I am surprised that you noticed ...
> Xorg has been using evdev driver for ages already by default, right?)
>
> What was the last kernel version that worked for you in this respect?
>
> Adding Dmitry and linux-input.
Does the patch below help?
Thanks.
--
Dmitry
Input: mousedev - move /deb/input/mice to teh correct minor
From: Dmitry Torokhov <[email protected]>
When doing conversion to dynamic input numbers I inadvertently moved
/dev/input/mice form c,13,63 to c,13,31. We need to fix this so that
setups with statically populated /dev continue working.
Signed-off-by: Dmitry Torokhov <[email protected]>
---
drivers/input/mousedev.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/input/mousedev.c b/drivers/input/mousedev.c
index 8f02e3d..4c842c3 100644
--- a/drivers/input/mousedev.c
+++ b/drivers/input/mousedev.c
@@ -12,8 +12,8 @@
#define pr_fmt(fmt) KBUILD_MODNAME ": " fmt
#define MOUSEDEV_MINOR_BASE 32
-#define MOUSEDEV_MINORS 32
-#define MOUSEDEV_MIX 31
+#define MOUSEDEV_MINORS 31
+#define MOUSEDEV_MIX 63
#include <linux/sched.h>
#include <linux/slab.h>
On Sun, Nov 18, 2012 at 12:56:38AM -0800, Dmitry Torokhov wrote:
>
> Input: mousedev - move /deb/input/mice to teh correct minor
s/teh/the/ ??
>
> From: Dmitry Torokhov <[email protected]>
>
> When doing conversion to dynamic input numbers I inadvertently moved
> /dev/input/mice form c,13,63 to c,13,31. We need to fix this so that
> setups with statically populated /dev continue working.
>
> Signed-off-by: Dmitry Torokhov <[email protected]>
I had the same problem and this patch fixes it (I even concurrently fixed
that in similar way).
If you need that:
Tested-by: Krzysztof Mazur <[email protected]>
Thanks,
Krzysiek
Hi!
> > That is correct and expected behavior.
> >
> > > So it seems to be "/dev/input/mice" issue. Does it work for you?
> >
> > Yes, it works for me properly (testing with rc4+, 1b42fc4 more precisely).
> > Even after disconnect/reconnect cycle of USB mouse, I am getting events
> > properly from /dev/input/mice (frankly I am surprised that you noticed ...
> > Xorg has been using evdev driver for ages already by default, right?)
> >
> > What was the last kernel version that worked for you in this respect?
> >
> > Adding Dmitry and linux-input.
>
> Does the patch below help?
Yes. With this patch, my mice are back.
Tested-by: Pavel Machek <[email protected]>
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html