From: Arik Raffael Funke <arik.funke@gmx.de>
To: cpufreq@lists.linux.org.uk
Subject: Re: Sempron 2800+
Date: Tue, 12 Sep 2006 22:31:15 +0200 [thread overview]
Message-ID: <45071913.7080708@gmx.de> (raw)
In-Reply-To: <B3870AD84389624BAF87A3C7B831499303FB29AD@SAUSEXMB2.amd.com>
shin, jacob wrote:
> On Tuesday, September 12, 2006 11:03 AM Arik Raffael Funke wrote:
>
>> dmesg | grep powern reports nothing at all... Is that supposed to be a
>> good or bad thing? I fear for the latter. ;-)
>>
>> Is there anything else I could provide to help with diagnosis?
>
> It is very possible that your Sempron does not support frequency
> scaling. Easy way to check is with cpuid instruction.
>
> Could you compile and run the following and copy us on the output?
Hi Shin,
the code you provided gives:
[root@funke ~]# ./cputest
00000009
[root@funke ~]#
Regards,
Arik
next prev parent reply other threads:[~2006-09-12 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-12 16:57 Sempron 2800+ shin, jacob
2006-09-12 20:31 ` Arik Raffael Funke [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-09-12 14:11 Arik Raffael Funke
2006-09-12 14:42 ` Langsdorf, Mark
2006-09-12 16:03 ` Arik Raffael Funke
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=45071913.7080708@gmx.de \
--to=arik.funke@gmx.de \
--cc=cpufreq@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox