Topic: depmod problem...

[rk]

I am not a kernel expert, but I beleive there is a bug in the V5 servers concerning depmod.  I was trying to set up a dialin session and I needed to do a depmod as part of it.  When you run depmod, you see:

depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/misc/ipsec.o
depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/scsi/megaide.o

I am running a fresh install of 5.1.2.  I don't recall seeing this error in 4.1.3.

I did a little poking around, and it looks like there is something missing from the precomiled Kernels.  Everything I have seen about these unresolved links says to go back in and run a 'make modules', which we can't do, unless we download the kernel source.

I beleive anyone who needs to run depmod (ie installing a RAID card), will have this error.  Can someone who knows a bit more about this please enlighten me.  Is this a bug, or is there some way to get around this error?  Below is a dump of /sbin/depmod -ae, detailing all of the errors.

TIA,
rk

depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/misc/ipsec.o
depmod:         send_sig
depmod:         sock_wfree
depmod:         proc_register
depmod:         skb_free_datagram
depmod:         sk_run_filter
depmod:         icmp_send
depmod:         __kfree_skb
depmod:         alloc_skb
depmod:         sock_no_socketpair
depmod:         sock_no_getsockopt
depmod:         skb_under_panic
depmod:         kmalloc
depmod:         skb_realloc_headroom
depmod:         unregister_netdevice_notifier
depmod:         ip_statistics
depmod:         sock_no_bind
depmod:         sock_unregister
depmod:         ip_id_count
depmod:         sk_alloc
depmod:         skb_recv_datagram
depmod:         unregister_netdev
depmod:         proc_net_inode_operations
depmod:         panic
depmod:         get_random_bytes
depmod:         dev_get
depmod:         ip_route_output
depmod:         inet_del_protocol
depmod:         inet_addr_type
depmod:         sock_no_setsockopt
depmod:         sock_no_accept
depmod:         proc_unregister
depmod:         sock_no_getname
depmod:         __ip_finish_output
depmod:         inet_add_protocol
depmod:         sock_no_connect
depmod:         proc_dointvec
depmod:         unregister_sysctl_table
depmod:         skb_copy_datagram_iovec
depmod:         register_netdev
depmod:         ip_fragment
depmod:         sk_free
depmod:         datagram_poll
depmod:         kfree
depmod:         sock_no_fcntl  
depmod:         netif_rx
depmod:         sock_no_listen
depmod:         skb_over_panic
depmod:         arp_broken_ops
depmod:         proc_net
depmod:         sock_no_ioctl
depmod:         memcpy_fromiovec
depmod:         sprintf
depmod:         register_netdevice_notifier
depmod:         jiffies
depmod:         printk
depmod:         sock_register
depmod:         sock_no_dup
depmod:         register_sysctl_table
depmod:         sock_init_data
depmod:         sock_rfree
depmod: *** Unresolved symbols in /lib/modules/2.2.19-7.0.8/scsi/megaide.o
depmod:         proc_register
depmod:         request_region
depmod:         __wake_up
depmod:         vsprintf
depmod:         kmalloc
depmod:         release_region
depmod:         _ctype
depmod:         scsi_unregister_module
depmod:         create_proc_entry
depmod:         pci_read_config_byte
depmod:         scsi_register
depmod:         pcibios_present
depmod:         free_irq
depmod:         panic
depmod:         iounmap
depmod:         __ioremap
depmod:         pci_read_config_word
depmod:         interruptible_sleep_on
depmod:         kfree
depmod:         pci_devices
depmod:         remove_proc_entry
depmod:         request_irq
depmod:         scsi_register_module
depmod:         xtime
depmod:         pci_find_device
depmod:         sleep_on_timeout
depmod:         proc_root  
depmod:         sprintf
depmod:         check_region
depmod:         jiffies
depmod:         printk
depmod:         scsi_unregister
depmod:         __const_udelay
depmod:         scsi_free
depmod:         scsi_malloc

[Tom Keiser]

I have also seen this problem, but only when trying to insmod a module that isn't properly compiled for 2.2.19. (And there aren't very many that are).