Date: Mon, 15 Jan 2007 16:11:18 -0800 From: Nate Lawson <nate@root.org> To: John Baldwin <jhb@freebsd.org> Cc: freebsd-acpi@freebsd.org Subject: Re: acpi ok but cpufreq not supporting my CPUs Message-ID: <45AC1826.6080307@root.org> In-Reply-To: <200701151739.46792.jhb@freebsd.org> References: <87A429B7-46CD-426B-A56F-07D57F2E769E@patpro.net> <20070115165059.GP4945@poupinou.org> <200701151739.46792.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote: > On Monday 15 January 2007 11:51, Bruno Ducrot wrote: >> On Sun, Jan 14, 2007 at 10:02:06PM +0100, Patrick Proniewski wrote: >>> est0: <Enhanced SpeedStep Frequency Control> on cpu0 >>> est: CPU supports Enhanced Speedstep, but is not recognized. >>> est: cpu_vendor GenuineIntel, msr a1e0a1e06000a1e >>> device_attach: est0 attach returned 6 >>> p4tcc0: <CPU Frequency Thermal Control> on cpu0 >>> >>> (same for cpu1/2/3) >>> >>> Is there anything I can do to make "est" work with the sossaman CPU ? >>> >>> thanks in advance, >>> >> It's not possible, AFAIK, to build a static table for your processor, >> and in that case, we have to use an ACPI table in order to compute >> a custom table. If such information is not available, then there >> is little hope to make est working, being an SMP problem or not is >> not your problem I'm afraid. It maybe possible you forgot a >> BIOS option somewhat so such this configuration will be generated >> and exposed via ACPI though, or maybe you have to upgrade to a >> newer BIOS. > > One thing we can do is at least support the two modes encoded into the MSR > (the highest and lowest IIRC). I think I have a patch laying around > somewhere to do that. > That's a good idea. If you can send me a patch, I'd be happy to test. -- Nate
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45AC1826.6080307>