From: Ducrot Bruno <ducrot@poupinou.org>
To: Matthias Hannich <dumb@tcpa-info.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Coppermine, cpufreq
Date: Thu, 30 Oct 2003 15:09:10 +0100 [thread overview]
Message-ID: <20031030140910.GH28351@poupinou.org> (raw)
In-Reply-To: <3FA11700.8080908@tcpa-info.org>
On Thu, Oct 30, 2003 at 02:49:52PM +0100, Matthias Hannich wrote:
> Hi,
>
> I have a laptop (Gericom Webboy) with a PIII Coppermine.
> I am working on a 2.4.22-kernel (from kernel.org) and patched the
> patch-2.4.22-ac4.bz2 from Alan Cox against it.
>
> Because of having a low battery-capacity I tried to enable cpufreq and
> ACPI-stuff in the kernel (and tried to compile them as modules as well).
>
...
> root:/usr/src/linux-2.4.22# insmod speedstep-ich
> Using /lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o
> /lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o:
> unresolved symbol speedstep_get_processor_frequency
> /lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o:
> unresolved symbol speedstep_detect_processor
> /lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o:
> unresolved symbol speedstep_get_freqs
>
What about a
modprobe speedstep-ich
instead of insmod?
PS: If modprobe speedstep-ich still do not work
modpbore speedstep-lib
modprobe speedstep-ich
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2003-10-30 14:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-30 13:49 Coppermine, cpufreq Matthias Hannich
2003-10-30 14:09 ` Ducrot Bruno [this message]
2003-10-30 21:08 ` Matthias Hannich
2003-10-31 7:14 ` Ducrot Bruno
2003-10-31 12:40 ` Matthias Hannich
2003-11-02 13:29 ` Ducrot Bruno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031030140910.GH28351@poupinou.org \
--to=ducrot@poupinou.org \
--cc=cpufreq@www.linux.org.uk \
--cc=dumb@tcpa-info.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox