4992 2013-08-07 17:05:21 +0000 Mouse unusable on NUC 2013-10-21 13:19:28 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-intel unspecified NUC Multiple VERIFIED FIXED Medium+ normal 1.5 M4 1 bluelightning nitin.a.kamble dvhart ionutx.chisanovici ross.burton tom.zanussi --- --- No (bug/feature does not impact docs) oldest_to_newest 35466 0 bluelightning 2013-08-07 17:05:21 +0000 With a fairly standard Logitech USB mouse, if it is plugged into the NUC during boot it is powered off and non-functional by the time X starts up. Unplugging it and plugging it back in makes it work, but after 3 seconds of inactivity it powers off and stops working. I strongly suspect this has to do with USB auto-suspend; the problem though is there doesn't seem to be any way of waking it up other than re-plugging, which is somewhat impractical. 35467 1 nitin.a.kamble 2013-08-07 17:24:47 +0000 Paul, You are right about this being a USB suspend issue. FYI, key press on keyboard wakes up the mouse. There is also a kernel parameter to disable USB suspend to overcome the issue, if you need that let me know. But IMO this needs further investigation, to understand why is it happening. 35470 2 bluelightning 2013-08-07 17:50:07 +0000 If I press keys on the keyboard it does not wake up the mouse. The way I have things currently plugged in (mostly by chance) I have the keyboard plugged into the front port and the mouse into one of the ones on the rear, so at first I thought that maybe this was because the front and rear ports were on separate hubs. However, lsusb -t seems to show that this is not the case. 35473 3 ross.burton 2013-08-07 18:32:08 +0000 I note that meta-nuc turns on autosuspend globally for all devices via a kernel parameter. I'm pretty sure this isn't encouraged by upstream (as it's not default) and they're taking the approach of whitelisting devices that *do* suspend or letting people with known working configurations turn it on globally on a case-by-case basis. (I've got a ThinkPad USB keyboard/trackpoint, and when it suspends only keyboard input wakes it, and that takes ~one second to actually wake fully) 35492 4 dvhart 2013-08-08 14:39:32 +0000 Nitin, could you please have a look at this today or tomorrow? 35509 5 nitin.a.kamble 2013-08-08 17:19:21 +0000 Darren, ok, I will to some poking here. I think this is not NUC specific. Possibly the generic kernel config meta data in v3.8 kernel repo. Nitin 35514 6 nitin.a.kamble 2013-08-08 17:59:32 +0000 I think a udev rules like this should solve the issue. I will be testing it out soon. SUBSYSTEM=="input", ACTION=="add", ATTR{power/control}="on" 35524 7 nitin.a.kamble 2013-08-09 00:57:06 +0000 A fix sent to linux-yocto mailing list. 35529 8 ross.burton 2013-08-09 09:12:42 +0000 So my thought that autosuspend was globally enabled on NUC was incorrect, it's globally enabled on atom-pc (which is why I was seeing on my NUC occasionally). I'll send a patch to fix that too. 35548 9 nitin.a.kamble 2013-08-09 15:09:39 +0000 The linux-yocto-3.8 kernel repo is updated to change the kernel config for Intel BSPs. Now all Intel BSPs using linux-yocto-3.8 kernel need to update the commit of their meta branch, which will solve the issue. I will be doing this for bunch of BSPs from meta-intel layer. Rest of the Intel BSPs need to be updated by their maintainers. Thanks, Nitin 35596 10 nitin.a.kamble 2013-08-13 03:20:24 +0000 commit a6b7129fa25bf295a5b0f6ae5fd3f28ef04974ad Author: Nitin A Kamble <nitin.a.kamble@intel.com> Date: Fri Aug 9 17:14:58 2013 +0000 nuc:linux-yocto-3.8: update meta branch srcrev This fixes USB autosuspend issues related to non-responsive mice & keyboards. Fixes bug: [YOCTO #4992] Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com> 38108 11 ionutx.chisanovici 2013-10-21 13:19:28 +0000 Verified, usb mouse and keyboard are working normally without interruptions on NUC, mouse is working/functional after minutes of inactivity.