From owner-freebsd-questions@FreeBSD.ORG Sat Dec 9 04:04:15 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 478F016A40F for ; Sat, 9 Dec 2006 04:04:15 +0000 (UTC) (envelope-from lists@qwirky.net) Received: from public.aci.on.ca (aci.on.ca [205.207.148.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C82F43C9D for ; Sat, 9 Dec 2006 04:03:13 +0000 (GMT) (envelope-from lists@qwirky.net) Received: from (invalid client hostname: host address literal does not match remote client address)[127.0.0.1] (xtreme-7-102.dyn.aci.on.ca[69.17.166.102] port=1804) by public.aci.on.ca([205.207.148.252] port=25) via TCP with esmtp (3741 bytes) (sender: ) id for ; Fri, 8 Dec 2006 23:04:13 -0500 (EST) (Smail-3.2.0.122-Pre 2005-Nov-17 #1 built 2006-Feb-21) Message-ID: <457A35BF.4010802@qwirky.net> Date: Fri, 08 Dec 2006 23:04:15 -0500 From: Jeff Royle User-Agent: Thunderbird 1.5.0.8 (Windows/20061025) MIME-Version: 1.0 To: freebsd-questions@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 0655-1, 08/12/2006), Outbound message X-Antivirus-Status: Clean Subject: ACPI Support Question for FreeBSD 6.2-RC1 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lists@qwirky.net List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 09 Dec 2006 04:04:15 -0000 Greetings List! I believe my ACPI issue is simply a support issue but I need this confirmed with some direction on a possible solution if available. The short version of the problem: In dmesg I get this: acpi_bus_number: can't get _ADR The motherboard being used is a Asus P5MT-S. Is this simply a issue with no support on my chipset? Or just an ACPI values not being detected correctly? Possibly need to recompile the kernel with additional support? The long version :-) Here is a section from my dmesg: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 Security auditing service present BSM auditing present ioapic0: Changing APIC ID to 2 ioapic1: Changing APIC ID to 3 ioapic0 irqs 0-23 on motherboard ioapic1 irqs 24-47 on motherboard kbd1 at kbdmux0 ath_hal: 0.9.17.2 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413) acpi0: on motherboard acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR acpi0: Power Button (fixed) acpi_bus_number: can't get _ADR acpi_bus_number: can't get _ADR Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 cpu0: on acpi0 acpi_throttle0: on cpu0 cpu1: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 28.0 on pci0 pci1: on pcib1 pcib2: at device 0.0 on pci1 pci2: on pcib2 aacu0: mem 0xfc600000-0xfc7fffff,0xfc5ff000-0xfc5fffff irq 24 at device 1.0 on pci2 aacu0: New comm. interface enabled aacu0: Adaptec Raid Controller 2.0.7-1 aacpu0: on aacu0 ahd0: port 0xa800-0xa8ff,0xa400-0xa4ff mem 0xfc5fc000-0xfc5fdfff irq 26 at device 3.0 on p ci2 ahd0: [GIANT-LOCKED] aic7901: Ultra320 Wide Channel A, SCSI Id=7, PCI-X 67-100Mhz, 512 SCBs pcib3: irq 16 at device 28.4 on pci0 pci3: on pcib3 Here is some output from pciconf -lv: pcib1@pci0:28:0: class=0x060400 card=0x00000040 chip=0x27d08086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801G (ICH7 Family) PCI Express Root Port' class = bridge subclass = PCI-PCI pcib3@pci0:28:4: class=0x060400 card=0x00000040 chip=0x27e08086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801GR/GH/GHM (ICH7 Family) PCI Express Root Port' class = bridge subclass = PCI-PCI pcib4@pci0:28:5: class=0x060400 card=0x00000040 chip=0x27e28086 rev=0x01 hdr=0x01 vendor = 'Intel Corporation' device = '82801GR/GH/GHM (ICH7 Family) PCI Express Root Port' class = bridge Thanks for the time, Jeff