Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Martyn Welch <martyn@welchs.me.uk>
To: openembedded-devel@lists.openembedded.org
Subject: Booting image on iPAQ h5550
Date: Sun, 21 Mar 2010 16:45:10 +0000	[thread overview]
Message-ID: <4BA64D16.3070901@welchs.me.uk> (raw)

I've had a fair amount of success booting pre-built GPE images on an 
iPAQ h5550 I've got lying around in the past, so I thought I'd have a go 
at building an image for it myself and see what the latest stuff looks like.

I've succeeded in building the bootstrap, x11 and x11-gpe images 
(distro: angstrom, machine: h5000) and flashing them onto the iPAQ, but 
none are getting to a serial or GUI login.

The kernel boots and I see the kernel messages on the iPAQ screen and 
the serial console, with the bootstrap image I see user space running, 
on the x11 builds I see the Angstrom splash screen running on the iPAQ 
screen, but they don't show up on the serial console. After a while, on 
the x11 builds, the splash screen disappears and I can see the end of 
the user space boot messages.

If I plug in the USB cable from the dock, I see some ethernet gadget 
messages on both the serial console and screen, so the kernel at least 
still seems to be alive and it shows that the serial is at least working:

[  494.060000] usb0: full speed config #1: 100 mA, Ethernet Gadget, 
using CDC Ethernet Subset
[  494.150000] usb0: full speed config #1: 100 mA, Ethernet Gadget, 
using CDC Ethernet Subset

Also, if I leave the iPAQ a few minutes, the screen darkens, the screen 
light can be brought back by pressing one of the keys, so it seems that 
at least on daemon is alive. But I don't have any method to interact 
with the device beyond that.

The settings for the serial port seem good in the inittab (I double 
checked in a tar.gz image I built) and the links to the getty seem good 
(tinylogin).

The only thing I can think of is that udev is destroying the static dev 
nodes and not replacing them. I can to this conclusion because I see 
"Starting udev" in the user space boot messages on the screen, shortly 
followed by "Caching udev dev nodes", "Populating dev cache" then "root: 
mount: special device /dev/mtdblock2 does not exist". This node 
definitely exists in /dev in the tar.

I'm a little lost as to where to go from here, any suggestions?

Martyn



                 reply	other threads:[~2010-03-21 16:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4BA64D16.3070901@welchs.me.uk \
    --to=martyn@welchs.me.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox