Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

All of lore.kernel.org
 help / color / mirror / Atom feed

* Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
@ 2013-04-08  8:42 Andreas Enbacka
  2013-04-08  9:18 ` Burton, Ross
  0 siblings, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-08  8:42 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 2076 bytes --]

Hello,

I have experienced some problems with getting the USB mouse and keyboard
detected in the default core-image-sato Yocto image, built for the Intel
Emenlow machine (with emgd graphics). X launches successfully to the Sato
desktop, but I get no response from the mouse or keyboard. When I from
terminal execute grep -i mouse /var/log/Xorg.0.log from terminal, I get the
following output:

root@emenlow:~# grep -i mouse /var/log/Xorg.0.log

        Using the default mouse configuration.

[3572708.190] (II) LoadModule: "mouse"

[3572708.191] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so

[3572708.195] (II) Module mouse: vendor="X.Org Foundation"

[3572708.196] (II) UnloadModule: "mouse"

[3572708.196] (II) Unloading /usr/lib/xorg/modules/input/mouse_drv.so

[3572708.196] (EE) Failed to load module "mouse" (module requirement
mismatch, 0)

[3572711.516] (==) EMGD(0): Silken mouse enabled

[3572713.120] (II) LoadModule: "mouse"

[3572713.121] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so

[3572713.121] (II) Module mouse: vendor="X.Org Foundation"

[3572713.127] (II) UnloadModule: "mouse"

[3572713.127] (II) Unloading /usr/lib/xorg/modules/input/mouse_drv.so

[3572713.127] (EE) Failed to load module "mouse" (module requirement
mismatch, 0)

[3572713.127] (EE) No input driver matching `mouse'

[3572713.486] (II) config/udev: Adding input device DIALOGUE INC PenMount
USB (/dev/input/mouse0)

root@emenlow:~#

The DIALOGUE INC PenMount USB is the USB mouse (touchscreen) that I am
using. Keyboard works correctly in terminal (with US keyboard layout), but
not in X. I have tried set "AutoAddDevices" to False/True in
/etc/X11/xorg.conf, but with no success. Also, cat /dev/input/mouse0 does
produce output in terminal when moving the USB mouse.

Any information concerning what could be the source of this problem would be
greatly appreciated, and in case additional information is required I will
happily provide it. 

Best regards,

Andreas Enbacka

[-- Attachment #2: Type: text/html, Size: 5521 bytes --]

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08  8:42 Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow) Andreas Enbacka
@ 2013-04-08  9:18 ` Burton, Ross
  2013-04-08  9:50   ` Andreas Enbacka
  0 siblings, 1 reply; 16+ messages in thread
From: Burton, Ross @ 2013-04-08  9:18 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

On 8 April 2013 09:42, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I have experienced some problems with getting the USB mouse and keyboard
> detected in the default core-image-sato Yocto image, built for the Intel
> Emenlow machine (with emgd graphics). X launches successfully to the Sato
> desktop, but I get no response from the mouse or keyboard. When I from
> terminal execute grep -i mouse /var/log/Xorg.0.log from terminal, I get the
> following output:

Attaching the entire X log instead of grepping for phrases that you
think are relevant would be more useful - in this case the module that
X should be using for USB input is "evdev", not "mouse".  Check that
you've got the xorg evdev driver present and that the server is
loading the module.  It's possible that the permissions are wrong on
the input nodes in /dev/input.

Oh, and what version of Poky  / oe-core were you using - 1.3 or master?

