From owner-freebsd-stable@FreeBSD.ORG Fri May 16 09:20:27 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0CED37B401 for ; Fri, 16 May 2003 09:20:27 -0700 (PDT) Received: from Shenton.org (23.ebbed1.client.atlantech.net [209.190.235.35]) by mx1.FreeBSD.org (Postfix) with SMTP id C45F743FA3 for ; Fri, 16 May 2003 09:20:26 -0700 (PDT) (envelope-from chris@Shenton.Org) Received: (qmail 68316 invoked by uid 1000); 16 May 2003 16:20:23 -0000 To: "Carl Morley" References: <001801c31a5c$dd4b2a30$ada628cb@cmlaptop> From: Chris Shenton Date: 16 May 2003 12:20:23 -0400 In-Reply-To: <001801c31a5c$dd4b2a30$ada628cb@cmlaptop> Message-ID: <87bry2amns.fsf@Pectopah.shenton.org> Lines: 23 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii cc: freebsd-stable@freebsd.org Subject: Re: Via EPIA Mini-ITX motherboard X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 May 2003 16:20:28 -0000 "Carl Morley" writes: > Yes, I have had these problems too. And even the HDD controller has > done some pretty mysterious stuff. > > Even with the patched drivers in 4.8, I still regularly get " vr0: rx > packet lost" errors. > > Not happy in general and would essentially advise to steer clear, or get > heavily involved! I've been running an EPIA M 600MHz fanless for a couple months. I'm running it diskless (booting from a FreeBSD-5.0 server and NFS mounting from it too) so that it's silent. It's not the fastest thing I've seen but is generally adequate. Kitchen# uname -a FreeBSD Kitchen.shenton.org 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Sun Apr 13 11:47:15 EDT 2003 chris@Pectopah.shenton.org:/usr/obj/usr/src/sys/PECTOPAH i386 I haven't seen the network problems you have mentioned (just checked the logs and dmesg). I see that the thread started in December 2002; perhaps more recent code has fixed this?