Doubt in the output when modules dependency builded using busybox script depmod.pl

Hi,
While i executed the depmod.pl script which was extracted from busybox for building dependency for modules, for a cross compiled kernel image like this in terminal:

ayyappan@ayyappan-desktop:/media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images$ ./depmod.pl -k ./media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images/vmlinux -b /media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images/modules_2.6.32.2/lib/modules > /media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images/modules_2.6.32.2/lib/modules/2.6.32.2-FriendlyARM/modules.dep

(the command pasted above gets new line automatically here due to edit space constraints in this window but it is consecutive in the terminal and it is correct when i gave in the terminal).I get output warnings in the console starting like this:

Guessed module directory as /media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images/modules_2.6.32.2/lib/modules/2.6.32.2-FriendlyARM

nm: './media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images/vmlinux': No such file

unresolved symbol printk in file /lib/modules/2.6.32.2-FriendlyARM/kernel/drivers/net/wireless/ath/ar9170/ar9170usb.ko

unresolved symbol __aeabi_idiv in file /lib/modules/2.6.32.2-FriendlyARM/kernel/drivers/net/wireless/ath/ar9170/ar9170usb.ko

but the command executed and exited.

Is this the indication that while in runtime these unresolved symbols cause termination while the modules was attempted to load if these unresolved symbols was needed and causes loading failure of the modules? If it so how to correct and what would be the problem? I have attached the complete console output pasted in the word document. If needed i can attach the modules.dep later that was created as a result of this command.

What you pasted is incorrect.

./depmod.pl -k ./media/...

The extra '.' on the front of the path makes the path relative to your current directory instead of an absolute path from the root directory. That's one reason it did not find your vmlinux file.

Hi smallpond I tried like you said and no warning messages came in the console output except this:

Guessed module directory as /media/540a136f-51dc-4d56-966b-332e7b45ea1c_/B/Practice_project/images/modules_2.6.32.2/lib/modules/2.6.32.2-FriendlyARM

but the contents of modules.dep is not differing from the previous one, but the modification time was updated to the command executed time. How is this possible when vmlinux file not recognized with it's correct path is producing the same result as when vmlinux file recognized? Is there anything missing like that it doesnot considering vmlinux file? If you need i can attach the modules.dep file.