Re: 2.5.X breaks PS/2 mouse

Re: 2.5.X breaks PS/2 mouse

[Vojtech Pavlik]

On Fri, Oct 04, 2002 at 09:20:26PM +0100, jbradford@dial.pipex.com wrote:
> One of my 486 laptops has a special port on the side, for a dedicated trackball.  I always assumed that it was electrically identical to the standard PS/2 mouse port, which is also present.
> 
> With 2.2.x, (I haven't tried 2.4.x on this machine), both the dedicated trackball and a standard external PS/2 mouse work fine, using /dev/psaux.
> 
> With 2.5.40, however, the behavior is as follows:
> 
> Booting:
> 
> With no pointing devices connected, just the port is detected:
> serio: i8042 AUX port at 0x60, 0x64 irq 12

This is OK.

> With the dedicated trackball connected, it also gets detected:
> input: PS/2 Generic mouse on isa0060/serio1
> serio: i8042 AUX port at 0x60, 0x64 irq 12

Also OK.

> Same with a PS/2 mouse, it also gets detected:
> input: PS/2 Generic mouse on isa0060/serio1
> serio: i8042 AUX port at 0x60, 0x64 irq 12

Also OK.

> Once booted:
> 
> Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:

Good, this is expected.

> Just to clarify, I am not trying to use them both at the same time.

Not sure if that would work, it might - depends on the notebook keyboard
controller hardware.

> X also works with the external PS/2 mouse,

Good.

> but not the dedicated trackball.

What are the exact symptoms? Does gpm work? Does cat /dev/psaux work? Does cat
/dev/input/mice work? What does cat /proc/bus/input/devices say in the
case it doesn't work? ....

> Any suggestions?

Just questions at this time ...

-- 
Vojtech Pavlik
SuSE Labs

2.5.X breaks PS/2 mouse

[jbradford]

One of my 486 laptops has a special port on the side, for a dedicated trackball.  I always assumed that it was electrically identical to the standard PS/2 mouse port, which is also present.

With 2.2.x, (I haven't tried 2.4.x on this machine), both the dedicated trackball and a standard external PS/2 mouse work fine, using /dev/psaux.

With 2.5.40, however, the behavior is as follows:

Booting:

With no pointing devices connected, just the port is detected:
serio: i8042 AUX port at 0x60, 0x64 irq 12

With the dedicated trackball connected, it also gets detected:
input: PS/2 Generic mouse on isa0060/serio1
serio: i8042 AUX port at 0x60, 0x64 irq 12

Same with a PS/2 mouse, it also gets detected:
input: PS/2 Generic mouse on isa0060/serio1
serio: i8042 AUX port at 0x60, 0x64 irq 12

Once booted:

Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:

Just to clarify, I am not trying to use them both at the same time.

X also works with the external PS/2 mouse, but not the dedicated trackball.

Any suggestions?

John.

Re: 2.5.X breaks PS/2 mouse

[Vojtech Pavlik]

On Fri, Oct 04, 2002 at 09:52:26PM +0100, jbradford@dial.pipex.com wrote:
> > > Once booted:
> > > 
> > > Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:
> > 
> > Good, this is expected.
> > 
> > > Just to clarify, I am not trying to use them both at the same time.
> > 
> > Not sure if that would work, it might - depends on the notebook keyboard
> > controller hardware.
> 
> I tried it, and it seems to get really confused - constant stream of seemingly random error messages.
> 
> > > X also works with the external PS/2 mouse,
> > 
> > Good.
> > 
> > > but not the dedicated trackball.
> > 
> > What are the exact symptoms?
> 
> No data at all from it.
> 
> > Does gpm work?
> 
> No.
> 
> > Does cat /dev/psaux work?
> 
> It doesn't say No such device, it just hangs, giving no data for the trackball, but works fine for the generic mouse.
> 
> > Does cat /dev/input/mice work?
> 
> Yes, it does the same as /dev/psaux
> 
> > What does cat /proc/bus/input/devices say in the
> > case it doesn't work? ....
> 
> I: Bus=0011 Vendor=0002 Product=0001 Version=0000
> N: Name="PS/2 Generic Mouse"
> P: Phys=isa0060/serio1/input0
> H: Handlers=mouse0
> B: EV=7
> B: KEY=70000 0 0 0 0 0 0 0 0
> B: REL=3
> 
> That's for both the generic mouse and the trackball.

Ok. Can you try the usual #define I8042_DEBUG_IO in
drivers/input/serio/i8042.h?

-- 
Vojtech Pavlik
SuSE Labs

Re: 2.5.X breaks PS/2 mouse

[jbradford]

> > Once booted:
> > 
> > Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:
> 
> Good, this is expected.
> 
> > Just to clarify, I am not trying to use them both at the same time.
> 
> Not sure if that would work, it might - depends on the notebook keyboard
> controller hardware.

I tried it, and it seems to get really confused - constant stream of seemingly random error messages.

> > X also works with the external PS/2 mouse,
> 
> Good.
> 
> > but not the dedicated trackball.
> 
> What are the exact symptoms?

No data at all from it.

> Does gpm work?

No.

> Does cat /dev/psaux work?

It doesn't say No such device, it just hangs, giving no data for the trackball, but works fine for the generic mouse.

> Does cat /dev/input/mice work?

Yes, it does the same as /dev/psaux

> What does cat /proc/bus/input/devices say in the
> case it doesn't work? ....

I: Bus=0011 Vendor=0002 Product=0001 Version=0000
N: Name="PS/2 Generic Mouse"
P: Phys=isa0060/serio1/input0
H: Handlers=mouse0
B: EV=7
B: KEY=70000 0 0 0 0 0 0 0 0
B: REL=3

That's for both the generic mouse and the trackball.

John.

Re: 2.5.X breaks PS/2 mouse

[jbradford]

> > > > Once booted:
> > > > 
> > > > Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:
> > > 
> > > Good, this is expected.
> > > 
> > > > Just to clarify, I am not trying to use them both at the same time.
> > > 
> > > Not sure if that would work, it might - depends on the notebook keyboard
> > > controller hardware.
> > 
> > I tried it, and it seems to get really confused - constant stream of seemingly random error messages.
> > 
> > > > X also works with the external PS/2 mouse,
> > > 
> > > Good.
> > > 
> > > > but not the dedicated trackball.
> > > 
> > > What are the exact symptoms?
> > 
> > No data at all from it.
> > 
> > > Does gpm work?
> > 
> > No.
> > 
> > > Does cat /dev/psaux work?
> > 
> > It doesn't say No such device, it just hangs, giving no data for the trackball, but works fine for the generic mouse.
> > 
> > > Does cat /dev/input/mice work?
> > 
> > Yes, it does the same as /dev/psaux
> > 
> > > What does cat /proc/bus/input/devices say in the
> > > case it doesn't work? ....
> > 
> > I: Bus=0011 Vendor=0002 Product=0001 Version=0000
> > N: Name="PS/2 Generic Mouse"
> > P: Phys=isa0060/serio1/input0
> > H: Handlers=mouse0
> > B: EV=7
> > B: KEY=70000 0 0 0 0 0 0 0 0
> > B: REL=3
> > 
> > That's for both the generic mouse and the trackball.
> 
> Ok. Can you try the usual #define I8042_DEBUG_IO in
> drivers/input/serio/i8042.h?

OK, no problem, but it might take a while.  The machine in question has a fubar floppy drive, and the only way to get a new kernel over to it is via a 9600 bps serial link...  I'll get to work straight away :-)

John.

Re: 2.5.X breaks PS/2 mouse

[jbradford]

> 
> On Fri, Oct 04, 2002 at 09:52:26PM +0100, jbradford@dial.pipex.com wrote:
> > > > Once booted:
> > > > 
> > > > Hot plugging either the dedicated trackball or a PS/2 mouse generates a message on connection:
> > > 
> > > Good, this is expected.
> > > 
> > > > Just to clarify, I am not trying to use them both at the same time.
> > > 
> > > Not sure if that would work, it might - depends on the notebook keyboard
> > > controller hardware.
> > 
> > I tried it, and it seems to get really confused - constant stream of seemingly random error messages.
> > 
> > > > X also works with the external PS/2 mouse,
> > > 
> > > Good.
> > > 
> > > > but not the dedicated trackball.
> > > 
> > > What are the exact symptoms?
> > 
> > No data at all from it.
> > 
> > > Does gpm work?
> > 
> > No.
> > 
> > > Does cat /dev/psaux work?
> > 
> > It doesn't say No such device, it just hangs, giving no data for the trackball, but works fine for the generic mouse.
> > 
> > > Does cat /dev/input/mice work?
> > 
> > Yes, it does the same as /dev/psaux
> > 
> > > What does cat /proc/bus/input/devices say in the
> > > case it doesn't work? ....
> > 
> > I: Bus=0011 Vendor=0002 Product=0001 Version=0000
> > N: Name="PS/2 Generic Mouse"
> > P: Phys=isa0060/serio1/input0
> > H: Handlers=mouse0
> > B: EV=7
> > B: KEY=70000 0 0 0 0 0 0 0 0
> > B: REL=3
> > 
> > That's for both the generic mouse and the trackball.
> 
> Ok. Can you try the usual #define I8042_DEBUG_IO in
> drivers/input/serio/i8042.h?

OK, here goes, here's a boot of the laptop, with no mouse or trackball connected:

register interface 'mouse' with class 'input
mice: PS/2 mouse device common for all mice
input: PC Speaker
i8042.c: 20 -> i8042 (command) [0]
i8042.c: 47 <- i8042 (return) [0]
i8042.c: 60 -> i8042 (command) [1]
i8042.c: 56 -> i8042 (parameter) [1]
i8042.c: d3 -> i8042 (command) [1]
i8042.c: 5a -> i8042 (parameter) [1]
i8042.c: a5 <- i8042 (return) [1]
i8042.c: a9 -> i8042 (command) [2]
i8042.c: 00 <- i8042 (return) [2]
i8042.c: a7 -> i8042 (command) [3]
i8042.c: 20 -> i8042 (command) [3]
i8042.c: 76 <- i8042 (return) [3]
i8042.c: a8 -> i8042 (command) [4]
i8042.c: 20 -> i8042 (command) [5]
i8042.c: 56 <- i8042 (return) [5]
i8042.c: 60 -> i8042 (command) [6]
i8042.c: 74 -> i8042 (parameter) [6]
i8042.c: 60 -> i8042 (command) [6]
i8042.c: 54 -> i8042 (parameter) [6]
i8042.c: 60 -> i8042 (command) [7]
i8042.c: 56 -> i8042 (parameter) [7]
i8042.c: d4 -> i8042 (command) [8]
i8042.c: f2 -> i8042 (parameter) [8]
i8042.c: fe <- i8042 (interrupt, aux, 12, timeout) [27]
i8042.c: 60 -> i8042 (command) [27]
i8042.c: 54 -> i8042 (parameter) [27]
i8042.c: 60 -> i8042 (command) [28]
i8042.c: 56 -> i8042 (parameter) [28]
i8042.c: d4 -> i8042 (command) [29]
i8042.c: ed -> i8042 (parameter) [29]
i8042.c: fe <- i8042 (interrupt, aux, 12, timeout) [48]
i8042.c: 60 -> i8042 (command) [48]
i8042.c: 54 -> i8042 (parameter) [48]
serio: i8042 AUX port at 0x60,0x64 irq 12
i8042.c: 60 -> i8042 (command) [50]
i8042.c: 44 -> i8042 (parameter) [50]
i8042.c: 60 -> i8042 (command) [51]
i8042.c: 45 -> i8042 (parameter) [51]
i8042.c: f2 -> i8042 (kbd-data) [52]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [54]
i8042.c: ab <- i8042 (interrupt, kbd, 1) [55]
i8042.c: 41 <- i8042 (interrupt, kbd, 1) [57]
i8042.c: 60 -> i8042 (command) [57]
i8042.c: 44 -> i8042 (parameter) [57]
i8042.c: 60 -> i8042 (command) [58]
i8042.c: 45 -> i8042 (parameter) [58]
i8042.c: ed -> i8042 (kbd-data) [59]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [61]
i8042.c: 00 -> i8042 (kbd-data) [62]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [64]
i8042.c: f2 -> i8042 (kbd-data) [65]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [67]
i8042.c: ab <- i8042 (interrupt, kbd, 1) [68]
i8042.c: 41 <- i8042 (interrupt, kbd, 1) [73]
i8042.c: f8 -> i8042 (kbd-data) [73]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [75]
i8042.c: f4 -> i8042 (kbd-data) [76]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [78]
i8042.c: ea -> i8042 (kbd-data) [79]
i8042.c: fe <- i8042 (interrupt, kbd, 1) [81]
i8042.c: f0 -> i8042 (kbd-data) [81]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [83]
i8042.c: 02 -> i8042 (kbd-data) [84]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [86]
i8042.c: f0 -> i8042 (kbd-data) [87]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [89]
i8042.c: 00 -> i8042 (kbd-data) [89]
i8042.c: fa <- i8042 (interrupt, kbd, 1) [94]
i8042.c: 41 <- i8042 (interrupt, kbd, 1) [96]
input: AT Set 2 keyboard on isa0060/serio0
serio: i8042 KBD port at 0x60,0x64 irq 1

Plugging in the trackball gives this:

i8042.c: aa <- i8042 (interrupt, aux, 0) [113024]
i8042.c: 60 -> i8042 (command) [113025]
i8042.c: 47 -> i8042 (parameter) [113025]
i8042.c: 00 <- i8042 (interrupt, aux, 0) [113025]
i8042.c: d4 -> i8042 (command) [113026]
i8042.c: f2 -> i8042 (parameter) [113026]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113030]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [113031]
i8042.c: d4 -> i8042 (command) [113031]
i8042.c: f6 -> i8042 (parameter) [113031]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113035]
i8042.c: d4 -> i8042 (command) [113035]
i8042.c: e8 -> i8042 (parameter) [113035]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113039]
i8042.c: d4 -> i8042 (command) [113039]
i8042.c: 03 -> i8042 (parameter) [113039]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113043]
i8042.c: d4 -> i8042 (command) [113043]
i8042.c: e6 -> i8042 (parameter) [113043]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113047]
i8042.c: d4 -> i8042 (command) [113047]
i8042.c: e6 -> i8042 (parameter) [113047]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113051]
i8042.c: d4 -> i8042 (command) [113051]
i8042.c: e6 -> i8042 (parameter) [113051]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113055]
i8042.c: d4 -> i8042 (command) [113055]
i8042.c: e9 -> i8042 (parameter) [113055]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113059]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [113060]
i8042.c: 03 <- i8042 (interrupt, aux, 12) [113065]
i8042.c: 64 <- i8042 (interrupt, aux, 12) [113066]
i8042.c: d4 -> i8042 (command) [113067]
i8042.c: e8 -> i8042 (parameter) [113067]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113070]
i8042.c: d4 -> i8042 (command) [113071]
i8042.c: 00 -> i8042 (parameter) [113071]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113074]
i8042.c: d4 -> i8042 (command) [113075]
i8042.c: e6 -> i8042 (parameter) [113075]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113078]
i8042.c: d4 -> i8042 (command) [113079]
i8042.c: e6 -> i8042 (parameter) [113079]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113083]
i8042.c: d4 -> i8042 (command) [113083]
i8042.c: e6 -> i8042 (parameter) [113083]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113087]
i8042.c: d4 -> i8042 (command) [113087]
i8042.c: e9 -> i8042 (parameter) [113087]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113091]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [113094]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [113095]
i8042.c: 64 <- i8042 (interrupt, aux, 12) [113096]
i8042.c: d4 -> i8042 (command) [113097]
i8042.c: f3 -> i8042 (parameter) [113097]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113100]
i8042.c: d4 -> i8042 (command) [113101]
i8042.c: c8 -> i8042 (parameter) [113101]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113105]
i8042.c: d4 -> i8042 (command) [113105]
i8042.c: f3 -> i8042 (parameter) [113105]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113109]
i8042.c: d4 -> i8042 (command) [113109]
i8042.c: 64 -> i8042 (parameter) [113109]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113113]
i8042.c: d4 -> i8042 (command) [113113]
i8042.c: f3 -> i8042 (parameter) [113113]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113117]
i8042.c: d4 -> i8042 (command) [113117]
i8042.c: 50 -> i8042 (parameter) [113117]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113121]
i8042.c: d4 -> i8042 (command) [113121]
i8042.c: f2 -> i8042 (parameter) [113121]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113125]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [113126]
input: PS/2 Generic Mouse on isa0060/serio1
i8042.c: d4 -> i8042 (command) [113128]
i8042.c: f3 -> i8042 (parameter) [113128]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113132]
i8042.c: d4 -> i8042 (command) [113132]
i8042.c: 64 -> i8042 (parameter) [113132]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113136]
i8042.c: d4 -> i8042 (command) [113136]
i8042.c: f3 -> i8042 (parameter) [113136]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113140]
i8042.c: d4 -> i8042 (command) [113140]
i8042.c: c8 -> i8042 (parameter) [113140]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113144]
i8042.c: d4 -> i8042 (command) [113144]
i8042.c: e8 -> i8042 (parameter) [113144]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113148]
i8042.c: d4 -> i8042 (command) [113148]
i8042.c: 03 -> i8042 (parameter) [113148]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113152]
i8042.c: d4 -> i8042 (command) [113152]
i8042.c: e6 -> i8042 (parameter) [113152]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113156]
i8042.c: d4 -> i8042 (command) [113156]
i8042.c: ea -> i8042 (parameter) [113156]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113160]
i8042.c: d4 -> i8042 (command) [113160]
i8042.c: f4 -> i8042 (parameter) [113160]
i8042.c: fa <- i8042 (interrupt, aux, 12) [113164]

Moving it around, (looks like some had already been lost from the top of this, I.E. it doesn't follow on directly from above):

i8042.c: 3d <- i8042 (interrupt, aux, 12) [189159]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189165]
i8042.c: 0d <- i8042 (interrupt, aux, 12) [189171]
i8042.c: 2b <- i8042 (interrupt, aux, 12) [189174]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189182]
i8042.c: f4 <- i8042 (interrupt, aux, 12) [189185]
i8042.c: 48 <- i8042 (interrupt, aux, 12) [189190]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189195]
i8042.c: cf <- i8042 (interrupt, aux, 12) [189198]
i8042.c: 3e <- i8042 (interrupt, aux, 12) [189201]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189207]
i8042.c: e6 <- i8042 (interrupt, aux, 12) [189211]
i8042.c: 29 <- i8042 (interrupt, aux, 12) [189214]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189220]
i8042.c: d1 <- i8042 (interrupt, aux, 12) [189223]
i8042.c: 3e <- i8042 (interrupt, aux, 12) [189227]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189232]
i8042.c: e1 <- i8042 (interrupt, aux, 12) [189234]
i8042.c: 26 <- i8042 (interrupt, aux, 12) [189235]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189238]
i8042.c: e8 <- i8042 (interrupt, aux, 12) [189239]
i8042.c: 15 <- i8042 (interrupt, aux, 12) [189241]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189244]
i8042.c: fc <- i8042 (interrupt, aux, 12) [189246]
i8042.c: f3 <- i8042 (interrupt, aux, 12) [189248]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189254]
i8042.c: fe <- i8042 (interrupt, aux, 12) [189256]
i8042.c: cb <- i8042 (interrupt, aux, 12) [189259]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189263]
i8042.c: 01 <- i8042 (interrupt, aux, 12) [189266]
i8042.c: cd <- i8042 (interrupt, aux, 12) [189269]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189274]
i8042.c: 0a <- i8042 (interrupt, aux, 12) [189275]
i8042.c: d7 <- i8042 (interrupt, aux, 12) [189277]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189279]
i8042.c: 0a <- i8042 (interrupt, aux, 12) [189280]
i8042.c: f9 <- i8042 (interrupt, aux, 12) [189282]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189284]
i8042.c: 0c <- i8042 (interrupt, aux, 12) [189286]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189289]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189297]
i8042.c: 1f <- i8042 (interrupt, aux, 12) [189300]
i8042.c: 19 <- i8042 (interrupt, aux, 12) [189303]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189310]
i8042.c: 3a <- i8042 (interrupt, aux, 12) [189316]
i8042.c: 3a <- i8042 (interrupt, aux, 12) [189319]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189324]
i8042.c: 36 <- i8042 (interrupt, aux, 12) [189327]
i8042.c: 48 <- i8042 (interrupt, aux, 12) [189331]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189337]
i8042.c: 1b <- i8042 (interrupt, aux, 12) [189340]
i8042.c: 27 <- i8042 (interrupt, aux, 12) [189343]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189348]
i8042.c: 1c <- i8042 (interrupt, aux, 12) [189350]
i8042.c: 47 <- i8042 (interrupt, aux, 12) [189351]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189353]
i8042.c: 02 <- i8042 (interrupt, aux, 12) [189355]
i8042.c: 0f <- i8042 (interrupt, aux, 12) [189359]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189363]
i8042.c: fd <- i8042 (interrupt, aux, 12) [189364]
i8042.c: 1d <- i8042 (interrupt, aux, 12) [189365]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189368]
i8042.c: f7 <- i8042 (interrupt, aux, 12) [189369]
i8042.c: 07 <- i8042 (interrupt, aux, 12) [189371]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189373]
i8042.c: f4 <- i8042 (interrupt, aux, 12) [189374]
i8042.c: 02 <- i8042 (interrupt, aux, 12) [189379]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189383]
i8042.c: db <- i8042 (interrupt, aux, 12) [189386]
i8042.c: f5 <- i8042 (interrupt, aux, 12) [189389]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189393]
i8042.c: e1 <- i8042 (interrupt, aux, 12) [189396]
i8042.c: e0 <- i8042 (interrupt, aux, 12) [189400]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189403]
i8042.c: ed <- i8042 (interrupt, aux, 12) [189405]
i8042.c: db <- i8042 (interrupt, aux, 12) [189407]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189409]
i8042.c: ff <- i8042 (interrupt, aux, 12) [189411]
i8042.c: ed <- i8042 (interrupt, aux, 12) [189414]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189418]
i8042.c: 16 <- i8042 (interrupt, aux, 12) [189422]
i8042.c: e2 <- i8042 (interrupt, aux, 12) [189425]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189429]
i8042.c: 29 <- i8042 (interrupt, aux, 12) [189432]
i8042.c: ed <- i8042 (interrupt, aux, 12) [189435]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189442]
i8042.c: 29 <- i8042 (interrupt, aux, 12) [189445]
i8042.c: f2 <- i8042 (interrupt, aux, 12) [189448]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189454]
i8042.c: 3b <- i8042 (interrupt, aux, 12) [189456]
i8042.c: ed <- i8042 (interrupt, aux, 12) [189459]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189466]
i8042.c: 21 <- i8042 (interrupt, aux, 12) [189469]
i8042.c: fb <- i8042 (interrupt, aux, 12) [189472]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189479]
i8042.c: 46 <- i8042 (interrupt, aux, 12) [189485]
i8042.c: f5 <- i8042 (interrupt, aux, 12) [189488]
i8042.c: 20 <- i8042 (interrupt, aux, 12) [189494]
i8042.c: 46 <- i8042 (interrupt, aux, 12) [189497]
i8042.c: ff <- i8042 (interrupt, aux, 12) [189500]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189507]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189509]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189512]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189517]
i8042.c: 4f <- i8042 (interrupt, aux, 12) [189520]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189526]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189530]
i8042.c: 32 <- i8042 (interrupt, aux, 12) [189533]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189536]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189539]
i8042.c: 30 <- i8042 (interrupt, aux, 12) [189541]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189547]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189552]
i8042.c: 50 <- i8042 (interrupt, aux, 12) [189554]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189556]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189559]
i8042.c: 16 <- i8042 (interrupt, aux, 12) [189561]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189563]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189568]
i8042.c: 25 <- i8042 (interrupt, aux, 12) [189570]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189572]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189577]
i8042.c: 24 <- i8042 (interrupt, aux, 12) [189578]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189580]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189582]
i8042.c: 10 <- i8042 (interrupt, aux, 12) [189584]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189585]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189589]
i8042.c: 0e <- i8042 (interrupt, aux, 12) [189591]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189592]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189597]
i8042.c: 19 <- i8042 (interrupt, aux, 12) [189598]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189599]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189602]
i8042.c: 0a <- i8042 (interrupt, aux, 12) [189603]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189604]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189607]
i8042.c: 09 <- i8042 (interrupt, aux, 12) [189611]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189612]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189616]
i8042.c: 0e <- i8042 (interrupt, aux, 12) [189618]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189619]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189622]
i8042.c: 05 <- i8042 (interrupt, aux, 12) [189623]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189624]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189627]
i8042.c: 04 <- i8042 (interrupt, aux, 12) [189628]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189632]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189636]
i8042.c: 06 <- i8042 (interrupt, aux, 12) [189638]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [189639]

Pressing the left button, then the right button, (this is complete, and follows the above immediately):

i8042.c: 01 <- i8042 (interrupt, aux, 12) [230409]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [230410]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [230411]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [230548]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [230552]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [230554]
i8042.c: 02 <- i8042 (interrupt, aux, 12) [231505]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [231506]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [231507]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [231694]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [231695]
i8042.c: 00 <- i8042 (interrupt, aux, 12) [231696]

So, it definitely seems to be sending data to the port...  Strange...

John.

Re: 2.5.X breaks PS/2 mouse

[Vojtech Pavlik]

On Fri, Oct 04, 2002 at 11:25:43PM +0100, jbradford@dial.pipex.com wrote:

> Pressing the left button, then the right button, (this is complete, and follows the above immediately):
> 
> i8042.c: 01 <- i8042 (interrupt, aux, 12) [230409]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [230410]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [230411]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [230548]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [230552]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [230554]
> i8042.c: 02 <- i8042 (interrupt, aux, 12) [231505]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [231506]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [231507]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [231694]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [231695]
> i8042.c: 00 <- i8042 (interrupt, aux, 12) [231696]
> 
> So, it definitely seems to be sending data to the port...  Strange...

It must work. I'm really wondering why it doesn't. What happens when you
load the 'evbug' module?

