From: yves piel <yvespiel@free.fr>
To: Dave Jones <davej@redhat.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: [VIA][C3] bad frequencies found
Date: Mon, 14 Nov 2005 23:10:01 +0100 [thread overview]
Message-ID: <1132006201.4650.3.camel@linimi.narma.net> (raw)
In-Reply-To: <20051114213909.GC16506@redhat.com>
Le lundi 14 novembre 2005 à 16:39 -0500, Dave Jones a écrit :
> On Mon, Nov 14, 2005 at 10:26:22PM +0100, yves piel wrote:
> >
> > So I should can scale my cpu frequency between 533Mhz and 1.2Ghz. But,
> > when I load longhaul module, the available cpu frquencies are 800000 for
> > the min, and 180000 for the max.
> > How can I tell t the longhaul driver than mys cpu can scale down to
> > 533Mhz and only up to 1.2Ghz ?
>
> My first guess is that we've guessed the FSB incorrectly.
> Can you boot with cpufreq.debug=7 and paste the extended
> debug messages that end up in dmesg after loading the module ?
>
> Dave
>
>
ho :( I add the option "cpufreq.debug=7" into the grub boot line (e for
edition and b to boot), I boot so, but when I load longhaul I have no
more infos into dmesg....
I try this to :
-------------------------------------------------------
linimi:/home/narma# modprobe longhaul cpufreq.debug=7
FATAL: Error inserting longhaul
(/lib/modules/2.6.14-1-386/kernel/arch/i386/kernel/cpu/cpufreq/longhaul.ko): Unknown symbol in module, or unknown parameter (see dmesg)
linimi:/home/narma# dmesg |tail
ReiserFS: sda8: checking transaction log (sda8)
ReiserFS: sda8: Using r5 hash to sort names
kjournald starting. Commit interval 5 seconds
EXT3-fs warning: maximal mount count reached, running e2fsck is
recommended
EXT3 FS on sda9, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
longhaul: VIA C3 'Nehemiah C' [C5N] CPU detected. Powersaver supported.
longhaul: Unknown parameter `cpufreq.debug'
longhaul: VIA C3 'Nehemiah C' [C5N] CPU detected. Powersaver supported.
longhaul: Unknown parameter `cpufreq.debug'
-------------------------------------------------------
What should I do ? (maybe I don't know how to pass parameter to the
kernel at boot time...)
prev parent reply other threads:[~2005-11-14 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-14 21:26 [VIA][C3] bad frequencies found yves piel
2005-11-14 21:39 ` Dave Jones
2005-11-14 22:10 ` yves piel [this message]
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=1132006201.4650.3.camel@linimi.narma.net \
--to=yvespiel@free.fr \
--cc=cpufreq@lists.linux.org.uk \
--cc=davej@redhat.com \
/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.