You are not logged in.

#1 2015-01-28 04:49:39

TripleE
Member
From: Houston, TX
Registered: 2006-10-10
Posts: 64

GDM give blank screen after upgrading to wayland-1.6.1-1 on Chromebook

I have a Chromebook 14 with a Intel Celeron 2955U. I just upgrade to wayland-1.6.1-1 and rebooted to find out the my screen is just blank. I rebooted in the arch installer on my flash drive and downgraded back to wayland-1.6.0-1 and everything is working fine now. I tried looking for error logs at /var/log/gdm/ but there is nothing there. Does this sound like a bug or is there a way I can provide detailed information for someone to investigate further? Maybe it is just me. FYI, I am running the chromebook 3.18.0-1-mainline-chromebook kernel. Could this be the issue? Thank for any help provided.

# uname -a
Linux chromebook 3.18.0-1-mainline-chromebook #1 SMP PREEMPT Sat Nov 22 00:03:35 CST 2014 x86_64 GNU/Linux


HP Chromebook 14

Offline

#2 2015-01-28 19:42:06

noctlos
Member
Registered: 2013-08-26
Posts: 36

Re: GDM give blank screen after upgrading to wayland-1.6.1-1 on Chromebook

I am also experiencing this problem, but it is not limited to GDM. Starting any wayland compositor (weston, etc.) gives a black screen. Will post error message.

Date: 2015-01-28 MST
[12:44:15.130] weston 1.6.0
               http://wayland.freedesktop.org/
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=1.6.0
               Build: 1.5.93-5-g2858cc2 configure.ac: bump version to 1.6.0 (2014-09-19 13:40:14 +0300)
[12:44:15.130] OS: Linux, 3.17.2-2-sp3_type-cover, #1 SMP PREEMPT Tue Nov 11 16:02:15 CET 2014, x86_64
[12:44:15.131] Using config file '/home/thonx/.config/weston.ini'
[12:44:15.131] Loading module '/usr/lib/weston/drm-backend.so'
[12:44:15.134] initializing drm backend
[12:44:15.134] using /dev/dri/card0
[12:44:15.134] Loading module '/usr/lib/weston/gl-renderer.so'
[12:44:15.155] warning: EGL_EXT_swap_buffers_with_damage not supported. Performance could be affected.
[12:44:15.156] input device 'Video Bus', /dev/input/event1 is a keyboard
[12:44:15.156] not using input device '/dev/input/event0'.
[12:44:15.156] not using input device '/dev/input/event4'.
[12:44:15.156] not using input device '/dev/input/event5'.
[12:44:15.156] not using input device '/dev/input/event6'.
[12:44:15.157] input device 'Microsoft Surface Type Cover', /dev/input/event13 is a pointer caps = absolute-motion relative-motion button
[12:44:15.157] input device 'Microsoft Surface Type Cover', /dev/input/event13 is a keyboard
[12:44:15.157] input device 'Microsoft LifeCam Front', /dev/input/event9 is a keyboard
[12:44:15.157] input device 'Microsoft LifeCam Rear', /dev/input/event10 is a keyboard
[12:44:15.157] not using input device '/dev/input/event3'.
[12:44:15.157] not using input device '/dev/input/event7'.
[12:44:15.157] not using input device '/dev/input/event8'.
[12:44:15.247] input device 'NTRG0001:01 1B96:1B05 Pen', /dev/input/event11 is a pointer caps = absolute-motion button
[12:44:15.248] input device 'NTRG0001:01 1B96:1B05', /dev/input/event12 is a touch device
[12:44:15.248] not using input device '/dev/input/event2'.
[12:44:15.248] launching '/usr/libexec/weston-keyboard'
[12:44:15.250] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[12:44:15.254] EGL version: 1.4 (DRI2)
[12:44:15.254] EGL vendor: Mesa Project
[12:44:15.254] EGL client APIs: OpenGL OpenGL_ES OpenGL_ES2 OpenGL_ES3 
[12:44:15.254] EGL extensions: EGL_MESA_drm_image EGL_MESA_configless_context
               EGL_WL_bind_wayland_display EGL_KHR_image_base
               EGL_KHR_image_pixmap EGL_KHR_image EGL_KHR_gl_texture_2D_image
               EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image
               EGL_KHR_surfaceless_context EGL_KHR_create_context
               EGL_EXT_buffer_age EGL_EXT_image_dma_buf_import
