+++ Wael Showair [2009-10-06 01:52 -0700]: > Hi All, > i have TS7800 board, it contains arm processor. > The board is shipped by linux kernel 2.6.21 & rootfs on its flash memory. both > of kernel image & filesystem binaries are built by gcc3.4. > > Now i am upgrading the kernel of the board to 2.6.29.5 which in turn must be > built by gcc4.3 i have successfully done this step but when i tried to use > this > new kernel image with the old filesystem i got the following error message: > > INIT: Id "T0" respawning too fast: disabled for 5 minutes > INIT: no more processes left in this runlevel
OK, so that means that the initial process is dying and being restarted repeatedly. One thing that could well be a problem: is the existing filesystem using the old arm ABI (OABI), but your new kernel has only been built with new (EABI) support (CONFIG_AEABI=y but not CONFIG_OABI_COMPAT=y)? > so i only have a doubt in the filesystem binaries, for sure they have been > built using gcc3.4 while my new kernel is built by gcc4.3 so this may be the > cause of the error so i decided to install simple debian rootfs for my board > from scratch? How can i do this? is there any simple guide to do this? yes. You can make a debian rootfs (assuming you have space) by using multistrap or debootstrap or cdebootstrap. Here is a page giving details: for multistrap: http://wiki.debian.org/Multistrap for debootstrap http://wiki.debian.org/EmDebian/DeBootstrap To have it work you will need to know a few things about your board - which filesystems to mount in /etc/fstab, which ports to add to /etc/securetty (allows root logins), which devices to run a getty on (in /etc/inittab) and which modules to load for e.g. networking to work, and a few others like /etc/hostname and /etc/hosts. Those files may well need modifying from the defaults in order to make a rootfs that boots/works. Wookey -- Principal hats: iEndian - Balloonboard - Toby Churchill - Emdebian http://wookware.org/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
