[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#594952: linux-image doesn't work properly with Pentium M CPU

-------- Forwarded Message --------
From: Alexey <nikvart@gmail.com>
To: Ben Hutchings <ben@decadent.org.uk>
Subject: Re: Bug#594952: linux-image doesn't work properly with Pentium M CPU
Date: Mon, 6 Sep 2010 14:13:53 +0700

Thanks for suggesting this, but after searching the web I don't think this
applies to my situation: my processor isn't stuck at the lowest frequency
when using acpi-cpufreq, but rather it refuses to load with the error
message "no such device"...

On Sun, Sep 5, 2010 at 8:40 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
        On Tue, 2010-08-31 at 12:11 +0700, Alexey wrote:
        > Package: linux-image-2.6-686
        > Version: 2.6.32+28
        > Computer: Fujitsu-Siemens AMILO L7300
        > The fact that acpi-cpufreq is not working properly with Dothan CPU's.
        I don't think that's true.  It really depends on whether the BIOS
        provides correct information about the available frequencies.
        > FATAL: Error inserting acpi_cpufreq: No such device
        Please try creating the file /etc/modprobe.d/processor-ppc.conf
        containing the text:
           options processor ignore_ppc=1
        and then reboot.
        > On Ubuntu Karmic/Jaunty all works fine. It uses speedstep_centrino
        > driver, which is deprecated, but works with BIOS which have broken
        > voltage tables..
        > Link to Ubuntu Patch:
        > http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=blobdiff;f=arch/x86/kernel/cpu/cpufreq/speedstep-centrino.c;h=ee4e9f8050752923f9671f61ffbea662bc9ad12a;hp=9b1ff37de46ae6a729f48d2d94ad30548806884d;hb=23120eb5ae5a12924565e8af3d946a015e1caaf9;hpb=215cc71ef0b26b9434404f387681d9bd173d2434
        This doesn't seem like a good idea, and it has not been accepted by the
        upstream developers.
        Ben Hutchings
        Once a job is fouled up, anything done to improve it makes it worse.

Reply to: