My Gpe-image Won't Boot

[ins0mniaque]

Hi! I'm trying to get a working environment to build some applications on my loved spitz. I followed the instructions in OpenEmbedded | Getting Started, and started "bitbake gpe-image". After having solved three lil problems :

1. linux-openzaurus 2.6.17 doesn't compile due to syntax error
2. Freetype 2.2.1 link error (libz in wrong location)
3. gpe-mini-browser: fetch failed, server does not answer to "PASV". (I got the file elsewhere).

Everything then compiled without problems.

so I took the files in build/tmp/deploy/images and copied them to a CF card :

gnu-tar -> gnu-tar
updater.sh.spitz -> updater.sh
zImage-2.6.17-spitz-20060731163151.bin -> zImage.bin
gpe-image-spitz-20060801210605.rootfs.tar.gz -> hdimage1.tgz


It "flashed" OK. But on boot up, I get:

Code: [Select]

INIT: cannot execute "/sbin/getty"
... (last line repeated 7 or 8 times)
INIT: cannot execute "/sbin/getty"
INIT: Id "1" respawning too fast: disabled for 5 minutes
INIT: cannot execute "/sbin/getty"
... (last line repeated 7 or 8 times)
INIT: cannot execute "/sbin/getty"
INIT: Id "S" respawning too fast: disabled for 5 minutes

I'm kinda stuck there. Any help will be appreciated.


JP

[lardman]

I don't know much about the Spitz, but....

I'd guess at the hdimage not flashing correctly - could this be something to do with the partition sizes? If you go to the recovery console, are there any files on the HDD?


Si

[ins0mniaque]

I don't know much about the Spitz, but....

I'd guess at the hdimage not flashing correctly - could this be something to do with the partition sizes? If you go to the recovery console, are there any files on the HDD?


Si
[div align=\"right\"][a href=\"index.php?act=findpost&pid=137640\"][{POST_SNAPBACK}][/a][/div]

/sbin/getty is on /dev/hda1...

I forgot one really important note in my previous message, I am compiling the dev branch...

I'm stuck there... any idea to figure out what is going on will be appreciated.

[lardman]

A post to the OE or OZ mailing list or a question on IRC (#oe or #openzaurus) would probably get you answers more quickly.


Si

[ins0mniaque]

Well, I was quite occupied this week, so I just checked this out today, and it doesn't happen in the lastest snapshot...

Thank you all for your help.