[VIA][C3] bad frequencies found

[VIA][C3] bad frequencies found

[yves piel]

Hello,

I have got a mini-itx C3 nehemoiah VIA mother board :
http://linitx.com/product_info.php?cPath=12_41&products_id=414

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 ?

thank you :)

ps : here is what I do as root :
------------------------------------------------
linimi:/tmp# modprobe longhaul

linimi:/tmp# dmesg |tail
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.
FAT: Filesystem panic (dev sda1)
    invalid access to FAT (entry 0x534c3436)
    File system has been set read-only
longhaul: VIA C3 'Nehemiah C' [C5N] CPU detected.  Powersaver supported.
longhaul: VIA C3 'Nehemiah C' [C5N] CPU detected.  Powersaver supported.
longhaul: VIA C3 'Nehemiah C' [C5N] CPU detected.  Powersaver supported.

linimi:/tmp# modprobe cpufreq_ondemand
linimi:/tmp# modprobe cpufreq_userspace

linimi:/tmp#cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
800000 1800000 900000 1100000 1200000 1400000 1600000 1000000 1300000
1500000 1700000 1800000
-------------------------------------------------

Re: [VIA][C3] bad frequencies found

[Dave Jones]

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

Re: [VIA][C3] bad frequencies found

[yves piel]

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...)