From owner-freebsd-hardware@FreeBSD.ORG  Thu Aug 25 19:01:58 2005
Return-Path: <owner-freebsd-hardware@FreeBSD.ORG>
X-Original-To: hardware@freebsd.org
Delivered-To: freebsd-hardware@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EC51416A41F
	for <hardware@freebsd.org>; Thu, 25 Aug 2005 19:01:58 +0000 (GMT)
	(envelope-from olivier@gautherot.net)
Received: from postfix4-2.free.fr (postfix4-2.free.fr [213.228.0.176])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9B1BA43D45
	for <hardware@freebsd.org>; Thu, 25 Aug 2005 19:01:58 +0000 (GMT)
	(envelope-from olivier@gautherot.net)
Received: from [192.168.1.2] (mas91-1-82-238-221-116.fbx.proxad.net
	[82.238.221.116])
	by postfix4-2.free.fr (Postfix) with ESMTP id 113F831D71A
	for <hardware@freebsd.org>; Thu, 25 Aug 2005 21:01:53 +0200 (CEST)
From: Olivier Gautherot <olivier@gautherot.net>
To: hardware@freebsd.org
Date: Thu, 25 Aug 2005 21:01:52 +0200
User-Agent: KMail/1.8.2
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200508252101.52515.olivier@gautherot.net>
Cc: 
Subject: VIA EPIA board with on-board graphics
X-BeenThere: freebsd-hardware@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: olivier@gautherot.net
List-Id: General discussion of FreeBSD hardware <freebsd-hardware.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hardware>
List-Post: <mailto:freebsd-hardware@freebsd.org>
List-Help: <mailto:freebsd-hardware-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hardware>, 
	<mailto:freebsd-hardware-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Aug 2005 19:01:59 -0000

Hi folks!

I've just set up a new system with a VIA EPIA mini-ITX motherboard. In 
essence, it is working just fine... apart from some occasional reboots. The 
first time it happened, I was running xosview (which was using about 256MB of 
system memory!) as well as other apps in parallel. It happened yesterday and 
today again while ripping some CD's. For info, the system is fitted with 
512MB, included 32MB of shared memory for graphics.

It is not the first time I experience system reboots on PC's with shared 
memory for graphics: my other machine had the same unstability until I 
plugged an NVidia graphics card and disabled the on-board chipset. I would 
like to avoid doing the same here as I would like to keep power low (I use it 
mainly for emails and word processing, not 3D games).

Any advice on stabilizing a system with shared memory? BTW, I'm running 
5.4-RELEASE with a few tweaks in the kernel but did not find a fix for  this 
yet.
-- 
Olivier Gautherot
olivier@gautherot.net