-- 
Vojtech Pavlik
SuSE Labs

Re: 2.5.X breaks PS/2 mouse

[Vojtech Pavlik]

On Mon, Oct 07, 2002 at 01:46:20PM +0100, jbradford@dial.pipex.com wrote:
> > > Pressing the left button, then the right button, (this is complete, and follows the above immediately):
> > > 
> > > i8042.c: 01 <- i8042 (interrupt, aux, 12) [230409]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230410]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230411]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230548]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230552]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230554]
> > > i8042.c: 02 <- i8042 (interrupt, aux, 12) [231505]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231506]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231507]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231694]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231695]
> > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231696]
> > > 
> > > So, it definitely seems to be sending data to the port...  Strange...
> > 
> > It must work. I'm really wondering why it doesn't. What happens when you
> > load the 'evbug' module?
> 
> I can't very easily - the kernel on the machine doesn't have kernel module support enabled, and with 4MB RAM, it's really painfully slow to work with if I use a kernel with modules enabled.  If there is no other way to debug it, I can try, but it's a last resort :-)

Do you have 'evdev' (Event interface) compiled in? It'd be a replacement
for evbug ...

> Something that occurred to me, and I could be totally wrong here, but
> is it possible that the trackball is being detected as a "generic
> mouse" when it isn't one?

