From owner-freebsd-acpi@FreeBSD.ORG Thu Dec 22 10:54:47 2005 Return-Path: X-Original-To: freebsd-acpi@freebsd.org Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6F5C616A420 for ; Thu, 22 Dec 2005 10:54:47 +0000 (GMT) (envelope-from groot@kde.org) Received: from pandora.cs.kun.nl (pandora.cs.kun.nl [131.174.33.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2770A43D73 for ; Thu, 22 Dec 2005 10:54:45 +0000 (GMT) (envelope-from groot@kde.org) Received: from pino.codeyard.cs.ru.nl [131.174.33.136] (helo=pino.codeyard.cs.ru.nl) by pandora.cs.kun.nl (8.13.5/5.7) with ESMTP id jBMAsfEC024742 for ; Thu, 22 Dec 2005 11:54:41 +0100 (MET) From: Adriaan de Groot Organization: KDE-NL To: freebsd-acpi@freebsd.org Date: Thu, 22 Dec 2005 11:55:04 +0100 User-Agent: KMail/1.9 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200512221155.04352.groot@kde.org> X-Spam-Score: 1.567 (*) BAYES_50 X-Scanned-By: MIMEDefang 2.48 on 131.174.33.4 Subject: Bad characters in Asus A8N-VM CSM X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Dec 2005 10:54:47 -0000 I just picked up an Asus A8N-VM CSM motherboard. It's a nForce 430 + GForge 6150 integrated mini-ATX job, amd64, very 1337 and new. That means trouble :) I knew that when buying it, and know now that it really needs work to get it working at all. FreeBSD 5.1-R amd64 boots just fine on the machine, so I do have _some_ tools for the machine. 6.0-R without ACPI hangs, and 6.0-R with ACPI craps out immediately with the following error: ACPI-0397: *** Error: NSSearchAndEnter: Bad character in ACPI Name: 43035350 ACPI-0381: *** Error: Looking up [0x43035350] (NON-ASCII) in namespace, AE_BAD_CHARACTER ACPI-0204: ACPI-0213: (not all error messages copied entirely). What's a good approach to dealing with this? My plan doesn't go much further than 1) Update to latest BIOS and then futz about. Suggestions? FWIW, I haven't found a Linux yet _either_ that boots and recognizes the devices on the board (2.6.15 seems more promising than 2.6.10, which fails with no NIC and no HDD drivers). [ade]