From: Stephen Clark <Stephen.Clark@seclark.us>
To: Shaun Q <shaun@c-think.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dual cores on Core2Duo not detected?
Date: Mon, 13 Nov 2006 08:46:34 -0500 [thread overview]
Message-ID: <4558773A.4040803@seclark.us> (raw)
In-Reply-To: <Pine.BSO.4.64.0611122322060.30536@ref.nmedia.net>
Hi Shaun,
Someone mentioned some bioses have an entry to enable the second core.
HTH,
Steve
Shaun Q wrote:
>Hi there everyone --
>
>I'm trying to build a custom kernel for using both cores of my new
>Core2Duo E6600 processor...
>
>I thought this was simply a matter of enabling the SMP support in the
>kernel .config and recompiling, but when the kernel comes back up, still
>only one core is detected.
>
>With the default vanilla text-based SuSE 10.1 install, it does find both
>cores...
>
>Anyone have any pointers for me on what I might be missing?
>
>Thanks!
>Shaun
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
--
"They that give up essential liberty to obtain temporary safety,
deserve neither liberty nor safety." (Ben Franklin)
"The course of history shows that as a government grows, liberty
decreases." (Thomas Jefferson)
next prev parent reply other threads:[~2006-11-13 13:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 7:24 Dual cores on Core2Duo not detected? Shaun Q
2006-11-13 13:46 ` Stephen Clark [this message]
2006-11-13 15:52 ` Shaun Q
2006-11-13 16:03 ` Jesper Juhl
2006-11-13 16:17 ` Shaun Q
2006-11-13 16:27 ` Arjan van de Ven
2006-11-13 16:33 ` Stephen Clark
2006-11-13 16:57 ` Shaun Q
2006-11-13 14:00 ` Jesper Juhl
2006-11-13 15:54 ` Shaun Q
2006-11-13 14:44 ` Mark Lord
2006-11-13 15:51 ` Shaun Q
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4558773A.4040803@seclark.us \
--to=stephen.clark@seclark.us \
--cc=linux-kernel@vger.kernel.org \
--cc=shaun@c-think.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox