Hi ,Dave, I am happy to tell you that your thought is perfect right! It's a tcpborph problem. Follow your instructions, I copy the tcpborph3 from soloboot file /sbin to netboot file /usr/local/sbin. Then run netboot again the overflow problem go away! What's more interesting, I found the no-work-in-soloboot roach did not have tcpborph3 in /sbin file .I copy a tcpborph3 from the other roach through mount command to this soloboot problem roach.finally all of my roaches could work normally in netboot without overflow. However there is one thing left that when I run usr/local/sbin# /etc/init.d/tcpborphserver stop,It's ok , but when I run /etc/init.d/tcpborphserver start, it shows somehow a bit wired.
root@pf5:/usr/local/sbin# /etc/init.d/tcpborphserver start tcpborphserver: ... loading roach mmap driver ... insmod: can't read '/lib/modules/roach_mmap.ko': No such file or directory version *3* using mmap root@pf5:/usr/local/sbin# tcpborphserver3: about to go into background hwmon: create hwsensor could not open /sys/bus/i2c/devices/0-0018/temp1_input (No such file or directory) hwmon: create hwsensor could not open /sys/bus/i2c/devices/0-0018/temp2_input (No such file or directory) hwmon: create hwsensor could not open /sys/bus/i2c/devices/0-0018/temp3_input (No such file or directory) ... I am not sure whether it is a bug error,Any way it doesn't influence the netboot work. Now the version got through telnet like this: [peter@roachserver ~]$ telnet pf5 7147 Trying 192.168.100.5... Connected to pf5. Escape character is '^]'. #version memcpy-88-g38ad77a-dirty #build-state 2013-04-11T11:50:43 In the end, could you tell me what is the difference between tcpborph and borph and uImage? I just guess they may be the linux system run in Fpga PPC. Thanks for your help! Peter At 2014-11-16 01:27:25, "David MacMahon" <dav...@astro.berkeley.edu> wrote: >Hi, Peter, > >I forgot two steps and had a typo in that cp command (should be >tcpborphserver3): > ># Remount root filesystem to be read/write >mount -o remount,rw / > ># Copy the soloboot tcpborphserver3 executable to the netboot filesystem >cp /mnt/sbin/tcpborphserver3 /usr/local/sbin/. > ># Remount root filesystem to be read-only >mount -o remount,ro / > >And just to clarify, yes, these command should be run on the ROACH2 (i.e. do >"ssh root@pf1" to login to ROACH2, then do all the commands). > >Thanks (and sorry about that), >Dave > > >On Nov 14, 2014, at 5:54 PM, Peter Niu wrote: > >> >> >> >> >> At 2014-11-15 08:34:51, "David MacMahon" <dav...@astro.berkeley.edu> wrote: >> >Hi, Peter, >> > >> >On Nov 13, 2014, at 11:19 PM, 牛晨辉 wrote: >> > >> >> The soloboot one use the telnet: >> >> [root@roachserver Downloads]# telnet pf4 7147 >> >> Trying 192.168.100.4... >> >> Connected to pf4. >> >> Escape character is '^]'. >> >> #version memcpy-88-g38ad77a-dirty >> >> #build-state 2013-04-11T11:50:43 >> >> >> >> And the netboot version like : >> >> [root@roachserver Downloads]# telnet pf1 7147 >> >> Trying 192.168.100.1... >> >> Connected to pf1. >> >> Escape character is '^]'. >> >> #version alpha-6-g0b8dd54 >> >> #build-state 2012-10-24T10:04:56 >> >> #version-connect katcp-library alpha-6-g0b8dd54 2012-10-24T10:04:56 >> >> #version-connect katcp-protocol 4.9-M >> >> #version-connect kernel 3.16.0-saska-03675-g1c70ffc >> >> #3\_Tue\_Aug\_26\_08:52:14\_SAST\_2014 >> > >> >Thanks for this information! Can you please run the following steps on a >> >netbooted roach2? >> > >> ># Rename existing tcpborphserver3 executable >> >mv /usr/local/sbin/tcpborphserver3 /usr/local/sbin/tcpborphserver3.netboot >> > >> ># Mount the soloboot root filesystem on /mnt >> >mount /dev/mtdblock1 /mnt >> > >> ># Copy the soloboot tcpborphserver3 executable to the netboot filesystem >> >cp /mnt/sbin/tcpborphserver2 /usr/local/sbin/. >> > >> ># Unmount the soloboot root filesystem >> >umount /mnt >> > >> ># Restart tcpborhserver >> >/etc/init.d/tcpborphserver stop >> >/etc/init.d/tcpborphserver start >> > >> >Then telnet to the roach port 7147 to verify that the running version of >> >tcpborphserver is the one copied from soloboot. If so, try to run the >> >PAPER model (or your own model) to see whether the new tcpborphserver3 >> >executable provides different (hopefully better!) results than the old >> >netboot one. >> > >> >Thanks, >> >Dave >> > >> >> >> >
