Skip to content

Errors running the pre-built engines. #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Clancey opened this issue Jul 8, 2020 · 5 comments
Closed

Errors running the pre-built engines. #66

Clancey opened this issue Jul 8, 2020 · 5 comments

Comments

@Clancey
Copy link

Clancey commented Jul 8, 2020

I am getting the following output when trying to run on a Raspbery Pi 3 B. I followed all the instructions for using your existing pre-built engine. Any thoughts?

engine_argv[0] = ./flutter-pi
initializing display...
Finding a suitable DRM device, since none is given...
looking for a suitable DRM device from 1 available DRM devices...
  devices[0]: 
    available nodes: DRM_NODE_PRIMARY, DRM_NODE_RENDER
    nodes[DRM_NODE_PRIMARY] = "/dev/dri/card0"
    nodes[DRM_NODE_RENDER] = "/dev/dri/renderD128"
    bustype: DRM_BUS_PLATFORM
    businfo.fullname: /soc/gpu
    opening DRM device candidate at "/dev/dri/card0"...
    getting resources of DRM device candidate at "/dev/dri/card0"...
    flutter-pi chose "/dev/dri/card0" as its DRM device.
Finding a connected connector from 1 available connectors...
  connectors[0]: connected? yes, type: 0x0B (HDMI-A), 600mm x 340mm
Choosing DRM mode from 16 available modes...
  modes[0]: name: "1920x1080", 1920x1080p, 60Hz, type: 64, flags: 5
  modes[1]: name: "1920x1080", 1920x1080p, 60Hz, type: 64, flags: 5
  modes[2]: name: "1920x1080", 1920x1080p, 30Hz, type: 64, flags: 5
  modes[3]: name: "1920x1080", 1920x1080p, 30Hz, type: 64, flags: 5
  modes[4]: name: "1600x900", 1600x900p, 60Hz, type: 64, flags: 5
  modes[5]: name: "1280x1024", 1280x1024p, 60Hz, type: 64, flags: 5
  modes[6]: name: "1280x800", 1280x800p, 60Hz, type: 64, flags: 9
  modes[7]: name: "1152x864", 1152x864p, 60Hz, type: 0, flags: 6
  modes[8]: name: "1280x720", 1280x720p, 60Hz, type: 64, flags: 5
  modes[9]: name: "1280x720", 1280x720p, 60Hz, type: 64, flags: 5
  modes[10]: name: "1024x768", 1024x768p, 60Hz, type: 64, flags: 10
  modes[11]: name: "800x600", 800x600p, 60Hz, type: 64, flags: 5
  modes[12]: name: "720x480", 720x480p, 60Hz, type: 64, flags: 10
  modes[13]: name: "720x480", 720x480p, 60Hz, type: 64, flags: 10
  modes[14]: name: "640x480", 640x480p, 60Hz, type: 64, flags: 10
  modes[15]: name: "640x480", 640x480p, 60Hz, type: 64, flags: 10
Display properties:
  1920 x 1080, 60Hz
  600mm x 340mm
  pixel_ratio = 1.000000
Finding DRM encoder...
Creating GBM device
Querying EGL client extensions...
Getting EGL display for GBM device...
Initializing EGL...
Querying EGL display extensions...
Using display 0x9197a0 with EGL version 1.4
===================================
EGL information:
  version: 1.4
  vendor: "Mesa Project"
  client extensions: "EGL_EXT_device_base EGL_EXT_device_enumeration EGL_EXT_device_query EGL_EXT_platform_base EGL_KHR_client_get_all_proc_addresses EGL_EXT_client_extensions EGL_KHR_debug EGL_EXT_platform_wayland EGL_EXT_platform_x11 EGL_MESA_platform_gbm EGL_MESA_platform_surfaceless EGL_EXT_platform_device"
  display extensions: "EGL_ANDROID_blob_cache EGL_ANDROID_native_fence_sync EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import EGL_EXT_image_dma_buf_import_modifiers EGL_KHR_cl_event2 EGL_KHR_config_attribs EGL_KHR_create_context EGL_KHR_create_context_no_error EGL_KHR_fence_sync EGL_KHR_get_all_proc_addresses EGL_KHR_gl_colorspace EGL_KHR_gl_renderbuffer_image EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_image EGL_KHR_image_base EGL_KHR_image_pixmap EGL_KHR_no_config_context EGL_KHR_reusable_sync EGL_KHR_surfaceless_context EGL_EXT_pixel_format_float EGL_KHR_wait_sync EGL_MESA_configless_context EGL_MESA_drm_image EGL_MESA_image_dma_buf_export EGL_MESA_query_driver EGL_WL_bind_wayland_display "
