From: Jarod Wilson <jwilson@redhat.com>
To: Uli Brueggemann <uli.brueggemann@gmail.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Modprobe of cpufreq modules fails
Date: Mon, 12 Nov 2007 10:04:38 -0500 [thread overview]
Message-ID: <47386B86.3010306@redhat.com> (raw)
In-Reply-To: <10a58eee0711120143v7b82e98cncb16e9f07a9de21f@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 903 bytes --]
Uli Brueggemann wrote:
> I'm running a Core 2 Duo system. With different kernels (up to 2.6.23.1 or
> 2.6.24-rc2) I cannot modprobe acpi_cpufreq or speedsteep-centrino or ...
> So I always get the report "no such device".
You definitely want acpi-cpufreq, not speedstep-centrino... The 'no such
device' message usually indicates that upon querying your BIOS ACPI
tables, acpi-cpufreq found no valid frequency scaling information, which
suggests either freq scaling is disabled in the BIOS or your BIOS has
busted ACPI (in which case a newer BIOS for your board, if available,
might help).
Also, you can boot with the added parameter 'cpufreq.debug=7' to get a
bit more info spit out in dmesg about what's going on when you try to
load acpi-cpufreq. Could give some further insight into what went wrong
and/or verify what I suggested above.
--
Jarod Wilson
jwilson@redhat.com
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 251 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
_______________________________________________
Cpufreq mailing list
Cpufreq@lists.linux.org.uk
http://lists.linux.org.uk/mailman/listinfo/cpufreq
next prev parent reply other threads:[~2007-11-12 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 9:43 Modprobe of cpufreq modules fails Uli Brueggemann
2007-11-12 15:04 ` Jarod Wilson [this message]
[not found] ` <10a58eee0711130024u2fb6f1das29db87d0932323@mail.gmail.com>
2007-11-13 8:25 ` Uli Brueggemann
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=47386B86.3010306@redhat.com \
--to=jwilson@redhat.com \
--cc=cpufreq@lists.linux.org.uk \
--cc=uli.brueggemann@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.