From: "Justin P. Mattock" <justinmattock@gmail.com>
To: linux-bluetooth@vger.kernel.org
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: magicmouse: claimed by neither input, hiddev nor hidraw
Date: Mon, 10 May 2010 14:08:24 -0700 [thread overview]
Message-ID: <4BE875C8.8050202@gmail.com> (raw)
In-Reply-To: <j2idd18b0c31005101341o43b652c1zf8729f5f9a60e0d3@mail.gmail.com>
On 05/10/2010 01:41 PM, Justin Mattock wrote:
> is it me, or is there something wrong
> with the magicmouse connecting
> i.g. I've had my system setup to use the
> magicmouse with 2.6.33* with no issues
> now coming back after sometime
> seems everything is connecting,but then no movement:
> (and some thing in dmesg):
> [ 116.267993] magicmouse 0005:05AC:030D.0007: claimed by neither
> input, hiddev nor hidraw
> [ 116.268053] magicmouse 0005:05AC:030D.0007: magicmouse hw start failed
>
> using osx magicmouse connects fine.
> Using standard mightymouse everything connects.
> are there any reports of such things?
>
>
nevermind.. my bad, ended up not
having hiddraw enabled in the kernel.
everything looks good, suspend etc..
Justin P. Mattock
next prev parent reply other threads:[~2010-05-10 21:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 20:41 magicmouse: claimed by neither input, hiddev nor hidraw Justin Mattock
2010-05-10 21:08 ` Justin P. Mattock [this message]
2010-05-10 21:34 ` Jiri Kosina
2010-05-10 21:39 ` Justin Mattock
2010-05-10 21:52 ` Jiri Kosina
2010-05-10 22:15 ` Justin P. Mattock
2010-05-11 2:28 ` Michael Poole
2010-05-11 2:45 ` Justin P. Mattock
2010-05-11 2:58 ` Justin P. Mattock
2010-05-11 7:47 ` Jiri Kosina
2010-05-11 7:56 ` Justin P. Mattock
2010-05-11 8:01 ` Justin P. Mattock
2010-05-11 14:26 ` Justin P. Mattock
2010-05-11 16:32 ` Justin P. Mattock
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=4BE875C8.8050202@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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).