Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 05 Dec 2006 12:14:40 +0000
From:      "Marwan Sultan" <dead_line@hotmail.com>
To:        lane@joeandlane.com, freebsd-questions@freebsd.org
Subject:   Re: Duo core enable/support help.
Message-ID:  <BAY104-F380F837FAD01A8CF3468BE9ADE0@phx.gbl>
In-Reply-To: <200612041858.45873.lane@joeandlane.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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: <INTEL  D11020M >
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: <INTEL D11020M> 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: <ACPI CPU> on acpi0
acpi_perf0: <ACPI CPU Frequency Control> on cpu0
acpi_perf0: failed in PERF_STATUS attach
device_attach: acpi_perf0 attach returned 6
acpi_perf0: <ACPI CPU Frequency Control> on cpu0
acpi_perf0: failed in PERF_STATUS attach
device_attach: acpi_perf0 attach returned 6
acpi_throttle0: <ACPI CPU Throttling> on cpu0
cpu1: <ACPI CPU> on acpi0
acpi_perf1: <ACPI CPU Frequency Control> on cpu1
acpi_perf1: failed in PERF_STATUS attach
device_attach: acpi_perf1 attach returned 6
acpi_perf1: <ACPI CPU Frequency Control> on cpu1
acpi_perf1: failed in PERF_STATUS attach
device_attach: acpi_perf1 attach returned 6
acpi_throttle1: <ACPI CPU Throttling> on cpu1
acpi_throttle1: failed to attach P_CNT
device_attach: acpi_throttle1 attach returned 6
acpi_button0: <Power Button> 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: <ATI SB400 USB 2.0 controller> 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

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar - get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BAY104-F380F837FAD01A8CF3468BE9ADE0>