[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

vfat module fails to load



I'm getting the following errors when I try to modprobe the vfat module:

# modprobe vfat

 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol block_sync_page_Ref99edfc
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol igrab_R62e53394
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol getblk_R54f282ac
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol block_write_full_page_Rd81ad31a
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_file_write_R15a7e0e2
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_read_dir_Rc97c344c
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol block_read_full_page_R5a3f09b4
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol mark_buffer_dirty_R6d8261a1
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol dget_locked_R305f0a53
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol unlock_new_inode_R453b020f
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol iget4_locked_R6c864bcd
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol __brelse_Rfb3506f3
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol ll_rw_block_Rc01115fc
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol inode_setattr_R270b186e
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol inode_change_ok_R2c0613ec
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_file_mmap_R990ff8ef
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_commit_write_Rdf2e1179
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol bread_Redab0393
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol insert_inode_hash_R29d31d65
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol make_bad_inode_Rcaea6ff7
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol new_inode_R825ac588
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol file_fsync_R246cf621
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_block_bmap_R31395d6c
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol clear_inode_Ra3797721
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol iput_R3b53c128
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_file_llseek_R9f152d25
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol cont_prepare_write_R8eed90a4
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol __mark_inode_dirty_R8b827363
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol generic_file_read_Rb343c590
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol is_bad_inode_Rae0b509a
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol iunique_R7c480d17
 /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o: unresolved symbol d_alloc_root_R00f97691
 insmod /lib/modules/2.4.27-1-386/kernel/fs/fat/fat.o failed
 insmod vfat failed

I'm running debian testing and the kernel indicated in the messages above. Does
anyone have any idea why this would occur?

-- 
---------------------------------------------------------- 
                            | /"\                         
 john harrold               | \ / ASCII ribbon campaign   
 jmh at member.fsf.org      |  X  against HTML mail       
 the most useful idiot      | / \                         
----------------------------------------------------------
 What difference does it make to the dead, the orphans, 
 and the homeless, whether the mad destruction is brought 
 under the name of totalitarianism or the holy name of 
 liberty and democracy?
 --Gandhi
----------------------------------------------------------
  gpg --keyserver keys.indymedia.org --recv-key F65A739E
----------------------------------------------------------

Attachment: signature.asc
Description: Digital signature


Reply to: