From: James Mabry <jamabryl@student.gc.maricopa.edu>
To: cpufreq@www.linux.org.uk
Subject: Re: Athlon Mobile Support
Date: Wed, 02 Jul 2003 00:26:17 -0700 [thread overview]
Message-ID: <3F028919.8060402@student.gc.maricopa.edu> (raw)
Hello,
I am also using a Mobile Athlon XP. I got the
cpufreq-LINUX_2_4-20030701.tar.bz2 patch and applied it using 'sh
patchin.sh'. I am not seeing any of the entries in /proc that other
people have using cpufreq. Am I doing something wrong? Are there better
(any) instructions on how to go about using cpufreq? The users-guide
didn't help :(. Thanks.
--
Slackware Linux -
Find out about the 4S rule.
www.slackware-advocacy.org/whyuse.html
Then try it out for yourself.
www.slackware.org
next reply other threads:[~2003-07-02 7:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-02 7:26 James Mabry [this message]
2003-07-02 7:28 ` Athlon Mobile Support Lars Gemeinhardt
2003-07-02 7:49 ` James Mabry
2003-07-02 7:55 ` Lars Gemeinhardt
-- strict thread matches above, loose matches on Subject: below --
2003-07-02 7:36 Athlon Mobile support Iacopo Spalletti
2003-07-02 6:19 Iacopo Spalletti
2003-07-02 6:28 ` Lars Gemeinhardt
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=3F028919.8060402@student.gc.maricopa.edu \
--to=jamabryl@student.gc.maricopa.edu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox