Project Home
Project Home		 Documents
Documents		 Wiki
Wiki		 Discussion Forums
Discussions		 Project Information
Project Info
Graphics/Discussion/Advanced Graphics/QNX 6.6 - i965 - screen startup failed/List of Posts
Forum Topic - QNX 6.6 - i965 - screen startup failed: (4 Items)
   
Update
Jefferson Biernastki(deleted)
09/03/2014 7:19 AM
post111614
QNX 6.6 - i965 - screen startup failed   
Hi,

while i was working with VMWare my graphics configuration were ok, but after boot QNX660 in a x86 PC with Intel Pineview
 video board my screen don't run anymore.

Same error happens in Intel Valleyview video board.

There is any configuration or initialization that i have to do before start drm-intel?

# drm-intel
# screen
[intel_init_bufmgr:946] Error initializing buffer manager.
libEGL warning: DRI2: failed to create dri screen
Screen startup failed

# graphics.conf

begin khronos

  begin egl display 1
    egl-dlls = libEGL-mesa.so
    glesv1-dlls = libglapi-mesa.so libGLESv1_CM-mesa.so
    glesv2-dlls = libglapi-mesa.so libGLESv2-mesa.so
  end egl display

  begin wfd device 1
    wfd-dlls = libwfdcfg-sample.so libWFDintel-drm.so
    pipeline1-display = 1
    pipeline2-display = 2
  end wfd device

end khronos

begin winmgr

 begin globals
    blit-config = gles2blt
    input = keyboard
    stack-size = 2048
  end globals

  begin display 1
    video-mode = 1024 x 768 @ 60
    stack-size = 2048
  end display

  begin display 2
    video-mode = 1024 x 768 @ 60
    stack-size = 2048
  end display

  begin class framebuffer
    display = 1
    pipeline = 1
    format = rgba8888
    usage = gles2blt
  end class
  
  begin class framebuffer
    display = 2
    pipeline = 2
    format = rgba8888
    usage = gles2blt
  end class

end winmgr
Leo Xu
09/03/2014 11:21 AM
post111617
Re: QNX 6.6 - i965 - screen startup failed   
Hi, are you running drm & screen inside vmware?
from the error message, it looks like the function drm_intel_bufmgr_gem_init failed, normally it should work fine, it 
will fail if the graphics device id is not supported. 

so can you run sloginfo and post the output ? also it will be helpful to run command pci and post the output. 

Thanks
OBC ALL(deleted)
09/03/2014 11:31 AM
post111618
Re: QNX 6.6 - i965 - screen startup failed   
Below sloginfo.

Runing LD_DEBUG=libs i checked i965 driver being loaded

# show_vesa
VESA Info Block

VESA Signature : VESA
VESA Version   : 0300
OEM String Ptr : 0080:0100
OEM String     : Intel(R)Valleyview Graphics Chipset Accelerated VGA BIOS

# drm-probe-displays
# drm-probe-displays
count_displays : 5
count_pipelines: 2

display 1: embedded displayport, connected
Mode: "1024x768" 1024x768 60
Mode: "1024x768" 1024x768 50
display 2: VGA, connected
Mode: "1024x768" 1024x768 60
Mode: "800x600" 800x600 60
Mode: "800x600" 800x600 56
Mode: "848x480" 848x480 60
Mode: "640x480" 640x480 60
display 3: HDMI-A, disconnected
display 4: HDMI-A, disconnected
display 5: displayport, disconnected

pipeline 1
pipeline 2

# sloginfo:

Sep 03 09:59:57    5     8   300 screen: starting up...
Sep 03 09:59:57    5     8   300 screen: connected to powman...
Sep 03 09:59:57    3     8   915 [ihold:265]"warning"
Sep 03 09:59:57    2     8   200 drm_intel_bufmgr_gem_init failed
Sep 03 09:59:57    2     8   300 screen: win_enumerate_displays: could not create display device 1
Sep 03 09:59:57    2     8   300 screen: invalid display id:
        >>>   begin display 1

Sep 03 09:59:57    2     8   300 screen: invalid display id:
        >>>   begin display 2

Sep 03 09:59:57    5     8   300 screen: loading EGL display 1...
Sep 03 09:59:57    5     8   300 screen: loading blit module gles2blt...
Sep 03 09:59:57    3     8   100 egl: DRI2: failed to create dri screen
Sep 03 09:59:57    2     8   300 screen-gles2blt: eglInitialize: EGL is not initialized, or could not be initialized, 
for the specified display
Sep 03 09:59:57    2     8   300 screen: win_blit_module_init: could not create a blitting context
Marcelo Souza Ramos(deleted)
10/21/2014 12:32 PM
post112085
Re: QNX 6.6 - i965 - screen startup failed   
Fixed after a update provided by QNX Support Team.

Return


  A subsidiary of BlackBerry             All content ©2004-2013, QNX Software Systems