I'm using meta-crownbay BSP (commit 902d2f3c919cd1d870dc8d35a7521cbba42e53ea)on a Tunnel Creek platform. After Xorg launch, The DVI output is not working anymore, nothing is displayed on the monitor. The screen is an acer Monitor with DVI input and supports resolution up to 1280x1024 at 60Hz my Xorg.conf : cat /etc/X11/xorg.conf Section "Device" Identifier "Intel Graphics Driver" Driver "emgd" Option "PcfVersion" "1792" Option "PortOrder" "20000" Option "ALL/1/Port/4/General/Edid" "1" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Intel Graphics Driver" Monitor "Generic Monitor" DefaultDepth 24 EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" EndSection Section "ServerFlags" Option "DontZap" "0" EndSection the xrandr output : root@crownbay:~# DISPLAY=:0 xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 960 x 540, maximum 1024 x 768 default connected 960x540+0+0 0mm x 0mm 960x540 60.0* 800x600 60.0 800x480 60.0 720x480 60.0 640x480 60.0 1024x768 60.0 My Xorg log is attached
Created attachment 215 [details] xorg.conf
Created attachment 216 [details] emgd Xorg output from successful DVI launch
using meta-intel commit 902d2f3c919cd1d870dc8d35a7521cbba42e53ea with poky/master commit 6c2b7beac3cd23ed44bd3e195c6360a0932876bf, I got successful DVI output after changing the PortOrder Option from 40000 to 24000: Option "ALL/1/General/PortOrder" "24000" Attached the xorg.conf I used and the Xorg.0.output from the successful boot into sato. I'll try to compare with the failure output and see if I can spot any differences. One thing it would make sense to do in any case would be to change the PortOrder as above i.e. basically try DVI output first, then LVDS.
I don't see the Xorg log from the failure. But the xorg.conf is different - not sure why you're using a different one from the version from the BSP. Can you try the attached xorg.conf that worked for me?
Created attachment 221 [details] Xorg with DVI out working
(In reply to comment #5) > Created attachment 221 [details] > Xorg with DVI out working I tried with your xorg.conf, and the DVI output is now drived but the resolution is not rightly detected. and the monitor displays "signal not supported". Here the output of xrandr : root@crownbay:~# DISPLAY=:0 xrandr xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 480, current 1600 x 900, maximum 1600 x 1050 default connected 1600x900+0+0 0mm x 0mm 1600x900 60.0* 1400x1050 60.0 1366x768 60.0 1280x1024 75.0 72.0 70.0 60.0 1280x960 75.0 60.0 1280x768 75.0 60.0 1280x720 75.0 60.0 1152x864 75.0 72.0 70.0 60.0 1024x768 75.0 70.0 60.0 960x540 60.0 800x600 75.0 72.0 70.0 60.0 800x480 60.0 720x480 60.0 640x480 75.0 72.0 70.0 60.0 It's now better than previously, where resolutions were those of the lvds output. I set the native resolution of my screen (1280x1024@60) and now the display is correct. I attached my correct Xorg.conf The problem I encountered now, it that mouse and keyboard are not working. I don't know if it's a xorg.conf configuration problem or a kernel/udev misconfiguration
PS/2 keyboard and mouse work here, but USB keyboard and mouse do not. Looking into it...
More information on my USB mouse/keyboard problem. Kernel detects usb input correctly. I tried to fix the mouse and keyboard configuration in my xorg.conf file and add these lines : Section "InputDevice" Identifier "Keyboard0" Driver "kbd" EndSection Section "InputDevice" Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "ZAxisMapping" "4 5 6 7" EndSection Section "ServerLayout" Identifier "Default Layout" Screen 0 "Screen0" 0 0 InputDevice "Mouse0" "CorePointer" InputDevice "Keyboard0" "CoreKeyboard" EndSection What i get in the Xorg.0.log is : [353919.071] (II) LoadModule: "mouse" [353919.072] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so [353919.072] (II) Module mouse: vendor="X.Org Foundation" [353919.072] compiled for 1.10.2, module version = 1.7.0 [353919.072] Module class: X.Org XInput Driver [353919.072] ABI class: X.Org XInput driver, version 12.2 [353919.072] (EE) module ABI major version (12) doesn't match the server's version (11) [353919.072] (II) UnloadModule: "mouse" [353919.072] (II) Unloading /usr/lib/xorg/modules/input/mouse_drv.so [353919.072] (EE) Failed to load module "mouse" (module requirement mismatch, 0) [353919.072] (EE) No input driver matching `mouse' This is really strange, it's like the xorg drivers wer not compiled with the same xorg server ? I build the same angstrom/oe-core config for MACHINE="beagleboard" and x input modules are correctly detected.
Hmm, your changes actually work for me - usb mouse and kbd now work, but in my case the same lines in Xorg.0.log shows the xserver is 1.9.3. [469190.108] (II) Loading /usr/lib/xorg/modules/input/mouse_drv.so [469190.120] (II) Module mouse: vendor="X.Org Foundation" [469190.120] compiled for 1.9.3, module version = 1.7.0 [469190.120] Module class: X.Org XInput Driver [469190.120] ABI class: X.Org XInput driver, version 11.0 [469190.120] (II) LoadModule: "kbd" [469190.120] (II) Loading /usr/lib/xorg/modules/input/kbd_drv.so [469190.126] (II) Module kbd: vendor="X.Org Foundation" [469190.126] compiled for 1.9.3, module version = 1.6.0 [469190.126] Module class: X.Org XInput Driver [469190.126] ABI class: X.Org XInput driver, version 11.0 [469190.126] (II) EMGD: Intel(R) Embedded Media and Graphics Driver version 1.8.2032 for: Could it be you're building the wrong version of the xserver in your build? Seems like it shouldn't happen because of the line in the crownbay.conf: PREFERRED_VERSION_xserver-xf86-dri-lite ?= "1.9.3"
With the latest meta-intel and poky, and the PortOrder change in place, I'm no longer seeing any problem with USB mouse/kb, and everything else seems to be working ok as well. I'll post the PortOrder patch - please try it and verify it allows the DVI output to show up. If you're still seeing other problems, it would probably be best to file a new bug for those. poky/master: 99cb233e0c8058c9a406e18fedae70b0f60e3864 meta-intel/master: 24a30eaf49c25c0b5d8b5d7405691c6c1b67588d
Fixed by meta-intel/master commit: 5f37a5631822bea013070b613d5a1cc7ec3daf96