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.

Broken Linux MMC using EZSDKv5.03...

We've finally gotten our own H/W up and running with our build of U-Boot, Linux Kernel and file system.  Mods have been done for our board-specific initialization, but most of what has been changed has been pretty minor.  We started testing with the EZSDK v5.02 and most everything worked fine out of the box (except for the few mentioned board-specific mods).  We were able to get U-Boot and the Kernel built and up without too much of a problem, as well as support for most of the other 8148-specific H/W devices (using the TI supplied Linux code).

Everything was ok until we started using the newer EZSDK v5.03.  Our U-boot changes ported and ran fairly easily from v5.02 to v5.03, but the Linux Kernel is giving us a few problems we need to solve.  The biggest v5.03 problem at the moment is that the MMC doesn't work under Linux at all (on our H/W).  It works from within U-boot just fine and we can have U-boot load the kernel from SD. But once the kernel loads the MMC support appears missing (even though it's being compiled in).  No kernel init messages about MMC are present in the log.  And because Linux support appears missing we can't use the MMC for the root filesystem, instead having to resort to an NFS mounted root filesystem...and we've got some issues with the Ethernet we're still trying to iron out, so Ethernet usage is sporadic...making using an NFS root mount problematic at the moment.  If we could only get the MMC working...;)...

To be sure, I tested the MMC and it appears to work just fine using the prebuilt images in the EZSDK v5.03 on a PG2.1 TI8148EVM.

Using EZSDK v5.03 we ran into a problem on our H/W where we had to disable kernel support for PCIe due to the kernel getting hung on booting in an endless loop during PCIe initialization, but after rebuilding the kernel without this support it booted fine, but with no MMC support in Linux.  The prior EZSDK v5.02 apparently didn't have PCIe support, but the MMC worked just fine on our H/W with this version.