Ross

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08  9:18 ` Burton, Ross
@ 2013-04-08  9:50   ` Andreas Enbacka
  2013-04-08 10:34     ` Burton, Ross
  0 siblings, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-08  9:50 UTC (permalink / raw)
  To: 'Burton, Ross'; +Cc: yocto

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

Ross,

Thanks for your reply, very much appreciated. I am currently using Poky master. I have attached the complete Xorg.0.log; it does not contain any mentions of evdev, only mouse, which would imply that evdev does not get loaded of some reason. 

//Andreas

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 8. huhtikuuta 2013 12:18
To: Andreas Enbacka
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

On 8 April 2013 09:42, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I have experienced some problems with getting the USB mouse and 
> keyboard detected in the default core-image-sato Yocto image, built 
> for the Intel Emenlow machine (with emgd graphics). X launches 
> successfully to the Sato desktop, but I get no response from the mouse 
> or keyboard. When I from terminal execute grep -i mouse 
> /var/log/Xorg.0.log from terminal, I get the following output:

Attaching the entire X log instead of grepping for phrases that you think are relevant would be more useful - in this case the module that X should be using for USB input is "evdev", not "mouse".  Check that you've got the xorg evdev driver present and that the server is loading the module.  It's possible that the permissions are wrong on the input nodes in /dev/input.

Oh, and what version of Poky  / oe-core were you using - 1.3 or master?

Ross

[-- Attachment #2: Xorg.0.log --]
[-- Type: application/octet-stream, Size: 38421 bytes --]

[3901747.965] 
X.Org X Server 1.9.3
Release Date: 2010-12-13
[3901747.971] X Protocol Version 11, Revision 0
[3901747.974] Build Operating System: Linux 3.5.0-17-generic i686 
[3901747.974] Current Operating System: Linux emenlow 3.4.28-yocto-standard #1 SMP PREEMPT Mon Mar 4 05:30:53 EST 2013 i686
[3901747.975] Kernel command line: reboot=pci initrd=/initrd LABEL=boot root=/dev/ram0 video=vesafb vga=0x318 vmalloc=256MB BOOT_IMAGE=/vmlinuz 
[3901747.977] Build Date: 05 March 2013  07:44:54AM
[3901747.980]  
[3901747.980] Current version of pixman: 0.29.2
[3901747.980] 	Before reporting problems, check http://wiki.x.org
	to make sure that you have the latest version.
[3901747.981] Markers: (--) probed, (**) from config file, (==) default setting,
	(++) from command line, (!!) notice, (II) informational,
	(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[3901747.988] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Apr  8 07:33:00 2013
[3901747.993] (==) Using config file: "/etc/X11/xorg.conf"
[3901747.995] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[3901748.003] (==) ServerLayout "Default Layout"
[3901748.003] (**) |-->Screen "Screen0" (0)
[3901748.003] (**) |   |-->Monitor "<default monitor>"
[3901748.004] (**) |   |-->Device "IntelEMGD-0"
[3901748.004] (==) No monitor specified for screen "Screen0".
	Using a default monitor configuration.
[3901748.004] (**) Option "DontZap" "0"
[3901748.004] (**) Option "AutoAddDevices" "False"
[3901748.009] (**) Not automatically adding devices
[3901748.009] (==) Automatically enabling devices
[3901748.018] (WW) The directory "/usr/share/fonts/X11/misc/" does not exist.
[3901748.018] 	Entry deleted from font path.
[3901748.018] (WW) The directory "/usr/share/fonts/X11/TTF/" does not exist.
[3901748.018] 	Entry deleted from font path.
[3901748.018] (WW) The directory "/usr/share/fonts/X11/OTF/" does not exist.
[3901748.018] 	Entry deleted from font path.
[3901748.018] (WW) The directory "/usr/share/fonts/X11/Type1/" does not exist.
[3901748.018] 	Entry deleted from font path.
[3901748.019] (WW) The directory "/usr/share/fonts/X11/100dpi/" does not exist.
[3901748.019] 	Entry deleted from font path.
[3901748.019] (WW) The directory "/usr/share/fonts/X11/75dpi/" does not exist.
[3901748.019] 	Entry deleted from font path.
[3901748.019] (==) FontPath set to:
	
[3901748.019] (==) ModulePath set to "/usr/lib/xorg/modules"
[3901748.019] (==) |-->Input Device "<default pointer>"
[3901748.019] (==) |-->Input Device "<default keyboard>"
[3901748.019] (==) The core pointer device wasn't specified explicitly in the layout.
	Using the default mouse configuration.
[3901748.019] (==) The core keyboard device wasn't specified explicitly in the layout.
	Using the default keyboard configuration.
[3901748.019] (II) Loader magic: 0x8212080
[3901748.019] (II) Module ABI versions:
[3901748.019] 	X.Org ANSI C Emulation: 0.4
[3901748.019] 	X.Org Video Driver: 8.0
[3901748.019] 	X.Org XInput driver : 11.0
[3901748.019] 	X.Org Server Extension : 4.0
[3901748.033] (--) PCI:*(0:0:2:0) 8086:8108:8100:8086 rev 7, Mem @ 0xfdf00000/524288, 0xd0000000/268435456, 0xfdf80000/262144, I/O @ 0x0000ff00/8
[3901748.039] (II) Open ACPI successful (/var/run/acpid.socket)
[3901748.039] (II) LoadModule: "extmod"
[3901748.060] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
[3901748.073] (II) Module extmod: vendor="X.Org Foundation"
[3901748.074] 	compiled for 1.9.3, module version = 1.0.0
[3901748.074] 	Module class: X.Org Server Extension
[3901748.074] 	ABI class: X.Org Server Extension, version 4.0
[3901748.074] (II) Loading extension MIT-SCREEN-SAVER
[3901748.074] (II) Loading extension XFree86-VidModeExtension
[3901748.074] (II) Loading extension XFree86-DGA
[3901748.074] (II) Loading extension DPMS
[3901748.074] (II) Loading extension XVideo
[3901748.074] (II) Loading extension XVideo-MotionCompensation
[3901748.074] (II) Loading extension X-Resource
[3901748.074] (II) LoadModule: "dbe"
[3901748.075] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
[3901748.088] (II) Module dbe: vendor="X.Org Foundation"
[3901748.088] 	compiled for 1.9.3, module version = 1.0.0
[3901748.088] 	Module class: X.Org Server Extension
[3901748.089] 	ABI class: X.Org Server Extension, version 4.0
[3901748.089] (II) Loading extension DOUBLE-BUFFER
[3901748.089] (II) LoadModule: "glx"
[3901748.089] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[3901748.118] (II) Module glx: vendor="X.Org Foundation"
[3901748.118] 	compiled for 1.9.3, module version = 1.0.0
[3901748.118] 	ABI class: X.Org Server Extension, version 4.0
[3901748.120] (==) AIGLX enabled
[3901748.120] (II) Loading extension GLX
[3901748.121] (II) LoadModule: "dri"
[3901748.121] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
[3901748.137] (II) Module dri: vendor="X.Org Foundation"
[3901748.138] 	compiled for 1.9.3, module version = 1.0.0
[3901748.138] 	ABI class: X.Org Server Extension, version 4.0
[3901748.138] (II) Loading extension XFree86-DRI
[3901748.138] (II) LoadModule: "dri2"
[3901748.138] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
[3901748.146] (II) Module dri2: vendor="X.Org Foundation"
[3901748.146] 	compiled for 1.9.3, module version = 1.2.0
[3901748.146] 	ABI class: X.Org Server Extension, version 4.0
[3901748.146] (II) Loading extension DRI2
[3901748.146] (II) LoadModule: "emgd"
[3901748.156] (II) Loading /usr/lib/xorg/modules/drivers/emgd_drv.so
[3901748.189] (II) Module emgd: vendor="Intel(R) Corporation"
[3901748.189] 	compiled for 1.9.0, module version = 1.16.3228
[3901748.189] 	Module class: X.Org Video Driver
[3901748.190] 	ABI class: X.Org Video Driver, version 8.0
[3901748.190] (II) LoadModule: "mouse"
[3901748.191] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[3901748.203] (II) Module mouse: vendor="X.Org Foundation"
[3901748.203] 	compiled for 1.13.1, module version = 1.8.1
[3901748.203] 	Module class: X.Org XInput Driver
[3901748.203] 	ABI class: X.Org XInput driver, version 18.0
[3901748.203] (EE) module ABI major version (18) doesn't match the server's version (11)
[3901748.204] (II) UnloadModule: "mouse"
[3901748.204] (II) Unloading /usr/lib/xorg/modules/input/mouse_drv.so
[3901748.204] (EE) Failed to load module "mouse" (module requirement mismatch, 0)
[3901748.205] (II) LoadModule: "kbd"
[3901748.205] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
[3901748.208] (II) Module kbd: vendor="X.Org Foundation"
[3901748.208] 	compiled for 1.13.1, module version = 1.6.2
[3901748.208] 	Module class: X.Org XInput Driver
[3901748.209] 	ABI class: X.Org XInput driver, version 18.0
[3901748.209] (EE) module ABI major version (18) doesn't match the server's version (11)
[3901748.209] (II) UnloadModule: "kbd"
[3901748.210] (II) Unloading /usr/lib/xorg/modules/input/kbd_drv.so
[3901748.210] (EE) Failed to load module "kbd" (module requirement mismatch, 0)
[3901748.210] (II) EMGD: Intel(R) Embedded Media and Graphics Driver version 1.16.3228 for:
	Intel US15W Class
[3901748.211] (--) using VT number 2

[3901748.217] (==) EMGD(0): RGB weight 888
[3901748.217] (==) EMGD(0): Default visual is TrueColor
[3901748.217] drmOpenDevice: node name is /dev/dri/card0
[3901748.218] drmOpenDevice: open result is -1, (No such device)
[3901748.218] drmOpenDevice: open result is -1, (No such device)
[3901748.218] drmOpenDevice: Open failed
[3901748.307] drmOpenByBusid: Searching for BusID PCI:00:00:00
[3901748.307] drmOpenDevice: node name is /dev/dri/card0
[3901748.307] drmOpenDevice: open result is 11, (OK)
[3901748.307] drmOpenByBusid: drmOpenMinor returns 11
[3901748.307] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901748.308] drmOpenDevice: node name is /dev/dri/card1
[3901748.308] drmOpenDevice: open result is -1, (No such device)
[3901748.308] drmOpenDevice: open result is -1, (No such device)
[3901748.308] drmOpenDevice: Open failed
[3901748.308] drmOpenByBusid: drmOpenMinor returns -19
[3901748.308] drmOpenDevice: node name is /dev/dri/card2
[3901748.308] drmOpenDevice: open result is -1, (No such device)
[3901748.309] drmOpenDevice: open result is -1, (No such device)
[3901748.309] drmOpenDevice: Open failed
[3901748.309] drmOpenByBusid: drmOpenMinor returns -19
[3901748.309] drmOpenDevice: node name is /dev/dri/card3
[3901748.309] drmOpenDevice: open result is -1, (No such device)
[3901748.309] drmOpenDevice: open result is -1, (No such device)
[3901748.309] drmOpenDevice: Open failed
[3901748.309] drmOpenByBusid: drmOpenMinor returns -19
[3901748.310] drmOpenDevice: node name is /dev/dri/card4
[3901748.310] drmOpenDevice: open result is -1, (No such device)
[3901748.310] drmOpenDevice: open result is -1, (No such device)
[3901748.310] drmOpenDevice: Open failed
[3901748.310] drmOpenByBusid: drmOpenMinor returns -19
[3901748.310] drmOpenDevice: node name is /dev/dri/card5
[3901748.310] drmOpenDevice: open result is -1, (No such device)
[3901748.311] drmOpenDevice: open result is -1, (No such device)
[3901748.311] drmOpenDevice: Open failed
[3901748.311] drmOpenByBusid: drmOpenMinor returns -19
[3901748.311] drmOpenDevice: node name is /dev/dri/card6
[3901748.311] drmOpenDevice: open result is -1, (No such device)
[3901748.311] drmOpenDevice: open result is -1, (No such device)
[3901748.311] drmOpenDevice: Open failed
[3901748.311] drmOpenByBusid: drmOpenMinor returns -19
[3901748.311] drmOpenDevice: node name is /dev/dri/card7
[3901748.312] drmOpenDevice: open result is -1, (No such device)
[3901748.312] drmOpenDevice: open result is -1, (No such device)
[3901748.312] drmOpenDevice: Open failed
[3901748.312] drmOpenByBusid: drmOpenMinor returns -19
[3901748.312] drmOpenDevice: node name is /dev/dri/card8
[3901748.312] drmOpenDevice: open result is -1, (No such device)
[3901748.314] drmOpenDevice: open result is -1, (No such device)
[3901748.315] drmOpenDevice: Open failed
[3901748.315] drmOpenByBusid: drmOpenMinor returns -19
[3901748.315] drmOpenDevice: node name is /dev/dri/card9
[3901748.315] drmOpenDevice: open result is -1, (No such device)
[3901748.315] drmOpenDevice: open result is -1, (No such device)
[3901748.315] drmOpenDevice: Open failed
[3901748.315] drmOpenByBusid: drmOpenMinor returns -19
[3901748.315] drmOpenDevice: node name is /dev/dri/card10
[3901748.315] drmOpenDevice: open result is -1, (No such device)
[3901748.316] drmOpenDevice: open result is -1, (No such device)
[3901748.316] drmOpenDevice: Open failed
[3901748.316] drmOpenByBusid: drmOpenMinor returns -19
[3901748.316] drmOpenDevice: node name is /dev/dri/card11
[3901748.316] drmOpenDevice: open result is -1, (No such device)
[3901748.316] drmOpenDevice: open result is -1, (No such device)
[3901748.316] drmOpenDevice: Open failed
[3901748.316] drmOpenByBusid: drmOpenMinor returns -19
[3901748.317] drmOpenDevice: node name is /dev/dri/card12
[3901748.317] drmOpenDevice: open result is -1, (No such device)
[3901748.317] drmOpenDevice: open result is -1, (No such device)
[3901748.317] drmOpenDevice: Open failed
[3901748.317] drmOpenByBusid: drmOpenMinor returns -19
[3901748.317] drmOpenDevice: node name is /dev/dri/card13
[3901748.317] drmOpenDevice: open result is -1, (No such device)
[3901748.318] drmOpenDevice: open result is -1, (No such device)
[3901748.318] drmOpenDevice: Open failed
[3901748.318] drmOpenByBusid: drmOpenMinor returns -19
[3901748.318] drmOpenDevice: node name is /dev/dri/card14
[3901748.318] drmOpenDevice: open result is -1, (No such device)
[3901748.318] drmOpenDevice: open result is -1, (No such device)
[3901748.318] drmOpenDevice: Open failed
[3901748.318] drmOpenByBusid: drmOpenMinor returns -19
[3901748.323] drmOpenDevice: node name is /dev/dri/card15
[3901748.323] drmOpenDevice: open result is -1, (No such device)
[3901748.323] drmOpenDevice: open result is -1, (No such device)
[3901748.323] drmOpenDevice: Open failed
[3901748.323] drmOpenByBusid: drmOpenMinor returns -19
[3901748.323] drmOpenDevice: node name is /dev/dri/card0
[3901748.323] drmOpenDevice: open result is 11, (OK)
[3901748.324] drmOpenDevice: node name is /dev/dri/card0
[3901748.324] drmOpenDevice: open result is 11, (OK)
[3901748.324] drmGetBusid returned ''
[3901748.324] (II) EMGD(0): Chipset: "Intel SCH US15 Chipset"
[3901748.324] (II) EMGD(0): Detected kernel module from EMGD build 3228
[3901748.324] (II) EMGD(0): Checking for new style options
[3901748.325] (II) EMGD(0): Processing version 7.0 options
[3901748.325] (II) EMGD(0): Using configuration 1
[3901748.325] (II) EMGD(0): Checking for US15 specific configuration.
[3901748.325] (II) EMGD(0): Checking for non-chipset specific configuration.
[3901748.325] (II) EMGD(0): Setting port_order to 40000
[3901748.325] (II) EMGD(0): Setting Tuning WA
[3901748.325] (II) EMGD(0): Option processing done!
[3901749.170] (II) EMGD(0): Valid Display Configurations:
[3901749.170] (II) EMGD(0):   DC: 0x00000041
[3901749.170] (II) EMGD(0):   DC: 0x00200042
[3901749.170] (II) EMGD(0):   DC: 0x00200048
[3901749.170] (II) EMGD(0):   DC: 0x00000021
[3901749.170] (II) EMGD(0):   DC: 0x00000000
[3901749.272] (II) EMGD(0): Using Display Configuration 0x00000041
[3901749.272] (==) EMGD(0): Depth 24, (--) framebuffer bpp 32
[3901749.272] (==) EMGD(0): Using gamma correction (1.0, 1.0, 1.0)
[3901749.275] (II) EMGD(0): 34 modes passed validation checks
[3901749.275] (--) EMGD(0): Virtual size is 800x480 (pitch 0)
[3901749.275] (**) EMGD(0): *Built-in mode "800x480": 33.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[3901749.275] (II) EMGD(0): Modeline "800x480"x60.0   33.23  800 863 991 1055  480 500 502 524 +vsync (31.5 kHz)
[3901749.275] (**) EMGD(0):  Built-in mode "1366x768": 74.1 MHz (scaled from 0.0 MHz), 44.5 kHz, 60.0 Hz
[3901749.275] (II) EMGD(0): Modeline "1366x768"x60.0   74.06  1366 1429 1557 1663  768 768 769 775 +hsync +vsync (44.5 kHz)
[3901749.276] (**) EMGD(0):  Built-in mode "1280x1024": 108.0 MHz (scaled from 0.0 MHz), 64.0 kHz, 60.0 Hz
[3901749.276] (II) EMGD(0): Modeline "1280x1024"x60.0  108.00  1280 1327 1439 1687  1024 1024 1027 1065 +hsync +vsync (64.0 kHz)
[3901749.276] (**) EMGD(0):  Built-in mode "1280x960": 108.0 MHz (scaled from 0.0 MHz), 60.0 kHz, 60.0 Hz
[3901749.276] (II) EMGD(0): Modeline "1280x960"x60.0  108.00  1280 1375 1487 1799  960 960 963 999 +hsync +vsync (60.0 kHz)
[3901749.276] (**) EMGD(0):  Built-in mode "1280x768": 103.0 MHz (scaled from 0.0 MHz), 60.2 kHz, 75.0 Hz
[3901749.276] (II) EMGD(0): Modeline "1280x768"x75.0  102.98  1280 1359 1495 1711  768 768 771 801 +vsync (60.2 kHz)
[3901749.276] (**) EMGD(0):  Built-in mode "1280x768": 80.1 MHz (scaled from 0.0 MHz), 47.7 kHz, 60.0 Hz
[3901749.276] (II) EMGD(0): Modeline "1280x768"x60.0   80.14  1280 1343 1479 1679  768 768 771 794 +vsync (47.7 kHz)
[3901749.276] (**) EMGD(0):  Built-in mode "1280x720": 110.0 MHz (scaled from 0.0 MHz), 64.3 kHz, 85.0 Hz
[3901749.276] (II) EMGD(0): Modeline "1280x720"x85.0  110.00  1280 1359 1495 1711  720 720 723 755 +vsync (64.3 kHz)
[3901749.277] (**) EMGD(0):  Built-in mode "1280x720": 96.0 MHz (scaled from 0.0 MHz), 56.6 kHz, 75.0 Hz
[3901749.277] (II) EMGD(0): Modeline "1280x720"x75.0   96.00  1280 1351 1487 1695  720 720 723 751 +vsync (56.6 kHz)
[3901749.277] (**) EMGD(0):  Built-in mode "1280x720": 74.5 MHz (scaled from 0.0 MHz), 44.8 kHz, 60.0 Hz
[3901749.277] (II) EMGD(0): Modeline "1280x720"x60.0   74.48  1280 1335 1471 1663  720 720 723 745 +vsync (44.8 kHz)
[3901749.277] (**) EMGD(0):  Built-in mode "1152x864": 108.0 MHz (scaled from 0.0 MHz), 67.5 kHz, 75.0 Hz
[3901749.277] (II) EMGD(0): Modeline "1152x864"x75.0  108.00  1152 1215 1343 1599  864 864 867 899 +hsync +vsync (67.5 kHz)
[3901749.280] (**) EMGD(0):  Built-in mode "1152x864": 100.0 MHz (scaled from 0.0 MHz), 65.1 kHz, 72.0 Hz
[3901749.280] (II) EMGD(0): Modeline "1152x864"x72.0  100.00  1152 1223 1343 1535  864 864 867 900 +vsync (65.1 kHz)
[3901749.280] (**) EMGD(0):  Built-in mode "1152x864": 97.0 MHz (scaled from 0.0 MHz), 63.2 kHz, 70.0 Hz
[3901749.280] (II) EMGD(0): Modeline "1152x864"x70.0   97.00  1152 1223 1343 1535  864 864 867 899 +vsync (63.2 kHz)
[3901749.281] (**) EMGD(0):  Built-in mode "1152x864": 81.6 MHz (scaled from 0.0 MHz), 53.7 kHz, 60.0 Hz
[3901749.281] (II) EMGD(0): Modeline "1152x864"x60.0   81.62  1152 1215 1335 1519  864 864 867 894 +vsync (53.7 kHz)
[3901749.281] (**) EMGD(0):  Built-in mode "1024x768": 94.5 MHz (scaled from 0.0 MHz), 68.7 kHz, 85.0 Hz
[3901749.281] (II) EMGD(0): Modeline "1024x768"x85.0   94.50  1024 1071 1167 1375  768 768 771 807 +hsync +vsync (68.7 kHz)
[3901749.281] (**) EMGD(0):  Built-in mode "1024x768": 78.8 MHz (scaled from 0.0 MHz), 60.1 kHz, 75.0 Hz
[3901749.281] (II) EMGD(0): Modeline "1024x768"x75.0   78.75  1024 1039 1135 1311  768 768 771 799 +hsync +vsync (60.1 kHz)
[3901749.281] (**) EMGD(0):  Built-in mode "1024x768": 75.0 MHz (scaled from 0.0 MHz), 56.5 kHz, 70.0 Hz
[3901749.281] (II) EMGD(0): Modeline "1024x768"x70.0   75.00  1024 1047 1183 1327  768 770 776 805 (56.5 kHz)
[3901749.281] (**) EMGD(0):  Built-in mode "1024x768": 65.0 MHz (scaled from 0.0 MHz), 48.4 kHz, 60.0 Hz
[3901749.282] (II) EMGD(0): Modeline "1024x768"x60.0   65.00  1024 1047 1183 1343  768 770 776 805 (48.4 kHz)
[3901749.282] (**) EMGD(0):  Built-in mode "960x540": 40.8 MHz (scaled from 0.0 MHz), 33.6 kHz, 60.0 Hz
[3901749.282] (II) EMGD(0): Modeline "960x540"x60.0   40.78  960 991 1087 1215  540 540 543 558 +vsync (33.6 kHz)
[3901749.282] (**) EMGD(0):  Built-in mode "800x600": 84.0 MHz (scaled from 0.0 MHz), 77.2 kHz, 120.0 Hz
[3901749.282] (II) EMGD(0): Modeline "800x600"x120.0   83.95  800 855 943 1087  600 600 603 642 +vsync (77.2 kHz)
[3901749.282] (**) EMGD(0):  Built-in mode "800x600": 68.2 MHz (scaled from 0.0 MHz), 63.7 kHz, 100.0 Hz
[3901749.282] (II) EMGD(0): Modeline "800x600"x100.0   68.18  800 847 935 1071  600 600 603 635 +vsync (63.7 kHz)
[3901749.282] (**) EMGD(0):  Built-in mode "800x600": 56.2 MHz (scaled from 0.0 MHz), 53.7 kHz, 85.0 Hz
[3901749.282] (II) EMGD(0): Modeline "800x600"x85.0   56.25  800 831 895 1047  600 600 603 630 +hsync +vsync (53.7 kHz)
[3901749.299] (**) EMGD(0):  Built-in mode "800x600": 49.5 MHz (scaled from 0.0 MHz), 46.9 kHz, 75.0 Hz
[3901749.299] (II) EMGD(0): Modeline "800x600"x75.0   49.50  800 815 895 1055  600 600 603 624 +hsync +vsync (46.9 kHz)
[3901749.299] (**) EMGD(0):  Built-in mode "800x600": 50.0 MHz (scaled from 0.0 MHz), 48.1 kHz, 72.0 Hz
[3901749.299] (II) EMGD(0): Modeline "800x600"x72.0   50.00  800 855 975 1039  600 636 642 665 +hsync +vsync (48.1 kHz)
[3901749.299] (**) EMGD(0):  Built-in mode "800x600": 45.5 MHz (scaled from 0.0 MHz), 43.8 kHz, 70.0 Hz
[3901749.299] (II) EMGD(0): Modeline "800x600"x70.0   45.50  800 839 919 1039  600 600 603 624 +vsync (43.8 kHz)
[3901749.299] (**) EMGD(0):  Built-in mode "800x600": 40.0 MHz (scaled from 0.0 MHz), 37.9 kHz, 60.0 Hz
[3901749.299] (II) EMGD(0): Modeline "800x600"x60.0   40.00  800 839 967 1055  600 600 604 627 +hsync +vsync (37.9 kHz)
[3901749.299] (**) EMGD(0):  Built-in mode "720x576": 27.5 MHz (scaled from 0.0 MHz), 31.8 kHz, 50.0 Hz
[3901749.300] (II) EMGD(0): Modeline "720x576"x50.0   27.50  720 732 795 864  576 581 587 625 +vsync (31.8 kHz)
[3901749.300] (**) EMGD(0):  Built-in mode "720x480": 27.0 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[3901749.300] (II) EMGD(0): Modeline "720x480"x60.0   27.00  720 735 797 857  480 488 494 524 +vsync (31.5 kHz)
[3901749.300] (**) EMGD(0):  Built-in mode "640x480": 52.4 MHz (scaled from 0.0 MHz), 61.9 kHz, 120.0 Hz
[3901749.300] (II) EMGD(0): Modeline "640x480"x120.0   52.41  640 679 743 847  480 480 483 514 +vsync (61.9 kHz)
[3901749.300] (**) EMGD(0):  Built-in mode "640x480": 43.2 MHz (scaled from 0.0 MHz), 51.0 kHz, 100.0 Hz
[3901749.300] (II) EMGD(0): Modeline "640x480"x100.0   43.16  640 679 743 847  480 480 483 508 +vsync (51.0 kHz)
[3901749.300] (**) EMGD(0):  Built-in mode "640x480": 36.0 MHz (scaled from 0.0 MHz), 43.3 kHz, 85.0 Hz
[3901749.300] (II) EMGD(0): Modeline "640x480"x85.0   36.00  640 695 751 831  480 480 483 508 (43.3 kHz)
[3901749.329] (**) EMGD(0):  Built-in mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.5 kHz, 75.0 Hz
[3901749.329] (II) EMGD(0): Modeline "640x480"x75.0   31.50  640 655 719 839  480 480 483 499 (37.5 kHz)
[3901749.329] (**) EMGD(0):  Built-in mode "640x480": 31.5 MHz (scaled from 0.0 MHz), 37.9 kHz, 72.0 Hz
[3901749.329] (II) EMGD(0): Modeline "640x480"x72.0   31.50  640 663 703 831  480 488 491 519 (37.9 kHz)
[3901749.329] (**) EMGD(0):  Built-in mode "640x480": 28.6 MHz (scaled from 0.0 MHz), 35.0 kHz, 70.0 Hz
[3901749.329] (II) EMGD(0): Modeline "640x480"x70.0   28.56  640 663 727 815  480 480 483 499 +vsync (35.0 kHz)
[3901749.329] (**) EMGD(0):  Built-in mode "640x480": 25.2 MHz (scaled from 0.0 MHz), 31.5 kHz, 60.0 Hz
[3901749.329] (II) EMGD(0): Modeline "640x480"x60.0   25.18  640 655 751 799  480 489 491 524 (31.5 kHz)
[3901749.347] (==) EMGD(0): DPI set to (96, 96)
[3901749.347] (II) Loading sub module "fb"
[3901749.347] (II) LoadModule: "fb"
[3901749.364] (II) Loading /usr/lib/xorg/modules/libfb.so
[3901749.367] (II) Module fb: vendor="X.Org Foundation"
[3901749.367] 	compiled for 1.9.3, module version = 1.0.0
[3901749.367] 	ABI class: X.Org ANSI C Emulation, version 0.4
[3901749.367] (II) Loading sub module "ramdac"
[3901749.367] (II) LoadModule: "ramdac"
[3901749.367] (II) Module "ramdac" already built-in
[3901749.408] (II) EMGD(0): General Driver Configuration Options
[3901749.408] (II) EMGD(0):   PCF Version:            7.00
[3901749.408] (II) EMGD(0):   Configuration ID:       1
[3901749.409] (II) EMGD(0): Primary Display Configuration Options
[3901749.409] (II) EMGD(0):   VideoRam (Pixmap Cache): 32768
[3901749.409] (II) EMGD(0):   PORT AND DISPLAY OPTIONS
[3901749.409] (II) EMGD(0):     Port Order:           40000
[3901749.409] (II) EMGD(0):     Display Config:       Single
[3901749.409] (II) EMGD(0):     Display Detect:       On
[3901749.409] (II) EMGD(0):     FB Blend Overlay:     Off
[3901749.409] (II) EMGD(0):     Gang DVO:             Off
[3901749.409] (II) EMGD(0):     Refresh Rate:         0
[3901749.409] (II) EMGD(0):     Clone Width:          0
[3901749.409] (II) EMGD(0):     Clone Height:         0
[3901749.409] (II) EMGD(0):     Clone Refresh:        0
[3901749.409] (II) EMGD(0):   FRAMEBUFFER OPTIONS
[3901749.409] (II) EMGD(0):     Shadow FB:            Off
[3901749.413] (II) EMGD(0):     Tear FB:              On
[3901749.416] (II) EMGD(0):     Resize:               Off
[3901749.417] (II) EMGD(0):    GL TEXTURE STREAM OUTPUT:		Off
[3901749.417] (II) EMGD(0):   FRAMEBUFFER ORIENTATION OPTIONS
[3901749.417] (II) EMGD(0):     Rotation:             0 degrees
[3901749.417] (II) EMGD(0):     Flip:                 Off
[3901749.417] (II) EMGD(0):   HARDWARE ACCELERATION OPTIONS
[3901749.417] (II) EMGD(0):     HW 2D Accel:          On
[3901749.417] (II) EMGD(0):     HW Cursor:            On
[3901749.417] (II) EMGD(0):   XVIDEO OPTIONS
[3901749.417] (II) EMGD(0):     XVideo:               On
[3901749.417] (II) EMGD(0):     XVideoBlend:          On
[3901749.417] (II) EMGD(0):     XVideoMC:             Off
[3901749.417] (II) EMGD(0):     XVideoKey:            0xff00ff00
[3901749.417] (II) EMGD(0):     Overlay Gamma Red:    0x100
[3901749.417] (II) EMGD(0):     Overlay Gamma Green:  0x100
[3901749.417] (II) EMGD(0):     Overlay Gamma Blue:   0x100
[3901749.417] (II) EMGD(0):     Overlay Brightness:   0x8000
[3901749.418] (II) EMGD(0):     Overlay Contrast:     0x8000
[3901749.418] (II) EMGD(0):     Overlay Saturation:   0x8000
[3901749.418] (II) EMGD(0):     DRI:                  Off
[3901749.418] (II) EMGD(0):     DRI2:                 On
[3901749.418] (II) EMGD(0):     EDID:                 On
[3901749.418] (II) EMGD(0):   QUICKBOOT OPTIONS
[3901749.418] (II) EMGD(0):     QuickBoot:            1
[3901749.418] (II) EMGD(0):     Seamless:             Off
[3901749.418] (II) EMGD(0):     Video Input:          0
[3901749.418] (II) EMGD(0):     Splash Screen:        Off
[3901749.418] (II) EMGD(0):     Freeze FB:        Off
[3901749.418] (II) EMGD(0):    INTERRUPT OPTIONS
[3901749.418] (II) EMGD(0):      Polling:             Off
[3901749.418] (II) EMGD(0):   GLOBAL PER PORT OPTIONS
[3901749.418] (II) EMGD(0):   Port 2            (null)
[3901749.432] (II) EMGD(0):      Multi-DVO:      Off
[3901749.432] (II) EMGD(0):      Rotation:       0 degrees
[3901749.432] (II) EMGD(0):      Flip:           Off
[3901749.432] (II) EMGD(0):      Centering:      Off
[3901749.432] (II) EMGD(0):      RenderScale:    Off
[3901749.432] (II) EMGD(0):      EDID:           Off
[3901749.432] (II) EMGD(0):      EDID Avail:     0x5
[3901749.432] (II) EMGD(0):      EDID Not Avail: 0x5
[3901749.432] (II) EMGD(0):      PANEL INFORMATION
[3901749.432] (II) EMGD(0):         FP width:     0
[3901749.432] (II) EMGD(0):         FP height:    0
[3901749.433] (II) EMGD(0):         BKLT Enable:  0
[3901749.433] (II) EMGD(0):         BKLT Method:  0
[3901749.433] (II) EMGD(0):         BKLT T1:      0
[3901749.433] (II) EMGD(0):         BKLT T2:      0
[3901749.433] (II) EMGD(0):         BKLT T3:      0
[3901749.433] (II) EMGD(0):         BKLT T4:      0
[3901749.433] (II) EMGD(0):         BKLT T5:      0
[3901749.433] (II) EMGD(0):         GPIO Pin VDD: 0
[3901749.433] (II) EMGD(0):         GPIO Pin VEE: 0
[3901749.433] (II) EMGD(0):         GPIO Pin BKLT:0
[3901749.433] (II) EMGD(0):         DVO i2c pin:  0
[3901749.433] (II) EMGD(0):         DVO i2c DAB:  0
[3901749.433] (II) EMGD(0):         DVO i2c speed:0
[3901749.433] (II) EMGD(0):         DVO ddc pin:  0
[3901749.433] (II) EMGD(0):         DVO ddc speed:0
[3901749.433] (II) EMGD(0):      Number DTD's:   0
[3901749.433] (II) EMGD(0):      Number Attr's:  0
[3901749.434] (II) EMGD(0):   Port 4            lvds
[3901749.434] (II) EMGD(0):      Multi-DVO:      Off
[3901749.434] (II) EMGD(0):      Rotation:       0 degrees
[3901749.434] (II) EMGD(0):      Flip:           Off
[3901749.434] (II) EMGD(0):      Centering:      Off
[3901749.434] (II) EMGD(0):      RenderScale:    Off
[3901749.434] (II) EMGD(0):      EDID:           Off
[3901749.434] (II) EMGD(0):      EDID Avail:     0x3
[3901749.434] (II) EMGD(0):      EDID Not Avail: 0x1
[3901749.434] (II) EMGD(0):      PANEL INFORMATION
[3901749.434] (II) EMGD(0):         FP width:     0
[3901749.434] (II) EMGD(0):         FP height:    0
[3901749.434] (II) EMGD(0):         BKLT Enable:  0
[3901749.434] (II) EMGD(0):         BKLT Method:  0
[3901749.447] (II) EMGD(0):         BKLT T1:      0
[3901749.448] (II) EMGD(0):         BKLT T2:      0
[3901749.448] (II) EMGD(0):         BKLT T3:      0
[3901749.448] (II) EMGD(0):         BKLT T4:      0
[3901749.448] (II) EMGD(0):         BKLT T5:      0
[3901749.448] (II) EMGD(0):         GPIO Pin VDD: 0
[3901749.448] (II) EMGD(0):         GPIO Pin VEE: 0
[3901749.448] (II) EMGD(0):         GPIO Pin BKLT:0
[3901749.448] (II) EMGD(0):         DVO i2c pin:  0
[3901749.448] (II) EMGD(0):         DVO i2c DAB:  0
[3901749.448] (II) EMGD(0):         DVO i2c speed:0
[3901749.448] (II) EMGD(0):         DVO ddc pin:  0
[3901749.448] (II) EMGD(0):         DVO ddc speed:0
[3901749.448] (II) EMGD(0):      Number DTD's:   0
[3901749.448] (II) EMGD(0):      Number Attr's:  0
[3901749.448] (==) Depth 24 pixmap format is 32 bpp
[3901749.463] drmOpenDevice: node name is /dev/dri/card0
[3901749.464] drmOpenDevice: open result is 12, (OK)
[3901749.464] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901749.464] drmOpenDevice: node name is /dev/dri/card0
[3901749.464] drmOpenDevice: open result is 12, (OK)
[3901749.464] drmOpenByBusid: drmOpenMinor returns 12
[3901749.464] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901749.464] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901749.872] drmOpenDevice: node name is /dev/dri/card0
[3901749.872] drmOpenDevice: open result is 12, (OK)
[3901749.872] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901749.872] drmOpenDevice: node name is /dev/dri/card0
[3901749.872] drmOpenDevice: open result is 12, (OK)
[3901749.872] drmOpenByBusid: drmOpenMinor returns 12
[3901749.872] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901749.872] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901749.873] drmOpenDevice: node name is /dev/dri/card0
[3901749.873] drmOpenDevice: open result is 12, (OK)
[3901749.873] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901749.873] drmOpenDevice: node name is /dev/dri/card0
[3901749.873] drmOpenDevice: open result is 12, (OK)
[3901749.873] drmOpenByBusid: drmOpenMinor returns 12
[3901749.873] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901749.874] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901749.875] drmOpenDevice: node name is /dev/dri/card0
[3901749.875] drmOpenDevice: open result is 12, (OK)
[3901749.875] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901749.875] drmOpenDevice: node name is /dev/dri/card0
[3901749.875] drmOpenDevice: open result is 12, (OK)
[3901749.875] drmOpenByBusid: drmOpenMinor returns 12
[3901749.875] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901749.881] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901750.895] drmOpenDevice: node name is /dev/dri/card0
[3901750.895] drmOpenDevice: open result is 13, (OK)
[3901750.896] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901750.896] drmOpenDevice: node name is /dev/dri/card0
[3901750.896] drmOpenDevice: open result is 13, (OK)
[3901750.896] drmOpenByBusid: drmOpenMinor returns 13
[3901750.896] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901750.896] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901750.896] drmOpenDevice: node name is /dev/dri/card0
[3901750.940] drmOpenDevice: open result is 13, (OK)
[3901750.940] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901750.940] drmOpenDevice: node name is /dev/dri/card0
[3901750.940] drmOpenDevice: open result is 13, (OK)
[3901750.940] drmOpenByBusid: drmOpenMinor returns 13
[3901750.940] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901750.940] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901750.976] drmOpenDevice: node name is /dev/dri/card0
[3901750.976] drmOpenDevice: open result is 13, (OK)
[3901750.976] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901750.976] drmOpenDevice: node name is /dev/dri/card0
[3901750.976] drmOpenDevice: open result is 13, (OK)
[3901750.976] drmOpenByBusid: drmOpenMinor returns 13
[3901751.013] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901751.013] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901751.271] (II) EMGD(0): [DRI2] Setup complete
[3901751.271] (II) EMGD(0): [DRI2]   DRI driver: emgd
[3901751.271] (II) EMGD(0): DRI2 initialization complete.
[3901751.306] (II) UXA(0): Driver registered support for the following operations:
[3901751.306] (II)         solid
[3901751.306] (II)         copy
[3901751.306] (II)         composite (RENDER acceleration)
[3901751.306] (II) EMGD(0): [hal to drm] Communication With DRM Failed

[3901751.306] (II) EMGD(0): Video acceleration initialization complete
[3901751.306] (==) EMGD(0): Backing store disabled
[3901751.356] drmOpenDevice: node name is /dev/dri/card0
[3901751.357] drmOpenDevice: open result is 14, (OK)
[3901751.357] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901751.357] drmOpenDevice: node name is /dev/dri/card0
[3901751.357] drmOpenDevice: open result is 14, (OK)
[3901751.357] drmOpenByBusid: drmOpenMinor returns 14
[3901751.357] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901751.357] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901751.367] drmOpenDevice: node name is /dev/dri/card0
[3901751.367] drmOpenDevice: open result is 14, (OK)
[3901751.368] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901751.368] drmOpenDevice: node name is /dev/dri/card0
[3901751.368] drmOpenDevice: open result is 14, (OK)
[3901751.368] drmOpenByBusid: drmOpenMinor returns 14
[3901751.368] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901751.368] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901751.491] (II) EMGD(0): Hardware Cursor Initialization complete.
[3901751.491] (==) EMGD(0): Silken mouse enabled
[3901751.491] (==) EMGD(0): DPMS enabled
[3901751.505] (==) RandR enabled
[3901751.505] (II) Initializing built-in extension Generic Event Extension
[3901751.505] (II) Initializing built-in extension SHAPE
[3901751.505] (II) Initializing built-in extension MIT-SHM
[3901751.505] (II) Initializing built-in extension XInputExtension
[3901751.505] (II) Initializing built-in extension XTEST
[3901751.505] (II) Initializing built-in extension BIG-REQUESTS
[3901751.505] (II) Initializing built-in extension SYNC
[3901751.506] (II) Initializing built-in extension XKEYBOARD
[3901751.506] (II) Initializing built-in extension XC-MISC
[3901751.506] (II) Initializing built-in extension XFIXES
[3901751.506] (II) Initializing built-in extension RENDER
[3901751.506] (II) Initializing built-in extension RANDR
[3901751.506] (II) Initializing built-in extension COMPOSITE
[3901751.506] (II) Initializing built-in extension DAMAGE
[3901752.039] drmOpenDevice: node name is /dev/dri/card0
[3901752.039] drmOpenDevice: open result is 14, (OK)
[3901752.040] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901752.040] drmOpenDevice: node name is /dev/dri/card0
[3901752.040] drmOpenDevice: open result is 14, (OK)
[3901752.040] drmOpenByBusid: drmOpenMinor returns 14
[3901752.040] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901752.040] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901752.040] drmOpenDevice: node name is /dev/dri/card0
[3901752.040] drmOpenDevice: open result is 14, (OK)
[3901752.041] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901752.041] drmOpenDevice: node name is /dev/dri/card0
[3901752.042] drmOpenDevice: open result is 14, (OK)
[3901752.042] drmOpenByBusid: drmOpenMinor returns 14
[3901752.042] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901752.042] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901752.084] drmOpenDevice: node name is /dev/dri/card0
[3901752.084] drmOpenDevice: open result is 14, (OK)
[3901752.084] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901752.084] drmOpenDevice: node name is /dev/dri/card0
[3901752.084] drmOpenDevice: open result is 14, (OK)
[3901752.084] drmOpenByBusid: drmOpenMinor returns 14
[3901752.085] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901752.085] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901752.179] drmOpenDevice: node name is /dev/dri/card0
[3901752.180] drmOpenDevice: open result is 15, (OK)
[3901752.180] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901752.180] drmOpenDevice: node name is /dev/dri/card0
[3901752.180] drmOpenDevice: open result is 15, (OK)
[3901752.180] drmOpenByBusid: drmOpenMinor returns 15
[3901752.180] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901752.180] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901752.180] drmOpenDevice: node name is /dev/dri/card0
[3901752.181] drmOpenDevice: open result is 15, (OK)
[3901752.181] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901752.181] drmOpenDevice: node name is /dev/dri/card0
[3901752.181] drmOpenDevice: open result is 15, (OK)
[3901752.181] drmOpenByBusid: drmOpenMinor returns 15
[3901752.181] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901752.181] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901752.190] drmOpenDevice: node name is /dev/dri/card0
[3901752.190] drmOpenDevice: open result is 15, (OK)
[3901752.190] drmOpenByBusid: Searching for BusID PCI:00:02:00
[3901752.190] drmOpenDevice: node name is /dev/dri/card0
[3901752.190] drmOpenDevice: open result is 15, (OK)
[3901752.190] drmOpenByBusid: drmOpenMinor returns 15
[3901752.190] drmOpenByBusid: Interface 1.4 failed, trying 1.1
[3901752.190] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
[3901752.342] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[3901752.342] (II) AIGLX: enabled GLX_INTEL_swap_event
[3901752.342] (II) AIGLX: enabled GLX_SGI_make_current_read
[3901752.342] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[3901752.355] (II) AIGLX: Loaded and initialized /usr/lib/dri/emgd_dri.so
[3901752.356] (II) GLX: Initialized DRI2 GL provider for screen 0
[3901753.105] (II) LoadModule: "mouse"
[3901753.106] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[3901753.106] (II) Module mouse: vendor="X.Org Foundation"
[3901753.107] 	compiled for 1.13.1, module version = 1.8.1
[3901753.107] 	Module class: X.Org XInput Driver
[3901753.107] 	ABI class: X.Org XInput driver, version 18.0
[3901753.107] (EE) module ABI major version (18) doesn't match the server's version (11)
[3901753.112] (II) UnloadModule: "mouse"
[3901753.112] (II) Unloading /usr/lib/xorg/modules/input/mouse_drv.so
[3901753.112] (EE) Failed to load module "mouse" (module requirement mismatch, 0)
[3901753.113] (EE) No input driver matching `mouse'
[3901753.113] (II) LoadModule: "kbd"
[3901753.114] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so
[3901753.114] (II) Module kbd: vendor="X.Org Foundation"
[3901753.114] 	compiled for 1.13.1, module version = 1.6.2
[3901753.114] 	Module class: X.Org XInput Driver
[3901753.114] 	ABI class: X.Org XInput driver, version 18.0
[3901753.114] (EE) module ABI major version (18) doesn't match the server's version (11)
[3901753.120] (II) UnloadModule: "kbd"
[3901753.120] (II) Unloading /usr/lib/xorg/modules/input/kbd_drv.so
[3901753.120] (EE) Failed to load module "kbd" (module requirement mismatch, 0)
[3901753.120] (EE) No input driver matching `kbd'
[3901753.458] (II) config/udev: Adding input device DIALOGUE INC PenMount USB (/dev/input/mouse0)
[3901753.458] (II) AutoAddDevices is off - not adding device.

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08  9:50   ` Andreas Enbacka
@ 2013-04-08 10:34     ` Burton, Ross
  2013-04-08 10:50       ` Andreas Enbacka
  2013-04-08 12:12       ` Andreas Enbacka
  0 siblings, 2 replies; 16+ messages in thread
From: Burton, Ross @ 2013-04-08 10:34 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

On 8 April 2013 10:50, Andreas Enbacka <aenbacka@gmail.com> wrote:
> Thanks for your reply, very much appreciated. I am currently using Poky master. I have attached the complete Xorg.0.log; it does not contain any mentions of evdev, only mouse, which would imply that evdev does not get loaded of some reason.

That's interesting, it should be loading the evdev module.  Can you
confirm that it's present in /usr/lib/xorg/modules/input?

Your log shows that it didn't load the kbd and mouse modules because
the versions don't match:

[3901748.190] (II) LoadModule: "mouse"
[3901748.191] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[3901748.208] (II) Module kbd: vendor="X.Org Foundation"
[3901748.208]   compiled for 1.13.1, module version = 1.6.2
[3901748.203] (EE) module ABI major version (18) doesn't match the
server's version (11)
[3901748.204] (EE) Failed to load module "mouse" (module requirement
mismatch, 0)

This shouldn't happen in master because the server and the modules
have runtime-dependences injected to stop this happening:

$ dpkg -I xf86-input-mouse_1.8.1-r21.0.0_armv5te.ipk
...
 Depends: xorg-abi-input-19, libc6 (>= 2.17)

$ dpkg -I xserver-xorg_1.14.0-r8.0.0_armv5te.ipk
...
 Provides: xserver-xorg-extension-extmod, xserver-xorg-extension-dri,
xorg-abi-video-14, xorg-abi-input-19, xserver-xorg-extension-dbe,
xserver-xorg-extension-record, xserver-xorg-extension-dri2

Something went wrong and your drivers were built with a newer version
of the server (1.13.1) than you're actually running (1.9.3). I suspect
what's happened is that you've done a non-emenlow build (say, atom-pc)
in the same build directory and your emenlow build is re-using the
drivers.  Rebuilding the drivers should help, so "bitbake
-ccleansstate xorg-input-keyboard xorg-input-mouse" and then re-build
your image.

Ross


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08 10:34     ` Burton, Ross
@ 2013-04-08 10:50       ` Andreas Enbacka
  2013-04-08 12:12       ` Andreas Enbacka
  1 sibling, 0 replies; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-08 10:50 UTC (permalink / raw)
  To: 'Burton, Ross'; +Cc: yocto

