All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: cpufreq@www.linux.org.uk
Subject: [Bug 8228] acpi-cpufreq does not load - Fujitsu Siemens Amilo M1425, M1437G - Intel(R) Pentium(R) M
Date: Mon, 18 Jun 2007 22:02:43 -0700 (PDT)	[thread overview]
Message-ID: <20070619050243.C20DB10812A@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-8228-3570@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=8228





------- Comment #30 from daniel@pressure.net.nz  2007-06-18 22:06 -------
(In reply to comment #20)
> >Len, hope this is sufficient info for you. Kernel compiled with cpufreq debug
> >enabled, and booted with cpufreq.debug=7
> Please
> #echo 0x1f >/sys/module/acpi/parameter/debug_level
> and modprobe the cpufreq driver again.
> Hope we can get more information from the _dmesg_ output.

With 2.6.22-rc3, I'm unable to modprobe acpi or acpi-cpufreq ("No such device")
and thus unable to echo the 0x1f debug flag. lsmod shows asus-acpi already
loaded however.

Attaching an updated dmesg output.


-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

       reply	other threads:[~2007-06-19  5:02 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8228-3570@http.bugzilla.kernel.org/>
2007-06-19  5:02 ` bugme-daemon [this message]
2007-06-19  5:03 ` [Bug 8228] acpi-cpufreq does not load - Fujitsu Siemens Amilo M1425, M1437G - Intel(R) Pentium(R) M bugme-daemon
2007-06-19  6:12 ` bugme-daemon
2007-06-19  6:16 ` bugme-daemon
2007-06-19  6:28 ` bugme-daemon
2007-06-19  8:16 ` bugme-daemon
2007-06-19  8:51 ` bugme-daemon
2007-06-19  9:01 ` bugme-daemon
2007-06-19 10:37 ` bugme-daemon
2007-06-19 10:40 ` bugme-daemon
2007-06-20  1:40 ` bugme-daemon
2007-06-20  3:49 ` bugme-daemon
2007-06-20  3:49 ` bugme-daemon
2007-06-20  3:50 ` bugme-daemon
2007-06-20  3:50 ` bugme-daemon
2007-06-20  3:51 ` bugme-daemon
2007-06-20  3:51 ` bugme-daemon
2007-06-20  3:52 ` bugme-daemon
2007-06-20  9:03 ` bugme-daemon
2007-06-20 11:35 ` bugme-daemon
2007-07-05 11:23 ` bugme-daemon
2007-07-05 23:51 ` bugme-daemon
2007-07-09  6:47 ` bugme-daemon
2007-08-07 22:58 ` bugme-daemon
2007-06-06  5:06 bugme-daemon
  -- strict thread matches above, loose matches on Subject: below --
2007-06-05  8:14 bugme-daemon
2007-04-30 14:15 bugme-daemon
2007-04-30 14:14 bugme-daemon
2007-04-30 14:12 bugme-daemon
2007-04-30 14:12 bugme-daemon
2007-04-30 14:11 bugme-daemon
2007-04-30 14:10 bugme-daemon
2007-04-30 14:10 bugme-daemon
2007-04-30 14:09 bugme-daemon
2007-04-30 13:42 bugme-daemon
2007-04-12  9:08 bugme-daemon
2007-03-27  1:16 bugme-daemon
2007-03-27  1:12 bugme-daemon
2007-03-26 20:07 bugme-daemon
2007-03-26 19:52 bugme-daemon
2007-03-26 16:49 bugme-daemon
2007-03-26 16:46 bugme-daemon

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=20070619050243.C20DB10812A@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=cpufreq@www.linux.org.uk \
    /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.