linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stian Jordet <liste@jordet.nu>
To: Vojtech Pavlik <vojtech@suse.cz>
Cc: linux-kernel@vger.kernel.org, Thomas Molina <tmolina@cox.net>
Subject: Re: Mouse/Keyboard problems with 2.5.38
Date: 08 Oct 2002 19:14:19 +0200	[thread overview]
Message-ID: <1034097327.902.8.camel@chevrolet> (raw)
In-Reply-To: <20021008085842.A4412@ucw.cz>

tir, 2002-10-08 kl. 08:58 skrev Vojtech Pavlik:
> 
> > But now I decided I should try again. I got 2.5.38 booted after some
> > initial trouble. But, I have a couple of weird problems. First, the
> > mouse. I have a Logitech Cordless Optical mouse. With kernel 2.4.x I use
> > MouseManPlusPS/2 as the XFree mouse-driver. Then I can use the wheel and
> > the fourth button just as expected. But with kernel 2.5.38 neither the
> > wheel or the fourth button works. I change protocol to IMPS/2 in XFree,
> > and everything works like expected, but the fourth button works just
> > like pussing the wheel (third button). This is excactly the same
> > behavior as with 2.4.20-pre7 (that's why I use MouseManPlusPS/2). Anyone
> > have a clue why this doesn't work with kernel 2.5.38?
> 
> Does it work when you use "ExplorerPS/2" instead?

Uhm, you answered that 26th september, and I replied the same day.Yes,
it works perfect now :)
 
> > Second problem, if I press SHIFT+PAGEUP, my computer freezes. It spits
> > out this message: "input: AT Set 2 keyboard on isa0060/serio0, and then
> > it's dead. I have a Logitech cordless keyboard. 
> 
> It should be fixed in 2.5.39 or 2.5.40. Does it work fine on 2.5.41?

It does not. I'll answer your other mail instead :)

Best regards,
Stian Jordet


       reply	other threads:[~2002-10-08 17:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20021008085842.A4412@ucw.cz>
2002-10-08 17:14 ` Stian Jordet [this message]
2002-10-08 17:23   ` Mouse/Keyboard problems with 2.5.38 Vojtech Pavlik
2002-09-25 23:31 Stian Jordet
2002-09-25 23:47 ` Brad Hards
2002-09-26  8:58 ` Vojtech Pavlik
2002-09-26 11:32   ` Stian Jordet
2002-09-26 11:37     ` Vojtech Pavlik
2002-09-26 15:30       ` Stian Jordet
2002-09-26 16:57         ` Vojtech Pavlik
2002-09-26 22:50           ` Stian Jordet
2002-09-27  7:10             ` Vojtech Pavlik
2002-09-27 11:51               ` Stian Jordet
2002-10-07 13:00                 ` Vojtech Pavlik
2002-10-07 19:55                   ` Stian Jordet
2002-10-07 20:01                     ` Vojtech Pavlik
2002-10-08  0:20                       ` Stian Jordet
2002-10-08  8:17                         ` Vojtech Pavlik
2002-10-08 17:18                           ` Stian Jordet
2002-10-08 17:25                             ` Vojtech Pavlik
2002-10-08 23:48                               ` Stian Jordet
     [not found]                                 ` <20021009082215.C1890@ucw.cz>
2002-10-09 10:42                                   ` Stian Jordet
2002-10-09  0:54                               ` Stian Jordet
2002-09-30 22:10               ` Stian Jordet

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=1034097327.902.8.camel@chevrolet \
    --to=liste@jordet.nu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cox.net \
    --cc=vojtech@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).