test9-mm1 breaks PS/2 mouse function

wrc1944

Apparently, test9-mm1 has broken some PS/2 mouse functions. I'm using the same .config file as in test9 vanilla, and now the pointer movement with mm1 is extremely slow- less than 5% of test9. Everything is exactly the same- all settings, all hardware. The only difference is adding mm1 to test9. Other mm versions of 2.6.0 kernels have always worked fine, and still do- just test9-mm1suddenly has this problem.

No amount of adjusting & increasing mouse advanced settings in kde control center has any effect. Scroll still works at normal speed. It renders test9-mm1 completely unusable- it's as if all mouse speed settings have defaulted to .05x, with no way to increase pointer speed and response. A reboot to any other 2.6.0-test version, and the mouse immediately returns to normal fast, smooth operation.

Any ideas as to why and how to fix this- it's a show stopper for me?

wrc1944
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

Martin · Posted: Fri Oct 31, 2003 1:01 am Post subject:

Has anyone else installed test9-mm1 to confirm whether this is a general problem?

wrc1944, I'll give it a shot tonight at home...

wrc1944 · Posted: Fri Oct 31, 2003 2:04 am Post subject:

Thanks Martin,
Every time I try to post to:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&group=linux.kernel

to try and get feedback on my testing experiences, it fails.

I always get moderated out. I'm certainly an amateur, but I only post serious relevant problems, about mm patches, or vanilla. Many other oops get posted, but if test9-mm1 fails with PS/2 mice, that seems like a major problem for the masses. However, vanilla test9 works fine. What's the trick about getting posted on the kernel google group?

Anyway, I'd like to know if anybody else has this problem occur.

wrc1944
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

Martin · Posted: Fri Oct 31, 2003 2:32 am Post subject:

wrc1944, I've compiled test9-mm1 and am having the same problems with the PS/2 mouse (in my case an Intellimouse Explorer).

We shall see...

Martin · Posted: Fri Oct 31, 2003 2:39 am Post subject:

wrc: Did you set a custom resolution in the Input Device Drivers > Mouse section?

manywele · l33t Joined: 12 Jul 2003 Posts: 739 Location: Inside

I just booted into test9-mm1 and the PS/2 mouse is fine (just a cheap memorex optical scroll mouse).

dill1 · n00b Joined: 29 Oct 2002 Posts: 3

I had the same problem with ps2 and test9-mm1. I tried using the xset command from "xset m 5 2" to "xset m 25 2" and it does speed up the pointer quite a bit but it was still way to difficult to use properly. The solution for me was to switch to a usb mouse.
Apparently this is not a bug but a measure to keep from using default values for some reason. It showed up in bk2 I think. It definitely breaks ps2 mouse functionality even with custom values. Something needs fixin'.

ba747heavy · Posted: Fri Oct 31, 2003 3:45 am Post subject:

Damn, at least it isn't me. I am really pissed off now, because I really like test9-mm1, except for this effing mouse :evil:

_________________
Fred Clausen
"leet [speak] is a cry for help from a shallow mind" - Doomwookie Jan 05

nanoczar · Posted: Fri Oct 31, 2003 6:25 am Post subject:

I am using a Logitech PS/2 mouse and found the 2.6-test9-mm1 kernel to give the same result. Upon reading dill1's comment about "xset m 5 2" I tried "xset m 3 2"...and my mouse seems to be working as it did under the previously released test kernels. Note: I am using XFCE4 if that makes any difference...
_________________
Don't fight the LaTeX. WORK with the LaTeX!! Become one with the LaTeX!!! - JIC

shakti · Guru Joined: 15 May 2002 Posts: 358 Location: omnipresent

with a gyromouse pro ps/2 works fine under 2.6.0-test9-mm1
_________________
Using Gentoo since 2002.

yodermk · Posted: Fri Oct 31, 2003 7:00 am Post subject:

Same here, with a Logitech PS/2 + wheel.

I could be wrong, but I think it's overall less responsive, like when I Ctrl-Tab between virtual screens, than test8mm1.

