Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!paladin.american.edu!gatech!newsfeed.internetmci.com!uwm.edu!fnnews.fnal.gov!unixhub!news.Stanford.EDU!not-for-mail
From: ritchief@cmgm.stanford.edu (Ritchie Froehlich)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: PS/2 mouse config on a laptop
Date: 21 Apr 1996 02:27:38 -0700
Organization: Stanford University, CA 94305, USA
Lines: 64
Message-ID: <4lcv2a$r1a@cmgm.stanford.edu>
References: <4l23jn$lvq@cmgm.stanford.edu> <LARSON.96Apr17120353@hydra2b.cs.utk.edu> <4latat$2ne@news.mainelink.net>
NNTP-Posting-Host: cmgm.stanford.edu
In article <4latat$2ne@news.mainelink.net>,
Lord Chameleon <Lord_Chameleon@onf.com> wrote:
>larson@cs.utk.edu (Chris Larson) wrote:
>>In article <4l23jn$lvq@cmgm.stanford.edu> ritchief@cmgm writes:
>>:>After loading the kernel in the configuration mode (/kernel -c), I
>>:>looked for a PS/2 mouse in the list of dirvers.
>>:>[random guessing deleted]
>
>>Is this a kernel that you have compiled or the one that came with the
>>distribution? PS/2 mouse support is not available until you recompile
>>and add the PS/2 driver to the kernel. Then it should work fine.
Actually, it was the GENERIC kernel off the cd-rom. I've since recompiled
the kernel with the PS/2 mouse device enabled (via the line in the hand-
book and several e-mail messages; to all who responded, thanks for the help)
>what is the command you put in kernel for a ps/2 style mouse
Glad you asked :
# psm: PS/2 mouse port [note: conflicts with sc0/vt0, thus "conflicts" keywd]
device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr
I'm still having problems, though. On boot-up I get this message :
psm0 at 0x60-0x63 IRQ 12 on the motherboard
and indeed crwxrwxrwx /dev/psm0 and lrwxr-xr-x /dev/mouse->mouse exist.
However, when I startx with either the MouseMan or Logitech pointers
configured in /usr/X11R6/lib/X11/XF86Config, the following warning is
issued :
Warning: unable to get statuse of mouse fd (invalid argument).
So... making an random guess I figured that either the device or the mode
is fubared in the call to mouse_fd = open("/dev/{mouse/psm0}",???) in
startx (actually xinit?). When I use the MouseMan protocol, X windows
seems to get some sort of mouse input, but the cursor likes to stay at
the top of the display and random mouse button events cause various menus
to pop up and text to be highlighted.
Any ideas ?
BTW, I think I did a "sh MAKEDEV mouse" after building the psm0
enabled kernel. I didn't bother to check to see if the device was
there or not.
>>:>mouse without going into X (I'm getting really tired of rebooting).
I've since learned that <cntl>-<alt>-<Fn> switch between virt. terms.
I have noticed that if I switch between virt. terms when X is starting,
I somtimes don't return to X Windows, but rather end up looking at the
startup diag. messages X printed to the tty.
Also, I'm still interested in ways to use/test the mouse without starting
X. When I added the psm0 device to the kernel, I noticed it too a really
long time to rebuild and install (about 1.5 hrs on a 486 33). At first,
I thougth that it was because this was the first time I'de built a new
kernel; however, on successive builds, the amount of time required was
roughly the same. Does a 1 line change in the kernel config really
necessitate a complete rebuild or am I missing a critical point here?
Thanks (in advance) for any help that might be out there...