since I don't have a connection from the laptop to the pc that will handle
anything over 1.4mb (ie.floppy drive) I compiled the kernel on my desktop,
then copied the kernel, system.map and module tree. (adding in the modules
and startup information for pcmcia) so all of that is as it should be....
but when I startup the computer, and it goes to load the modules it prints
the error "kernel version not found" and doesn't load the module, that is
the case for modules that are loaded in the beginning, and ones that I
manually load. Is there a file or environment variable that is causing this?

Erik Ekedahl
(e-mail) [EMAIL PROTECTED]
(web page) www.geocities.com/soho/atrium/9422/

Erik was beginning to behave rather strangely, or rather not actually
beginning to behave strangely but beginning to behave in a way which was
strangely different from the other strange ways in which he more regularly
behaved.

----- Original Message -----
From: "E Justin M Rowles" <[EMAIL PROTECTED]>
To: "The Ekedahl Family" <[EMAIL PROTECTED]>
Sent: Friday, June 02, 2000 3:25 AM
Subject: Re: kernel version for all to find?


> The Ekedahl Family wrote:
> >
> > I installed the distro "Giotto" onto my laptop, I then installed a new
> > kernel, it was running a 2.0.37 kernel, I couldn't get that to work with
> > pcmcia so I compiled on my desktop kernel version 2.2.14 then copied the
> > kernel, modules, and pcmcia package over to the laptop and installed it
in
> > lilo, it will boot up but it has problems loading modules. I fixed the
>
> PCMCIA modules use some kernel classes.  You *must* have PCMCIA compiled
> for the kernel you are running.
>
> The easiest way to do this is download a tarball of the source, unzip in
> /usr/src/ and follow the instructions in the accompanying PCMCIA-HOWTO
> document.  It's not a complex package.  If you are running a (say)
> 2.2.14 kernel then the kernel will load modules from /lib/2.2.14/ so
> they need to be *there*.
>
> Have fun.
>
> J.
> --
> You're only jealous cos the little penguins are talking to me.
>

Reply via email to