On Fri, Mar 15, 2024 at 10:09:37AM +0100, Christer Solskogen via misc wrote: > On Fri, Mar 15, 2024 at 10:00 AM Jonathan Gray <j...@jsg.id.au> wrote: > > > > On Fri, Mar 15, 2024 at 08:49:14AM +0100, Christer Solskogen via misc wrote: > > > On Fri, Mar 15, 2024 at 1:15 AM Jonathan Gray <j...@jsg.id.au> wrote: > > > > > > > > > > > The 1MHz higher is the turbo setting. When speedstep speeds are shown > > > > in dmesg it is the highest. > > > > > > > > The sensors use cpu_hz_update_sensor(). > > > > > > > > > > I don't understand. dmesg says this: > > > cpu0: Intel(R) N95, 2693.79 MHz, 06-be-00, patch 00000015 > > > > > > But hw.cpuspeed stays the same no matter what happens. > > > > your dmesg will have a "Enhanced SpeedStep" line, for example: > > cpu0: Enhanced SpeedStep 2494 MHz: speeds: 2601, 2600, 2500, 2300, 2100, > > 2000, 1800, 1700, 1500, 1400, 1200, 1100, 900, 800, 600, 500 MHz > > > > hw.cpuspeed is only updated when a set speed is selected by the kernel. > > With turbo mode the hardware continually changes the speed without > > notifying the kernel. > > > > to force the lowest non-turbo mode > > > > sysctl hw.perfpolicy=manual > > sysctl hw.setperf=0 > > > > Ah, yes. > cpu0: Enhanced SpeedStep 2693 MHz: speeds: 1701, 1700, 1600, 1500, > 1400, 1300, 1200, 1100, 1000, 900, 800 MHz > > I wonder why it never reaches 2,6GHz. >
Your cpu*.frequency lines show you that it does. --
