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.

Warnings when booting Linux on OMAP-L138

Other Parts Discussed in Thread: OMAP-L138, OMAP3530

Hello.

I have downloaded latest versions of Linux DVSDK and Arago FS for OMAP-L138 from http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/omap_l138/1_00/latest/index_FDS.html. When I try to run Linux on board I have the following warning messages:

 

Looking up port of RPC 100003/2 on 10.10.1.125

Looking up port of RPC 100005/1 on 10.10.1.125

VFS: Mounted root (nfs filesystem) on device 0:13.

Freeing init memory: 148K

INIT: version 2.86 booting

Please wait: booting...

Starting udev

udev: starting version 141

udevd[523]: inotify_add_watch(3, (null), 10) failed: Bad address


udevd-event[531]: error changing netif name eth0 to eth1: Device or resource busy

Remounting root file system...

WARNING: Couldn't open directory /lib/modules/2.6.33-rc4: No such file or directory

FATAL: Could not open /lib/modules/2.6.33-rc4/modules.dep.temp for writing: No such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such file or directory

modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such file or directory

root: mount: mounting rootfs on / failed: No such file or directory

root: mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

Setting up IP spoofing protection: rp_filter.

Configuring network interfaces... udhcpc (v1.13.2) started

Sending discover...

Sending select for 10.10.1.78...

Lease of 10.10.1.78 obtained, lease time 14400

done.

Fri Dec 11 13:58:00 UTC 2009

INIT: Entering runlevel: 5

Starting telnet daemon.

modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such file or directory

Starting syslogd/klogd: done

Starting thttpd.

 _____                    _____           _         _

|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_

|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|

|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|

              |___|                    |___|

Arago Project http://arago-project.org da850-omapl138-evm ttyS2

Arago 2009.11 da850-omapl138-evm ttyS2

da850-omapl138-evm login:

Is it OK? Linux finishes booting successfully after this messages. Should I fix it or it's OK? What kind of problems can I be encounterred with because of it?

In our Arago FS we have "/lib/modules/2.6.32-rc6" directory but not "/lib/modules/2.6.33-rc4". Linux booting image is 2.6.33 too:

Uncompressing Linux... done, booting the kernel.                                                                                                                                                           

Linux version 2.6.33-rc4 (x0029463@psplinux051) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Thu Mar 25 15:06:29 IST 2010                                                                

CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177                                                                                                                                              

CPU: VIVT data cache, VIVT instruction cache                                                                                                                                                               

Machine: DaVinci DA850/OMAP-L138/AM18xx EVM                                                                                                                                                                

Memory policy: ECC disabled, Data cache writeback                                                                                                                                                          

DaVinci da850/omap-l138 variant 0x0   


So, Arago has older release then Linux kernel?

Thank you.

  • I'm using OMAP3530 EVM with images from the latest AM35x-OMAP35x-PSP-SDK-03.00.00.05. I ran into similar errors when the processor boots.

    I'm using rootfs_base.jffs2 to boot from flash. Even with the errors., the filesys is still able to come up and complete the booting. However, this is not the case for this other rootfs.jffs2 from the same PSP-SDK folder. The rootfs.jffs2 appears to stay in an endless error loop and just doesn't boot . Is there a fix to all these  problems?

    INIT: version 2.86 booting

    Please wait: booting...

    Starting udev

    udev: starting version 141

    udevd[530]: inotify_add_watch(3, (null), 10) failed: Bad address ß repeated 24 times

     

    Remounting root file system...

    modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory

    WARNING: Couldn't open directory /lib/modules/2.6.32: No such file or directory

    FATAL: Could not open /lib/modules/2.6.32/modules.dep.temp for writing: No such file or directory

    /etc/init.d/rc: /etc/default/mountall: line 1: 091120522009: not found

    modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory

     

    modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory

     

    root: mount: mounting rootfs on / failed: No such file or directory

    root: mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

    modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory

     

    modprobe: FATAL: Could not load /lib/modules/2.6.32/modules.dep: No such file or directory

     

    Setting up IP spoofing protection: rp_filter.

    Configuring network interfaces... net eth0: SMSC911x/921x identified at 0xc8860000, IRQ: 336

    udhcpc (v1.13.2) started

    Sending discover...

    Sending discover...

    Sending discover...

    No lease, failing

     

  • Hello,

    Artem Vorobyov said:
    So, Arago has older release then Linux kernel?

    Yes, the filesystem may have been created by installing modules from an older kernel release.

    To get rid of these, you need to install new modules into the target filesystem and then run depmod on boot-up.

    Thanks,

    Sekhar

     

  • Thank you Sekhar Nori.

    Now it works fine.