[12:44:15.254] GL version: OpenGL ES 3.0 Mesa 10.4.3
[12:44:15.254] GLSL version: OpenGL ES GLSL ES 3.0
[12:44:15.254] GL vendor: Intel Open Source Technology Center
[12:44:15.254] GL renderer: Mesa DRI Intel(R) Haswell Mobile 
[12:44:15.254] GL extensions: GL_EXT_blend_minmax GL_EXT_multi_draw_arrays
               GL_EXT_texture_filter_anisotropic
               GL_EXT_texture_compression_dxt1 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_standard_derivatives
               GL_OES_stencil8 GL_OES_texture_3D GL_OES_texture_npot
               GL_OES_EGL_image GL_OES_depth_texture
               GL_OES_packed_depth_stencil GL_EXT_texture_type_2_10_10_10_REV
               GL_OES_get_program_binary GL_APPLE_texture_max_level
               GL_EXT_discard_framebuffer GL_EXT_read_format_bgra
               GL_NV_fbo_color_attachments GL_OES_EGL_image_external
               GL_OES_vertex_array_object GL_ANGLE_texture_compression_dxt3
               GL_ANGLE_texture_compression_dxt5 GL_EXT_texture_rg
               GL_EXT_unpack_subimage GL_NV_draw_buffers GL_NV_read_buffer
               GL_EXT_map_buffer_range GL_OES_depth_texture_cube_map
               GL_OES_surfaceless_context GL_EXT_color_buffer_float
               GL_EXT_separate_shader_objects GL_EXT_shader_integer_mix
               GL_KHR_context_flush_control
[12:44:15.254] GL ES 2 renderer features:
               read-back format: BGRA
               wl_shm sub-image to texture: yes
               EGL Wayland extension: yes
[12:44:15.254] Chosen EGL config details:
               RGBA bits: 8 8 8 8
               swap interval range: 0 - 0
[12:44:15.254] Failed to initialize backlight
[12:44:15.254] EDID data 'SEC', '', ''
[12:44:15.254] Output eDP1, (connector 18, crtc 7)
               mode 2160x1440@60.0, preferred, current
               mode 2160x1440@48.0
[12:44:15.255] Compositor capabilities:
               arbitrary surface rotation: yes
               screen capture uses y-flip: yes
[12:44:15.256] Loading module '/usr/lib/weston/fullscreen-shell.so'
[12:44:15.256] Loading module '/usr/lib/weston/xwayland.so'
[12:44:15.260] xserver listening on display :1
[12:44:15.290] input_method died, respawning...
[12:44:15.290] launching '/usr/libexec/weston-keyboard'
[12:44:15.291] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[12:44:15.291] input_method died, respawning...
[12:44:15.291] launching '/usr/libexec/weston-keyboard'
[12:44:15.292] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[12:44:15.292] input_method died, respawning...
[12:44:15.292] launching '/usr/libexec/weston-keyboard'
[12:44:15.293] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[12:44:15.293] input_method died, respawning...
[12:44:15.293] launching '/usr/libexec/weston-keyboard'
[12:44:15.294] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[12:44:15.294] input_method died, respawning...
[12:44:15.294] launching '/usr/libexec/weston-keyboard'
[12:44:15.295] compositor: executing '/usr/libexec/weston-keyboard' failed: No such file or directory
[12:44:15.295] input_method died, giving up.
[12:44:18.611] deactivating session
[12:44:48.570] caught signal 15

Last edited by noctlos (2015-01-28 19:52:49)

Offline

#3 2015-01-31 19:26:56

TripleE
Member
From: Houston, TX
Registered: 2006-10-10
Posts: 64

Re: GDM give blank screen after upgrading to wayland-1.6.1-1 on Chromebook

OK, so I have had a chance to play with this. I figured the only thing that may have caused the problem was the kernel I was using (mainline-chromebook). I reinstalled the uninstalled it and installed the regular linux kernel and rebooted with wayland 1.6.1-1 installed and the display is working now. Guess I will have to find another tweak to get restore working with my chromebook.


HP Chromebook 14

Offline

#4 2015-02-01 20:48:58

noctlos
Member
Registered: 2013-08-26
Posts: 36

Re: GDM give blank screen after upgrading to wayland-1.6.1-1 on Chromebook

I am also using a patched kernel. The linux-mainline kernel did not work when I tried it. I have yet to try it with the vanilla kernel.

Offline

Board footer

Powered by FluxBB