lucida · Apprentice Joined: 20 Feb 2003 Posts: 191

2 mice here, logitech trackball on PS/2 and MS IE3 on USB. Both work fine with test9-mm1.

Elm0 · Apprentice Joined: 24 Nov 2002 Posts: 281 Location: UK

My mouse, standard ps/2 MS mouse into a KT600 based board, completely haywire and really hard to use. Shame, this 2.6 kernel had been completely stable for me up till now! I'm sure mm2 will be out soon to fix this.

wrc1944 · Posted: Fri Oct 31, 2003 6:15 pm Post subject:

No, I didn't set any custom mouse resolution- just used my test9 vanilla config when I did an mm1. Judging from the comments on this, it seems to be a random thing. I'm using an el cheapo Belkin generic scroll mouse, and it works fine with all the other test kernels. I think I read test-10 will be out before an mm2, so I guess I'll just use vanilla test-9 for now.

wrc1944
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

Rhino · Apprentice Joined: 12 Feb 2003 Posts: 177

it was one pre-fix that was merged by linus, and the real fix is on line waiting.

for now just save this patch and issue a patch -p1 -R -i /path/to/the/patch

IvoryTiger · Tux's lil' helper Joined: 27 Jun 2002 Posts: 132

love-sources-beta9-r1

Patch is also included in the new love-sources according to Lovechild.
_________________
--
For those about to compile...we salute you!

wrc1944 · Posted: Sat Nov 01, 2003 5:22 pm Post subject:

The patch posted above wouldn't apply to test9-mm1. I followed the directions, but it failed at line 4. Tried -p0 instead of -p1, but same result. When you save the patch as a text file, what are you supposed to name it? In fact, I looked at the patch, and the relevant lines, and it appears that the mm1 version already had the changes that the patch was supposed to correct. Very curious.

Anyway, I couldn't figure out what was wrong, so I downloaded test9-love1, and applied it to test9. That, and all mm patches always apply fine. Then I compiled, and have the same ps/2 mouse problems with love1 as with mm1. I compared the two psmouse-base.c files with xxdiff, and they are identical, so the failure is to be expected, I suppose.

I then decided to simply replace the mm1 psmouse-base.c file in mm1 with the one in vanilla test9 that works. The compile went fine until the end of make modules, where it errors out, as below:

drivers/built-in.o(.text+0xc26cc): In function `psmouse_disconnect':
: undefined reference to `synaptics_disconnect'
drivers/built-in.o(.text+0xc271f): In function `psmouse_pm_callback':
: undefined reference to `synaptics_disconnect'
drivers/built-in.o(.text+0xc2757): In function `psmouse_pm_callback':
: undefined reference to `synaptics_pt_init'
drivers/built-in.o(.text+0xc295d): In function `psmouse_connect':
: undefined reference to `synaptics_pt_init'
make: *** [.tmp_vmlinux1] Error 1
wrc@mymachine linux-2.6.0-test9 $

I'm open to any ideas, and am wondering if anyone else has these problems with love1, and finally, how exactly does one apply this patch? I must be doing something wrong, but I have no problems with other patches.

wrc1944
_________________
Main box- AsRock x370 Gaming K4
Ryzen 7 3700x, 3.6GHz, 16GB GSkill Flare DDR4 3200mhz
Samsung SATA 1000GB, Radeon HD R7 350 2GB DDR5
OpenRC Gentoo ~amd64 plasma, glibc-2.36-r7, gcc-13.2.1_p20230304
kernel-6.8.4 USE=experimental python3_11

Elm0 · Apprentice Joined: 24 Nov 2002 Posts: 281 Location: UK

Hold on for mm2 and revert to a previous kernel version imo; mm2 will be today tommorow, because this is such a huge bug.

prometheus0815 · Posted: Mon Nov 03, 2003 1:21 am Post subject:

On my Asus notebook, the Synaptics touchpad is addressed as a PS/2 device as well (as far as I know). Under 2.6.0-test9-mm1 and XFree 4.3.0, the touchpad and a Logitech optical notebook wheel mouse on USB are working fine. Only during the first seconds of a new X session, the cursor jumps a little (!), but nothing to worry about.

This is the relevant part of my XF86Config:

flav2000 · Posted: Mon Nov 03, 2003 2:10 am Post subject:

I have the same problem with my mouse.

I use Toshiba Tecra S1 laptop. It works fine with the 2.6.0-test6-mm1 sources but with test9-mm1 the touchpad is unusable. Interesting thing is that the Accupoint/joystick thingy is not affected.

I'm waiting for the fix in mm2.

Deepu Sudhakar · Tux's lil' helper Joined: 30 Aug 2003 Posts: 84

I'm so glad I found this tpic because I was having the same problem. For now, I set the mouse resolution in XF86Config to a higher value.

invaderzim · Posted: Wed Nov 05, 2003 3:56 pm Post subject:

Broke mine too. I had set a custom resolution, and after unsetting it, it still didnt work. How long till MM2? I didnt see any mention of this error in the fixmes

Elm0 · Apprentice Joined: 24 Nov 2002 Posts: 281 Location: UK

test9-mm2 is still broken for me (sigh) maybe no one filed a bug report for this?

invaderzim · Posted: Wed Nov 05, 2003 4:13 pm Post subject:

Gar! I dont see how this would happen so late in the game.

Torvalds did it!

thats from 2.6.0-test9-bk10.log at

http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.0-test9-bk10.log

ChangeSet@1.1370, 2003-10-27 11:52:49-08:00, torvalds@home.osdl.org
Don't force PS/2 mouse rate or resolution by default.

Only set the rate/resolution if the user actually asked
for it. Some mice and KVM switches don't like to have
their rate forced.

/me will attempt to undo his 'fix'

invaderzim · Posted: Thu Nov 06, 2003 12:00 am Post subject:

i fixed the mouse in mm2.

save this as daPatch

[code]
--- drivers/input/mouse/psmouse-base.c 2003-11-05 19:33:12.000000000 -0500
+++ /usr/src/linux/drivers/input/mouse/psmouse-base.c 2003-11-05 12:50:12.000000000 -0500
@@ -40,7 +40,7 @@

static int psmouse_noext;
int psmouse_resolution;
-unsigned int psmouse_rate;
+unsigned int psmouse_rate=60;
int psmouse_smartscroll = PSMOUSE_LOGITECH_SMARTSCROLL;
unsigned int psmouse_resetafter;

@@ -466,14 +466,16 @@
* We set the mouse report rate.
*/

- if (psmouse_rate)
+
+
+// if (psmouse_rate)
psmouse_set_rate(psmouse);

/*
* We also set the resolution and scaling.
*/

- if (psmouse_resolution)
+// if (psmouse_resolution)
psmouse_set_resolution(psmouse);

psmouse_command(psmouse, NULL, PSMOUSE_CMD_SETSCALE11);
@@ -706,17 +708,17 @@
return 1;
}

-static int __init psmouse_rate_setup(char *str)
-{
- get_option(&str, &psmouse_rate);
- return 1;
-}
+//static int __init psmouse_rate_setup(char *str)
+//{
+// get_option(&str, &psmouse_rate);
+// return 1;
+//}

__setup("psmouse_noext", psmouse_noext_setup);
__setup("psmouse_resolution=", psmouse_resolution_setup);
__setup("psmouse_smartscroll=", psmouse_smartscroll_setup);
__setup("psmouse_resetafter=", psmouse_resetafter_setup);
-__setup("psmouse_rate=", psmouse_rate_setup);
+//__setup("psmouse_rate=", psmouse_rate_setup);

#endif
[code]

cd /usr/src/linux/
cat /path/to/daPatch |patch -Np0

and done!

my comp has never felt better. i was on 2.4.20-ck6 forever. but i guess i really wont know till i have sound anyway!undefined