Hi Sepherosa,
Well, I think I will need AMD 06h family BKDG to figure out how the
ACPI VID and FID should be used. The code we have messed w/ so far is
according to AMD 0fh family BKDG.
I'm doing some research and looking how other operating systems works
with my Athlon XP-M processor.
1)
Ok. Remove the old patch and try this one:
http://leaf.dragonflybsd.org/~sephe/pstate.c.diff1
Thanks for your support Sepherosa, but unfortunately it still does not work.
The last patch triggered others errors like the following:
cpu0: Invalid FID 0x20, out [0xe, 0x16]
cpu0: Invalid VID 0x6,
On 14 sep 2011, at 20.45, Maurizio Lombardi wrote
Ok. Remove the old patch and try this one:
http://leaf.dragonflybsd.org/~sephe/pstate.c.diff1
Thanks for your support Sepherosa, but unfortunately it still does not work.
The last patch triggered others errors like the following:
cpu0:
You could try to set hw.acpi.cpu.pstate.strigent_check=0 in
/boot/loader.conf. My K8 box needs that for it's messed up FID/VID.
Thanks,
I tried but the kernel freezes at boot.
It prints a lot of error like:
cpu0: Invalid FID
cpu0: Invalid VID...
The last two lines it prints are a bit
On Thu, Sep 15, 2011 at 4:13 AM, Maurizio Lombardi
m.lombard...@gmail.com wrote:
You could try to set hw.acpi.cpu.pstate.strigent_check=0 in
/boot/loader.conf. My K8 box needs that for it's messed up FID/VID.
Thanks,
I tried but the kernel freezes at boot.
It prints a lot of error like:
Try following patch:
http://leaf.dragonflybsd.org/~sephe/pstate_machdep.c.diff
See whether following sysctl appears:
hw.acpi.cpu.px_dom0.select
I applied your patch and rebuild the kernel.
Unfortunately it does not work:
#sysctl -a | grep px
#
Now it does not print anything at all!
Any
On Wed, Sep 14, 2011 at 5:25 AM, Maurizio Lombardi
m.lombard...@gmail.com wrote:
Try following patch:
http://leaf.dragonflybsd.org/~sephe/pstate_machdep.c.diff
See whether following sysctl appears:
hw.acpi.cpu.px_dom0.select
I applied your patch and rebuild the kernel.
Unfortunately it
On Sun, Sep 11, 2011 at 6:46 PM, Maurizio Lombardi
m.lombard...@gmail.com wrote:
Under most of the cases, powernow kernel module is outdated, you
should use acpi p-states if possible.
It looks like acpi p-states do exist, but lacking CPU driver. Could
you post the dmesg?
dmesg attached,
Hi,
I installed DFly on an old laptop with an AMD Athlon XP-Mobile processor,
unfortunately I'm unable to scale down the processor frequency, it's a
problem for me because it makes the laptop to become very hot.
First of all, I tried to load the powernow kernel module:
#kldload powernow.ko
but
I'm looking at the DFly BSD powernow and the FreeBSD's powernow
drivers differences.
If I'm not wrong, the DFly powernow does not support the K7
architecture, is it correct?
--
Maurizio Lombardi
On Sun, Sep 11, 2011 at 5:51 PM, Maurizio Lombardi
m.lombard...@gmail.com wrote:
I'm looking at the DFly BSD powernow and the FreeBSD's powernow
drivers differences.
If I'm not wrong, the DFly powernow does not support the K7
architecture, is it correct?
Under most of the cases, powernow
11 matches
Mail list logo