From owner-freebsd-acpi@FreeBSD.ORG Fri May 6 06:09:16 2005 Return-Path: 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 454CB16A4CE for ; Fri, 6 May 2005 06:09:16 +0000 (GMT) Received: from pandora.afflictions.org (asylum.afflictions.org [64.7.134.90]) by mx1.FreeBSD.org (Postfix) with ESMTP id 77C2F43D53 for ; Fri, 6 May 2005 06:09:15 +0000 (GMT) (envelope-from dgerow@afflictions.org) Received: from localhost (localhost [127.0.0.1]) by pandora.afflictions.org (Postfix) with ESMTP id 42B2C78C64 for ; Fri, 6 May 2005 02:11:42 -0400 (EDT) Received: from pandora.afflictions.org ([127.0.0.1]) by localhost (pandora.afflictions.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 40330-06 for ; Fri, 6 May 2005 02:11:37 -0400 (EDT) Received: from dementia.afflictions.org (dementia.afflictions.org [172.19.206.56]) by pandora.afflictions.org (Postfix) with ESMTP id 81BFA78C5F for ; Fri, 6 May 2005 02:11:36 -0400 (EDT) Received: by dementia.afflictions.org (Postfix, from userid 1001) id CF76433C79; Fri, 6 May 2005 02:09:07 -0400 (EDT) Date: Fri, 6 May 2005 02:09:07 -0400 From: Damian Gerow To: freebsd-acpi@freebsd.org Message-ID: <20050506060907.GC29838@afflictions.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-GPG-Fingerprint: B3D7 D901 A53A 1A99 BFD6 E6DF 9F3B 742B C288 9CC9 User-Agent: Mutt/1.5.9i X-Virus-Scanned: amavisd-new at pandora.afflictions.org Subject: ACPI on Tyan K8WE (mostly works!) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 06 May 2005 06:09:16 -0000 I just got my hands on a Tyan K8WE (S2895), and was pleasantly surprised to see that after very little effort, the board booted with almost full ACPI support. I've not actually had any ACPI troubles yet, but a non-verbose boot does complain a bit about ACPI: real memory = 1072824320 (1023 MB) avail memory = 1023733760 (976 MB) ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-27 on motherboard ioapic2 irqs 28-31 on motherboard acpi0: on motherboard ACPI-0438: *** Error: Looking up [\_SB_.PCI1.LNK3] in namespace, AE_NOT_FOUND SearchNode 0xffffff0000a3d1c0 StartNode 0xffffff0000a3d1c0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\_SB_.PCI1.LNK4] in namespace, AE_NOT_FOUND SearchNode 0xffffff0000a3bcc0 StartNode 0xffffff0000a3bcc0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\_SB_.PCI1.LNK1] in namespace, AE_NOT_FOUND SearchNode 0xffffff0000a3b9c0 StartNode 0xffffff0000a3b9c0 ReturnNode 0 ACPI-0438: *** Error: Looking up [\_SB_.PCI1.LNK2] in namespace, AE_NOT_FOUND SearchNode 0xffffff0000a3b6c0 StartNode 0xffffff0000a3b6c0 ReturnNode 0 acpi0: Power Button (fixed) There's no functionality impairment, which I was pleasantly surprised to see. Thanks! In case anyone's interested in prodding any further a mostly-full dmesg and an ASL dump can be found here: Note that the dmesg isn't full: my full verbose dmesg output is greater than kern.consmsgbuf_size, and for some reason, isn't recorded in dmesg.today. I'll look into expanding it on bootup tomorrow, but for the time being, that's the vast majority of a dmesg. - Damian