Most likely (95%) it behaves a generic ps/2 mouse. After all, it seems
to send generic ps/2 data. Why the data isn't getting through, is the
question.

> I tried connecting the generic mouse, disconnecting it, and then
> connecting the trackball, and saw in dmesg that some kind of handshake
> was going on.  This was completely different for mouse and trackball.
> Would it be any use to post this output?

If it was different, then definitely!

> If the evbug module is the only way to go, I'll try it, but it'll
> probably take me the rest of the day, (seriously) :-).

Let's try other ways before that.

-- 
Vojtech Pavlik
SuSE Labs

Re: 2.5.X breaks PS/2 mouse

[jbradford]

> > Pressing the left button, then the right button, (this is complete, and follows the above immediately):
> > 
> > i8042.c: 01 <- i8042 (interrupt, aux, 12) [230409]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230410]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230411]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230548]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230552]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230554]
> > i8042.c: 02 <- i8042 (interrupt, aux, 12) [231505]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231506]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231507]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231694]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231695]
> > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231696]
> > 
> > So, it definitely seems to be sending data to the port...  Strange...
> 
> It must work. I'm really wondering why it doesn't. What happens when you
> load the 'evbug' module?

I can't very easily - the kernel on the machine doesn't have kernel module support enabled, and with 4MB RAM, it's really painfully slow to work with if I use a kernel with modules enabled.  If there is no other way to debug it, I can try, but it's a last resort :-)

