1859 2011-12-22 00:40:28 +0000 [fri2] No keyboard or mouse in X for core-image-sato 2012-02-22 14:16:52 +0000 1 1 7 Build System, Metadata & Runtime BSPs bsps-configuration 1.2 x86 Multiple RESOLVED WORKSFORME High critical 1.2 M3 1 dvhart edwin.zhai shane.wang yp.bsp.watcher yp.watcher --- --- --- oldest_to_newest 17818 0 dvhart 2011-12-22 00:40:28 +0000 OE Build Configuration: BB_VERSION = "1.15.0" TARGET_ARCH = "i586" TARGET_OS = "linux" MACHINE = "fri2-noemgd" DISTRO = "poky" DISTRO_VERSION = "1.1+snapshot-20111222" TUNE_FEATURES = "m32 core2" TARGET_FPU = "" meta meta-yocto = "master:4648aadfe161d2e0ec51408f35fdf8996727bd22" meta-intel meta-fri2 = "tzanussi/libva-glx-rootfs-fix-4:97e00bc6db2e3f2be4222c836e4c5d446e88d0d5" X starts, but the keyboard and mouse do not respond. The fri version appears to be working. The fri2-noemgd xorg.conf follows: Section "Device" Identifier "Generic VESA" Driver "vesa" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Generic VESA" Monitor "Generic Monitor" DefaultDepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" EndSection Section "ServerFlags" Option "DontZap" "0" Option "AutoAddDevices" "False" EndSection 18080 1 dvhart 2012-01-11 13:28:04 +0000 Xorg.0.log complains about a module ABI mismatch for the mouse and kbd drivers. [3465994.854] (II) Module mouse: vendor="X.Org Foundation" [3465994.855] compiled for 1.9.3, module version = 1.7.1 [3465994.855] Module class: X.Org XInput Driver [3465994.855] ABI class: X.Org XInput driver, version 11.0 [3465994.855] (EE) module ABI major version (11) doesn't match the server's version (13) [3465994.855] (II) UnloadModule: "mouse" [3465994.855] (II) Unloading mouse [3465994.855] (EE) Failed to load module "mouse" (module requirement mismatch, 0) [3465994.855] (EE) No input driver matching `mouse' [3465994.855] (II) LoadModule: "kbd" [3465994.855] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so [3465994.855] (II) Module kbd: vendor="X.Org Foundation" [3465994.855] compiled for 1.9.3, module version = 1.6.0 [3465994.855] Module class: X.Org XInput Driver [3465994.856] ABI class: X.Org XInput driver, version 11.0 [3465994.856] (EE) module ABI major version (11) doesn't match the server's version (13) [3465994.856] (II) UnloadModule: "kbd" [3465994.856] (II) Unloading kbd [3465994.856] (EE) Failed to load module "kbd" (module requirement mismatch, 0) [3465994.856] (EE) No input driver matching `kbd' 18084 2 dvhart 2012-01-11 14:07:51 +0000 Saul, this does not appear to be an fri2 issue, but rather a build issue where stale sstate was used for the xf86-input drivers. I've assigned this to you to either close as is, or hand off to someone to investigate further. It's certainly possible that things have changed enough that nobody will hit this again with sstate generated from now on, so I'm not sure how much more time we should spend on this. 18088 3 dvhart 2012-01-11 15:53:42 +0000 Forgot to include the following which I posted to the wrong bug earlier: This was apparently due to using stale sstate for the xf86-input packages. Running the following generated a functional image: $ bitbake -c cleanall xf86-input-evdev xf86-input-keyboard xf86-input-mouse xf86-input-synaptics $ bitbake core-image-sato 18276 4 dvhart 2012-01-19 15:14:18 +0000 Closing as unreproducible. 18476 5 dvhart 2012-02-03 11:17:26 +0000 This is back and the cleanall of the various input recipes doesn't fix it for me. 18477 6 dvhart 2012-02-03 11:18:25 +0000 Now the emgd driver is ABI 8 and server is 11, the kbd and mouse are still 11 vs 13 on the server. So this is fri2 and fri2-noemgd. 18540 7 shane.wang 2012-02-07 16:49:32 +0000 Edwin, Saul doesn't have FRI 2 device. Can you help to have a look at this and test with our FRI 2? Shane 18559 8 edwin.zhai 2012-02-08 23:43:17 +0000 Yilong and I tried latest fri2-noemgd/emgd from autobuilder, keyboard and mouse works well. http://autobuilder03.jf.intel.com/pub/fri2-noemgd/20120131-1/machines/fri2-noemgd/core-image-sato-fri2-noemgd.hddimg Darren, Can you test it on your machine, and verify it if works for you? 18566 9 dvhart 2012-02-09 05:55:13 +0000 I'll try that image when I'm back in PDX. Moving to NEEDINFO rather than RESOLVED. 18567 10 dvhart 2012-02-09 05:55:28 +0000 . 18706 11 dvhart 2012-02-22 14:16:52 +0000 I tested a clean build today on M2 hardware and X doesn't start, ends with a black screen and a white _ in the upper left. Can't switch VTs. I can ssh in, and the Xorg.log ends with: [2801368.384] (II) EMGD(0): Chipset: "Intel Atom E6xx Processor" [2801368.384] (II) EMGD(0): Kernel and userspace drivers are incompatible: [2801368.384] (II) EMGD(0): - Kernel: ddkbuild=0, release build [2801368.384] (II) EMGD(0): - Userspace: ddkbuild=3226, release build [2801368.384] (**) EMGD(0): Option "ConfigID" "1" But no complaints about version mismatch in the input modules. Running X manually results in: X: symbol lookup error: /usr/lib/xorg/modules/drivers/emgd_drv.so: undefined symbol: EDID_bin_read This is another bug. I'm going to close this one out and chalk it up wreakage in my local build system. I'll open a new bug for the above.