On Sat, 2005-11-26 at 01:51 -0800, Ted Unangst wrote:
> since the dmesg you posted previously contains the line:
> ichpcib0 at pci0 dev 31 function 0 "Intel 82801DBM LPC" rev 0x03: SpeedStep
>
> i think you're confused about something.
Indeed, I must be very confused. I did the dmesg check on the
On 11/26/05, Lars Hansson <[EMAIL PROTECTED]> wrote:
> On Sat, 2005-11-26 at 01:33 -0800, Ted Unangst wrote:
> > On 11/25/05, Lars Hansson <[EMAIL PROTECTED]> wrote:
> > > Is there any way to determine from the dmesg if speedstep is
> > > detected?
> >
> > dmesg | grep SpeedStep works pretty well.
On Sat, 2005-11-26 at 01:33 -0800, Ted Unangst wrote:
> On 11/25/05, Lars Hansson <[EMAIL PROTECTED]> wrote:
> > Is there any way to determine from the dmesg if speedstep is
> > detected?
>
> dmesg | grep SpeedStep works pretty well.
Well, that comes up empty so I guess the speedstep in this
box
On 11/25/05, Lars Hansson <[EMAIL PROTECTED]> wrote:
> Is there any way to determine from the dmesg if speedstep is
> detected?
dmesg | grep SpeedStep works pretty well.
On Friday 25 November 2005 20:03, Ted Unangst wrote:
> maybe, speedstep can only be set to fast and slow, and the driver
> won't move things if it thinks nothing is changing. maybe there's a
> bug, maybe you need to fiddle it up and down some to make it actually
> work, but 0 and 100 are the only
On 11/23/05, Lars Hansson <[EMAIL PROTECTED]> wrote:
> This seems a bit strange to ne:
> $ sysctl hw | tail -2
> hw.cpuspeed=1296
> hw.setperf=100
>
> $ sudo sysctl -w hw.setperf=0
> hw.setperf: 100 -> 0
> $ sysctl hw | tail -2
> hw.cpuspeed=1296
> hw.setperf=0
>
> Hmm..shouldnt cpuspeed have chang
On Thu, 24 Nov 2005 18:48:44 -0700
Theo de Raadt <[EMAIL PROTECTED]> wrote:
> Oh come on.
>
> You think we have all day to find various mails from various people and
> piece them together?
Indeed, that would be silly. I should have attached it. My mistake.
---
Lars Hansson
On Thu, 24 Nov 2005 10:03:44 +0800
Lars Hansson <[EMAIL PROTECTED]> wrote:
> It would appear that changing hw-setperf doesn't actually do anything at all
> on this box. The dmesg says it has Speedstep though.
Err, it has speedstep but that's not in the dmesg.
---
Lars Hansson
> > *classic* bug report. You completely fail to mention the machine
> > type, or show a dmesg.
> Actually, I sent the dmesg in my immediatelly previous message to the list
> and therefore I didnt attach again.
Oh come on.
You think we have all day to find various mails from various people and
p
On Thu, 24 Nov 2005 09:23:32 -0700
Theo de Raadt <[EMAIL PROTECTED]> wrote:
> *classic* bug report. You completely fail to mention the machine
> type, or show a dmesg.
Actually, I sent the dmesg in my immediatelly previous message to the list
and therefore I didnt attach again.
As for the machine
*classic* bug report. You completely fail to mention the machine
type, or show a dmesg. I just don't get it. How is it that people
keep forgetting that? Are they just totally unaware that there
are machine differences, and they might matter?
> This seems a bit strange to ne:
> $ sysctl hw | ta
11 matches
Mail list logo