Something that occurred to me, and I could be totally wrong here, but is it possible that the trackball is being detected as a "generic mouse" when it isn't one?

I tried connecting the generic mouse, disconnecting it, and then connecting the trackball, and saw in dmesg that some kind of handshake was going on.  This was completely different for mouse and trackball.  Would it be any use to post this output?

If the evbug module is the only way to go, I'll try it, but it'll probably take me the rest of the day, (seriously) :-).

John.

Re: 2.5.X breaks PS/2 mouse

[jbradford]

> > > > Pressing the left button, then the right button, (this is complete, and follows the above immediately):
> > > > 
> > > > i8042.c: 01 <- i8042 (interrupt, aux, 12) [230409]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230410]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230411]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230548]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230552]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [230554]
> > > > i8042.c: 02 <- i8042 (interrupt, aux, 12) [231505]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231506]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231507]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231694]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231695]
> > > > i8042.c: 00 <- i8042 (interrupt, aux, 12) [231696]
> > > > 
> > > > So, it definitely seems to be sending data to the port...  Strange...
> > > 
> > > It must work. I'm really wondering why it doesn't. What happens when you
> > > load the 'evbug' module?
> > 
> > I can't very easily - the kernel on the machine doesn't have kernel module
> > support enabled, and with 4MB RAM, it's really painfully slow to work with
> > if I use a kernel with modules enabled.  If there is no other way to debug
> > it, I can try, but it's a last resort :-)
> 
> Do you have 'evdev' (Event interface) compiled in? It'd be a replacement
> for evbug ...

