on 01/11/2010 15:36 Joerg Traeger said the following:
> Est still cannot attach.
> 
> Nov  1 14:28:10 kiste kernel: est0: <Enhanced SpeedStep Frequency Control> on 
> cpu0
> Nov  1 14:28:10 kiste kernel: est0: Guessed bus clock (high) of 32 MHz
> Nov  1 14:28:10 kiste kernel: est0: Guessed bus clock (low) of 416 MHz
> Nov  1 14:28:10 kiste kernel: est: CPU supports Enhanced Speedstep, but is 
> not 
> recognized.
> Nov  1 14:28:10 kiste kernel: est: cpu_vendor GenuineIntel, msr 
> 61a4c1f06004c1f
> Nov  1 14:28:10 kiste kernel: device_attach: est0 attach returned 6
> Nov  1 14:28:10 kiste kernel: est1: <Enhanced SpeedStep Frequency Control> on 
> cpu1
> Nov  1 14:28:10 kiste kernel: est1: Guessed bus clock (high) of 32 MHz
> Nov  1 14:28:10 kiste kernel: est1: Guessed bus clock (low) of 416 MHz
> Nov  1 14:28:10 kiste kernel: est: CPU supports Enhanced Speedstep, but is 
> not 
> recognized.
> Nov  1 14:28:10 kiste kernel: est: cpu_vendor GenuineIntel, msr 
> 61a4c1f06004c1f
> Nov  1 14:28:10 kiste kernel: device_attach: est1 attach returned 6
> 
> Is there anything else to try or is Intel (the board vendor) just to blame to 
> omit something important?
> Windows is able to bypass this problem so Intel will never fix this?

I am out of ideas.
Perhaps other OSes have hardcoded tables for your CPU.
You can try searching for that.

You can also try some other OS and see what speeds and voltages are reported
E(I)ST there.

-- 
Andriy Gapon
_______________________________________________
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"

Reply via email to