Thanks again for your assistance. I checked /usr/lib/xorg/modules/input, and evdev_drv.so is indeed present. 

I will try rebuild the specified modules, and see in case it solves the problem (I have indeed built some atom-pc images previously). 

Thanks,
Andreas

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 8. huhtikuuta 2013 13:34
To: Andreas Enbacka
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

On 8 April 2013 10:50, Andreas Enbacka <aenbacka@gmail.com> wrote:
> Thanks for your reply, very much appreciated. I am currently using Poky master. I have attached the complete Xorg.0.log; it does not contain any mentions of evdev, only mouse, which would imply that evdev does not get loaded of some reason.

That's interesting, it should be loading the evdev module.  Can you confirm that it's present in /usr/lib/xorg/modules/input?

Your log shows that it didn't load the kbd and mouse modules because the versions don't match:

[3901748.190] (II) LoadModule: "mouse"
[3901748.191] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[3901748.208] (II) Module kbd: vendor="X.Org Foundation"
[3901748.208]   compiled for 1.13.1, module version = 1.6.2
[3901748.203] (EE) module ABI major version (18) doesn't match the server's version (11) [3901748.204] (EE) Failed to load module "mouse" (module requirement mismatch, 0)

This shouldn't happen in master because the server and the modules have runtime-dependences injected to stop this happening:

