Re: Problems with DEC Etherworks 3

[Kent Snook <kent.snook@echostar.com>]

Darryl Bond wrote:

> Hi,
> I have compiled and built a bootrom using the DEC Etherworks 3 packet
> driver from the DEC site.
>
> It requires an interrupt between 60-80 as a command line to the packet
> driver.
> I have successfully used the floppy boot and the packet driver seems to
> find the card Ok.
>
> It finds the card at IRQ5 IO:300 Memory Address:D000 memory Mode:2k
> Ethernet Address:08-00-2B-BC-FE-50
>
> Found Packet Driver at int 60 (I have tried several interrupts with
> similar effect)
>
> It starts sending bootp requests.
> I have snooped the wire and found:
>
> OLD-BROADCAST -> BROADCAST    DHCP/BOOTP BOOTREQUEST
>         lady -> 203.4.168.242 DHCP/BOOTP BOOTREPLY
> OLD-BROADCAST -> BROADCAST    DHCP/BOOTP BOOTREQUEST
>         lady -> 203.4.168.242 DHCP/BOOTP BOOTREPLY
> OLD-BROADCAST -> BROADCAST    DHCP/BOOTP BOOTREQUEST
>         lady -> 203.4.168.242 DHCP/BOOTP BOOTREPLY
> OLD-BROADCAST -> BROADCAST    DHCP/BOOTP BOOTREQUEST
>         lady -> 203.4.168.242 DHCP/BOOTP BOOTREPLY
> OLD-BROADCAST -> BROADCAST    DHCP/BOOTP BOOTREQUEST
>         lady -> 203.4.168.242 DHCP/BOOTP BOOTREPLY
> OLD-BROADCAST -> BROADCAST    DHCP/BOOTP BOOTREQUEST
>         lady -> 203.4.168.242 DHCP/BOOTP BOOTREPLY
>
> Bootp running on a sun box in -d4 debug mode prints the following
>
> bootpd: info(6):   recvd pkt from IP addr 0.0.0.0
> bootpd: info(6):   bootptab mtime: Wed Mar  1 12:18:36 2000
> bootpd: info(6):   request from Ethernet address 08:00:2B:BC:FE:50
> bootpd: info(6):   found 203.4.168.242 (dectest)
> bootpd: info(6):   bootfile="/lts/vmlinuz.3COM"
> bootpd: info(6):   vendor magic field is 99.130.83.99
> bootpd: info(6):   sending reply (with RFC1048 options)
> bootpd: info(6):   setarp 203.4.168.242 - 08:00:2B:BC:FE:50
>
> The same settings on a different 3C509 card (with the right MAC address)
> booted correctly.
>
> I does not seem to do anything after the initial request. It cannot be
> pinged after bootpd has sent its reply etc.
>
> TIA
> Darryl Bond
> ===========================================================================
> This Mail was sent to netboot mailing list by:
> Darryl Bond <dbond@nrggos.com.au>
> To get help about this list, send a mail with 'help' as the only string in
> it's body to majordomo@baghira.han.de. If you have problems with this list,
> send a mail to netboot-owner@baghira.han.de.

I experienced the same symptoms when our vendor moved from DEC21440 chipset to
DEC21441. We were never able to resolve the problem with etherboot. The
consensus we finally arrived at was that the drivers available did not support
the new chipset. The card was detected properly, sent bootp requests, but did
not respond to replies from the server.

I was able to work around the problem by moving from etherboot to netboot
0.8.0 and just using packet drivers.  Note: The netboot image will boot all of
our DEC nics regardless of chipset.

Kent

===========================================================================
This Mail was sent to netboot mailing list by:
Kent Snook <kent.snook@echostar.com>
To get help about this list, send a mail with 'help' as the only string in
it's body to majordomo@baghira.han.de. If you have problems with this list,
send a mail to netboot-owner@baghira.han.de.