99% percent sure that this change won't break
>>> anything.
>> It is even correct: A mouse isn't required to be able to jump straight
>> into the Explorer mode, it is supposed to always go through the
>> IntelliMouse mode.
>
> Any takers to test this change with yo
t;> mouse works great.
>>
>> I think that this change is quite safe to make in FreeBSD, because with
>> Linux user-base we can be 99% percent sure that this change won't break
>> anything.
>
> It is even correct: A mouse isn't required to be able to jum
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Krzysztof
> Parzyszek
> Sent: Wednesday, February 21, 2001 1:47 PM
> To: Matt Heckaman
> Cc: FreeBSD-STABLE
> Subject: Re: PS/2 mouse problem solved
>
>
> On Wed, Feb 2
connection to the device so you know it is properly connected.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tyler McGeorge
Sent: Wednesday, February 21, 2001 5:04 PM
To: Matt Heckaman; Krzysztof Parzyszek
Cc: FreeBSD-STABLE
Subject: Re: PS/2 mouse problem
Last time I forgot to say that I was getting those ``psmintr out of sync''
messages. Now, I set flags 0x100 for the psm0 device and everything
runs just fine (with the KVM switch).
Thank you everyone who responded to me the first time.
--
,oOo.Bc -=EEKrzysztof Parzyszek <[EMAIL PROTECTED]
4 5
Buttons 3
EndSection
I allso installed de imwheel port.
In the kernel configuration i have:
---
# atkbdc0 controls both the keyboard and the PS/2 mouse
device atkbdc0 at isa? port IO_KBD
device atkbd0
use"
Option "Protocol""Auto"
Option "Device" "/dev/sysmouse"
Option "Buttons" "5"
Option "ZAxisMapping" "4 5"
EndSection
the above makes the mouse wheel work as well.
[EMAIL PROTECTED]> wr
I tried to hook a PS/2 mouse (IntelliMouse) to my FreeBSD box and I couldn't
make it work with X 4.0.2. I did some experimenting and I can't quite
remember particular symptoms with different configurations, but problems
included:
- X server not starting at all (no core pointer)
ENTRY macro was defined to be an incorrect value. This
value changes with my patch in any case, so I haven't included a
separate fix.
Those who know something about PS/2 mouse packets will notice that I am
not using the overflow bits in my synchronisation check. It seems that
overflow can occur
nd using /dev/psm0 for X simply froze the mouse --
>>although switching to another console and back seemed to work.
>
>Would you please provide the following information.
>
>1. The model of your Logitech PS/2 mouse.
MouseMan Serial-MousePort Model M-CQ38
>2. When booting the syste
gh switching to another console and back seemed to work.
Would you please provide the following information.
1. The model of your Logitech PS/2 mouse.
2. When booting the system, give "boot -v" at the loader prompt
to obtain verbose messages, and send us /var/log/dmesg.boot.
3. Run `mouse
On Sun, 12 Dec 1999, Alvin Jiang wrote:
>Hmm, I just solved this problem last night. It took me all of 5 mins to
>search "psmintr" and find the solution at:
>
>http://www.freebsd.org/FAQ/x.html#AEN2255
>
>You'd probably save a lot of time if you read the FAQ, rather than post and
>wait for a repl
12 matches
Mail list logo