$ dpkg -I xf86-input-mouse_1.8.1-r21.0.0_armv5te.ipk
...
 Depends: xorg-abi-input-19, libc6 (>= 2.17)

$ dpkg -I xserver-xorg_1.14.0-r8.0.0_armv5te.ipk
...
 Provides: xserver-xorg-extension-extmod, xserver-xorg-extension-dri, xorg-abi-video-14, xorg-abi-input-19, xserver-xorg-extension-dbe, xserver-xorg-extension-record, xserver-xorg-extension-dri2

Something went wrong and your drivers were built with a newer version of the server (1.13.1) than you're actually running (1.9.3). I suspect what's happened is that you've done a non-emenlow build (say, atom-pc) in the same build directory and your emenlow build is re-using the drivers.  Rebuilding the drivers should help, so "bitbake -ccleansstate xorg-input-keyboard xorg-input-mouse" and then re-build your image.

Ross

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08 10:34     ` Burton, Ross
  2013-04-08 10:50       ` Andreas Enbacka
@ 2013-04-08 12:12       ` Andreas Enbacka
  2013-04-08 12:19         ` Burton, Ross
  1 sibling, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-08 12:12 UTC (permalink / raw)
  To: 'Burton, Ross'; +Cc: yocto

I rebuilt xf86-input-keyboard and xf86-input-mouse (as well as the core-image-sato image), and now the mouse / keyboard works ok in X. Thanks for the assistance.

