From: Miles Lane <miles@megapathdsl.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: 2.4.11-pre1 -- depmod: Unexpected value (20) in drivers/ieee1394/sbp2.o for ieee1394_device_size
Date: 30 Sep 2001 23:53:22 -0700 [thread overview]
Message-ID: <1001919223.1247.13.camel@stomata.megapathdsl.net> (raw)
Here's the error:
if [ -r System.map ]; then /sbin/depmod -ae -F System.map 2.4.11-pre1; fi
depmod: Unexpected value (20) in '/lib/modules/2.4.11-pre1/kernel/drivers/ieee1394/sbp2.o' for ieee1394_device_size
It is likely that the kernel structure has changed, if so then
you probably need a new version of modutils to handle this kernel.
Check linux/Documentation/Changes.
make: *** [_modinst_post] Error 255
ver_linux reports:
Linux stomata.megapathdsl.net 2.4.11-pre1 #1 Sun Sep 30 22:03:05 PDT 2001 i686 unknown
Gnu C 2.96
Gnu make 3.79.1
binutils 2.10.91.0.2
util-linux 2.10s
mount 2.11b
modutils 2.4.9
e2fsprogs 1.25
reiserfsprogs 3.x.0f
pcmcia-cs 3.1.22
PPP 2.4.0
isdn4k-utils 3.1pre1
Linux C Library 2.2.2
Dynamic linker (ldd) 2.2.2
Procps 2.0.7
Net-tools 1.57
Console-tools 0.3.3
Sh-utils 2.0
Modules Loaded emu10k1 sound ac97_codec soundcore serial_cs af_packet 3c59x keybdev hid input usb-ohci nls_iso8859-1 nls_cp850
My .config file includes:
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
CONFIG_IEEE1394=m
CONFIG_IEEE1394_PCILYNX=m
CONFIG_IEEE1394_PCILYNX_LOCALRAM=y
CONFIG_IEEE1394_PCILYNX_PORTS=y
CONFIG_IEEE1394_OHCI1394=m
CONFIG_IEEE1394_VIDEO1394=m
CONFIG_IEEE1394_SBP2=m
CONFIG_IEEE1394_RAWIO=m
CONFIG_IEEE1394_VERBOSEDEBUG=y
next reply other threads:[~2001-10-01 7:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 6:53 Miles Lane [this message]
2001-10-01 7:02 ` 2.4.11-pre1 -- Unresolved symbols in media/radio/miropcm20.o -- aci_port, aci_version and aci_rw_cmd Miles Lane
2001-10-01 7:13 ` 2.4.11-pre1 -- depmod: Unexpected value (20) in drivers/ieee1394/sbp2.o for ieee1394_device_size Keith Owens
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=1001919223.1247.13.camel@stomata.megapathdsl.net \
--to=miles@megapathdsl.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
all inboxes | Powered by JetHome®