Wow. I was dealing with issues trying to boot an NFS exported nfsroot with Angstrom Linux.. and was having this exact same issue. It would hang after booting to the login and display:
nfs: server <nfs ip> not responding, still trying removing /lib/systemd/system/conman.service does fix this problem. I am replying here as this is the only place I saw this mentioned. So, if you are having trouble booting from barebox into a custom kernel via tftp and attempting to mount the rootfs over nfs using Ångström linux.. (either don't use angstrom or delete the connman.service) On Sunday, January 19, 2014 at 6:12:28 PM UTC-5, [email protected] wrote: > > "If your NFS root freezes during boot with a message similar to: > > nfs: server 192.168.0.251 not responding, still trying > > Then it is possible the network connection used by the NFS connection has > been re-configured. On Angstrom, this connection is re-established by the > Connection Manager (ConnMan. <https://connman.net/about>) To quickly > overcome this problem, remove /lib/systemd/system/connman.service from your > rootFS." > > From Beyondlogic > > > Il giorno venerdì 2 agosto 2013 04:31:52 UTC+2, Marcel Claro ha scritto: >> >> I got sucessfully the boot-up of angstrom by NFS, but after appears >> "beaglebone login: ", appears: "nfs: server server.domain.name not >> responding, still trying" and then kernel panic after few seconds, anyone >> knows why? >> >> ps.: I try to follow this tutorial: >> http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-network-boot/ >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