I checked the Xorg log file, it seems to add the mouse using the mouse_drv.so module, not evdev_drv.so. Do I need to rebuild xf86-input-evdev as well to get the mouse added using evdev? This because I have a custom application that handles the touch screen calibration running on top of X, and itexpects the mouse to be added via evdev. 

//Andreas

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 8. huhtikuuta 2013 13:34
To: Andreas Enbacka
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

On 8 April 2013 10:50, Andreas Enbacka <aenbacka@gmail.com> wrote:
> Thanks for your reply, very much appreciated. I am currently using Poky master. I have attached the complete Xorg.0.log; it does not contain any mentions of evdev, only mouse, which would imply that evdev does not get loaded of some reason.

That's interesting, it should be loading the evdev module.  Can you confirm that it's present in /usr/lib/xorg/modules/input?

Your log shows that it didn't load the kbd and mouse modules because the versions don't match:

[3901748.190] (II) LoadModule: "mouse"
[3901748.191] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so
[3901748.208] (II) Module kbd: vendor="X.Org Foundation"
[3901748.208]   compiled for 1.13.1, module version = 1.6.2
[3901748.203] (EE) module ABI major version (18) doesn't match the server's version (11) [3901748.204] (EE) Failed to load module "mouse" (module requirement mismatch, 0)

