>Number:         28997
>Category:       port-i386
>Synopsis:       sk0 NIC not functioning properly.
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-i386-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Jan 18 08:21:00 +0000 2005
>Originator:     Jonathan D. Hicks
>Release:        2.99.14 (CVS'd at 15/1/05)
>Organization:
Project Ivory
>Environment:
NetBSD 2.99.14 NetBSD 2.99.14 (GENERIC) #0: Mon Jan 17 14:14:21 PST 2005  root@:/usr/obj/sys/arch/i386/compile/GENERIC i386
>Description:
# dmesg | grep sk0
sk0 at skc0 port A: Ethernet address 00:0e:a6:11:60:a3
makphy0 at sk0 phy 0: Marvell 88E1011 Gigabit PHY, rev. 5

This NIC has not been functioning properly for me under NetBSD 2.0, or NetBSD-current.

For a short while it would function under NetBSD 2.0 if I configured the IP, netmask, route, and resolv.conf manually. 'dhclient' however was not functioning (it failed to get responses from DHCPDISCOVER), despite the machine having no difficulties with DHCP in other operating systems. Eventually this ceased to work as well, and I CVS'd the latest src/ as of 15/1/05. I built the kernel with the following method as root (it was my first time, so there is a good chance this wasn't the proper way to do it.)

----------------------------------------------------
./build.sh tools kernel=GENERIC
mv /netbsd /netbsd.old
cp /usr/obj/sys/arch/i386/compile/GENERIC/netbsd /netbsd
shutdown -r now

(after rebooting)

./build.sh -u distribution install=/

shutdown -r now
----------------------------------------------------

Running ifconfig on sk0 gives normal results. However, 'dhclient' always returns with the error page stating "Please do not under any circumstances..." I can give the device an IP, netmask, and set up a route manually. But it fails to utilize connectivity, and I get an error saying, "sk0: watchdog timed out" intermittently. It cannot ping the router.

>How-To-Repeat:
Run NetBSD >= 2.0 on an Asus A7N8X-E Deluxe motherboard and attempt to utilize its onboard LAN. =)
>Fix: