Re: magicmouse: claimed by neither input, hiddev nor hidraw

["Justin P. Mattock" <justinmattock@gmail.com>]

On 05/10/2010 02:52 PM, Jiri Kosina wrote:
> On Mon, 10 May 2010, Justin Mattock wrote:
>
>>>> 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?
>>>
>>> Adding Michael Poole to CC.
>>>
>>> No, I haven't seen any such reports. First -- could you please provide
>>> complete dmesg?
>>
>> everything seems to be working o.k. now, just had to enable HIDRAW=y
>> maybe something changed to where I needed this(I remember never really
>> using hidraw, just HIDDEV(but could be wrong)).
>
> This sounds a bit strange.
>
> hidraw shouldn't be making too much difference in the case you describe.
> hidraw is basically just a mean of relaying HID events to userspace so
> that any driver/application in userspace can access them. But magicmouse
> driver is written completely in kernelspace.
>
> Does anything on your system have /dev/hidraw* nodes open? (you could
> check by lsof).
>


right now I see
/dev/hidraw0,1,2,3

./lsof | grep /dev
(showing bluetooth)

bluetooth 2020   root    0u      CHR                1,3       0t0 2551 
/dev/null
bluetooth 2020   root    1u      CHR                1,3       0t0 2551 
/dev/null
bluetooth 2020   root    2u      CHR                1,3       0t0 2551 
/dev/null
bluetooth 2020   root   14u      CHR              10,62       0t0 3895 
/dev/rfkill

I can try a bisect on this and see.


Justin P. Mattock