All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mr Dash Four <mr.dash.four@googlemail.com>
To: openembedded-devel@lists.openembedded.org
Subject: fso-console-image problems
Date: Fri, 02 Dec 2011 01:57:19 +0000	[thread overview]
Message-ID: <4ED8307F.2060306@googlemail.com> (raw)

I am trying to build the above image for htcdream (MACHINE=htcdream, 
DISTRO=shr), but ran into two problems:

1. The bitbake almost finished when I got an error from 
fso-console-image.bb that "cannot satisfy the following dependencies for 
task-fso-compliance: connman-plugin-udhcp". OK, I edited the recipe for 
the task-fso-compliance recipe and deactivated this plugin (I don't plan 
to use any dhcp clients at all), then removed all traces of 
"task-fso-compliance" to force a complete rebuild of this and restarted 
bitbake. The build was successful this time.

2. I then proceeded to unpack the newly-created 
"fso-console-image-htcdream.tar" (the phone rootfs) into my 
newly-formatted smartcard (a single ext3 partition) and then did the 
same with "modules-2.6.32-*.tar" (the kernel modules). I then used 
fastboot and executed  "fastboot boot zImage-2.6.32-*.fastboot" to load 
the new kernel and boot the smartphone. The phone boots up, but the only 
thing I am seeing is a black-and-white stripes boot up screen (this is a 
splash image embedded into the kernel image) and then nothing happens at 
all.

I then tried passing various combinations of the kernel command line 
parameters via fastboot:

console=tty1 no_console_suspend=1 root=/dev/mmcblk0p1 rootdelay=8 
fbcon=rotate:1
console=tty0 no_console_suspend=1 root=/dev/mmcblk0p1 rootdelay=8 
fbcon=rotate:1
console=tty1 no_console_suspend=1 root=/dev/mmcblk0p1 rootdelay=8 
fbcon=rotate:1 nomodeset

etc etc etc, but to no avail - nothing apart from the damned 
black-and-white stripes screen just sitting there!

As a last resort I then did a complete rebuild (wiped out build/tmp and 
started from scratch with the modified recipe for task-fso-compliance to 
exclude the connman-plugin-udhcp plugin) and when it finished I repeated 
the same steps as above - nothing, exactly the same screen, NADA!

If I build shr-image all is well - the black-and-white-stripes bootup 
screen is soon replaced by the SHR logo and then I get the SHR Desktop 
after a while and I have a GUI. When I try to build "console-image" 
(similar in many ways to fso-console-image - simple cli interface), I am 
stuck also at the same step as above, but with a tiny difference - the 
black-and-white stripes screen is replaced after a short period of time 
with the OpenEmbedded logo with an empty progress bar and then I am 
stuck at this stage - nothing happens after that at all.

What am I doing wrong or am I missing something obvious here? Help is 
very much appreciated!



             reply	other threads:[~2011-12-02  2:04 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  1:57 Mr Dash Four [this message]
2011-12-02 10:20 ` fso-console-image problems Denis 'GNUtoo' Carikli
2011-12-02 14:08   ` Mr Dash Four
2011-12-02 14:52     ` Martin Jansa
2011-12-02 15:12       ` Mr Dash Four
2011-12-02 15:46         ` Martin Jansa
2011-12-02 16:20           ` Mr Dash Four
2011-12-02 16:25             ` Martin Jansa
2011-12-02 17:27       ` Denis 'GNUtoo' Carikli
2011-12-02 17:42         ` Mr Dash Four
2011-12-02 20:06       ` Mr Dash Four
2011-12-02 22:24         ` Denis 'GNUtoo' Carikli
2011-12-02 23:35           ` Mr Dash Four
2011-12-02 23:50             ` Mr Dash Four
2011-12-03  9:46               ` Denis 'GNUtoo' Carikli
2011-12-03 16:37                 ` Mr Dash Four
2011-12-03 16:52                   ` Martin Jansa
2011-12-03 17:47                     ` Mr Dash Four
2011-12-03 18:03                       ` Martin Jansa
2011-12-03 18:35                         ` Mr Dash Four
2011-12-04 12:39                           ` Mr Dash Four

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4ED8307F.2060306@googlemail.com \
    --to=mr.dash.four@googlemail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.