i386/80265: D-Link NIC with VIA Rhine II has no carrier signal on
boot
Martin Piayda
martin.piayda at udo.edu
Fri Apr 22 14:30:34 PDT 2005
>Number: 80265
>Category: i386
>Synopsis: D-Link NIC with VIA Rhine II has no carrier signal on boot
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-i386
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Fri Apr 22 21:30:33 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: Martin Piayda
>Release: 5.3-p7
>Organization:
>Environment:
FreeBSD themis 5.3-RELEASE-p7 FreeBSD 5.3-RELEASE-p7 #16: Tue Apr 5 12:55:41 CEST 2005 martin at themis:/usr/obj/usr/src/sys/Themis i386
>Description:
So, I'm using a D-Link NIC with a VIA Rhine II chipset (exactly a VIA VT6102 Rhine II 10/100BaseTX) for hooking up to the WAN.
When rebooting the system the vr0-device (this is the nic's order) has no carrier signal. Plugging out the endpoint and plugging it back in (the cable :) restores the signal.
There is no instability while the carrier is online, it's just gone when the nic is reinitialized e.g. by rebooting.
This makes remote rebooting unusable.
I tested the nic in a different system on a different operating system and it works fine there.
That's what makes me suspect the driver for the card.
If used vr as the driver for the nic.
>How-To-Repeat:
Reboot the system or reinitialize the card.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-i386
mailing list