This shouldn't happen in master because the server and the modules have runtime-dependences injected to stop this happening:

$ dpkg -I xf86-input-mouse_1.8.1-r21.0.0_armv5te.ipk
...
 Depends: xorg-abi-input-19, libc6 (>= 2.17)

$ dpkg -I xserver-xorg_1.14.0-r8.0.0_armv5te.ipk
...
 Provides: xserver-xorg-extension-extmod, xserver-xorg-extension-dri, xorg-abi-video-14, xorg-abi-input-19, xserver-xorg-extension-dbe, xserver-xorg-extension-record, xserver-xorg-extension-dri2

Something went wrong and your drivers were built with a newer version of the server (1.13.1) than you're actually running (1.9.3). I suspect what's happened is that you've done a non-emenlow build (say, atom-pc) in the same build directory and your emenlow build is re-using the drivers.  Rebuilding the drivers should help, so "bitbake -ccleansstate xorg-input-keyboard xorg-input-mouse" and then re-build your image.

Ross

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08 12:12       ` Andreas Enbacka
@ 2013-04-08 12:19         ` Burton, Ross
  2013-04-08 17:44           ` Andreas Enbacka
  0 siblings, 1 reply; 16+ messages in thread
From: Burton, Ross @ 2013-04-08 12:19 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

On 8 April 2013 13:12, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I rebuilt xf86-input-keyboard and xf86-input-mouse (as well as the core-image-sato image), and now the mouse / keyboard works ok in X. Thanks for the assistance.
>
> I checked the Xorg log file, it seems to add the mouse using the mouse_drv.so module, not evdev_drv.so. Do I need to rebuild xf86-input-evdev as well to get the mouse added using evdev? This because I have a custom application that handles the touch screen calibration running on top of X, and itexpects the mouse to be added via evdev.

Probably - you could try removing the mouse and keyboard drivers and
leaving just evdev if it still prefers mouse/keyboard over evdev.

Ross


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08 12:19         ` Burton, Ross
@ 2013-04-08 17:44           ` Andreas Enbacka
  2013-04-09 10:06             ` Burton, Ross
  0 siblings, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-08 17:44 UTC (permalink / raw)
  To: 'Burton, Ross'; +Cc: yocto

I tried to rebuild the xf86-input-evdev; however the core-image-sato still insists on using the default mouse / keyboard drivers instead of evdev. Also no /dev/input/event* entries exist (only /dev/input/mice and /dev/input/mouse0). 

Concerning removing xf86-input-mouse / xf86-input-keyboard from the image, what is the easiest way to achieve this using yocto? I have created a custom bitbake recipe already, inheriting from core-image-sato, which adds a few packages. Can removal of packages be easily specified in the custom recipe as well?

//Andreas

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 8. huhtikuuta 2013 15:19
To: Andreas Enbacka
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

On 8 April 2013 13:12, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I rebuilt xf86-input-keyboard and xf86-input-mouse (as well as the core-image-sato image), and now the mouse / keyboard works ok in X. Thanks for the assistance.
>
> I checked the Xorg log file, it seems to add the mouse using the mouse_drv.so module, not evdev_drv.so. Do I need to rebuild xf86-input-evdev as well to get the mouse added using evdev? This because I have a custom application that handles the touch screen calibration running on top of X, and itexpects the mouse to be added via evdev.

Probably - you could try removing the mouse and keyboard drivers and leaving just evdev if it still prefers mouse/keyboard over evdev.

Ross

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-08 17:44           ` Andreas Enbacka
@ 2013-04-09 10:06             ` Burton, Ross
  2013-04-10  6:34               ` Andreas Enbacka
  0 siblings, 1 reply; 16+ messages in thread
From: Burton, Ross @ 2013-04-09 10:06 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

Hi Andreas,

On 8 April 2013 18:44, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I tried to rebuild the xf86-input-evdev; however the core-image-sato still insists on using the default mouse / keyboard drivers instead of evdev. Also no /dev/input/event* entries exist (only /dev/input/mice and /dev/input/mouse0).

So in that case evdev won't help anyway.  I wonder why that is.  I
guess you'll need to try evtest and look at dmesg.

> Concerning removing xf86-input-mouse / xf86-input-keyboard from the image, what is the easiest way to achieve this using yocto? I have created a custom bitbake recipe already, inheriting from core-image-sato, which adds a few packages. Can removal of packages be easily specified in the custom recipe as well?

They're pulled in through the machine configuration, eventually
reaching XSERVER_IA32_BASE.  The packages are tiny and the choice of
what ones to use can be made by xorg.conf anyway.

Ross


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-09 10:06             ` Burton, Ross
@ 2013-04-10  6:34               ` Andreas Enbacka
  2013-04-10 14:50                 ` Bruce Ashfield
  0 siblings, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-10  6:34 UTC (permalink / raw)
  To: 'Burton, Ross'; +Cc: yocto

Ross,

Tried to dig around a little more in the core-image-sato image; dmesg output does not list anything at all related to evdev. The evdev_drv.so module is present in the image, but e.g., lsmod | grep evdev does not produce any output (modprobe evdev reports fatal error: cannot load module). Is the evdev support missing from the kernel of some reason, and can it be fixed easily somehow?

//Andreas

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 9. huhtikuuta 2013 13:07
To: Andreas Enbacka
Cc: yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

Hi Andreas,

On 8 April 2013 18:44, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I tried to rebuild the xf86-input-evdev; however the core-image-sato still insists on using the default mouse / keyboard drivers instead of evdev. Also no /dev/input/event* entries exist (only /dev/input/mice and /dev/input/mouse0).

So in that case evdev won't help anyway.  I wonder why that is.  I guess you'll need to try evtest and look at dmesg.

> Concerning removing xf86-input-mouse / xf86-input-keyboard from the image, what is the easiest way to achieve this using yocto? I have created a custom bitbake recipe already, inheriting from core-image-sato, which adds a few packages. Can removal of packages be easily specified in the custom recipe as well?

They're pulled in through the machine configuration, eventually reaching XSERVER_IA32_BASE.  The packages are tiny and the choice of what ones to use can be made by xorg.conf anyway.

Ross

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-10  6:34               ` Andreas Enbacka
@ 2013-04-10 14:50                 ` Bruce Ashfield
  2013-04-12  5:58                   ` Andreas Enbacka
  0 siblings, 1 reply; 16+ messages in thread
From: Bruce Ashfield @ 2013-04-10 14:50 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

On 13-04-10 02:34 AM, Andreas Enbacka wrote:
> Ross,
>
> Tried to dig around a little more in the core-image-sato image; dmesg output does not list anything at all related to evdev. The evdev_drv.so module is present in the image, but e.g., lsmod | grep evdev does not produce any output (modprobe evdev reports fatal error: cannot load module). Is the evdev support missing from the kernel of some reason, and can it be fixed easily somehow?

EVDEV is typically built into our images, not as a module. If you
zcat /proc/config.gz, and grep for EVDEV, what do you see ?

Bruce

>
> //Andreas
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: 9. huhtikuuta 2013 13:07
> To: Andreas Enbacka
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
>
> Hi Andreas,
>
> On 8 April 2013 18:44, Andreas Enbacka <aenbacka@gmail.com> wrote:
>> I tried to rebuild the xf86-input-evdev; however the core-image-sato still insists on using the default mouse / keyboard drivers instead of evdev. Also no /dev/input/event* entries exist (only /dev/input/mice and /dev/input/mouse0).
>
> So in that case evdev won't help anyway.  I wonder why that is.  I guess you'll need to try evtest and look at dmesg.
>
>> Concerning removing xf86-input-mouse / xf86-input-keyboard from the image, what is the easiest way to achieve this using yocto? I have created a custom bitbake recipe already, inheriting from core-image-sato, which adds a few packages. Can removal of packages be easily specified in the custom recipe as well?
>
> They're pulled in through the machine configuration, eventually reaching XSERVER_IA32_BASE.  The packages are tiny and the choice of what ones to use can be made by xorg.conf anyway.
>
> Ross
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-10 14:50                 ` Bruce Ashfield
@ 2013-04-12  5:58                   ` Andreas Enbacka
  2013-04-12 10:27                     ` Burton, Ross
  0 siblings, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-12  5:58 UTC (permalink / raw)
  To: 'Bruce Ashfield'; +Cc: yocto

