3294 2012-10-17 15:40:07 +0000 [FRI2] Keyboard not detected 2013-05-01 06:38:45 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-meta-intel 1.3 Other Multiple VERIFIED INVALID Low normal 1.5 1 alexandrux.palalau dvhart tom.zanussi --- --- --- oldest_to_newest 26683 0 alexandrux.palalau 2012-10-17 15:40:07 +0000 Branch danny Poky Commit ID: c9de24d3f4845251b01e2eab0aeeb7472badc5bb meta-intel Commit ID: 5d8a05811101f7d69994f4028ec620c4480f6da4 Core-image-sato-sdk from http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20121011-1/ fails to detect keyboard. Mouse is fully functional. The same poky commit, core-image-sato-sdk from http://autobuilder03.jf.intel.com/pub/nightly-meta-intel/20121010-2/ does not present the keyboard issue. 26684 1 dvhart 2012-10-17 15:55:50 +0000 Is this the live image? Does the keyboard work in Syslinux? Does the keyboard work in GRUB? You mentioned in IM that it didn't work on the console nor in X. Does the num-lock key work? If none of the above work, please try inserting a USB 2.0 Hub into the host usb port on the FRI2 and connecting the keyboard to the hub. Does it work then? Which firmware are you using? The Kontron supplied BIOS or the Intel provided Fastboot UEFI firmware? 26685 2 dvhart 2012-10-17 15:57:26 +0000 Do you know the meta-intel commit of the image that did work? 26793 3 alexandrux.palalau 2012-10-22 12:27:40 +0000 Live and installed image, the same behavior is encountered. In Grub, the keyboard is functional. During Yocto boot, the NumLock key becomes non functional. Also tried inserting the keyboard directly into the usb/micro usb or usb hub but I get the same result. I set up the DHCP connection via connman and I was able to SSH into the FRI2. No dmesg errors other than the PowerButton one. I was able to get some logs from the moment when the keyboard was disconnected: usb 2-1.2: USB disconnect, device number 4 usb 8-1: new low-speed USB device number 2 using ohci_hcd input: Dell Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:1a.0/0000:04:00.0/0000:05:08.2/usb8/8-1/8-1:1.0/input/input4 generic-usb 0003:413C:2107.0003: input: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-0000:05:08.2-1/input0 Disconnecting both keyboard and mouse and reconnect: usb 8-1: USB disconnect, device number 2 generic-usb 0003:0461:4D81.0002: can't reset device, 0000:05:08.3-1.3/input0, status -71 generic-usb 0003:0461:4D81.0002: can't reset device, 0000:05:08.3-1.3/input0, status -71 generic-usb 0003:0461:4D81.0002: can't reset device, 0000:05:08.3-1.3/input0, status -71 generic-usb 0003:0461:4D81.0002: can't reset device, 0000:05:08.3-1.3/input0, status -71 usb 2-1.3: USB disconnect, device number 5 usb 8-1: new low-speed USB device number 3 using ohci_hcd input: USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/0000:04:00.0/0000:05:08.2/usb8/8-1/8-1:1.0/input/input5 generic-usb 0003:0461:4D81.0004: input: USB HID v1.11 Mouse [USB Optical Mouse] on usb-0000:05:08.2-1/input0 usb 2-1.3: new low-speed USB device number 8 using ehci_hcd input: Dell Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:1a.0/0000:04:00.0/0000:05:08.3/usb2/2-1/2-1.3/2-1.3:1.0/input/input6 generic-usb 0003:413C:2107.0005: input: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-0000:05:08.3-1.3/input0 The meta-intel commit ID is the same for both images: 5d8a05811101f7d69994f4028ec620c4480f6da4 on danny branch. Hope this helps. Hope this helps. 26910 4 dvhart 2012-10-25 14:59:29 +0000 This is mostly resolved in version 1018, but the keyboard is still not detected on reset (is fine on power cycle). 30423 5 dvhart 2013-03-05 00:41:20 +0000 This is not something the Yocto Project team can do anything about. I have reported to the firmware team and they will have to track the issue independently. 32513 6 alexandrux.palalau 2013-04-23 08:56:10 +0000 Well, seems that the same issue returns under dylan branch, commit ID:789b2b7e0cca404ff8ba8ed5ba823d215e6ba5b4 Meta-intel commit ID: 76f70c337e5daa9593153dfdf5107aec08610a44 Under GRUB everything works fine, but as soon as Yocto boots, the keyboard becomes inactive. Not the same about the mouse, which works fine. The reboot doesn't solve the issue. dmesg shows that the keyboard is detected. Apr 19 03:26:11 fri2 user.info kernel: usb 8-1: USB disconnect, device number 4 Apr 19 03:26:15 fri2 user.info kernel: usb 8-1: new low-speed USB device number 5 using ohci_hcd Apr 19 03:26:15 fri2 user.info kernel: input: Dell Dell USB Entry Keyboard as /devices/pci0000:00/0000:00:1a.0/0000:04:00.0/0000:05:08.2/usb8/8-1/8-1:1.0/input/input6 Apr 19 03:26:15 fri2 user.info kernel: hid-generic 0003:413C:2107.0005: input: USB HID v1.10 Keyboard [Dell Dell USB Entry Keyboard] on usb-0000:05:08.2-1/input0 32527 7 alexandrux.palalau 2013-04-23 13:20:34 +0000 Starting under runlevel 3, keyboard works fine. 32532 8 dvhart 2013-04-23 14:26:19 +0000 How are the mouse and keyboard connected to the FRI2? 32536 9 alexandrux.palalau 2013-04-23 15:04:19 +0000 USB Hub or USB direct connecion for both mouse and keyboard provide the same result. 32538 10 dvhart 2013-04-23 15:31:39 +0000 It was reported above as being only after reset. Does this now happen at power-on too, or just after reset? Can you check the permissions of /dev/input/* ? 32539 11 dvhart 2013-04-23 15:32:02 +0000 Reopening 32540 12 dvhart 2013-04-23 15:32:13 +0000 . 32541 13 alexandrux.palalau 2013-04-23 15:41:14 +0000 Also at first boot. I could'n make the keyboard to function in any way. Tried with different keyboards. root@fri2:~# ls -la /dev/input/* crw-rw---- 1 root input 13, 63 Apr 2 12:49 /dev/input/mice crw-rw---- 1 root input 13, 32 Apr 2 12:49 /dev/input/mouse0 /dev/input/by-id: total 0 drwxr-xr-x 2 root root 60 Apr 2 12:49 . drwxr-xr-x 4 root root 120 Apr 2 12:49 .. lrwxrwxrwx 1 root root 9 Apr 2 12:49 usb-0461_USB_Optical_Mouse-mouse -> ../mouse0 /dev/input/by-path: total 0 drwxr-xr-x 2 root root 60 Apr 2 12:49 . drwxr-xr-x 4 root root 120 Apr 2 12:49 .. lrwxrwxrwx 1 root root 9 Apr 2 12:49 pci-0000:05:08.3-usb-0:1.3:1.0-mouse -> ../mouse0 32542 14 dvhart 2013-04-23 16:00:58 +0000 (In reply to comment #13) > Also at first boot. > I could'n make the keyboard to function in any way. > Tried with different keyboards. > > root@fri2:~# ls -la /dev/input/* > crw-rw---- 1 root input 13, 63 Apr 2 12:49 /dev/input/mice > crw-rw---- 1 root input 13, 32 Apr 2 12:49 /dev/input/mouse0 > Is that really everything in /dev/input? no event0, event1, etc. ? (Please allow the requester of information to reset the NEEDINFO state) 32544 15 alexandrux.palalau 2013-04-23 16:39:56 +0000 Nothing else in /dev/input other than the provided output. On freshly installed image, the output of "ls -la /dev/input/*" is the same. 32545 16 dvhart 2013-04-23 16:44:26 +0000 This is either a major USB fail (firmware or OS) or something is misconfigured in the kernel or udev. The kernel could be FRI2 specific, udev should not be, firmware is. Have you seen anything like this on other BSPs? Can you look in /proc/config.gz for the INPUT configs? $ zcat /proc/config.gz | grep INPUT and paste the output here? 32557 17 dvhart 2013-04-23 21:47:49 +0000 Are you testing in both the console and X, or just in X? It works for me on the conosle. About to test X. 32558 18 dvhart 2013-04-23 22:00:42 +0000 I've verified this works in X as well for me. Do you have another device you can test? At this point I'm going to chalk this up to a bad device unless you can demonstrate this failure on more than one FRI2 of the same revision with the same firmware image. 32753 19 alexandrux.palalau 2013-04-30 07:25:31 +0000 Well, this seems to be due to HW issues. Tested right now on other FRI2 BSP and the behavior did not reproduce. root@fri2:~# ls -la /dev/input/ total 0 drwxr-xr-x 4 root root 120 Jan 1 2001 . drwxr-xr-x 14 root root 13360 Apr 28 00:07 .. drwxr-xr-x 2 root root 60 Jan 1 2001 by-id drwxr-xr-x 2 root root 60 Jan 1 2001 by-path crw-rw---- 1 root input 13, 63 Jan 1 2001 mice crw-rw---- 1 root input 13, 32 Jan 1 2001 mouse0 root@fri2:~# zcat /proc/config.gz |grep INPUT CONFIG_INPUT=y # CONFIG_INPUT_FF_MEMLESS is not set # CONFIG_INPUT_POLLDEV is not set # CONFIG_INPUT_SPARSEKMAP is not set # CONFIG_INPUT_MATRIXKMAP is not set CONFIG_INPUT_MOUSEDEV=y CONFIG_INPUT_MOUSEDEV_PSAUX=y CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024 CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768 # CONFIG_INPUT_JOYDEV is not set # CONFIG_INPUT_EVDEV is not set # CONFIG_INPUT_EVBUG is not set CONFIG_INPUT_KEYBOARD=y CONFIG_INPUT_MOUSE=y # CONFIG_INPUT_JOYSTICK is not set # CONFIG_INPUT_TABLET is not set # CONFIG_INPUT_TOUCHSCREEN is not set # CONFIG_INPUT_MISC is not set # CONFIG_SND_HDA_INPUT_BEEP is not set # CONFIG_SND_HDA_INPUT_JACK is not set Thank you for your patience. 32780 20 dvhart 2013-04-30 18:21:26 +0000 I believe this to be a firmware issue, they are actively working on it. Closing as there is nothing we can do for it in the kernel. 32802 21 alexandrux.palalau 2013-05-01 06:38:20 +0000 Most probably, will keep up an eye for any firmware updates. 32803 22 alexandrux.palalau 2013-05-01 06:38:45 +0000 Switching to verified