[regression] Origen: HDMI doesn't work with 3.2 kernel

Bug #906762 reported by Ricardo Salveti on 2011-12-20
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linaro Ubuntu
Ricardo Salveti
Fix Released
Tushar Behera

Bug Description

Using 11.12 RC on Origen, I'm unable to get any output with HDMI (monitor doesn't even turns itself on).

Hwpack: hwpack_linaro-leb-origen_20111219-1_armel_supported.tar.gz
Image: linaro-o-ubuntu-desktop-tar-20111219-0.tar.gz

This is using the 3.2-rc5 kernel from the Samsung LT.

visibility: private → public
Changed in linaro-ubuntu:
status: New → Confirmed
Changed in linaro-landing-team-samsung:
status: New → Confirmed
Changed in linaro-ubuntu:
importance: Undecided → High
summary: - Origen: HDMI doesn't work with 3.2 kernel
+ [regression] Origen: HDMI doesn't work with 3.2 kernel
Changed in linaro-ubuntu:
milestone: none → 11.12
assignee: nobody → Ricardo Salveti (rsalveti)
Matt Waddel (mwaddel) wrote :

Just out of curiosity, does the output recover if you disconnect the HDMI cable and plug it back in again?
If so, then it could be related to to bug #905493.

Ricardo Salveti (rsalveti) wrote :

No, it doesn't work at all with the current kernel.

Changed in linaro-ubuntu:
milestone: 11.12 → 12.01
Changed in linaro-landing-team-samsung:
assignee: nobody → Tushar Behera (tusharbehera)
Usman Ahmad (usman-ah) on 2012-01-24
Changed in linaro-landing-team-samsung:
importance: Undecided → High
milestone: none → 2012.02
Changed in linaro-ubuntu:
milestone: 12.01 → 12.02
Changed in linaro-landing-team-samsung:
status: Confirmed → In Progress
Tushar Behera (tusharbehera) wrote :

Updating xorg.conf like below enables HDMI display with Origen board.

Changed in linaro-landing-team-samsung:
status: In Progress → Fix Committed

On Mon, Feb 6, 2012 at 8:25 PM, Tushar Behera <email address hidden> wrote:
> Updating xorg.conf like below enables HDMI display with Origen board.

Question is, why can't we make it to work directly from the kernel
boot itself? Is there any reason to only make it to work with this
specific xorg config file?

Otherwise people will need to depend on X11 all the time just to know
if the kernel is giving any valid output (if they don't have the LCD

Tushar Behera (tusharbehera) wrote :

Giving a brief overview of current status:
Currently the LCD FB is registered as /dev/fb0 and the HDMI FB is registered as /dev/fb1. While booting up, by default /dev/fb0 is used as the primary display device and the output is routed accordingly.

If we don't enable support for LCD FB, the display comes on HDMI during boot-time, but again that might not be desirable considering many people would also like to use the LCD.

The earlier solution of routing LCD data to HDMI is basically a hack and that limits the HDMI display resolution to 1024x600. And considering the amount of effort required for it to work with newer V4L2-based HDMI driver, that is not a good idea either.

Is there any way where we can force the default frame-buffer (whether to choose /dev/fb0 or /dev/fb1) during boot-time?

tags: added: audio-hdmi
tags: removed: audio-hdmi
Ricardo Salveti (rsalveti) wrote :

I can confirm that the X11 works fine when we manually force the fb1 as the default output.

But I wonder if we could identify the default output at runtime, while booting the kernel, and then enable the default framebuffer. I believe it's easy to check if the lvds or hdmi output is enabled during boot.

Will close this bug and create another one to track how we could enable the hdmi output automatically.

Changed in linaro-ubuntu:
status: Confirmed → Fix Released
djesus (danieljpb) wrote :

Please check it:


add kernel command line option fbcon=map:1

This will tell the fbcon to map itself to the /dev/fb1 framebuffer dev and not the /dev/fb0, that in our case exist on the wrong graphics card.

Tushar Behera (tusharbehera) wrote :

Let this bug be closed in linaro-landing-team-samsung also. We will track the issue through the other bug filed for automatic detection.

Changed in linaro-landing-team-samsung:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers