From: Dave Jones <davej@suse.de>
To: Nathan <wfilardo@fuse.net>
Cc: Greg KH <greg@kroah.com>, lkml <linux-kernel@vger.kernel.org>,
vojtech@suse.cz
Subject: Re: Issues with 2.5.3-dj1
Date: Sun, 3 Feb 2002 15:02:50 +0100 [thread overview]
Message-ID: <20020203150250.A24149@suse.de> (raw)
In-Reply-To: <3C5B5EC0.40503@fuse.net> <20020202055115.GA11359@kroah.com> <3C5B8C0D.8090009@fuse.net> <20020202133358.A5738@suse.de> <3C5C8CA2.9000103@fuse.net> <20020203062124.GA15134@kroah.com> <3C5CD8FD.6@fuse.net>
In-Reply-To: <3C5CD8FD.6@fuse.net>; from wfilardo@fuse.net on Sun, Feb 03, 2002 at 01:30:21AM -0500
On Sun, Feb 03, 2002 at 01:30:21AM -0500, Nathan wrote:
> >>w/ Greg's USB driverfs patch : system proves to be stable.
> >> (though 2.5.3 sometimes looses my keyboard after a time?)
> >Is this a USB keyboard? Are there any kernel log messages?
> It's a regular AT keyboard... no, there are no kernel log messages
> dumped to the screen and I highly doubt any captured to any file because
> the only way out is to power down the system. Searching kern.log, all I
> see is hotplug add NAME=AT commands, which is nothing unusual. This
> "losing" only seems to happen after 2.5.2-dj6 (did not try -dj7).
>
> But even 2.5.2-dj6 will lose my mouse... or rather, it will never see it
> to begin with. It's a regular, bland, boring PS/2 mouse.
Strange. If you only see this in my tree (and not vanilla 2.5.x),
then this is Vojtech's input changes. Probably some more twiddling
needed to get it perfect.
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
next prev parent reply other threads:[~2002-02-03 14:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 3:36 Issues with 2.5.3-dj1 Nathan
2002-02-02 5:51 ` Greg KH
2002-02-02 6:49 ` Nathan
2002-02-02 12:33 ` Dave Jones
2002-02-03 1:04 ` Nathan
2002-02-03 6:21 ` Greg KH
2002-02-03 6:30 ` Nathan
2002-02-03 14:02 ` Dave Jones [this message]
2002-02-03 15:05 ` Vojtech Pavlik
2002-02-02 11:19 ` Allan Sandfeld
-- strict thread matches above, loose matches on Subject: below --
2002-02-02 13:36 Andreas Happe
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=20020203150250.A24149@suse.de \
--to=davej@suse.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vojtech@suse.cz \
--cc=wfilardo@fuse.net \
/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