Hi Steve, I am not sure about EFI. My PC is not at all new (Dell E521) 
and it seems to have a standard BIOS to me. The only slightly unusual 
thing is that I boot it from an external USB hard drive, as this is all 
just experimental. My SATA drive still has 10.04 on it. Is it possible 
that the system "thinks" I have EFI when I dont, and that is messing 
things up?


On 04/05/12 21:12, Steve Langasek wrote:
> Thanks, yes, you added it correctly and that's the logfile we're looking
> for.
>
> This particular log shows that plymouth could not find any graphical
> output to connect to, which is unusual.
>
> [./plugin.c]                                create_backend:creating renderer 
> backend for device /dev/dri/card0
> [./plugin.c]                                   load_driver:Attempting to load 
> driver '(null)'
> [./plugin.c]                                   load_driver:drmOpen failed
> [ply-renderer.c]                             ply_renderer_open:could not open 
> rendering device for plugin /lib/plymouth/renderers/drm.so
> [./plugin.c]                                create_backend:creating renderer 
> backend for device /dev/fb0
> [ply-terminal.c]                             ply_terminal_open:trying to open 
> terminal '/dev/tty7'
> [ply-terminal.c]                 ply_terminal_look_up_geometry:looking up 
> terminal text geometry
> [ply-terminal.c]                 ply_terminal_look_up_geometry:terminal is 
> now 80x43 text cells
> [./plugin.c]                                  query_device:Visual is 
> FB_VISUAL_TRUECOLOR; not using graphics
> [ply-renderer.c]                             ply_renderer_open:could not 
> query rendering device for plugin /lib/plymouth/renderers/frame-buffer.so
>
> What's unusual here is that FB_VISUAL_TRUECOLOR is exactly the one we
> want.
>
> Can you install the fbset package, and try running the following
> command:
>
>    sudo fbset -i
>
> I also see in your dmesg output that this is a system that boots with
> EFI.  So it's possible there's a race condition here in the handoff
> between the EFI framebuffer and the nouveau framebuffer, that causes
> plymouth-splash to try to start too early.
>
> ** Summary changed:
>
> - blank screen on startup
> + [nouveaufb, efifb] blank screen on startup
>
> ** Summary changed:
>
> - [nouveaufb, efifb] blank screen on startup
> + [nouveaufb, efifb] blank screen on startup, "Visual is FB_VISUAL_TRUECOLOR; 
> not using graphics"
>
> ** Changed in: plymouth (Ubuntu)
>     Importance: Undecided =>  Medium
>
Scanned by Google Postini - Managed email security from Google Apps

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/989793

Title:
  [nouveaufb, efifb] blank screen on startup, "Visual is
  FB_VISUAL_TRUECOLOR; not using graphics"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/989793/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to