Unresponsive beagleboard after booting ansgtrom

Hi!

I have got the latest versions of uboot, uImage and x-load.bin.ift, all compiled and built myself (I downloaded the git repositories of the source).

However, on booting I get the following error repeatedly -

[....]
WARNING: Couldn't open directory /lib/modules/2.6.31-omap1-05952-g945044d-dirty: No such file or directory
FATAL: Could not open /lib/modules/2.6.31-omap1-05952-g945044d-dirty/modules.dep.temp for writing: No such file or directory
WARNING: Couldn't open directory /lib/modules/2.6.31-omap1-05952-g945044d-dirty: No such file or directory
FATAL: Could not open /lib/modules/2.6.31-omap1-05952-g945044d-dirty/modules.dep.temp for writing: No such file or directory
[...]

Is there some kernel version mismatch? If yes, how can this be corrected?
The Angstrom build I am using has been downloaded from http://www.angstrom-distribution.org/narcissus/ around 2 or 3 weeks ago.

Also, on booting Angstrom (or Ubuntu), the following don't work -
1) any input given through the serial cable is not detected - however, it does work in the initial prompt, when one sets the bootcmds and the bootargs
2) usb otg is not detected
3) no dvi output

Are the above problems a result of some kernel mismatch?
Will downloading a newer image solve the problem?

Regards,
Kedar

Hello,

[....]
WARNING: Couldn't open directory /lib/modules/2.6.31-omap1-05952-g945044d-dirty: No such file or directory
FATAL: Could not open /lib/modules/2.6.31-omap1-05952-g945044d-dirty/modules.dep.temp for writing: No such file or directory
WARNING: Couldn't open directory /lib/modules/2.6.31-omap1-05952-g945044d-dirty: No such file or directory
FATAL: Could not open /lib/modules/2.6.31-omap1-05952-g945044d-dirty/modules.dep.temp for writing: No such file or directory
[...]

If you build your own uImage, you should also build the modules, and
dump them to /lib/modules/2.6.31-omap1-05952-g945044d-dirty

make -j2 ARCH=arm CROSS_COMPILE=${CC} modules
make ARCH=arm CROSS_COMPILE=${CC} modules_install
INSTALL_MOD_PATH=${DIR}/deploy/

Regards,

Hi Robert,

Will adding the modules solve problems such as -

  1. any input given through the serial cable is not detected - however, it does work in the initial prompt, when one sets the bootcmds and the bootargs
  2. usb otg is not detected
  3. no dvi output

Thanks
Kedar