Has anybody seen this before? I have an android system where I use NFS for the root file system and use tftp to load the zImage.
Linux starts just fine and is able to source the init.rc file stored in the rootfs in /. At about the time Android starts, NFS server contact is lost and the console displays the famous message: nfs: server ###.###.###.### not responding, still trying. The message is displayed about six times. The target system still responds to pings. It also presents a prompt where I can do very limited commands. I traced the hang to something related to starting zygote, but I have no clue about what zygote might be doing that causes the hang. Commenting out zygote related lines in the init.rc keeps the system from hanging, but Android doesn't start. Here is the really odd thing: the problem only happens on Debian systems (both Debian 10 and Ubuntu 8.10 display the problem). I can serve the same zImage and root file system from Red Hat systems (Fedora 10 and RHEL5) with no problems at all. I can also mount the rootfs from the Debian machines to either the RedHat or Debian machines without issues. Any suggestions about what might be going on with Debian? Thanks Erik --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