I didn't, but I've compiled a new kernel with it in.  Unfortunately, it doesn't seem to do anything useful :-(.

cat /dev/input/eventX | hexdump

returns nothing, not even for keyboard events, which makes me think I've gone wrong somewhere :-/

> > Something that occurred to me, and I could be totally wrong here, but
> > is it possible that the trackball is being detected as a "generic
> > mouse" when it isn't one?
> 
> Most likely (95%) it behaves a generic ps/2 mouse. After all, it seems
> to send generic ps/2 data. Why the data isn't getting through, is the
> question.
> 
> > I tried connecting the generic mouse, disconnecting it, and then
> > connecting the trackball, and saw in dmesg that some kind of handshake
> > was going on.  This was completely different for mouse and trackball.
> > Would it be any use to post this output?
> 
> If it was different, then definitely!

Sorry, I was wrong, I think I pressed a mouse button whilst connecting it and mis-read the info.  The init is exactly the same.

However, the data sent from each one seems to be very different, (I've re-formatted this a bit to save space, but it's from the dmesg output):

mouse

 Left button - 09 00 00 08 00 00
Right button - 0a 00 00 08 00 00

trackball

 Left button - 01 00 00 00 00 00
Right button - 02 00 00 00 00 00

> > If the evbug module is the only way to go, I'll try it, but it'll
> > probably take me the rest of the day, (seriously) :-).
> 
> Let's try other ways before that.

Good idea :-)

John.

Re: 2.5.X breaks PS/2 mouse

[Vojtech Pavlik]

On Mon, Oct 07, 2002 at 03:17:13PM +0100, jbradford@dial.pipex.com wrote:

> I didn't, but I've compiled a new kernel with it in.  Unfortunately, it doesn't seem to do anything useful :-(.
> 
> cat /dev/input/eventX | hexdump
> 
> returns nothing, not even for keyboard events, which makes me think I've gone wrong somewhere :-/

Have you tried all of them (0, 1, 2 ...)? Btw, you can compile evbug in
also.

> > If it was different, then definitely!
> 
> Sorry, I was wrong, I think I pressed a mouse button whilst connecting it and mis-read the info.  The init is exactly the same.
> 
> However, the data sent from each one seems to be very different, (I've re-formatted this a bit to save space, but it's from the dmesg output):
> 
> mouse
> 
>  Left button - 09 00 00 08 00 00
> Right button - 0a 00 00 08 00 00
> 
> trackball
> 
>  Left button - 01 00 00 00 00 00
> Right button - 02 00 00 00 00 00

Hmm, interesting ... let's see what that means ...

Indeed the 0x08 byte indicates the beginning of a packet. The driver
synchronizes on that, and when it's missing, it ignores the packets.
Thus, it ignores all the packets from the trackball.

This patch should fix that:

===================================================================

diff -Nru a/drivers/input/mouse/psmouse.c b/drivers/input/mouse/psmouse.c
--- a/drivers/input/mouse/psmouse.c	Mon Oct  7 16:22:53 2002
+++ b/drivers/input/mouse/psmouse.c	Mon Oct  7 16:22:53 2002
@@ -201,7 +201,7 @@
 	psmouse->packet[psmouse->pktcnt++] = data;
 
 	if (psmouse->pktcnt == 3 + (psmouse->type >= PSMOUSE_GENPS)) {
-		if ((psmouse->packet[0] & 0x08) == 0x08) psmouse_process_packet(psmouse);
+		psmouse_process_packet(psmouse);
 		psmouse->pktcnt = 0;
 		return;
 	}

===================================================================

-- 
Vojtech Pavlik
SuSE Labs

[FUNNY] Re: 2.5.X breaks PS/2 mouse

[jbradford]

[snip conversation about PS/2 mice]

OK, this is amusing for everybody else, and very irritating for me, but as you're all bound to find it funny, I'm posting it so that you can all have a laugh at my expense:

Whilst capturing all of the DMESG data, I decided it would be a Good Thing (tm) to use a serial terminal, to avoid getting console keypresses in the output.  So, I configured /dev/ttyS0 in /etc/inittab/ and /etc/securetty, to run a getty on the serial port, and allow root login.  No problem there.  Then I needed to transfer a kernel image through the serial port, so I edited back /etc/securetty to how it was, and removed tty1 from /etc/inittab.

Yes, exactly, I removed the tty1 from /etc/inittab, so when I rebooted, I got nothing on the console, after the console font was loaded.

"Ah, no problem, just use another VT!", I can hear you all shouting, which is fine, except for the fact that I disabled them all to save memory, (this is a 4MB RAM machine).

"Boot from a floppy!", somebody is probably shouting - good idea, except that the floppy drive is broken on this laptop

"Re-connect the serial console!", is another Good Idea (tm), and the one I thought of.  Except that /etc/securetty doesn't list /dev/ttyS0 anymore, so I can't log in as root, and there are no other user accounts on the system.

So, the only way to fix the problem is to take apart the laptop, put the hard disk in to another machine, boot another kernel from CD, and add tty1 back in to /etc/inittab.

Anyway, feel free to laugh, it is quite funny after all :-)

Now, where is that screwdriver...

John.

Re: 2.5.X breaks PS/2 mouse

[Vojtech Pavlik]

On Mon, Oct 07, 2002 at 09:15:45PM +0100, jbradford@dial.pipex.com wrote:
> Finally re-assembled the laptop :-)
> 
> > > I didn't, but I've compiled a new kernel with it in.  Unfortunately,
> > > it doesn't seem to do anything useful :-(.
> > > 
> > > cat /dev/input/eventX | hexdump
> > > 
> > > returns nothing, not even for keyboard events, which makes me think
> > > I've gone wrong somewhere :-/
> > 
> > Have you tried all of them (0, 1, 2 ...)? Btw, you can compile evbug in
> > also.
> 
> Whoops, me being silly again, I actually created a single device node
> called /dev/input/eventX instead of event1, event2, etc.  :-)
> 
> > > mouse
> > > 
> > >  Left button - 09 00 00 08 00 00
> > > Right button - 0a 00 00 08 00 00
> > > 
> > > trackball
> > > 
> > >  Left button - 01 00 00 00 00 00
> > > Right button - 02 00 00 00 00 00
> > 
> > Hmm, interesting ... let's see what that means ...
> > 
> > Indeed the 0x08 byte indicates the beginning of a packet. The driver
> > synchronizes on that, and when it's missing, it ignores the packets.
> > Thus, it ignores all the packets from the trackball.
> > 
> > This patch should fix that:
> 
> It does.  Cool!
> 
> GPM and X work perfectly.
> 
> Cheers!

And yet another case closed. :)

-- 
Vojtech Pavlik
SuSE Labs

Re: 2.5.X breaks PS/2 mouse

[jbradford]

Finally re-assembled the laptop :-)

> > I didn't, but I've compiled a new kernel with it in.  Unfortunately,
> > it doesn't seem to do anything useful :-(.
> > 
> > cat /dev/input/eventX | hexdump
> > 
> > returns nothing, not even for keyboard events, which makes me think
> > I've gone wrong somewhere :-/
> 
> Have you tried all of them (0, 1, 2 ...)? Btw, you can compile evbug in
> also.

Whoops, me being silly again, I actually created a single device node
called /dev/input/eventX instead of event1, event2, etc.  :-)

> > mouse
> > 
> >  Left button - 09 00 00 08 00 00
> > Right button - 0a 00 00 08 00 00
> > 
> > trackball
> > 
> >  Left button - 01 00 00 00 00 00
> > Right button - 02 00 00 00 00 00
> 
> Hmm, interesting ... let's see what that means ...
> 
> Indeed the 0x08 byte indicates the beginning of a packet. The driver
> synchronizes on that, and when it's missing, it ignores the packets.
> Thus, it ignores all the packets from the trackball.
> 
> This patch should fix that:

It does.  Cool!

GPM and X work perfectly.

Cheers!

John.

Re: 2.5.X breaks PS/2 mouse

[Thomas Molina]

On Mon, 7 Oct 2002, Vojtech Pavlik wrote:

> > > Indeed the 0x08 byte indicates the beginning of a packet. The driver
> > > synchronizes on that, and when it's missing, it ignores the packets.
> > > Thus, it ignores all the packets from the trackball.
> > > 
> > > This patch should fix that:
> > 
> > It does.  Cool!
> > 
> > GPM and X work perfectly.
> > 
> > Cheers!
> 
> And yet another case closed. :)

Before I even get to add it to my problem report page :)