Date: Wed, 09 Jan 2008 22:30:55 +0200 From: Toomas Aas <toomas.aas@raad.tartu.ee> To: Kris Kennaway <kris@FreeBSD.org> Cc: freebsd-stable@freebsd.org, Wayne Sierke <ws@au.dyndns.ws> Subject: Re: 6.3-PRERELEASE desktop system periodically freezes momentarily Message-ID: <47852EFF.8000103@raad.tartu.ee> In-Reply-To: <4785186E.4070609@FreeBSD.org> References: <1199812249.96494.133.camel@predator-ii.buffyverse> <4783C8A8.2090705@raad.tartu.ee> <4783D41B.3000204@FreeBSD.org> <4783D748.1050401@raad.tartu.ee> <4783D824.1050502@FreeBSD.org> <4783DB72.6030605@raad.tartu.ee> <4783DCAA.1080108@FreeBSD.org> <47851247.1020306@raad.tartu.ee> <4785186E.4070609@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Kris Kennaway wrote: > Toomas Aas wrote: >> >> # grep psm /var/run/dmesg.boot >> psm0: <PS/2 Mouse> irq 12 on atkbdc0 >> psm0: [GIANT-LOCKED] >> psm0: model IntelliMouse, device ID 3 >> > > There was another report of problems with psm. Can you try with > sysmouse instead? If that works around the issue then we can > investigate psm further. Sorry, but I'm not sure I understand how to use sysmouse instead of psm. Do you mean I should run 'moused -p /dev/sysmouse' (setting moused_port="/dev/sysmouse" in rc.conf)? If I do that, the mouse refuses to move. When I add more options: #/usr/sbin/moused -p /dev/sysmouse -t ps/2 -d -f moused: mouse type mismatch (mousesystems != ps/2, mousesystems is assumed) moused: proto params: f8 80 00 00 5 00 ff moused: port: /dev/sysmouse interface: sysmouse type: mousesystems model: generic moused: received char 0x87 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: received char 0x0 moused: assembled full packet (len 5) 87,0,0,0,0,0,0,0 -- Toomas Aas ... Why is it called tourist season if we can't shoot at them?
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47852EFF.8000103>