===================================
Binding OpenGL ES API...
Choosing EGL config...
Finding EGL configs with appropriate attributes...
Creating EGL context...
Creating EGL window surface...
===================================
OpenGL ES information:
  version: "OpenGL ES 2.0 Mesa 19.3.2"
  shading language version: "OpenGL ES GLSL ES 1.0.16"
  vendor: "Broadcom"
  renderer: "VC4 V3D 2.1"
  extensions: "GL_EXT_blend_minmax GL_EXT_multi_draw_arrays GL_EXT_texture_format_BGRA8888 GL_OES_compressed_ETC1_RGB8_texture GL_OES_depth24 GL_OES_element_index_uint GL_OES_fbo_render_mipmap GL_OES_mapbuffer GL_OES_rgb8_rgba8 GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_npot GL_OES_vertex_half_float GL_OES_EGL_image GL_OES_depth_texture GL_AMD_performance_monitor GL_OES_packed_depth_stencil GL_OES_get_program_binary GL_APPLE_texture_max_level GL_EXT_discard_framebuffer GL_EXT_read_format_bgra GL_EXT_frag_depth GL_NV_fbo_color_attachments GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_array_object GL_EXT_occlusion_query_boolean GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer GL_NV_read_depth GL_NV_read_depth_stencil GL_NV_read_stencil GL_EXT_draw_buffers GL_EXT_map_buffer_range GL_KHR_debug GL_KHR_texture_compression_astc_ldr GL_OES_required_internalformat GL_OES_surfaceless_context GL_EXT_separate_shader_objects GL_EXT_compressed_ETC1_RGB8_sub_texture GL_EXT_draw_elements_base_vertex GL_EXT_texture_border_clamp GL_KHR_context_flush_control GL_OES_draw_elements_base_vertex GL_OES_texture_border_clamp GL_KHR_no_error GL_KHR_texture_compression_astc_sliced_3d GL_KHR_parallel_shader_compile GL_MESA_tile_raster_order "
===================================
Swapping buffers...
Locking front buffer...
getting new framebuffer for BO...
Setting CRTC...
Clearing current context...
finished display setup!
Initializing Application...
Initializing Plugin Registry...
[services] Initializing...
[services] Done.
[raw_keyboard] Initializing...
[raw_keyboard] Done.
[test_input] Initializing...
[text_input] Done.
[test_plugin] Initializing...
[test_plugin] Done.
[elm327plugin] elm_open: process doesn't have access to serial device "/dev/rfcomm0": No such file or directory
[elm327plugin] ELM327Plugin_init: ELM327 communication was not initialized successfully. elm327plugin won't supply any OBDII data. error code: No such file or directory
[flutter_gpiod] Initializing...
[flutter_gpiod] Done.
[flutter_spidev] Initializing...
[flutter_spidev] Done.
[elm327plugin] running pid query queue processor
WARNING: Kernel didn't return a valid vblank timestamp. (timestamp == 0)
         VSync will be disabled.
         See https://github.com/ardera/flutter-pi/issues/38 for more info.
[ERROR:engine/src/flutter/shell/platform/embedder/embedder_surface_gl.cc(107)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
detected VideoCore IV as underlying graphics chip, and VC4 as the driver.
Reporting modified GL_EXTENSIONS string that doesn't contain non-working extensions.
[ERROR:engine/src/flutter/shell/platform/embedder/embedder_surface_gl.cc(107)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
flutter engine successfully started up.
Initializing Input devices...
  input device 0: path="/dev/input/event0"
      Cooler Master Technology Inc. MASTERKEYS PRO S, connected via USB. vendor: 0x2516, product: 0x003C, version: 0x0111
  input device 1: path="/dev/input/event1"
      Cooler Master Technology Inc. MASTERKEYS PRO S System Control, connected via USB. vendor: 0x2516, product: 0x003C, version: 0x0111
  input device 2: path="/dev/input/event2"
      Cooler Master Technology Inc. MASTERKEYS PRO S Consumer Control, connected via USB. vendor: 0x2516, product: 0x003C, version: 0x0111
  input device 3: path="/dev/input/event3"
      Cooler Master Technology Inc. MASTERKEYS PRO S Keyboard, connected via USB. vendor: 0x2516, product: 0x003C, version: 0x0111
[ERROR:engine/src/flutter/shell/common/shell.cc(213)] Dart Error: Can't load Kernel binary: Invalid kernel binary format version.
[ERROR:engine/src/flutter/shell/common/engine.cc(200)] Could not prepare to run the isolate.
[ERROR:engine/src/flutter/shell/common/engine.cc(139)] Engine not prepare and launch isolate.
Running IO thread...
[ERROR:engine/src/flutter/shell/common/shell.cc(485)] Could not launch engine with configuration.
Running message loop...```
@GioPan04
Copy link

GioPan04 commented Jul 8, 2020

With which flutter version you compiled the app?

@Clancey
Copy link
Author

Clancey commented Jul 8, 2020

Latest stable.

@GioPan04
Copy link

GioPan04 commented Jul 8, 2020

The prebuilt engines are compiled for flutter 1.17 if I remember correctly. Try to built yourself for your flutter version

@ardera
Copy link
Owner

ardera commented Jul 8, 2020

Works fine for me with latest stable.

The only way this error can happen is when there is a version mismatch between flutter SDK and flutter engine. Minor version mismatches are okay, i.e. a 1.17.0 engine should work with a 1.17.5 SDK (it's not impossible that it won't work, in which case I'll just upload updated binaries.). The latest engine binaries I provide are for 1.17.0.

Are you sure the flutter engine you have installed on your target are the latest ones I provide on engine-binaries?

@Clancey
Copy link
Author

Clancey commented Jul 8, 2020

So I had the right engine, but it looks like the build machine was on dev channel, Sorry about that!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants