Kubuntu Mobile Maverick on Omap3 & Omap4: screen goes black and never comes back

Bug #657281 reported by Marjo F. Mercado
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Expired
Undecided
Unassigned

Bug Description

Submitting on behalf of Mathieu Poirier.

Note that during the installation process the display is working and the resolution set correctly. After the installation, the installer reboots the board and users are presented with the expected login prompt. Once again, display is working and the resolution set properly. This behavior is the same on both omap3 and omap4 boards.

After typing in your username and password in the dialog box and press login, you get the following behaviors:

Omap3: The screen goes black and never come back. The white arrow representing the mouse can be moved around but nothing else can be seen.

Omap4: The KDE initialization panel is displayed and you see the various
icons appearing one after the other. Once initialized, the screen goes
black and never comes back.

VGA is still alive since the monitor doesn't go in power saving mode.

Tags: armel
description: updated
summary: - Kubuntu Maverick on Omap3: screen goes black and never come back
+ Kubuntu Maverick on Omap3 & Omap4: screen goes black and never come back
summary: - Kubuntu Maverick on Omap3 & Omap4: screen goes black and never come back
+ Kubuntu Maverick on Omap3 & Omap4: screen goes black and never comes
+ back
Revision history for this message
Emmet Hikory (persia) wrote : Re: Kubuntu Maverick on Omap3 & Omap4: screen goes black and never comes back

How much RAM was available on the tested omap device? At least for me (256MB), the OOM killer kills KDE before it can get started, which results in a black screen: if this is the issue, it's notabug, as the minimum RAM requirements for all flavours of Ubuntu are 384MB (yes, some flavours can kinda run with less than this, but not officially).

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Fabio Marconi (fabiomarconi) wrote :

In this case you can try installing from alternate version
for maverick
http://cdimage.ubuntu.com/kubuntu/daily/20101007/maverick-alternate-i386.iso

Changed in ubuntu:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Oliver Grawert (ogra) wrote :

there is no alternate version for any of the OMAP architectures, we only support the preinstalled images in maverick

Revision history for this message
Oliver Grawert (ogra) wrote :

Oh, and note that the initial report talks about OMAP4, all OMAP4 images use 768M currently. The bug is very likely caused by the fact that omap only uses the framebuffer and no video HW acceleration at all. i will do a verification test tomorrow. On OMAP3 only the beagle XM with 512M should be used for KDE based images.

Revision history for this message
Tobin Davis (gruemaster) wrote :

It would appear that the kubuntu-preinstalled-mobile-omap* images are either corrupted or incompletely built. There is no filesystem.

Here is what a desktop img file looks like:
> file maverick-preinstalled-desktop-armel+omap4.img
maverick-preinstalled-desktop-armel+omap4.img: x86 boot sector; partition 1: ID=0xc, active, starthead 1, startsector 63, 144522 sectors; partition 2: ID=0x83, starthead 0, startsector 144585, 4128705 sectors, code offset 0x0

These images:
> file maverick-preinstalled-mobile-armel+omap4.img
maverick-preinstalled-mobile-armel+omap4.img: Linux rev 1.0 ext3 filesystem data, UUID=66183d73-8be3-46b7-86fc-74066056aa96 (large files)

This is an image build issue.

Oliver Grawert (ogra)
tags: added: armel
Oliver Grawert (ogra)
summary: - Kubuntu Maverick on Omap3 & Omap4: screen goes black and never comes
- back
+ Kubuntu Mobile Maverick on Omap3 & Omap4: screen goes black and never
+ comes back
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
Revision history for this message
Ian Lawrence (ianlawrence) wrote :

this seems to still be an issue. Can someone take a look at the build?

Changed in ubuntu:
status: Expired → New
Revision history for this message
Tobin Davis (gruemaster) wrote :

I'm marking this as incomplete as it is for a tech preview image that isn't supported (kubuntu-mobile), and there is no defined package that this fails on. As to the images being incomplete, this seems to have been finally resolved just prior to natty release (mirror sync timing issue).

Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Ubuntu because there has been no activity for 60 days.]

Changed in ubuntu:
status: Incomplete → Expired
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.