From: michel.mengis@epfl.ch
To: linux <linux-kernel@vger.kernel.org>
Subject: Kernel 2.6.8 and DELL's DOTHAN Processor B0
Date: Fri, 8 Oct 2004 08:21:29 +0200 [thread overview]
Message-ID: <1097216489.416631e91faf9@imapwww.epfl.ch> (raw)
Hi all,
I have a lot of trouble to bring the kernel 2.6.8-1 to detect my dothan
processor.
It's a Pentium M Dothan B0 version, 1.7Ghz/600Mhz.
The BIOS is DELL's D800 Bios version 09.
I added 3 patches:
cpufreq-speedstep-dothan-3.patch :add correct frequency table in speedstep.c
dothan-speedstep-fix.patch : add correct Level2 cache
bk-cpufreq.patch : from http://linux-dj.bkbits.net/cpufreq
I added a lot of output in speedstep-centrino.c, acpi/processor.c to track the
problem.
I notice that my computer is running always in the lowest speed evenif I'm
stressing it... All ouputs I added show me that Speedstep isn't the cause,
neither CPUFreq but while CPUFreq calls all notifiers, acpi/processor.c's
CPUFREQ_INCOMPATIBLE change the max speed to the lowest evenif during
cpufreq_acpi_cpu_init the max speed is well detected.
Seems to be like it's coz at boot time the kernel doesn't detect correctly the
max speed.
dmesg shows me that a 600Mhz processor has been detected only and not 1.7Ghz.
(on my D600 pentium M not dothan, it detects correctly 1.6Ghz)
is there a fix for that ?
is it a known bug ?
thx for all help I can get,
best regards,
michel.
next reply other threads:[~2004-10-08 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 6:21 michel.mengis [this message]
2004-10-08 6:34 ` Con Kolivas
2004-10-08 6:56 ` michel.mengis
2004-10-08 7:36 ` Kernel 2.6.8 and DELL's DOTHAN Processor B0 (more informations) michel.mengis
[not found] <20041008073837.GA7413@dominikbrodowski.de>
2004-10-08 8:17 ` Kernel 2.6.8 and DELL's DOTHAN Processor B0 michel.mengis
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=1097216489.416631e91faf9@imapwww.epfl.ch \
--to=michel.mengis@epfl.ch \
--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
all inboxes | Powered by JetHome®