On 07/09/2015 03:17 PM, g...@novadsp.com 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.
So you see the dhcp request, bump up the logging level on your dhcp
server, look at it's logs. Could be a config issue with dpcp server.
Does Wireshark show unique mac address in the dhcp request?
Mike
--
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 beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
