Preinstalled Maverick netbook image has no display on omap3 EVM (no LCD)

(MLO attached.)

(u-boot attached.)

Thank you for taking the time to report this issue and help to improve Ubuntu.

The ubuntu-cdimage porject is for tracking bugs in the scripts used to assemble images for Ubuntu. Please file bugs such as this one against the responsible Ubuntu package instead (in this case: linux). Reassigning the bug.

You may wish to check if installing the linux-image-linaro-omap package from maverick corrects this issue for you; I know the linaro beta image included some last-minute fixes for omapfb, but I don't know if they apply to your situation.

I find this bug similar to bug 597904.

Using the patch from Pawel Moll (http://www.spinics.net/lists/linux-omap/msg34327.html) on top of Ubuntu-2.6.35-19.28, plus the small patch attached to enable vdds_sdi, the LCDis functional.

(Attaching the .config also.)

I fixed bug 597904 and I suspect the same problem is happening here - it probably stems from a missing regulator declaration in the board specific file.

Vincent, what board are you booting this on ?

Vincent,

I have applied the following patch:

http://marc.info/?l=linux-omap&m=126829773001754&w=2

and uploaded a kernel for your to test:

http://people.canonical.com/~mpoirier/linux-image-2.6.35-21-omap_2.6.35-21.30_armel.deb

It is indeed the same problem I had to fix on the beagle board.

Mathieu, thanks for your concern!

FYI: My board is an OMAP3 EVM rev. D (See http://www.mistralsolutions.com/products/omap_3evm.php).

I gave a try at your kernel, and I am sorry to report this is not working. Here is the UART log in attachment; you'll notice:

[ 8.257751] omapdss SDI error: can't get VDDS_SDI regulator
[ 8.257781] omapdss CORE error: Failed to initialize SDI

I think you need an additional patch (like mine in #6) to enable VDDS_SDI. Looking with 'git log', I did not find any in some kernel trees I track, which makes me think it might need to go "upstream" as well.

Bien évidamment que je pouvais pas l'avoir du premier coup...

Ok, j'y travaille.

Mathieu.

On Mon, 2010-09-13 at 21:45 +0000, Vincent Stehlé wrote:
> Mathieu, thanks for your concern!
>
> FYI: My board is an OMAP3 EVM rev. D (See
> http://www.mistralsolutions.com/products/omap_3evm.php).
>
> I gave a try at your kernel, and I am sorry to report this is not
> working. Here is the UART log in attachment; you'll notice:
>
> [ 8.257751] omapdss SDI error: can't get VDDS_SDI regulator
> [ 8.257781] omapdss CORE error: Failed to initialize SDI
>
> I think you need an additional patch (like mine in #6) to enable
> VDDS_SDI. Looking with 'git log', I did not find any in some kernel
> trees I track, which makes me think it might need to go "upstream" as
> well.
>
> ** Attachment added: "UART log of boot, VDDS_SDI missing."
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/630885/+attachment/1579975/+files/screenlog.2
>

"sdi_init" (dss/sdi.c:159), called by "omap_dss_probe" (dss/core.c:496) is specifically looking for a regulator named "vdds_sdi", something that isn't part of the patch I applied (see above) but part of the patch provided in #6.

Attached is the patch I used to generate "http://people.canonical.com/~mpoirier/linux-image-2.6.35-21-omap_2.6.35-21.30_armel.deb".

Please try it.

Thanks, it works (console displayed on LCD).

Mathieu, t'es une estie d'bon gars ! :)

SRU Justification:

Impact: When booting the omapdss subsystem is looking for a regulator named "vdds_sdi". When the regulator is not found the initialisation sequence is aborted, resulting in omapfb not finding a display to work with.

Fix: The problem was fixed by lumping a "vdds_sdi" with the already existing "vdds_dsi" regulator. This fix take its root from work done on the Beagle board and the Pandora board. More spefically:
 - 7b097896e4a5b5ea4798db806e63a1138b1b8eb8
 - f6873eedd94df20cfb705856a78440a4c176c6b6

Testcase:
 - When booting an EVM board without the patch there is no LCD display. When booting with the patch you get a graphical display.

SRU justification> do you mean that you're proposing this to be fixed via maverick-updates rather than in the maverick release? (You didn't subscribe either the ubuntu-release or the ubuntu-sru teams, so I'm not sure if "SRU" was just a typo here.)

no, i think the new kernel team policy is that after final freeze updates are treated like SRUs (someone might correct me if i misunderstood)

This should be fixed as of 2.6.35-22.33:

https://launchpad.net/ubuntu/+source/linux/2.6.35-22.33

linux (2.6.35-22.33) maverick; urgency=low

  [ Andy Whitcroft ]

  * Revert "SAUCE: Add support for Intellimouse Mode in ALPS touchpad on
    Dell E2 series Laptops"
    - LP: #641320

  [ Brian Rogers ]

  * SAUCE: ir-core: Fix null dereferences in the protocols sysfs
  * interface
    - LP: #624701

  [ Christopher James Halse Rogers ]

  * SAUCE: Nouveau: Add quirk framework to disable acceleration
    - LP: #544088, #546393
  * SAUCE: Nouveau: Disable acceleration on MacBook Pros
    - LP: #546393

  [ John Johansen ]

  * Revert "SAUCE: AppArmor: allow newer tools to load policy on older
    kernels"
  * SAUCE: AppArmor: allow newer tools to load policy on older kernels
    - LP: #639758

  [ Mathieu J. Poirier ]

  * SAUCE: Adding vdd_sdi regulator supply to OMAP3EVM

  [ Upstream Kernel Changes ]

  * ALSA: HDA: Enable internal speaker on Dell M101z
    - LP: #640254

 -- Leann Ogasawara <email address hidden> Fri, 17 Sep 2010 13:21:28 -0700

I confirm it works with daily image of 23-Sep.
I can see the console messages of filesystem check, resize, swap creation... nice :)