No video output from Ubuntu Desktop ARM Images on my Pandaboard to my DVI monitor

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 961133

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Serial port output from above shows "rootfstype=ext3" which is a curiosity.

Related lines:
 EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
 No filesystem could mount root, tried: ext3
 Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)

I have a pandaboard revision A1

I move the boot.scr file to Env.txt and remove the first line of non-human readable characters and remove "quiet splash" from linux boot options

13:21 < ogra_> give me the serial output of a freshly downloaded and dd'ed image, lets see if it loads initrd
13:21 < ogra_> and to be 100% sure, make sure to zero out the card before dd'ing
13:23 < ogra_> sudo dd if=/dev/zero of=/path/to/your/SD/device bs=1M count=<make a pick how many megs you want to wipe>
13:23 < ogra_> i would suggest something like 10-20M for the count= value

as of today (21th March 2012), the desktop preinstalled omap4 image work in mu panda A1:

http://cdimage.ubuntu.com/daily-preinstalled/current/precise-preinstalled-desktop-armhf+omap4.img.gz

zcat Downloads/precise-preinstalled-desktop-armhf+omap4.img.gz | sudo dd of=/dev/sdX bs=4M

where X is you device letter.
Put the resulting sd card in the panda sd slot, power the board, follow the installation procedure and you are done.

The board does not boot so they cannot easily get those logs for now.

when you say that the validation image works, are you 100% sure you dont have still bits of it on your SD ? the rootfs and rootwait options were never in any ubuntu image and it is not clear what you are booting.

aside from that, who told you to remove the whole first line from the boot.scr, this will definitely not boot anymore since it is the line that contains the load command for the kernel. at most you can delete the first few (unreadable) chars from that line, but not the complete line.

ubuntu desktop 2012-03-23 daily boot log rebooted twice at ~10 minute internals

Current thinking is the graphics driver is at fault:
16:15 < ogra_> Riddell, between oneiric and precise the graphics driver was cvompletely redone by TI, that might explain your issues
16:16 < ogra_> Riddell, talk to robclark if he knows anything about issues with that monitor (he maintains the graphics stack and we actually know that some monitors and brands
               dont work well at all)
16:22 < ogra_> Riddell, just run through the server install, then edit /boto/boot.script and change the bootargs there ... then you run sudo flash-kernel and reboot

dmesg output from ubuntu server when plugged into my monitor

dmesg output when plugged into another monitor

I installed linux-ti-omap4 from ppa:tiomap-dev/omap-trunk version 3.3.0.1481

I now get a console on the monitor when it is plugged into the DVI port (but not when plugged into the HDMI port)

So I hope the driver in that linux build can be backported

Trying with today's beta 2 candidate images and my DVI monitor it did not work using either monitor output.

I got hold of another HDMI monitor and trying today's beta 2 candidate image with it, it does work but only on the HDMI output and only at 600x800 resolution.

So I fear this graphics driver does have issues talking to monitors.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/961133

Bumping this to high as it makes Ubuntu Desktop OMAP4 ARM images completely unusable. In addition, this also affects display output on Ubuntu Server.

Update, on ubuntu server, after a full powercycle, I got display. Looks like Ubuntu Server OMAP has a different bug, and not this one. Sorry for the false alarm.