From: emmel <the_emmel@gmx.net>
To: cpufreq@www.linux.org.uk
Subject: Athlon XP1600+
Date: Thu, 17 Jul 2003 10:22:19 +0200 [thread overview]
Message-ID: <03071710221906.00210@gate> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
That problem may have been discussed before...
I've run cpufreq with a 2.4.20 and everything worked all right (well, at
least it looked like it did; I never checked the real CPU speed). With 2.5.72
(and 2.6.0-test1) I suddenly have cpufreq tell me that it can scale between
500MHz and 600MHz and I'm getting infos about the CPU running at 866 or 600
MHz (from some kde info tool, I think it reads out /proc). I'm using the k7
code, but I have been doing so with the 2.4.20 kernel as well. If someone
could point me to my problem...
(odd enough ACPi reports my processor as 1500+ since I upgraded the kernel as
well - maybe that has something to do with it)
- --
emmel <the_emmel@gmx.net>
Official AGC feedback maniac
"God is playing creatures - and we're the norns."
"A hundred dead are a tragedy - a hundred thousand are statistics."
"I guess you can call yourself lucky." -
"I could, but Linda suits me a little better... :)
Things called lucky tend to get hit by trucks."
GPG 1.2.1 signed
Fingerprint: 60B4 D8E3 9617 900C 6726 168F D677 5AAD D40F CCE7
Certserver : ldap://certserver.pgp.com
Hi, I'm a .sig virus. Just copy me to your .signature. And don't worry.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE/Fly81ndardQPzOcRAvepAJ9tY8o7IGqlH7Ll8qZY5+HL7Q0+jgCgiIZB
RVLUifMCkYs06Rrjz40m5yM=
=72jp
-----END PGP SIGNATURE-----
reply other threads:[~2003-07-17 8:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=03071710221906.00210@gate \
--to=the_emmel@gmx.net \
--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.