public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix von Leitner <felix-linuxkernel@fefe.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Adam Belay <abelay@novell.com>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, cpufreq@ZenII.linux.org.uk
Subject: Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10
Date: Fri, 25 Mar 2005 01:17:30 +0100	[thread overview]
Message-ID: <20050325001729.GA30397@codeblau.de> (raw)
In-Reply-To: <42434E60.1060209@goop.org>

Thus spake Jeremy Fitzhardinge (jeremy@goop.org):
> Unfortunately, the Dothans *REQUIRE* some degree of ACPI support; the
> speedfreq-centrino needs to extract a table from ACPI to know what are
> valid operating (voltage/frequency) points to use for the CPU.  The
> patch you're using is definitely wrong in principle, though if it works
> for you in practice then by all means use it.

I enabled these:

  CONFIG_CPU_FREQ=y
  CONFIG_CPU_FREQ_STAT=y
  CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y
  CONFIG_CPU_FREQ_GOV_PERFORMANCE=y
  CONFIG_CPU_FREQ_GOV_POWERSAVE=y
  CONFIG_CPU_FREQ_GOV_USERSPACE=y
  CONFIG_CPU_FREQ_GOV_ONDEMAND=y
  CONFIG_CPU_FREQ_TABLE=y
  CONFIG_X86_SPEEDSTEP_CENTRINO=y
  CONFIG_X86_SPEEDSTEP_CENTRINO_ACPI=y
  CONFIG_X86_SPEEDSTEP_CENTRINO_TABLE=y

It should have worked, shouldn't it?

Well, it did not.  You can look at the kernel messages at
http://dl.fefe.de/dmesg.gz if that helps.

No cpufreq, and as far as I can see, no speedstep.
The fan is running, that's all I can tell.

Felix

  reply	other threads:[~2005-03-25  0:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-11 20:21 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Felix von Leitner
2005-03-12  1:32 ` Andrew Morton
2005-03-13 21:30   ` Felix von Leitner
2005-03-12  1:33 ` Andrew Morton
2005-03-22  0:33   ` Andrew Morton
2005-03-22  2:18     ` Johannes Stezenbach
2005-03-22 16:22       ` Johannes Stezenbach
2005-03-24 11:59   ` [PATCH] [IPV6] Fix address/interface handling according to the scoping architecture (is Re: 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10) YOSHIFUJI Hideaki / 吉藤英明
2005-04-25 19:57     ` IPv6 has trouble assigning an interface Felix von Leitner
2005-04-25 21:00       ` Pekka Savola
2005-04-26  6:10         ` Felix von Leitner
2005-04-27 22:57           ` Kyle Moffett
2005-04-27 23:31             ` David Stevens
2005-03-12  1:35 ` 2.6.11: USB broken on nforce4, ipv6 still broken, centrino speedstep even more broken than in 2.6.10 Andrew Morton
2005-03-12  3:54   ` Adam Belay
2005-03-22  0:32     ` Andrew Morton
2005-03-22  1:20       ` Adam Belay
2005-03-22 22:29         ` Felix von Leitner
2005-03-24 23:33           ` Jeremy Fitzhardinge
2005-03-25  0:17             ` Felix von Leitner [this message]
2005-03-25 13:37         ` Bruno Ducrot
2005-03-13 21:31   ` Felix von Leitner
2005-03-12  3:51 ` Adam Belay
     [not found] <3GZyA-16B-17@gated-at.bofh.it>
2005-03-12  5:06 ` Robert Hancock
2005-03-12  5:19   ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2005-03-12 10:24 Stefan Rompf
2005-03-12 20:34 ` Greg KH

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=20050325001729.GA30397@codeblau.de \
    --to=felix-linuxkernel@fefe.de \
    --cc=abelay@novell.com \
    --cc=akpm@osdl.org \
    --cc=cpufreq@ZenII.linux.org.uk \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@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