• Locked Locked
  • Replies 1 reply
  • Subscribers 98 subscribers
  • Views 811 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Video capture device

SJackson
Intellectual 375 points

I've just started using the kernel source tree that comes with the DVSDK 1.30.  I've build the Video 4 Linux 2 and applicable DaVinci drivers into my kernel (not as modules) and created a video device with major/minor number 81/0 in the /dev folder of my NFS filesystem using 'mknod video0 c 81 0'.

 When I run my application and try to open /dev/video0 I get the following message: 

modprobe: FATAL: Could not load /lib/modules/2.6.10_mvl401-davinci_evm-PSP_01_30
_00_082/modules.dep: No such file or directory

I'm not sure where I find this file within the SDK or why I need it since I'm not using modules. I tried running "make modules" and "make modules_install" but didn't see any modules.dep file in the install directory.

 Thanks in advance for any insight into this problem.

  • TI__Mastermind 41665 points

    Someone else had the same error on an internal forum, the response below is thanks to one of our software engineers:

    "During Linux boot-up; /sbin/init executes all the scripts from run level S,1,2 and 3 and those scripts resides in /etc/rc.d/rcS.d,rc1.d rc2.d and rc3.d directory respectively. One of script (S29module-init-tool) runs a modprobe/depmod command to install all the modules from the /lib/module/<kernel_version>/build directory. depmod command creates module.dep file and and modprobe command refer "module.dep" file for resolving the module dependency (e.g module x should be loaded before module y etc). 

    Since we don't have any modules installed on target file system and this results in Warning during bootup.  You can follow the below steps to disable the modprobe during system bootup

    # initdconfig --list | grep module-init-tools
    module-init-tools       S:on
    # initdconfig --level S module-init-tools off
    # initdconfig --list | grep module-init-tools
    module-init-tools       S:off

    First command will use the initdconfig executable to check the module run level and status. Second command will disable the script. Third command checks if the script is disabled for the next boot.

    If you want to enable the module then follow the below steps

    1) check your running kernel name

    #uname -a

    Linux xxx.xxx.xxx.xxx 2.6.10_mvl401-davinci_evm-PSP_xx_xx_xx_xxx #2 Thu May 29 09:53:22 CDT 20
    08 armv5tejl GNU/Linux

    # mkdir -p /lib/modules/Linux xxx.xxx.xxx.xxx1 2.6.10_mvl401-davinci_evm-PSP_xx_xx_xx_xxx

    # depmod -a

    This will create the module.dep file. Now whenever you add any module in /lib/modules/Linux 156.117.95.11 2.6.10_mvl401-davinci_evm-PSP_01_30_00_070 directory make sure you run the "depmod -a" command regenerate module.dep file."