[Voyage-linux]resolved: pxe-boot from live-cd

[Jan Hetges]

On Tue, Jun 26, 2007 at 12:11:26AM +0800, Punky Tse wrote:
 
> Regards,
> Punky
> 
> 
> 
> 
> Jan Hetges wrote:
> >Hi Punky
> >On Mon, Jun 25, 2007 at 09:36:47AM +0800, Kim-man 'Punky' TSE wrote:
> >  
> >>Jan Hetges wrote:
> >>    
> >>>i tried yesterday's (d3de00dd64d7fc1a02e7a9b7b62b0393
> >>>voyage-current.iso) to pxe-boot a soekris net4526...
> >>>but does'nt work :(
> >>>after starting /etc/init.d/voyage-pxe i found something like:
> >>>aftpd: could not bind to port 69/udp
> >>>in syslog, and there is no atftpd running.
> >>>dhcp seems to work though.
> >>>is there a known_to_work image ?
> >>>      
> >>voyage-current is a moving target.  If you are unfortunate, you may get 
> >>a faulty image somehow.
> >
> >i know, but it should work, so i took it for testing :)
> >  
> >>Instead, try the release version, 0.3.1 or 0.4.0, they were tested 
> >>before release.
> >
> >i tried both of these, but having the same issue with both (including
> >the voyage-current with all three!) i ran 0.4.0 only in qemu, but 
> >burned current and 0.3.1 on cd and it's always the same:
> >voyage:~# /etc/init.d/voyage-pxe start 19200
> >Setting serial 19200 to /etc/inittab ... Done.
> >Setting serial 19200 to /tftpboot/pxelinux.cfg/default ... Done.
> >Setting up eth0 to 192.168.1.200 ... Done.
> >Stopping NFS servers: mountd nfsd.
> >Starting NFS servers: nfsd mountd.
> >Restarting Advanced Trivial FTP server: atftpd.
> >
> >but then i find at the end of syslog:
> >Jun 25 14:55:20 voyage atftpd[3756]: Advanced Trivial FTP server started 
> >(0.7)
> >Jun 25 14:55:20 voyage atftpd[3757]: atftpd: can´t bind port :69/udp
> I didn't look at the syslog before.  Just run the live cd and I see the 
> same message in syslog.  But don't be paranoid for syslog message, and I 
> would say: it is normal.
> >
> >and no atftpd is running:
> >voyage:~# ps awux | grep 3756
> >root	  3778  0.0  0.8   1644   548 tty1    S+  14:57   0:00 grep 3756
> >voyage:~# ps awux | grep 3757
> >root	  3780  0.0  0.8   1640   544 tty1    S+  14:57   0:00 grep 3757
> >voyage:~# ps awux | grep tftp
> >root	  3783  0.0  0.8   1644   500 tty1    R+  14:57   0:00 grep tftp
> >
> >any suggestions?
> >
> You can see tftp is running (see the line with 
> tftp):
> =============================================
> voyage:~# netstat -l
> Active Internet connections (only servers)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State
> tcp        0      0 *:nfs                   *:*                     LISTEN
> tcp        0      0 *:805                   *:*                     LISTEN
> tcp        0      0 *:sunrpc                *:*                     LISTEN
> tcp        0      0 *:domain                *:*                     LISTEN
> tcp        0      0 *:1723                  *:*                     LISTEN
> tcp6       0      0 *:domain                *:*                     LISTEN
> tcp6       0      0 *:ssh                   *:*                     LISTEN
> udp        0      0 *:2048                  *:*
> udp        0      0 *:nfs                   *:*
> udp        0      0 *:802                   *:*
> udp        0      0 *:domain                *:*
> udp        0      0 *:bootps                *:*
> udp        0      0 *:tftp                  *:*
> udp        0      0 *:sunrpc                *:*
> udp6       0      0 *:domain                *:*
> Active UNIX domain sockets (only servers)
> Proto RefCnt Flags       Type       State         I-Node Path
> =============================================
> 
> So, tftp is running, and you are ready for pxe boot.  Just plug you 
> board to it, and start the net4826 for netboot.  This should work, and 
> ask me again otherwise.  Since the introduction of live cd, I have using 
> pxeboot to install voyage on my boards for testing, more than using 
> voyage.update.

it doesn't do anything (no dhcp request, checked with tcpdump), so it
seems to be the board :(, of course i made sure: 
 > show PXEBoot
 > PXEBoot Enabled
so i tried with a net4801 and pxe-boot works just fine
really nice work BTW
> 
> And try to avoid qemu, as setting up the network interface could be 
> difficult.  I mean, you need a some special setup to bridge the guest 
> (live cd) and the host so that the board is able to see the live cd 
> under qemu.
yes, i saw it might be a pain_in_the_a** to get network working with
qemu ;-)

so i'll gonna upgrade from pebble :), which is installed on that net4526.
do you know howto get a lilo prompt through minicom?

cheers

  --Jan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
URL: <http://list.voyage.hk/pipermail/voyage-linux/attachments/20070625/0af23b65/attachment-0002.pgp>