From: GregR <grcore@usamtb.com>
To: linux-acpi@vger.kernel.org
Subject: Re: 2.6.15-mm2 (acpi-cpufreq not loading)
Date: Fri, 20 Jan 2006 01:36:02 +0000 (UTC) [thread overview]
Message-ID: <loom.20060120T023226-507@post.gmane.org> (raw)
In-Reply-To: 43D00C86.3050403@ens-lyon.org
Brice Goglin <Brice.Goglin <at> ens-lyon.org> writes:
> Yes, modprobe's error is not shown in dmesg (I don't know whether it is
> configurable or not). I just double-checked my boot, I get :
[SNIP]
> In case if matters, acpi-cpufreq is loaded early (in /etc/modules on my
> Debian), before any other acpi modules is loaded (except processor since
> it depends on it).
If it helps, I had the same problem with 2.6.15, and I ended up building it in
[*], as opposed to a module [M] at compile time. Worked fine after that.
g
next prev parent reply other threads:[~2006-01-20 1:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 21:06 2.6.15-mm2 (acpi-cpufreq not loading) Brown, Len
2006-01-19 22:02 ` Brice Goglin
2006-01-20 1:36 ` GregR [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 8:31 Brown, Len
2006-01-20 13:59 ` Brice Goglin
2006-01-20 22:44 Pallipadi, Venkatesh
2006-01-21 4:24 ` Brice Goglin
2006-01-21 6:00 Pallipadi, Venkatesh
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=loom.20060120T023226-507@post.gmane.org \
--to=grcore@usamtb.com \
--cc=linux-acpi@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