From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: Martin MOKREJ?? <mmokrejs@ribosome.natur.cuni.cz>
Cc: Arjan van de Ven <arjan@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Unresolved symbols in /lib/modules/2.4.28-pre2/xfree-drm/via_drv.o
Date: Wed, 16 Mar 2005 08:53:12 -0300 [thread overview]
Message-ID: <20050316115312.GA12881@logos.cnet> (raw)
In-Reply-To: <42384EE8.9000003@ribosome.natur.cuni.cz>
On Wed, Mar 16, 2005 at 04:21:12PM +0100, Martin MOKREJ? wrote:
> Arjan van de Ven wrote:
> >On Wed, 2005-03-16 at 16:03 +0100, Martin MOKREJ?? wrote:
> >
> >>Hi,
> >> does anyone still use 2.4 series kernel? ;)
>
> >># make dep; make bzImage; make modules
> >>[cut]
> >># make modules_install
> >>[cut]
> >>cd /lib/modules/2.4.30-pre3-bk2; \
> >>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.30-pre3-bk2; fi
> >>depmod: *** Unresolved symbols in
> >>/lib/modules/2.4.28-pre2/xfree-drm/via_drv.o
> >
> >
> >this is not the module shipped by the kernel.org kernel...
>
> Right. Sorry that I didn't say it more clearly, but I'm installing
> 2.4.30-pre3-bk2 kernel.
> cd /usr/src/linux-2.4.30-pre3-bk2
> make dep
> make bzImage
> make modules
> make modules_install
>
> and then I hit the error about some totally unrelated kernel version in
> /lib/modules? :(
Martin,
Can you find out why is depmod trying to open /lib/modules/2.4.28-pre2/ ?
I've got no clue.
next prev parent reply other threads:[~2005-03-16 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 15:03 Unresolved symbols in /lib/modules/2.4.28-pre2/xfree-drm/via_drv.o Martin MOKREJŠ
2005-03-16 15:16 ` Arjan van de Ven
2005-03-16 15:21 ` Martin MOKREJŠ
2005-03-16 11:53 ` Marcelo Tosatti [this message]
2005-03-17 21:21 ` Martin MOKREJŠ
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=20050316115312.GA12881@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmokrejs@ribosome.natur.cuni.cz \
/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