From: John Weber <john.weber@linuxhq.com>
To: Darrel Hunt <darrelhu@earthlink.net>, linux-kernel@vger.kernel.org
Subject: Re: Upgrading Kernel
Date: Thu, 25 Apr 2002 16:06:34 -0400 [thread overview]
Message-ID: <3CC861CA.3040104@linuxhq.com> (raw)
In-Reply-To: <ucf0d9ilcjqge3@corp.supernews.com> <3CC845EA.6060405@linuxhq.com> <000201c1ec89$21025440$0400a8c0@famas>
Is this for real? comx.o has been broken since 2.4.0 it seems!
Anyone know anything about these modules?
Darrel, these errors are caused because (though the modules compile)
they are making references to functions that no longer exist in the
kernel. My advice is that (unless you really need to use these modules)
you configure your kernel to not include them.
Darrel Hunt wrote:
> Thanks, that helped alot. Now I'm running into another small problem,
> I've done it just as you listed. Everything goes good unitll I go to
> "make modules_install". The problem is that it halts with this description.
>
> mkdir -p pcmcia; \
> find kernel -path '*/pcmcia/*' -name '*.o' | xargs -i -r ln -sf ../{} pcmcia
> if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.18; fi
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18/kernel/drivers/net/wan/comx.o
> depmod: proc_get_inode
> depmod: *** Unresolved symbols in
> /lib/modules/2.4.18/kernel/drivers/telephony/ixj_pcmcia.o
> depmod: register_pccard_driver
> depmod: unregister_pccard_driver
> depmod: CardService
> > cp /usr/src/linux-2.4.5/.config /usr/src/linux-2.4.18/.config
> > cd /usr/src/linux-2.4.18
> > make oldconfig
> > make dep
> > make bzImage
> > make modules
> > make modules_install
> >
> > cp /usr/src/linux-2.4.18/arch/i386/boot/bzImage /boot/vmlinuz-2.4.18
> >
> > Then edit your /etc/lilo.conf, and add an entry for your new kernel.
> >
> > Run "lilo"
> >
> > Reboot.
> >
> > Hope this helps.
> >
parent reply other threads:[~2002-04-25 20:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <000201c1ec89$21025440$0400a8c0@famas>]
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=3CC861CA.3040104@linuxhq.com \
--to=john.weber@linuxhq.com \
--cc=darrelhu@earthlink.net \
--cc=linux-kernel@vger.kernel.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