Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!agate!remarque.berkeley.edu!cuccia
From: cuccia@remarque.berkeley.edu (Nick Cuccia)
Newsgroups: comp.os.386bsd.questions
Subject: Re: [NetBSD] problems with Logitech Busmouse
Date: 3 Sep 1993 03:41:48 GMT
Organization: Bump City Brewery and Barbecue, Berkeley, CA
Lines: 34
Message-ID: <266eds$2g1@agate.berkeley.edu>
References: <262pa0$1md@agate.berkeley.edu> <MYCROFT.93Sep2030728@trinity.gnu.ai.mit.edu>
NNTP-Posting-Host: remarque.berkeley.edu
In article <MYCROFT.93Sep2030728@trinity.gnu.ai.mit.edu>,
Charles Hannum <mycroft@trinity.gnu.ai.mit.edu> wrote:
>
>In article <262pa0$1md@agate.berkeley.edu>
>cuccia@remarque.berkeley.edu (Nick Cuccia) writes:
>
> Busmouse "/dev/mse0"
>
>Huh? Did you import this driver yourself? The Logitech driver that
>comes in 0.9 is called `lms', and works fine at least on my machine.
An artifact from when my system was running 386BSD 0.1 patches. Kept the
old name but updated the major number. However....
> The mouse responds fine. But when I type anything in one of the
> windows, nothing echos or happens until I move the mouse.
>
>This is a symptom of an ancient bug in the kernel select() interface
>that was fixed even before NetBSD 0.8.
...while I updated the major number of my old device name to match the
current device (36), I used the old minor number (0), which corresponds to
the blocking version of the current driver. Changing the minor number to
1 fixed the problem. I'm typing this from a tip from one of my xterms
right now.
I was right. It was something stoopid.
--Nick
--
===============================================================================
Nick Cuccia
cuccia@talamasca.berkeley.ca.us cuccia@remarque.berkeley.edu
===============================================================================