[ply-renderer.c] ply_renderer_open_plugin:trying to open renderer plugin /lib/plymouth/renderers/drm.so [./plugin.c] create_backend:creating renderer backend for device /dev/dri/card0 [./plugin.c] load_driver:Attempting to load driver 'radeon' [...] [./plugin.c] query_device:Could not initialize heads [ply-renderer.c] ply_renderer_open_plugin:could not query rendering device for plugin /lib/plymouth/renderers/drm.so [./plugin.c] close_device:closing device [./plugin.c] unload_driver:unloading driver [ply-renderer.c] ply_renderer_open_plugin:trying to open renderer plugin /lib/plymouth/renderers/frame-buffer.so [./plugin.c] create_backend:creating renderer backend for device /dev/fb0 [...] [./plugin.c] query_device:32 bpp (8, 8, 8, 0) with rowstride 6912 [./plugin.c] initialize_head:initializing 1680x1050 head [ply-renderer.c] ply_renderer_open_plugin:opened renderer plugin /lib/plymouth/renderers/frame-buffer.so
So this appears to be opening the framebuffer at the right resolution, which suggests it ought to work. However, it *should* be opening with the DRM driver, and this is failing, leading to a fallback to the framebuffer driver. ** Summary changed: - monitor inactive during plymouth animation + monitor inactive during plymouth animation (radeon, fallback to /dev/fb0) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1056468 Title: monitor inactive during plymouth animation (radeon, fallback to /dev/fb0) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1056468/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
