On Sun, 8 Dec 2002, Sam Halliday wrote: >*** err [mice.c(1876)]: imps2: PS/2 mouse failed to read id, assuming standard PS/2 >*** err [mice.c(1876)]: imps2: PS/2 mouse failed to read id, assuming standard PS/2 >*** err [mice.c(1882)]: imps2: PS/2 mouse failed setup, continuing... >sometimes when i restart gpm i get >*** err [mice.c(1891)]: imps2: Auto-detected unknown mouse type 250, assuming standard PS/2 >*** err [mice.c(1891)]: imps2: Auto-detected unknown mouse type 250, assuming standard PS/2 250 is PS2 ack. The problem is, that the input and the output is not in sync. >but the mouse doesnt work correctly Because the mouse is successfuly changed to 4 byte wheel mode, but parsed with 3 byte normal ps2 mode. >is this a known problem? and do you have any temporary fixes for it? You can try restart gpm. gpm -k (don't move the mouse) and then gpm start again. Another way to workaround is maybe use netmouse "driver". gpm -t imps2 gpm -k gpm -t netmouse Since netmouse uses always the wheel modified version of ps2. The first will put the mouse in 4 byte mode, and netmouse use it regardless detected or not. (this may not work) I had the same problem also. I've made a patch also, but not yet accepted. You can find it in the archive. Should help. Btw, please next specify the mouse type also. I think it is more relevant as the X version. (There are many mouse that comp. with imps2) Cheers, -- Cserveny Tamas A só olyan fűszer, ami minden olyan ételt elront, amiből hiányzik.