Date: Wed, 3 Mar 2004 15:11:44 -0800 (PST) From: Jim Sims <freebsd@esims.org> To: freebsd-gnats-submit@FreeBSD.org Subject: i386/63721: VT6103 NIC broken since 5.2 Message-ID: <200403032311.i23NBi2a014817@www.freebsd.org> Resent-Message-ID: <200403032320.i23NK0pK098002@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 63721 >Category: i386 >Synopsis: VT6103 NIC broken since 5.2 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-i386 >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Wed Mar 03 15:20:00 PST 2004 >Closed-Date: >Last-Modified: >Originator: Jim Sims >Release: 4.6.2, 5.1, other >Organization: None >Environment: Not Available. Without networking this is kinda difficult. It is just a clean install of 5.2 or later. >Description: Prior to 5.2 the vr0 correctly worked with the VT6103 chipset. I have been running several boxes for over a year and a half. I loaded 5.2 and 5.2.1 and the result was the same: The nic is seen and assigned vr0, but on boot get watchdog timeout error repeatedly. Nic IP can be pinged, but nothing beyond NIC. I can reload 5.1 or 4.X and the NIC works fine. Although the hardware is NOT listed on the supported hardware list, the fact that it used to work, but now does not may be of interest. I have several machines and am willing to spend time testing/reporting on this if anyone wants to investigate the problem. I will be happy to allow someone remote access to a clean system for testing purposes as long as it is scheduled in advance. >How-To-Repeat: Install FreeBSD 5.2 or later on system with Shuttle MV43N motherboard. >Fix: Revert to 5.1 is the only workaround I have been able to find. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403032311.i23NBi2a014817>