From owner-freebsd-questions@FreeBSD.ORG Tue Dec 5 13:41:11 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 1C33F16A51E for ; Tue, 5 Dec 2006 13:41:11 +0000 (UTC) (envelope-from lane@joeandlane.com) Received: from elasmtp-dupuy.atl.sa.earthlink.net (elasmtp-dupuy.atl.sa.earthlink.net [209.86.89.62]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7008344116 for ; Tue, 5 Dec 2006 13:32:29 +0000 (GMT) (envelope-from lane@joeandlane.com) Received: from [66.47.111.183] (helo=joeandlane.com) by elasmtp-dupuy.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1GraPw-0001d7-DO for freebsd-questions@freebsd.org; Tue, 05 Dec 2006 08:33:04 -0500 Received: from joeandlane.com (localhost.localnet.local [127.0.0.1]) by joeandlane.com (8.13.8/8.13.1) with ESMTP id kB5DZZlb044996 for ; Tue, 5 Dec 2006 07:35:35 -0600 (CST) (envelope-from lane@joeandlane.com) Received: from localhost (localhost [[UNIX: localhost]]) by joeandlane.com (8.13.8/8.13.1/Submit) id kB5DZYNc044952 for freebsd-questions@freebsd.org; Tue, 5 Dec 2006 07:35:34 -0600 (CST) (envelope-from lane@joeandlane.com) X-Authentication-Warning: joeandlane.com: lholcombe set sender to lane@joeandlane.com using -f From: Lane To: freebsd-questions@freebsd.org Date: Tue, 5 Dec 2006 07:35:33 -0600 User-Agent: KMail/1.9.4 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200612050735.34101.lane@joeandlane.com> X-CD-SOLUTIONS-MailScanner-Information: Please contact the ISP for more information X-CD-SOLUTIONS-MailScanner: Found to be clean X-CD-SOLUTIONS-MailScanner-From: lane@joeandlane.com X-ELNK-Trace: e56a4b6ca9bdfda11aa676d7e74259b7b3291a7d08dfec799e802fe9538aaa9d718b2ad67e39d0d5350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c X-Originating-IP: 66.47.111.183 Subject: Re: Duo core enable/support help. X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Dec 2006 13:41:11 -0000 On Tuesday 05 December 2006 06:14, you wrote: > Hello Lane! > > I'm a frequent reader to /usr/src/UPDATING > But whenever I need to update or upgrade only, since years! > > Also I knew very well whats KERNCONF! i just wanted to know and make > sure of the duo core > options, and i searched the NOTES file, didnot find anything about it. > > Thank you for your "short" problematic answer :) > > by the way, After recompiling the kernel and From my dmesg > -------------------- > ACPI APIC Table: > FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs > cpu0 (BSP): APIC ID: 0 > cpu1 (AP): APIC ID: 1 > ioapic0: Changing APIC ID to 4 > SMP: AP CPU #1 Launched! > --------------------- > > But I still have few dmesg errors, these are the lines, > > acpi0: on motherboard > acpi0: Overriding SCI Interrupt from IRQ 9 to IRQ 21 > acpi0: Power Button (fixed) > 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 > unknown: I/O range not supported > Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000 > acpi_timer0: <32-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 > cpu0: on acpi0 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_perf0: on cpu0 > acpi_perf0: failed in PERF_STATUS attach > device_attach: acpi_perf0 attach returned 6 > acpi_throttle0: on cpu0 > cpu1: on acpi0 > acpi_perf1: on cpu1 > acpi_perf1: failed in PERF_STATUS attach > device_attach: acpi_perf1 attach returned 6 > acpi_perf1: on cpu1 > acpi_perf1: failed in PERF_STATUS attach > device_attach: acpi_perf1 attach returned 6 > acpi_throttle1: on cpu1 > acpi_throttle1: failed to attach P_CNT > device_attach: acpi_throttle1 attach returned 6 > acpi_button0: on acpi0 > > and > usb2: waiting for BIOS to give up control > usb2: timed out waiting for BIOS > usb2: EHCI version 1.0 > usb2: companion controllers, 4 ports each: usb0 usb1 > usb2: on ehci0 > usb2: USB revision 2.0 > > Any easy problematic ideas? :) > Thank you > > ---Marwan > > >First read /usr/src/UPDATING. > > > >Really. > > > >No, really. I mean read it :) > > > >And, since no one expects you to really, really read it, I'll give you > > some shortcuts. > > > >First, look for the word KERNCONF in /usr/src/UPDATING > > > >Read all of the language around every occurence of that word (KERNCONF). > > > >Then, when you are ready, do this: > > > >make buildkernel KERNCONF=SMP > >make installkernel KERNCONF=SMP > > > >Then reboot. > > > >Note here that I'm giving you the shortest possible route, which may be > >problematic for you. You really must become familiar with > >/usr/src/UPDATING. > > > >Anyway, after the reboot, you should type: > > > >cat /var/log/messages | grep -i launch > > > >if you see the terms "CPU1 Launched!" then you've got yourself an SMP > >kernel. > > > >Good Luck! > > > >lane > > _________________________________________________________________ Marwan, Please don't top post because >follow >to >hard >it's I'm guessing here: The acpi messages such as > acpi_bus_number: can't get _ADR > acpi_perf0: failed in PERF_STATUS attach may be appearing because these features are not yet fully supported. Check on "man acpi" to learn how to selectively disable acpi functions. The read is rather short, and you may ultimately decide that it's better left alone. As long as these errors don't repeat then it is likely the selected features are simply disabled by the kernel (or not loaded, or however acpi works :) Regarding the acpi errors AND the usb error: Do you detect any diminished performance? Are you unable to mount drives and/or other devices? lane