ubuntu: /dev/fb0 is not created unless there is a screen connected to the board

Bug #1012026 reported by Alexandros Frantzis
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
IglooCommunity
New
Wishlist
vathsala

Bug Description

Unless there is a screen connected to the HDMI port, /dev/fb0 is not created. The HDMIservice init script keeps waiting in a loop for /dev/fb0 to come up.

A side effect of this is that X11 doesn't start if there is no screen connected, because it uses /dev/fb0. This makes it impossible to run any graphics related tests in the LAVA lab for snowball boards, as they are not connected to monitors.

For example, here is the log of an attempt to run the Linaro Graphics tests on snowball: http://validation.linaro.org/lava-server/dashboard/streams/anonymous/alf/bundles/eabd40abecb50c9c62b41f53b6f683092c11a230/8f351fee-b3a5-11e1-9729-68b599be548c/attachments/79587/

At line 4396 (and at many other points in the log) it can be clearly seen that we can't communicate with the X server: "xhost: unable to open display ":0""

Changed in igloocommunity:
milestone: none → 2012.08
importance: Undecided → Medium
assignee: nobody → vathsala (vathsala-nagaraju)
milestone: 2012.08 → 2012.07
tags: added: graphics ubuntu
Changed in igloocommunity:
milestone: 2012.07 → 2012.08
Changed in igloocommunity:
milestone: 2012.08 → none
importance: Medium → Wishlist
tags: added: linaro-ubuntu
removed: ubuntu
Revision history for this message
Kalle Vahlman (kvahlman) wrote :

I think this bug/feature can be worked around with this kernel option:

  http://www.igloocommunity.org/gitweb/?p=kernel/igloo-kernel.git;a=blob;f=drivers/video/mcde/Kconfig#l60

Maybe there's no need to "fix" this in other ways?

The idea here is, if I understand it correctly, that the framebuffer is created only after negotiating a video mode so that the framebuffer will be of the correct size for the resolution (ie. no overallocation).

While the idea is reasonable, I'm not sure how useful that is in practise though.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.