On Tue, 13 Apr 2004, Pigeon wrote:

> On Tue, Apr 13, 2004 at 09:46:26AM -0500, James Miller wrote:
> > On Tue, 13 Apr 2004, Ralph Crongeyer wrote:
> >
> > > In /etc/modules add the line:
> > >
> > > psmouse
> > >
> > > Then restart X.
> >
> > Unfortunately this did not change anything.  Even after putting the entry
> > psmouse in the file /etc/modules, the mouse cursor remains frozen when the
> > computer gets into gui mode.  It does not respond to anything I do with
> > the physical mouse.  Incidentally, gpm also does not work in the console
> > (i.e., no cursor appears when I move the mouse around, as it does when I
> > am in a console when using the 2.4.25 kernel).  Perhaps I need to
> > uncomment the generic mouse entry in XF86Config-4 again?  I don't really
> > see how that could apply though, since it's not a USB mouse (unless my
> > understanding of the generic mouse stanza as referring to USB mice is
> > mistaken).
>
> Adding the line to /etc/modules is right, but it won't do anything
> until you reboot. But you don't need to reboot just to get it working,
> because you can load it by hand:
>
> # modprobe psmouse

Ok.  I see I should have mentioned that I rebooted.  It still didn't work.
Nor did manually modprobing it work (I didn't think it would if rebboting
after editing /etc/modules failed, but I thought I should try it anyway).
I also modprobed mousedev, which similarly didn't help.  Only when I ran
across something telling me to look at the output from cat
/proc/bus/input/devices did I begin to make any progress.  That output
told me the mouse was at /dev/input/mouse0, and when I entered that under
the Generic Mouse stanza of XF86Config-4, I got a working mouse cursor
under X.  But gpm is not working (i.e., no cursor appears in console mode
when I move the mouse, as it should), and I'm not sure why.  Neither do I
have a console beep - another mystery.  Anyone have input on getting gpm
and the console beep working under the 2.6.4 kernel?

Thanks, James


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to