From: Honza Pazdziora <adelton@informatics.muni.cz>
To: adevries@engsoc.carleton.ca (Alex deVries)
Cc: linux@cthulhu.engr.sgi.com
Subject: Mouse support in 2.1.100-2
Date: Fri, 17 Jul 1998 10:09:43 +0200 (MET DST) [thread overview]
Message-ID: <199807170809.KAA26176@aisa.fi.muni.cz> (raw)
In-Reply-To: <Pine.LNX.3.95.980717012901.5792D-100000@lager.engsoc.carleton.ca> from Alex deVries at "Jul 17, 98 01:32:29 am"
> > - mouse doesn't work?
>
> In the HH install, there's a package called 'kernel-2.1.100-2'. If you
> install this, you'll have something like /boot/vmlinux-2.1.100. That
> kernel (2.1.100) should have mouse support in it. you'll have to make a
> symbolic link from /dev/psaux to /dev/mouse.
I'm using the new kernel but am confused about the devices. Should I have
psaux (10/1) and mouse -> psaux ?
Here gpm fails with
gpm: /dev/mouse: Operation not supported by device
and the same message I get then I do cat /dev/psaux.
Or
mouse (4/64) and psaux -> mouse ?
Here gpm starts without a problem but no running cursor on the screen.
Yours,
------------------------------------------------------------------------
Honza Pazdziora | adelton@fi.muni.cz | http://www.fi.muni.cz/~adelton/
I can take or leave it if I please
------------------------------------------------------------------------
WARNING: multiple messages have this Message-ID (diff)
From: Honza Pazdziora <adelton@informatics.muni.cz>
To: Alex deVries <adevries@engsoc.carleton.ca>
Cc: linux@cthulhu.engr.sgi.com
Subject: Mouse support in 2.1.100-2
Date: Fri, 17 Jul 1998 10:09:43 +0200 (MET DST) [thread overview]
Message-ID: <199807170809.KAA26176@aisa.fi.muni.cz> (raw)
Message-ID: <19980717080943.XgiooTpgcEgmXxBIQNY8nGrxwpUirT7-VBLsFTvZXQo@z> (raw)
In-Reply-To: <Pine.LNX.3.95.980717012901.5792D-100000@lager.engsoc.carleton.ca> from Alex deVries at "Jul 17, 98 01:32:29 am"
> > - mouse doesn't work?
>
> In the HH install, there's a package called 'kernel-2.1.100-2'. If you
> install this, you'll have something like /boot/vmlinux-2.1.100. That
> kernel (2.1.100) should have mouse support in it. you'll have to make a
> symbolic link from /dev/psaux to /dev/mouse.
I'm using the new kernel but am confused about the devices. Should I have
psaux (10/1) and mouse -> psaux ?
Here gpm fails with
gpm: /dev/mouse: Operation not supported by device
and the same message I get then I do cat /dev/psaux.
Or
mouse (4/64) and psaux -> mouse ?
Here gpm starts without a problem but no running cursor on the screen.
Yours,
------------------------------------------------------------------------
Honza Pazdziora | adelton@fi.muni.cz | http://www.fi.muni.cz/~adelton/
I can take or leave it if I please
------------------------------------------------------------------------
next prev parent reply other threads:[~1998-07-17 8:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-07-16 18:53 apache and other problems (fwd) Ariel Faigon
1998-07-16 18:53 ` Ariel Faigon
1998-07-17 5:32 ` Alex deVries
1998-07-17 8:09 ` Honza Pazdziora [this message]
1998-07-17 8:09 ` Mouse support in 2.1.100-2 Honza Pazdziora
1998-07-17 8:23 ` apache and other problems (fwd) Francis M. J. Hsieh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199807170809.KAA26176@aisa.fi.muni.cz \
--to=adelton@informatics.muni.cz \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.engr.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox