Subject: kern/17538: onboard fxp does not come up when netbooting
To: None <gnats-bugs@gnats.netbsd.org>
From: Tom Spindler <dogcow@archive-3-350.redback.com>
List: netbsd-bugs
Date: 07/10/2002 01:06:11
>Number:         17538
>Category:       kern
>Synopsis:       onboard fxp does not come up when netbooting
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jul 09 18:07:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     
>Release:        NetBSD 1.6_BETA4
>Organization:
Redback Networks
	
>Environment:
	
	
System: NetBSD archive-3-350 1.6_BETA4 NetBSD 1.6_BETA4 (GENERIC) #15: Wed Jul 3 00:59:54 PDT 2002 notroot@erectile-dysfunction:/netbsd15/nbsrc16/obj.i386/sys/arch/i386/compile/GENERIC i386
Architecture: i386
Machine: i386

>Description:
On a Tyan ThunderLE-T or Intel D815EEA Desktop Board motherboard,
the onboard fxp devices will not come up when you try to netboot
of of them - it timeouts when trying to get its DHCP adddress. Try
as you might, tell them to cycle through over and over, it still
no workee. (The DHCP box doesn't even see the traffic.)

The Tyan motherboard also has the interesting problem where you
have to do an additional 'ifconfig fxp0 up' to get the thing to
start sending packets.

fwiw: the tyan has
pchb0: ServerWorks CNB20LE Host (rev. 0x06)
and the intel has
pchb0: Intel product 0x1130 (rev. 0x02)
	
>How-To-Repeat:
Netboot a Tyan ThunderLE-T motherboard or Intel D815EEA desktop board.
(1.6, 1.5.3, or -current)
	
>Fix:
The workaround is to disable the disabling during the attach:
--- if_fxp_pci.c        2002/06/25 22:07:42     1.22.4.1
+++ if_fxp_pci.c        2002/07/10 00:52:40
@@ -446,9 +446,10 @@
 
        /* Finish off the attach. */
        fxp_attach(sc);
+#if 0 /* XXX for netbooting */
        if (sc->sc_disable != NULL)
                fxp_disable(sc);
-
+#endif /* XXX */

	
>Release-Note:
>Audit-Trail:
>Unformatted: