Re: Problems with netboot 0.7.2

[Richard Gooch <rgooch@atnf.CSIRO.AU>]

I wrote:
>   Hi, all. I'm trying to set up a machine to boot Linux over the
> network, so I've downloaded netboot 0.7.2. Unfortunately, the bootp
> client does not seem to get an answer, and just prints dots. I know
> that my bootp server is working OK, because I have another bootp ROM
> (from Bootware, a commercial product) which *does* manage to receive a
> bootp reply and load a boot image using tftp. One reason for using
> netboot is that the Bootware ROM I have does not support images over
> around 450 kBytes. My Linux bootImage is 1.7 MBytes.
> 
> I turned on debugging for the packet driver in the bootp client and I
> get the following:
> 
> S 0000C0853DEE 45 00 01 48 00 ** 00 00 ff 11 * * 00 00 00 00 ff ff ff ff 00 44
> 
> where "*" changes every second. The network card is an SMC and I
> have checked the I/O address, IRQ and MEM address.
> 
> When I set the debugging level for bootpd on my server to 9, I get:
> 
> in.bootpd[17621]: connect from 0.0.0.0
> in.bootpd[17621]: version 2.4.0
> in.bootpd[17621]: bootptab mtime: Wed Sep 10 18:31:04 1997
> in.bootpd[17621]: reading "/etc/bootptab"
> in.bootpd[17621]: read 2 entries (1 hosts) from "/etc/bootptab"
> in.bootpd[17621]: recvd pkt from IP addr 0.0.0.0
> in.bootpd[17621]: bootptab mtime: Wed Sep 10 18:31:04 1997
> in.bootpd[17621]: request from Ethernet address 00:00:C0:85:3D:EE
> in.bootpd[17621]: found 130.155.196.205 (bcc05)
> in.bootpd[17621]: bootfile="//bcc.bw"
> in.bootpd[17621]: vendor magic field is 99.130.83.99
> in.bootpd[17621]: sending reply (with RFC1048 options)
> in.bootpd[17621]: setarp 130.155.196.205 - 00:00:C0:85:3D:EE
> 
> The bootpd server is running Linux 2.0.30.

I have managed to get a WD 8013 card to work properly, and also an
NE2000. However, my SMC (83c795) card does not receive the bootp
information, and I get the kind of messages show above. This seems to
indicate that the bootp request is being received by the bootp server,
but the client is not receiving the reponse packet. The IRQ and other
configuration are set correctly. The packet driver I'm using for my
SMC card is the 80x3 driver.
It appears that the SMC is not behaving as a "real" 80x3. Does anyone
have a solution to this problem?

				Regards,

					Richard....