So...anyone have any suggestions?  Does the PCIe and MMC share some common CPU blocks? Clocking, etc.,...?

  • Joe,

    The MMC card detect pin is not connected by default. So the card is not getting detected as it used to in TI8148EVM. You can use the MMC polling capability instead of card detect pin with the following patch. This will make the MMC work as fine.

    diff --git a/arch/arm/mach-omap2/board-dm385evm.c b/arch/arm/mach-omap2/board-dm385evm.c
    index 4511c53..85f3896 100644
    --- a/arch/arm/mach-omap2/board-dm385evm.c
    +++ b/arch/arm/mach-omap2/board-dm385evm.c
    @@ -64,7 +64,7 @@ static struct omap_board_mux board_mux[] __initdata = {
     static struct omap2_hsmmc_info mmc[] = {
            {
                    .mmc            = 1,
    -               .caps           = MMC_CAP_4_BIT_DATA,
    +               .caps           = MMC_CAP_4_BIT_DATA | MMC_CAP_NEEDS_POLL,
                    .gpio_cd        = -EINVAL, /* Dedicated pins for CD and WP */
                    .gpio_wp        = -EINVAL,
                    .ocr_mask       = MMC_VDD_33_34,
    diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
    index c348898..f2eaea2 100644
    --- a/drivers/mmc/host/omap_hsmmc.c
    +++ b/drivers/mmc/host/omap_hsmmc.c
    @@ -584,7 +584,10 @@ static int omap_hsmmc_gpio_init(struct omap_mmc_platform_data *pdata)
                    pdata->resume = omap_hsmmc_resume_cdirq;
                    pdata->slots[0].get_cover_state = omap_hsmmc_get_cover_state;
                    pdata->slots[0].get_ro = omap_hsmmc_get_wp;
    -               pdata->slots[0].card_detect = omap_hsmmc_card_detect;
    +               if (pdata->slots[0].caps & MMC_CAP_NEEDS_POLL)
    +                       pdata->slots[0].card_detect = NULL;
    +               else
    +                       pdata->slots[0].card_detect = omap_hsmmc_card_detect;
            }

            return 0;

    Regards,

    Parth

  • I added the code from the /arch/arm/mach-omap2/board-dm385evm.c file to our board specific file and then patched the /drivers/mmc/host/omap_hsmmc.c file and I can now see the MMC device and SD card partitions during the linux boot screen. 

    But when I try to mount a volume a bunch of I/O errors seems to occur.  I've got my kernel compiled with MMC debug info so I see alot of extraneous debug messages which seem to indicate that the mount command is issuing I/O requests which are failing, resulting in a subsequent mount failure.

    Any ideas where to go from here?

  • Joe,

    Can you check if this patch is included in your package:

    Author: Chase Maupin <Chase.Maupin@ti.com>
    Date:   Mon Nov 21 08:28:10 2011 -0600

        omap_hsmmc: make default dto value 14

        It seems that making the dto value makes all the various SD
        cards work.  If not we will sometimes see -110 errors during
        boot with certain SD cards.
        Based on input from Steve Kipisz

        Signed-off-by: Chase Maupin <Chase.Maupin@ti.com>

    diff --git a/drivers/mmc/host/omap_hsmmc.c b/drivers/mmc/host/omap_hsmmc.c
    index ba1be2e..c348898 100644
    --- a/drivers/mmc/host/omap_hsmmc.c
    +++ b/drivers/mmc/host/omap_hsmmc.c
    @@ -1513,6 +1513,9 @@ static void set_data_timeout(struct omap_hsmmc_host *host,
                    if (dto > 14)
                            dto = 14;
            }
    +       /* Use 14 by default because this seems
    +       to work will with all cards */
    +       dto = 14;

            reg &= ~DTO_MASK;
            reg |= dto << DTO_SHIFT;

    Regards,

    Parth

  • No...we don't have any such patch...similar to the last patch, we didn't have that either.  I've already raised this issue thru channels...that is to say, the pre-built binaries that have been delivered in the EZSDK v5.03 cannot be built from the codebase in the EZSDK.  Apparently, the prebuilt binaries have been built using some number of patches which have not been included in the EZSDK.  We see this behavior for the Linux Kernel as well as U-Boot.

    Back to our immediate issue...I added the patch code to the omap_hsmmc.c file and rebuilt the kernel...I can now mount the filesystem on the SD card.  But if I un-mount it, eject the SD and re-insert the SD I cannot mount it again, the mount fails.  It looks to me like the first patch you gave us (the POLL patch) polls at about 1 second intervals.  But it only does this when the kernel boots.

    If I keep the SD inserted while the kernel boots I can see the a bunch of debug output spewed to the console approx. every second.  If I check /dev/mmc* I can see the mmc device and the partitions on the SD as well.  I can then mount it and list the root of this filesystem.

    But if I then unmount the filesystem, eject the SD, re-insert the SD and then try to mount it fails.  I'm guessing because the polling has stopped the card insertion event processing hasn't occured, thus the failure.

    Also, if I boot U-Boot from the SD, load the kernel via TFTP (NFS mounted root configuration), and eject the SD before the kernel starts running, I still see the polling going on.  If I then insert the SD I can see in the console log what appears to be the output from processing the card insertion event logic.  But my whole system is hosed at this point.  I cannot view the NFS mounted root volume.  I cannot even list the /dev directory.  In fact, the simplest operation results in the command prompt disappearing never to return.

    Clearly, more work is needed in this area, no?

  • Joe,

    The MMC/SD polling method seems to be working fine for me.

    1) When unmounted and ejected, in the kernel, card is detected back when reinserted.

    2)When removed before kernel bootup, the boot log doesn't seem to hang waiting for MMC/SD. The MMC/SD is then again detected in the kernel if inserted.

    Please find the logs attached.

    MMC/SD UNMOUNTING AND CARD DETECT:
    
    
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|
    
    Arago Project http://arago-project.org ti8168-evm ttyO0
    
    Arago 2009.11 ti8168-evm ttyO0
    
    ti8168-evm login: root
    login[1064]: root login  on `ttyO0'
    
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    root@ti8168-evm:~# mmc0: card b368 removed
    
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    root@ti8168-evm:~# mmc0: new high speed SDHC card at address b368
    mmcblk0: mmc0:b368 USD   3.75 GiB
     mmcblk0: p1
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    root@ti8168-evm:~# mount /dev/mmcblk0p1 /mnt/
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    root@ti8168-evm:~# umount /mnt/
    root@ti8168-evm:~# mmc0: card b368 removed
    
    root@ti8168-evm:~#
    root@ti8168-evm:~# mmc0: new high speed SDHC card at address b368
    mmcblk0: mmc0:b368 USD   3.75 GiB
     mmcblk0: p1
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    root@ti8168-evm:~#
    
    
    
    
    
    
    
    
    WHEN MMC/SD IS EJECTED ON BOOT-UP:
    
    
    
    ## Booting kernel from Legacy Image at 81000000 ...
       Image Name:   Linux-2.6.37+
       Image Type:   ARM Linux Kernel Image (uncompressed)
       Data Size:    2692264 Bytes = 2.6 MiB
       Load Address: 80008000
       Entry Point:  80008000
       Verifying Checksum ... OK
       Loading Kernel Image ... OK
    OK
    
    Starting kernel ...
    
    Uncompressing Linux... done, booting the kernel.
    Linux version 2.6.37+ (a0131646@psplinux063) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #4 Wed Jan 25 20:45:45 IST 2012
    CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
    CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
    Machine: dm385evm
    bootconsole [earlycon0] enabled
    reserved size = 52428800 at 0x0
    FB: Reserving 52428800 bytes SDRAM for VRAM
    Memory policy: ECC disabled, Data cache writeback
    OMAP chip is DM385 1.0
    SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
    Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 19712
    Kernel command line: console=ttyO0,115200n8 root=/dev/nfs nfsroot=172.24.191.70:/srv/nfs/ti81xx,nolock rw mem=128M ip=dhcp earlyprintk
    PID hash table entries: 512 (order: -1, 2048 bytes)
    Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
    Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
    Memory: 78MB = 78MB total
    Memory: 72944k/72944k available, 58128k reserved, 0K highmem
    Virtual kernel memory layout:
        vector  : 0xffff0000 - 0xffff1000   (   4 kB)
        fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
        DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
        vmalloc : 0xc8800000 - 0xf8000000   ( 760 MB)
        lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
        pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
        modules : 0xbf000000 - 0xbfe00000   (  14 MB)
          .init : 0xc0008000 - 0xc003c000   ( 208 kB)
          .text : 0xc003c000 - 0xc0519000   (4980 kB)
          .data : 0xc051a000 - 0xc0565000   ( 300 kB)
    SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
    NR_IRQS:407
    IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
    Total of 128 interrupts on 1 active controller
    GPMC revision 6.0
    Trying to install interrupt handler for IRQ400
    Trying to install interrupt handler for IRQ401
    Trying to install interrupt handler for IRQ402
    Trying to install interrupt handler for IRQ403
    Trying to install interrupt handler for IRQ404
    Trying to install interrupt handler for IRQ405
    Trying to install interrupt handler for IRQ406
    Trying to install type control for IRQ407
    Trying to set irq flags for IRQ407
    OMAP clockevent source: GPTIMER1 at 20000000 Hz
    Console: colour dummy device 80x30
    Calibrating delay loop... 599.65 BogoMIPS (lpj=2998272)
    pid_max: default: 32768 minimum: 301
    Security Framework initialized
    Mount-cache hash table entries: 512
    CPU: Testing write buffer coherency: ok
    devtmpfs: initialized
    omap_voltage_early_init: voltage driver support not added
    regulator: core version 0.5
    regulator: dummy:
    NET: Registered protocol family 16
    omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
    omap_voltage_add_dev: VDD specified does not exist!
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    OMAP GPIO hardware version 0.1
    omap_mux_init: Add partition: #1: core, flags: 4
    NOR: Can't request GPMC CS
    Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
    registered ti81xx_vpss device
    registered ti81xx_vidout device
    registered ti81xx on-chip HDMI device
    registered ti81xx_fb device
    registered ti81xx_vin device
    ti81xx_pcie: Invoking PCI BIOS...
    ti81xx_pcie: Setting up Host Controller...
    ti81xx_pcie: Register base mapped @0xc8820000
    ti81xx_pcie: Starting PCI scan...
    PCI: bus0: Fast back to back transfers enabled
    bio: create slab <bio-0> at 0
    vgaarb: loaded
    SCSI subsystem initialized
    omap2_mcspi: probe of omap2_mcspi.3 failed with error -2
    omap2_mcspi: probe of omap2_mcspi.4 failed with error -2
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    usbcore: registered new device driver usb
    registerd cppi-dma Intr @ IRQ 17
    Cppi41 Init Done
    omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
    regulator: VRTC: 1800 mV
    regulator: VIO: 1500 mV
    regulator: VDD1: 600 <--> 1500 mV at 1200 mV
    regulator: VDD2: 600 <--> 1500 mV at 1200 mV
    regulator: VDDCTRL: 600 <--> 1400 mV at 1200 mV
    regulator: LDO1: 1100 <--> 3300 mV at 1800 mV
    regulator: LDO2: 1100 <--> 3300 mV at 1800 mV
    regulator: LDO3: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO4: 1100 <--> 3300 mV at 1800 mV
    regulator: LDO5: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO6: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO7: 1100 <--> 3300 mV at 3300 mV
    regulator: LDO8: 1100 <--> 3300 mV at 1800 mV
    tps65910 1-002d: No interrupt support, no core IRQ
    Advanced Linux Sound Architecture Driver Version 1.0.23.
    Switching to clocksource gp timer
    musb-hdrc: version 6.0, host, debug=0
    musb-hdrc musb-hdrc.0: dma type: dma-cppi41
    musb-hdrc musb-hdrc.0: MUSB HDRC host driver
    musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
    usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb1: Product: MUSB HDRC host driver
    usb usb1: Manufacturer: Linux 2.6.37+ musb-hcd
    usb usb1: SerialNumber: musb-hdrc.0
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 1 port detected
    musb-hdrc musb-hdrc.0: USB Host mode controller at c881e000 using DMA, IRQ 18
    musb-hdrc musb-hdrc.1: dma type: dma-cppi41
    musb-hdrc musb-hdrc.1: MUSB HDRC host driver
    musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
    usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
    usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
    usb usb2: Product: MUSB HDRC host driver
    usb usb2: Manufacturer: Linux 2.6.37+ musb-hcd
    usb usb2: SerialNumber: musb-hdrc.1
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 1 port detected
    musb-hdrc musb-hdrc.1: USB Host mode controller at c8826800 using DMA, IRQ 19
    NET: Registered protocol family 2
    IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
    TCP established hash table entries: 4096 (order: 3, 32768 bytes)
    TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
    TCP: Hash tables configured (established 4096 bind 4096)
    TCP reno registered
    UDP hash table entries: 256 (order: 0, 4096 bytes)
    UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
    NET: Registered protocol family 1
    RPC: Registered udp transport module.
    RPC: Registered tcp transport module.
    RPC: Registered tcp NFSv4.1 backchannel transport module.
    NetWinder Floating Point Emulator V0.97 (double precision)
    PMU: registered new PMU device of type 0
    omap-iommu omap-iommu.0: ducati registered
    omap-iommu omap-iommu.1: sys registered
    JFFS2 version 2.2. (NAND) � 2001-2006 Red Hat, Inc.
    msgmni has been set to 142
    io scheduler noop registered
    io scheduler deadline registered
    io scheduler cfq registered (default)
    Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
    omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
    console [ttyO0] enabled, bootconsole disabled
    console [ttyO0] enabled, bootconsole disabled
    omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
    omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
    brd: module loaded
    loop: module loaded
    ahci ahci.0: forcing PORTS_IMPL to 0x1
    ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
    scsi0 : ahci_platform
    ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
    ahci ahci.1: forcing PORTS_IMPL to 0x1
    ahci ahci.1: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
    ahci ahci.1: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
    scsi1 : ahci_platform
    ata2: SATA max UDMA/133 mmio [mem 0x4a0ae000-0x4a0befff] port 0x100 irq 59
    m25p80 spi1.0: w25x32 (4096 Kbytes)
    Creating 5 MTD partitions on "spi_flash":
    0x000000000000-0x000000020000 : "U-Boot-min"
    0x000000020000-0x000000060000 : "U-Boot"
    0x000000060000-0x000000062000 : "U-Boot Env"
    0x000000062000-0x0000002e2000 : "Kernel"
    0x0000002e2000-0x000000400000 : "File System"
    omap2-nand driver initializing
    ONFI flash detected
    ONFI param page 0 valid
    NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)
    Creating 6 MTD partitions on "omap2-nand.0":
    0x000000000000-0x000000020000 : "U-Boot-min"
    0x000000020000-0x000000260000 : "U-Boot"
    0x000000260000-0x000000280000 : "U-Boot Env"
    0x000000280000-0x0000006c0000 : "Kernel"
    0x0000006c0000-0x00000cee0000 : "File System"
    0x00000cee0000-0x000010000000 : "Reserved"
    davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
    davinci_mdio davinci_mdio.0: detected phy mask fffffffc
    davinci_mdio.0: probed
    davinci_mdio davinci_mdio.0: phy[0]: device 0:00, driver unknown
    davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver unknown
    usbcore: registered new interface driver cdc_ether
    usbcore: registered new interface driver dm9601
    usbcore: registered new interface driver cdc_acm
    cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
    Initializing USB Mass Storage driver...
    usbcore: registered new interface driver usb-storage
    USB Mass Storage support registered.
    mice: PS/2 mouse device common for all mice
    qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
    qt602240_ts: probe of 1-004a failed with error -5
    omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
    i2c /dev entries driver
    Linux video capture interface: v2.00
    usbcore: registered new interface driver uvcvideo
    USB Video Class driver (v1.0.0)
    OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
    ata1: SATA link down (SStatus 0 SControl 300)
    ata2: SATA link down (SStatus 0 SControl 300)
    usbcore: registered new interface driver usbhid
    usbhid: USB HID core driver
    usbcore: registered new interface driver snd-usb-audio
    asoc: tlv320aic3x-hifi <-> davinci-mcasp.1 mapping ok
    ALSA device list:
      #0: TI81XX EVM
    TCP cubic registered
    NET: Registered protocol family 17
    Registering the dns_resolver key type
    VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
    omap_voltage_late_init: Voltage driver support not added
    Power Management for TI81XX.
    Detected MACID=8:0:28:32:70:ea
    omap_rtc omap_rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
    
    CPSW phy found : id is : 0x4dd074
    
    CPSW phy found : id is : 0x4dd074
    Sending DHCP requests .
    PHY: 0:01 - Link is Up - 0/Half
    PHY: 0:01 - Link is Down
    PHY: 0:01 - Link is Up - 100/Full
    .., OK
    IP-Config: Got DHCP answer from 0.0.0.0, my address is 172.24.191.39
    IP-Config: Complete:
         device=eth0, addr=172.24.191.39, mask=255.255.252.0, gw=172.24.188.1,
         host=172.24.191.39, domain=india.ti.com, nis-domain=(none),
         bootserver=0.0.0.0, rootserver=172.24.191.70, rootpath=
    VFS: Mounted root (nfs filesystem) on device 0:14.
    devtmpfs: mounted
    Freeing init memory: 208K
    INIT: version 2.86 booting
    Please wait: booting...
    Starting udev
    udevd (74): /proc/74/oom_adj is deprecated, please use /proc/74/oom_score_adj instead.
    udev: starting version 141
    udevd-event[87]: error changing netif name eth0 to eth113: Device or resource busy
    
    Root filesystem already rw, not remounting
    WARNING: Couldn't open directory /lib/modules/2.6.37+: No such file or directory
    FATAL: Could not open /lib/modules/2.6.37+/modules.dep.temp for writing: No such file or directory
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    root: mount: mounting rootfs on / failed: No such file or directory
    Configuring network interfaces... udhcpc (v1.13.2) started
    Sending discover...
    Sending select for 172.24.191.39...
    Lease of 172.24.191.39 obtained, lease time 3600
    adding dns 172.24.170.29
    adding dns 172.24.170.30
    done.
    net.ipv4.conf.default.rp_filter = 1
    net.ipv4.conf.all.rp_filter = 1
    Sat Jan 15 16:23:00 UTC 2000
    INIT: Entering runlevel: 5
    Starting telnet daemon.
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    /etc/rc5.d/S20syslog: /etc/syslog.conf: line 1: *.=info: not found
    Starting thttpdmodprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    .
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    
     _____                    _____           _         _
    |  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
    |     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
    |__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
                  |___|                    |___|
    
    Arago Project http://arago-project.org ti8168-evm ttyO0
    
    Arago 2009.11 ti8168-evm ttyO0
    
    ti8168-evm login: root
    login[973]: root login  on `ttyO0'
    
    root@ti8168-evm:~#
    root@ti8168-evm:~# mmc0: new high speed SDHC card at address b368
    mmcblk0: mmc0:b368 USD   3.75 GiB
     mmcblk0: p1
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    modprobe: FATAL: Could not load /lib/modules/2.6.37+/modules.dep: No such file or directory
    
    
    root@ti8168-evm:~#
    root@ti8168-evm:~#

    Regards,

    Parth