From: Greg KH <gregkh@linuxfoundation.org>
To: John Travell <john@travell.uk.net>
Cc: linux-usb@vger.kernel.org
Subject: Re: USB keyboard and mouse non responsive at login
Date: Fri, 5 Apr 2019 06:49:04 +0200 [thread overview]
Message-ID: <20190405044904.GA553@kroah.com> (raw)
In-Reply-To: <a8c6d4e9-29c5-73cc-ca9d-8c973a5876ac@travell.uk.net>
On Thu, Apr 04, 2019 at 10:16:36PM +0100, John Travell wrote:
> Summary: USB keyboard and mouse non responsive at login
> Product: Drivers
> Version: 2.5
> Kernel Version: 3.13.0-166-generic
> Kernel Version: 3.13.0-167-generic
> Kernel Version: 3.13.0-168-generic
3.13 was released back in January of 2014, if you are stuck on this old,
obsolete kernel version, please contact the company you are paying for
support for this, as they are the only ones that can provide this (and
you are paying for it, so use that!)
good luck,
greg k-h
next parent reply other threads:[~2019-04-05 4:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a8c6d4e9-29c5-73cc-ca9d-8c973a5876ac@travell.uk.net>
2019-04-05 4:49 ` Greg KH [this message]
2019-04-05 8:38 ` USB keyboard and mouse non responsive at login John Travell
2019-04-05 9:19 ` Greg KH
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=20190405044904.GA553@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=john@travell.uk.net \
--cc=linux-usb@vger.kernel.org \
/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).