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). -- Jiri Kosina SUSE Labs, Novell Inc. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
