Bug 902 - Unresolved Symbols in 1394.ko and deo1394.ko
Summary: Unresolved Symbols in 1394.ko and deo1394.ko
Status: REJECTED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: IEEE1394 (show other bugs)
Hardware: i386 Linux
: P2 blocking
Assignee: Ben Collins
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-11 08:56 UTC by Brandon Jackson
Modified: 2003-07-11 11:21 UTC (History)
0 users

See Also:
Kernel Version: 2.5.75
Subsystem:
Regression: ---
Bisected commit-id:


Attachments

Description Brandon Jackson 2003-07-11 08:56:03 UTC
Distribution: Gentoo Linux 1.4_rc4 
Hardware Environment: Dell Inspiron 8100 
Software Environment: gcc 3.2.2 vanilla kernel 2.4.21 
Problem Description: 
if [ -r System.map ]; then /sbin/depmod -ae -F System.map  2.5.75; fi 
depmod: *** Unresolved symbols in /lib/modules/2.5.75/kernel/drivers/ieee1394/dv 
1394.ko 
depmod:         ohci1394_init_iso_tasklet 
depmod:         ohci1394_unregister_iso_tasklet 
depmod:         ohci1394_register_iso_tasklet 
depmod: *** Unresolved symbols in /lib/modules/2.5.75/kernel/drivers/ieee1394/vi 
deo1394.ko 
depmod:         ohci1394_init_iso_tasklet 
depmod:         ohci1394_unregister_iso_tasklet 
depmod:         ohci1394_register_iso_tasklet 
depmod:         ohci1394_stop_context 
 
 
Steps to reproduce: 
 
In Xconfig set section: 
 
# 
# Texas Instruments PCILynx requires I2C bit-banging 
# 
CONFIG_IEEE1394_OHCI1394=m 
 
# 
# Protocol Drivers 
# 
CONFIG_IEEE1394_VIDEO1394=m 
CONFIG_IEEE1394_SBP2=m 
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set 
CONFIG_IEEE1394_ETH1394=m 
CONFIG_IEEE1394_DV1394=m 
CONFIG_IEEE1394_RAWIO=m 
CONFIG_IEEE1394_CMP=m 
# CONFIG_IEEE1394_AMDTP is not set 
 
do: 
make    <-(works fine) 
make modules_install  (fails with above message)
Comment 1 Ben Collins 2003-07-11 09:19:11 UTC
All of those symbols are supplied by ohci1394.ko. Nothing changed there. Are you
sure that ohci1394.ko exists and is installed in the modules directory?
Comment 2 Brandon Jackson 2003-07-11 09:48:15 UTC
I forgot to make modules... therefore it wasn't there.  You are correct.  My next bug is a 
show stopper though, because the build process actually fails.  See bug 903 (regarding 
sbp2) 
 

Note You need to log in before you can comment on or make changes to this bug.