cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Hannich <dumb@tcpa-info.org>
To: Ducrot Bruno <ducrot@poupinou.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: Coppermine, cpufreq
Date: Thu, 30 Oct 2003 22:08:47 +0100	[thread overview]
Message-ID: <3FA17DDF.5000600@tcpa-info.org> (raw)
In-Reply-To: <20031030140910.GH28351@poupinou.org>

Am 10/30/2003 03:09 PM schrieb Ducrot Bruno:
> What about a
> modprobe speedstep-ich
> instead of insmod?

root:/# modprobe speedstep-ich
/lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o: 
init_module: No such device
Hint: insmod errors can be caused by incorrect module parameters, 
including invalid IO or IRQ parameters.
       You may find more information in syslog or the output from dmesg 
(can't find anything there)

/lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o: 
insmod 
/lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o failed
/lib/modules/2.4.22-ac4-486/kernel/arch/i386/kernel/speedstep-ich.o: 
insmod speedstep-ich failed

> PS: If modprobe speedstep-ich still  do not work
> modpbore speedstep-lib

No error messages.

> modprobe speedstep-ich

The same as above.

Thanks, Matthias
-- 
Freundliche Grüße,          ###  http://www.stop1984.com
Matthias Hannich            ###  nulli@stop1984.com
                             ###  KeyID: 407A2F69
Fingerprint: 600D 7E07 105C F674 0C4B  12C2 4DE4 A8DF 407A 2F69

  reply	other threads:[~2003-10-30 21:08 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
2003-10-30 21:08   ` Matthias Hannich [this message]
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=3FA17DDF.5000600@tcpa-info.org \
    --to=dumb@tcpa-info.org \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ducrot@poupinou.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