Installation Fails With "ln Respawning Too Fast"

[Sy Ali]

I did this:

* Download the files from: http://ewi546.ewi.utwente.nl/mirror/www.op...le/3.5.3/c1000/
* Follow the install instructions: http://openzaurus.berlios.de/Akita/Install

Upon reboot, I get:

INIT: ld "ln" respawning too fast: disabled for 5 minutes


Ideas?

And if OZ is all about GPE vs Opie, where do I make this decision?  Did I download a mega-bundle which includes both software packages?  I feel that I missed something completely, and the installation instructions left something very very important out (i.e. how to get and install GPE or Opie separately)

[bam]

go to here:
http://openzaurus.org/wordpress/2006/05/22...penzaurus-3541/

[Sy Ali]

go to here:
http://openzaurus.org/wordpress/2006/05/22...penzaurus-3541/
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]

Thanks, I'll check out 3.5.4.1-test/rc4

download:
[a href=\"http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4.1-test/rc4/images/akita/]http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4...4/images/akita/[/url]

announcement:
http://openzaurus.org/wordpress/2006/05/22...penzaurus-3541/

announcement thread:
https://www.oesf.org/forums/index.php?showtopic=18318

[edit]

The problem persists with 3.5.4.1-rc4

I used gpe-image-3.5.4.1-rc4-akita.rootfs.img and renamed it to rootfs.img .. was this the correct thing to do?

There are no additional installation instructions which would advice me to do something different, but there are other rootfs files there which I could use.

[edit]
   
The problem persists with using bootstrap-image-3.5.4.1-rc4-akita.rootfs.img

I'll guess that the issue is with my partitioning, but I have not seen advice on repartitioning.

A simple boot image would need to exist, preferably with a nice automated script like pdaXrom or just with a basic shell. Then I could do it.. but I'm not sure what to do to get to that point. =)

I'll revisit this ROM later.
User is online!Profile CardPM
   
[edit]

Ok, as this error has been reproduced with pdaXrom 1.1.0beta4 where a previous installation of 1.1.0beta4 succeeded, I can only assume that this is a partitioning or NAND issue.

I will perform a complete NAND restore from my original Sharp NAND, and I am certain that the problem will be fixed.

[edit]

The NAND restore did not resolve the issue.  I must be using the wrong files to flash with.  Oh well.. maybe better installation instructions are needed?  I give up.  =)

[lardman]

I used gpe-image-3.5.4.1-rc4-akita.rootfs.img and renamed it to rootfs.img .. was this the correct thing to do?

No. It should be renamed to initrd.bin, not rootfs.img

Installation instructions here (linked from the top bar above the announcement of the 3.5.4.1 release):

http://wiki.openzaurus.org/Install

These are the same ones you used - they need some editting to give more detail on the filenames


Si

[Sy Ali]

rename gpe-image-3.5.4.1-rc4-akita.rootfs.img to initrd.bin

initrd.bin
updater.sh
zImage.bin

Now I get:

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

So I will do everything from scratch.. perhaps I have screwed up a different installation step.

[edit]

I have taken some time to revisit this, and I am doing everything the documentation describes.  I have also checked the md5sums of the three files I was using:

initrd.bin (gpe-image)
zImage.bin
updater.sh

All three files were from
http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4...4/images/akita/

initrd.bin:
http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4...kita.rootfs.img
zImage.bin
http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4....6.16-akita.bin
updater.sh
http://ewi546.ewi.utwente.nl/tmp/hrw/3.5.4...pdater.sh.akita

--

So if this problem is not with the installation routine, then it must be an issue with:
* partitioning
* the home folder
* maybe something else?

[lardman]

Sounds like the kernel can't find init - this could mean that the rootfs (initrd.bin) didn't flash (so it can't be found), or that you're using a kernel which was built using the Spitz defconfig and it's looking for init on the hdd (which you don't have).


Si

[Sy Ali]

If it's possible that the particular version of OZ I'm trying is a bad build for the C1000.. then I'll check out other revisions to try to reproduce the issue.

[edit]

Hey wait, there are no other revisions to try.  This looks like the first time OZ has been able to run on the C1000

[edit]

I reproduced the same error with all zinit.bin variants.

Just an aside, when initially doing the flash it does recognize the zinit.bin file, and it shows its byte size, but there is no progress bar for working with that file.  I see the 0% and 100% but no dots are displayed as its working, as with the next step.

So perhaps there is something wrong with the installer, in that it is finding and checking the zImage file but not doing anything with it?

Or you could be right about the boot process looking in the wrong place for the init stuff.  I could use another distro and boot up into a console and take a look, if I knew what to look for.  =)

[lardman]

I've asked and been told that the kernel is good, so the only other option is that your initrd.bin didn't flash, or has become corrupted somehow.

You could try to flash the hentges images from here:

http://hentges.net/tmp/do_not_use/Akita/


Si

[Sy Ali]

Got these files, and renamed them thusly:
updater.sh
inirtrd.bin (uncompressing it, of course)
zimage.bin

Checked the md5sums
wrote them out to the SD card
flushed my cache  =)

performed a regular install as per http://wiki.openzaurus.org/Akita/Install

When installing .. the second 0% ... 100% goes on for longer than it should, with 15% more periods.. then it gives a flash error, reboots and immediately gives:

Kernel panic - not syncing: No init found.  Try passing init= option to kernel.

[edit]

The same thing is seen when I use hentges-opie-image-akita_T1-RC6-3.5.4.1-rc4-akita.rootfs.ext2.gz (uncompressed, renamed to initrd.bin)

[CoreDump]

Got these files, and renamed them thusly:
updater.sh
inirtrd.bin (uncompressing it, of course)
zimage.bin

Checked the md5sums
wrote them out to the SD card
flushed my cache  =)

performed a regular install as per http://wiki.openzaurus.org/Akita/Install

When installing .. the second 0% ... 100% goes on for longer than it should, with 15% more periods.. then it gives a flash error

Ugh, not good. Well the "dots" not stopping at 100% is normal for this image but the flash error is a real problem.

Restore a NAND backup from trisoft.de and retry.

[Sy Ali]

I used my own reference NAND backup, and restored from it.

The trisoft.de files don't seem to make any sense .. I'm expecting systc100.dbk and the nand restore won't use the newer trisoft files. On request, I could use the trisoft ancient nand, as that is in the systc100.dbk "format".

I then re-attempted the flash installation using the last advice i had (above) using the gpe image.

I could see many more dots this time.  Probably 2x

However, I still got "Flash write error!" followed by a reboot that gave the same immediate kernel panic.

[CoreDump]

This is a correct NAND backup for Akita.
I believe your own backup is damaged
http://trisoft.de/download/C1000NAND240305.zip