Dear Andrey et al, I made /nfs world writable:
$ ls -l /nfs total 66464 -rwxrwxrwx 1 root root 256 2010-11-18 10:27 cmdline -rwxrwxrwx 1 root root 18218760 2010-11-17 16:41 kimage -rwxrwxrwx 1 root root 18219016 2010-11-18 10:27 kimage_1 -rwxrwxrwx 1 root root 101 2010-11-17 16:41 list -rwxrwxrwx 1 root root 267 2010-11-17 16:41 MD5SUM -rwxrwxrwx 1 root root 2156 2010-11-17 16:41 nfs_flashitall -rwxrwxrwx 1 root root 6646 2010-11-17 16:41 nfs_update -rwxrwxrwx 1 root root 131072 2010-11-17 16:41 part0.img -rwxrwxrwx 1 root root 3145728 2010-11-17 16:41 part1.img -rwxrwxrwx 1 root root 15728640 2010-11-17 16:41 part2.img -rwxrwxrwx 1 root root 12582912 2010-11-17 16:41 part3.img -rwxrwxrwx 1 root root 56 2010-11-17 16:41 partitions.conf if I mount nfs locally, I can write to the directory without permissions: $ mount | grep nfs 192.168.0.20:/nfs on /mnt/floppy type nfs (rw,addr=192.168.0.20) $ echo foo > /mnt/floppy/bar $ cat /mnt/floppy/bar foo but, when I try to do the netboot thing, no log directory is created. the output ends as before: # netboot -mac 000E64081973 -ip 192.168.0.9 -nfs 192.168.0.20:/nfs -cmd update -d eth0 -nfs_dir /nfs Using internal boot loader: INTERNAL_NW - Network boot (default). Using internal boot loader: INTERNAL2 - Level2 boot. Starting boot... > Did you put the camera in netboot mode ("yellow led lights up > constantly, while the green led flashes > vigorously for a while.") before starting the program? This is safer, > because if the program starts first and you connect/disconnect cable one > more time after it already entered netboot mode, the program can be I tried both ways: before and after starting the program. > already past the first part of the "dialog" with the camera and that > communication will break after camera is back into the "start" state. > Netboot mode is turned on by analog capacitor-based circuitry, so there > is no exact number of connections/disconnections needed to switch - > usually it happens on 3-rd, fourth or fifth time. yes, that's my experience too > But in your case it seems that something is wrong in either the software > built or maybe even some permissions for accessing Ethernet port. Can > you please compress and send build.log file (it should be in the top > installation directory)? well, I'm trying to flash to 'stock' 8.0.9 image, not the one I built. (as you've seen, by build didn't go trough). actually I'm not intersted in flashing a custom build - I just want to flash a stock image into the camera. On 18/11/10 01:11, Alexandre Poltorak wrote: > Can I ask you to send result from > ls -R /nfs > here pls ? see above On 18/11/10 01:26, Alexandre Poltorak wrote: > Akos, > > It is documented > here: http://wiki.elphel.com/index.php?title=Elphel_Software_Kit_for_Ubuntu#Configure_your_NFS_server > > You need to > sudo chmod 777 -R /nfs fair enough (this is explicitly not pointed out on the netboot page, though it does link here, that's true) > It will probably not solve the re-flashing problem by itself, but at > least you will have some logs. as you see above, there are no logs On 18/11/10 02:44, Oleg K Dzhimiev wrote: > Does your PC loses ip when you disconnect the camera? yes, network manager removes the IP from eth0 when disconnecting. but I also shut down network manager, and used ifconfig to have a stable eth0 config, but I got the same results > Could you check its ip after you launch ./netboot... (having "Starting > boot...") when the cam is disconnnected before putting it to the netboot > mode (you wrote somewhere the camera was connected directly to the PC). yes, it is. (laptop eth0 connected to the PoE injector, which is connected to the camera) On 18/11/10 02:46, Alexandre Poltorak wrote: > Important point - the camera should be connected to the PC directly, > some switches block the broadcast packages from netboot. it is, see above Akos _______________________________________________ Support-list mailing list Support-list@support.elphel.com http://support.elphel.com/mailman/listinfo/support-list_support.elphel.com