linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kenneth Crudup <kenny@panix.com>
To: haiyang kang <cornsea@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-laptop@vger.kernel.org
Subject: Re: sometimes kernel cannot detect GlidePoint input Device
Date: Sat, 11 Jul 2009 21:02:30 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0907112100480.9685@hp9800.localdomain> (raw)
In-Reply-To: <62c294d80907112005n6458193dye48d5bd3203d50f4@mail.gmail.com>


I had this problem once; try putting

  i8042.noloop=1

... in your kernel command line.

	-Kenny

-- 
Kenneth R. Crudup  Sr. SW Engineer, Scott County Consulting, Los Angeles
O: 3630 S. Sepulveda Blvd. #138, L.A., CA 90034-6809      (888) 454-8181

      reply	other threads:[~2009-07-12  4:02 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-12  3:05 sometimes kernel cannot detect GlidePoint input Device haiyang kang
2009-07-12  4:02 ` Kenneth Crudup [this message]

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=Pine.LNX.4.64.0907112100480.9685@hp9800.localdomain \
    --to=kenny@panix.com \
    --cc=cornsea@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-laptop@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).