So this is new. When I rebooted to check the boot process, it took the IP
address immediately, started loading Uboot, but restarted around block 162.
Wireshark shows multiple packets of the same number being send and
acknowledged.
Yes, I'm using dnsmasq.
U-Boot 2008.10-svn3231 (Jul 15 2010 -
I have no issues with the Roach2 that is also connected to this host
computer.
I switched the Roach1's and Roach'2 ethernet cables and still have the same
problem on the Roach1 and Roach2 is still working fine.
Which pins / voltages should I be checking on the power supply?
Brad Dober
Ph.D.
Hi, Brad,
On May 27, 2015, at 9:37 AM, Brad Dober wrote:
I have no issues with the Roach2 that is also connected to this host computer.
No issues meaning that you can tftp the uImage file from the server to the
roach2? Does tcpdump/wireshark show any clues vis a vis the ROACH1's attempted
So I plugged my other Roach1 that's in the lab into where the troubled
Roach1 was sitting and started up the netboot. The uImage transferred fine
this time, but I got another problem: *VFS: Unable to mount root fs via
NFS, trying floppy.*
*VFS: Cannot open root device
There was a very long thread about this new problem a few weeks ago.
Bottom line is that it's likely that your host isn't exporting the
filesystem correctly, there's a typo in the DHCP offer, or some other such
host problem. Look in the mail archives...
John
So I plugged my other Roach1
Hi, Brad,
On May 27, 2015, at 1:15 PM, Brad Dober wrote:
Kernel command line: console=ttyS0,115200
mtdparts=physmap-flash.0:1792k(linux),256k@0x1c(fdt),8192k@0x20(root),54656k@0xa0(usr),256k@0x3f6(env),384k@0x3fa(uboot)fdt_addr=0xfc1c
Hi Dave,
Here is the configuration of the network. The host computer, a ROACH1 and a
working ROACH2 running in soloboot are the only ones connected. The host is
192.168.40.1 and is offering 192.168.100.50 and the ROACH2 is assigned to
192.168.40.50. Is there anything weird about how the ROACH1
Nothing obvious comes to mind (yet). Can you watch the roach1 boot process via
serial console? What does that show? Are you using dnsmasq for the DHCP
server? What if you try direct connect with mii-tool to set the speed of eth1
to 100 Mbps?
Dave
On May 26, 2015, at 5:00 PM, Brad Dober
I've switched to NFS boot to avoid SD card corruptions.
However, when attempting to run netboot, the roach will send an IP
discover, the host will offer one, and then the roach will send a discover
again.
This goes on for 10-15 times when finally the roach will request the
correct IP, and the
Are you trying to run the ROACH1 on 1 GbE? ROACH1 is not reliable on 1 GbE.
You have to force it to be 100 Mbps. This can be done by using an unmanaged
non-gigabit switch (or hub), a managed switch that can force its port for the
ROACH1 to be 100 Mbsp only. For direct connect, you'll have
Hi Dave,
I switched to a 100 Mbps switch, and now I'm still getting the ROACH1
continuously sending DCHP discovers, and my host computer continuously
sending offers, but now the occasional request/acknowledge and uboot
download is no longer happening.
For what it's worth, I am not using jumbo
Weird. Are there any other hosts on the network that might be also sending
(non-netboot-aware) DHCP offers?
What does sudo tcpdump -i eth0 -n -e -v port bootps or port bootpc show
(replacing eth0 with the actual network interface name where the DHCP activity
is).
Dave
On May 26, 2015, at
Hi Casperites,
I have a Roach1 which is booting from an SD card.
I booted it up yesterday, and it was displaying the STALE NFS handle
error that other people have seen in the past (which suggested a corrupt
flash card). I ran fsck and fixed several errors, and when rebooting, the
stale nfs handle
I ran into this a lot when trying to use the sdcard filesystem. I think the
problem is that the filesystem is ext2 or something old like that which is
prone to corruption if the system is hard rebooted. My advice is use NFS
file system.
On May 20, 2015 1:20 PM, Brad Dober do...@sas.upenn.edu
14 matches
Mail list logo
