From: Dave Jones <davej@redhat.com>
To: Tomas.Linden@helsinki.fi
Cc: cpufreq@vger.kernel.org
Subject: Re: Intel Core 2 Quad Q8400 reported as Unknown CPU
Date: Fri, 29 Apr 2011 15:21:02 -0400 [thread overview]
Message-ID: <20110429192101.GA5498@redhat.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1104291730500.2256@tux.hip.helsinki.fi>
On Fri, Apr 29, 2011 at 05:50:00PM +0300, Tomas.Linden@helsinki.fi wrote:
> Hello!
>
> I upgraded my Intel Core 2 Duo to a Core 2 Quad Q8400 on my Intel DP35DP motherboard.
> I send this mail because I found this messages in my dmesg:
>
> p4-clockmod: Unknown CPU. Please send an e-mail to <cpufreq@vger.kernel.org>
> p4-clockmod: Unknown CPU. Please send an e-mail to <cpufreq@vger.kernel.org>
> p4-clockmod: Unknown CPU. Please send an e-mail to <cpufreq@vger.kernel.org>
> p4-clockmod: Unknown CPU. Please send an e-mail to <cpufreq@vger.kernel.org>
ignore it, p4-clockmod is a waste of bits anyway.
> cpuinfo and dmesg are at the end of this e-mail. I'm a bit worried because
> I bought the new CPU to have hardware virtualization support (VT-X).
> http://ark.intel.com/Product.aspx?id=38512&processor=Q8400&spec-codes=SLGT6
> but cpuinfo does not list the vtx flag for me. I'm using Fedora 13 and I
> tried booting to a F14 USB stick as well and neither shows the vtx flag.
...
> processor : 0
> vendor_id : GenuineIntel
> cpu family : 6
> model : 23
> model name : 06/17
^^^^^
This is a sign your BIOS has no idea what that CPU is. It should be a nice
non-numeric name.
Which could explain why VTX isn't showing up. (Possibly also EST too, which
would be much better than using p4-clockmod).
Look for a BIOS update.
Dave
next prev parent reply other threads:[~2011-04-29 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 14:50 Intel Core 2 Quad Q8400 reported as Unknown CPU Tomas.Linden
2011-04-29 19:21 ` Dave Jones [this message]
2011-05-04 11:19 ` Tomas.Linden
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=20110429192101.GA5498@redhat.com \
--to=davej@redhat.com \
--cc=Tomas.Linden@helsinki.fi \
--cc=cpufreq@vger.kernel.org \
/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