From owner-freebsd-hardware@FreeBSD.ORG Fri Aug 13 17:39:24 2004 Return-Path: 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 3B9A816A4CE for ; Fri, 13 Aug 2004 17:39:24 +0000 (GMT) Received: from marvin.muc.de (marvin.muc.de [193.149.48.2]) by mx1.FreeBSD.org (Postfix) with SMTP id 6465643D1D for ; Fri, 13 Aug 2004 17:39:23 +0000 (GMT) (envelope-from v.velox@vvelox.net) Received: (qmail 20032 invoked by alias); 13 Aug 2004 17:39:22 -0000 Delivered-To: mods-muc-lists-freebsd-hardware@moderators.muc.de Received: (qmail 20025 invoked from network); 13 Aug 2004 17:39:21 -0000 Received: from scanmail1.cableone.net (HELO mail.cableone.net) (24.116.0.121) by marvin.muc.de with SMTP; 13 Aug 2004 17:39:21 -0000 Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified [24.119.122.85]) by smail1.cableone.net (SurgeMail 1.9b) with ESMTP id 13905343 for multiple; Fri, 13 Aug 2004 10:28:19 -0700 Date: Fri, 13 Aug 2004 12:38:43 -0500 From: Vulpes Velox To: Andreas Just Message-Id: <20040813123843.01122c4a@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: References: X-Mailer: Sylpheed-Claws 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.10) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Server: High Performance Mail Server - http://surgemail.com X-Mailman-Approved-At: Sun, 15 Aug 2004 13:17:41 +0000 cc: muc-lists-freebsd-hardware@moderators.muc.de Subject: Re: unsupported mainboard? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Aug 2004 17:39:24 -0000 On Fri, 13 Aug 2004 09:15:40 +0200 Andreas Just wrote: > Hi, > > when I try to boot FreeBSD 5.2.1 from the install CD, I get the > following error: > > panic: pmap_mapdev: Couldn't alloc kernel virtual memory > > I assume, FreeBSD doesn't yet support my nForce2 chipset. > If anyone has another idea or a hint, I'd appreciate it. Possible CD problem. It should actually boot on nearly all i386 hardware afaik. Where you will run into probs is support for specific devices. Try with out ACPI, that some times helps, but I sorta doubt it will here.