cpufreq Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dominik Brodowski <linux@brodo.de>
To: Jan De Luyck <ml@kcore.org>
Cc: cpufreq@www.linux.org.uk
Subject: Re: 2.4.22-jl9: speedstep-centrino.o: init_module: No such device
Date: Wed, 27 Aug 2003 08:20:52 +0200	[thread overview]
Message-ID: <20030827062052.GA4468@brodo.de> (raw)
In-Reply-To: <200308270743.34643.ml@kcore.org>

On Wed, Aug 27, 2003 at 07:43:34AM +0200, Jan De Luyck wrote:
> On Tuesday 26 August 2003 22:36, Dominik Brodowski wrote:
> > On Tue, Aug 26, 2003 at 10:06:36PM +0200, Jan De Luyck wrote:
> > > I just patched my 2.4.22 with this patch - so i can get centrino
> > > speedstep support in 2.4 - but it won't load:
> > >
> > > # modprobe speedstep-centrino
> > > /lib/modules/2.4.22-jl9/kernel/arch/i386/kernel/speedstep-centrino.o:
> > > init_module: No such device
> > >
> > > Any ideas?
> >
> > Could you post your /proc/cpuinfo to the cpufreq mailing list at
> > cpufreq@www.linux.org.uk, please?

Thanks. Here's the (most likely) problem: the -jl kernel patch misses a
critical update to the speedstep-centrino module which is necessary to get
it loaded. Either get the latest cpufreq CVS sources from
http://cvs.arm.linux.org.uk [check for the latest LINUX_2_4 nightly build] and 
replace -jl9's arch/i386/kernel/speedstep-centrino.c with the version in the linux_2_4
CVS, or contact the -jl maintainer to do the update and release a new -jl
kernel.

	Dominik

  reply	other threads:[~2003-08-27  6:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200308262206.37039.lkml@kcore.org>
     [not found] ` <20030826203637.GA18392@brodo.de>
2003-08-27  5:43   ` 2.4.22-jl9: speedstep-centrino.o: init_module: No such device Jan De Luyck
2003-08-27  6:20     ` Dominik Brodowski [this message]
2003-08-27  8:12       ` Jan De Luyck
2003-08-27  8:28         ` Dominik Brodowski
2003-08-27  9:07       ` Bas Mevissen
2003-08-27 10:06         ` Russell King
2003-08-27 10:31           ` Bas Mevissen

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=20030827062052.GA4468@brodo.de \
    --to=linux@brodo.de \
    --cc=cpufreq@www.linux.org.uk \
    --cc=ml@kcore.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