Ok, that is interesting. So before making any changes( you really do not want to complicate thing right now, any more than you have to ). From the NFS server issue the command:
*sudo exportfs* and paste the output to us here. I'm thinking from the sound of it assuming every board is configured exactly alike, that you only have one address export. Which is why you're only getting one board to load over NFS / TFTP On Thu, Jul 9, 2015 at 12:17 PM, <[email protected]> wrote: > I got down to the stage of using Wireshark to trace the DHCP requests made > during boot. The good board issues one, immediately gets an address and > proceeds to the TTY. The others issue 2 DHCP requests that are never > acknowledged, despite apparently continuing to retry (as per the serial log > content). 'Interestingly' the same boards are slow at exactly the same > point when booting off an SD card. So I really am at a loss here. Bear in > mind all 3 have identical flashed images, uEnv settings and are using the > same TFTP server + NFS filesystem. > > There is a bug report from late 2014 regarding a problem in ifup ( > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=771943) which mentions > system.debug-shell. I've got this added to the kernel command line but not > sure if it is accessible. > > Does the omap-image-builder Ubuntu distro work with NFS? > > TAIA. > > > > -- > 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. > -- 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.
