Date: Tue, 24 Oct 2000 23:15:04 -0500 From: "Scott Milliken" <scott@e-comsultant.net> To: <stable@freebsd.org> Subject: moused problem in 4.0-STABLE Message-ID: <003401c03e3a$27290980$97a635d0@stripsearch.net>
index | next in thread | raw e-mail
[-- Attachment #1 --]
Hello,
I upgraded to 4.1.1 from 4.1 this past weekend and now have a problem
with the moused daemon. As long as I don't attempt to start it up,
everything else seems to be fine. None of my hardware has changed, only the
standard CVSUP of source, make world (in single user mode), mergemaster and
a reboot. If I try to leave in the line 'moused_enable="YES"' in my
/etc/rc.conf they system will lock up to the point of forcing a power reset.
Removing that lines lets the boot continue on as normal. Just to verify it
wasn't some other strange thing, I also booted up with the moused disabled
and manually ran it as:
moused -p /dev/cuaa0 -t auto
and my system again locked up.
I'm using a Logitech TrackMan (serial) device on /dev/cuaa0, same as
always. dmesg tells me that sio0 was found, so that should be fine. (see
below)
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1: configured irq 3 not in bitmap of probed irqs 0
If I reboot using the old 4.1 kernel (from Aug 25 2000) I get the same
dmesg output, but moused actually works. If there's any other information
that I need to supply, please let me know. Just in case, I've attached the
full dmesg output from the 4.1.1 boot.
Thanks,
Scott Milliken
[-- Attachment #2 --]
аЯрЁБс >