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'

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.

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

Closing as unreproducible.

This is back and the cleanall of the various input recipes doesn't fix it for me.

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.

Edwin,

Saul doesn't have FRI 2 device.
Can you help to have a look at this and test with our FRI 2?

Shane

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?

I'll try that image when I'm back in PDX. Moving to NEEDINFO rather than RESOLVED.

.

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.