Hello,

I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced the
following output:

#  CONFIG_INPUT_EVDEV is not set
CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y

Does the above shed some light what could be the problem with the image? 

//Andreas

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] 
Sent: 10. huhtikuuta 2013 17:51
To: Andreas Enbacka
Cc: 'Burton, Ross'; yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto
(core-image-sato on emenlow)

On 13-04-10 02:34 AM, Andreas Enbacka wrote:
> Ross,
>
> Tried to dig around a little more in the core-image-sato image; dmesg
output does not list anything at all related to evdev. The evdev_drv.so
module is present in the image, but e.g., lsmod | grep evdev does not
produce any output (modprobe evdev reports fatal error: cannot load module).
Is the evdev support missing from the kernel of some reason, and can it be
fixed easily somehow?

EVDEV is typically built into our images, not as a module. If you zcat
/proc/config.gz, and grep for EVDEV, what do you see ?

Bruce

>
> //Andreas
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: 9. huhtikuuta 2013 13:07
> To: Andreas Enbacka
> Cc: yocto@yoctoproject.org
> Subject: Re: [yocto] Problem with mouse and keyboard detection in 
> yocto (core-image-sato on emenlow)
>
> Hi Andreas,
>
> On 8 April 2013 18:44, Andreas Enbacka <aenbacka@gmail.com> wrote:
>> I tried to rebuild the xf86-input-evdev; however the core-image-sato
still insists on using the default mouse / keyboard drivers instead of
evdev. Also no /dev/input/event* entries exist (only /dev/input/mice and
/dev/input/mouse0).
>
> So in that case evdev won't help anyway.  I wonder why that is.  I guess
you'll need to try evtest and look at dmesg.
>
>> Concerning removing xf86-input-mouse / xf86-input-keyboard from the
image, what is the easiest way to achieve this using yocto? I have created a
custom bitbake recipe already, inheriting from core-image-sato, which adds a
few packages. Can removal of packages be easily specified in the custom
recipe as well?
>
> They're pulled in through the machine configuration, eventually reaching
XSERVER_IA32_BASE.  The packages are tiny and the choice of what ones to use
can be made by xorg.conf anyway.
>
> Ross
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>




^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-12  5:58                   ` Andreas Enbacka
@ 2013-04-12 10:27                     ` Burton, Ross
  2013-04-12 12:27                       ` Andreas Enbacka
  0 siblings, 1 reply; 16+ messages in thread
From: Burton, Ross @ 2013-04-12 10:27 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

On 12 April 2013 06:58, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced the
> following output:
>
> #  CONFIG_INPUT_EVDEV is not set
> CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
>
> Does the above shed some light what could be the problem with the image?

Erm, yes.  My atom-pc kernel has CONFIG_INPUT_EVDEV set.

There was a bug where kernel configuration was dropping fragments, so
you may want to try fetching the dylan branch (as we're about to
release) and trying again.

Ross


^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-12 10:27                     ` Burton, Ross
@ 2013-04-12 12:27                       ` Andreas Enbacka
  2013-04-12 12:34                         ` Bruce Ashfield
  0 siblings, 1 reply; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-12 12:27 UTC (permalink / raw)
  To: 'Burton, Ross'; +Cc: yocto

Hi,

Thanks for the suggestion, I will fetch the dylan branch and retry.

//Andreas

-----Original Message-----
From: Burton, Ross [mailto:ross.burton@intel.com] 
Sent: 12. huhtikuuta 2013 13:27
To: Andreas Enbacka
Cc: Bruce Ashfield; yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

On 12 April 2013 06:58, Andreas Enbacka <aenbacka@gmail.com> wrote:
> I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced 
> the following output:
>
> #  CONFIG_INPUT_EVDEV is not set
> CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
>
> Does the above shed some light what could be the problem with the image?

Erm, yes.  My atom-pc kernel has CONFIG_INPUT_EVDEV set.

There was a bug where kernel configuration was dropping fragments, so you may want to try fetching the dylan branch (as we're about to
release) and trying again.

Ross



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-12 12:27                       ` Andreas Enbacka
@ 2013-04-12 12:34                         ` Bruce Ashfield
  2013-04-15  9:27                           ` Andreas Enbacka
  0 siblings, 1 reply; 16+ messages in thread
From: Bruce Ashfield @ 2013-04-12 12:34 UTC (permalink / raw)
  To: Andreas Enbacka; +Cc: yocto

On 13-04-12 08:27 AM, Andreas Enbacka wrote:
> Hi,
>
> Thanks for the suggestion, I will fetch the dylan branch and retry.
>

And I can confirm that with an atom-pc board I configured just
minutes ago:

% grep EVDEV linux-atom-pc-standard-build/.config
CONFIG_INPUT_EVDEV=y

Cheers,

Bruce


> //Andreas
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: 12. huhtikuuta 2013 13:27
> To: Andreas Enbacka
> Cc: Bruce Ashfield; yocto@yoctoproject.org
> Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
>
> On 12 April 2013 06:58, Andreas Enbacka <aenbacka@gmail.com> wrote:
>> I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced
>> the following output:
>>
>> #  CONFIG_INPUT_EVDEV is not set
>> CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
>>
>> Does the above shed some light what could be the problem with the image?
>
> Erm, yes.  My atom-pc kernel has CONFIG_INPUT_EVDEV set.
>
> There was a bug where kernel configuration was dropping fragments, so you may want to try fetching the dylan branch (as we're about to
> release) and trying again.
>
> Ross
>



^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)
  2013-04-12 12:34                         ` Bruce Ashfield
@ 2013-04-15  9:27                           ` Andreas Enbacka
  0 siblings, 0 replies; 16+ messages in thread
From: Andreas Enbacka @ 2013-04-15  9:27 UTC (permalink / raw)
  To: 'Bruce Ashfield'; +Cc: yocto

Hello,

I was finally able to get evdev working with the core-image-sato image. First I tried to fetch the dylan branch (yocto and meta-intel/meta-emenlow), and did a rebuild. However, evdev support was still missing from the kernel (CONFIG_INPUT_EVDEV not set). Then I ran menuconfig, and enabled the event input interface in the kernel config, and performed image rebuild. After that evdev support was working fine. 

Thanks for the help!

Best regards,
Andreas

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] 
Sent: 12. huhtikuuta 2013 15:34
To: Andreas Enbacka
Cc: 'Burton, Ross'; yocto@yoctoproject.org
Subject: Re: [yocto] Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow)

On 13-04-12 08:27 AM, Andreas Enbacka wrote:
> Hi,
>
> Thanks for the suggestion, I will fetch the dylan branch and retry.
>

And I can confirm that with an atom-pc board I configured just minutes ago:

% grep EVDEV linux-atom-pc-standard-build/.config
CONFIG_INPUT_EVDEV=y

Cheers,

Bruce


> //Andreas
>
> -----Original Message-----
> From: Burton, Ross [mailto:ross.burton@intel.com]
> Sent: 12. huhtikuuta 2013 13:27
> To: Andreas Enbacka
> Cc: Bruce Ashfield; yocto@yoctoproject.org
> Subject: Re: [yocto] Problem with mouse and keyboard detection in 
> yocto (core-image-sato on emenlow)
>
> On 12 April 2013 06:58, Andreas Enbacka <aenbacka@gmail.com> wrote:
>> I tried to execute zcat /proc/config.gz | grep EVDEV, and it produced 
>> the following output:
>>
>> #  CONFIG_INPUT_EVDEV is not set
>> CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y
>>
>> Does the above shed some light what could be the problem with the image?
>
> Erm, yes.  My atom-pc kernel has CONFIG_INPUT_EVDEV set.
>
> There was a bug where kernel configuration was dropping fragments, so 
> you may want to try fetching the dylan branch (as we're about to
> release) and trying again.
>
> Ross
>




^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2013-04-15  9:27 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-04-08  8:42 Problem with mouse and keyboard detection in yocto (core-image-sato on emenlow) Andreas Enbacka
2013-04-08  9:18 ` Burton, Ross
2013-04-08  9:50   ` Andreas Enbacka
2013-04-08 10:34     ` Burton, Ross
2013-04-08 10:50       ` Andreas Enbacka
2013-04-08 12:12       ` Andreas Enbacka
2013-04-08 12:19         ` Burton, Ross
2013-04-08 17:44           ` Andreas Enbacka
2013-04-09 10:06             ` Burton, Ross
2013-04-10  6:34               ` Andreas Enbacka
2013-04-10 14:50                 ` Bruce Ashfield
2013-04-12  5:58                   ` Andreas Enbacka
2013-04-12 10:27                     ` Burton, Ross
2013-04-12 12:27                       ` Andreas Enbacka
2013-04-12 12:34                         ` Bruce Ashfield
2013-04-15  9:27                           ` Andreas Enbacka

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.