• State
  • Locked Locked
  • Replies 6 replies
  • Subscribers 99 subscribers
  • Views 736 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.

Stuck at freeing init memory while booting

Srinivas C
Prodigy 70 points

if are encountering this error you should try this

after mounting your root filesystem

sudo chmod -R 777 /media/ROOTFS/dev/*

 

it worked for me

 

regards

srinivas

  • 0
    Intellectual 625 points

    Hi there!

    I'm trying to set up a custom FS. But i also get stuck at:

    "Freeing init memory: 140 K"

    I decided to go slower. The FS provided by the SDK is properly working so i decided to uncompress it with the command:

    tar -xzf omapl138-lcdk-fs.tar.gz

    Then I compress everything without any modification with the command:

    tar czf omapl138-lcdk-fs-test.tar.gz

    And surprisingly doesn't work any more. It gets stuck again at the message "Freeing init memory: 140 K".

    Am I missing something? I already tried your solution and it didn't work for me. Any suggestions?

  • 0 in reply to Victor Mayoral
    Guru 31670 points

    Victor,

    There might a directory created in between the compress and uncompress operations. If this doesn't work, please share more logs and steps followed.

  • 0 in reply to Renjith Thomas
    Intellectual 625 points

    Renjith,

    Thanks for your reply.

    Just to make it clear, i'm trying to build a custom FS locally that hopefully i'll be able to load through NFS. So I decided to start with the one provided by the SDK.
    I re-did the process in the following way:

    • logged in as root
    • created a folder omap-fs 
    • uncompressed the provided FS with: tar xzf omapl138-lcdk-fs.tar.gz -C omap-fs/

      I get errors during the process such as:

      tar: ./var/volatile/run/lmbench: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile/run/sepermit: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile/run/ConsoleKit: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile/run: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile/tmp/.automount-mmcblk0p1: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile/tmp/atags: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile/tmp: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/volatile: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/spool: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var/local: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./var: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./www/logs: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./www/pages/dav: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./www/pages/index.html: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./www/pages: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./www/var: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./www: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./usr/sbin: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./usr/arm-arago-linux-gnueabi/bin: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./usr/arm-arago-linux-gnueabi: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./usr/share/terminfo/d: Cannot change ownership to uid 0, gid 0: Operation not permitted
      tar: ./usr/share/terminfo/x: Cannot change ownership to uid 0, gid 0: Operation not permitted

      I'm not sure of the importance of this. 

    • compress everything again with: tar -czf custom-fs.tar.gz *
    • using diff both binaries differ.
    This custom-fs.tar.gz is not working so definitely, the errors should mean something. Is this somehow related to creating a volume with dd if=/dev/zero of=/mnt/sample bs=1M count=100?
    Maybe somebody could clarify this?
    Thanks in advance.
  • 0 in reply to Victor Mayoral
    Guru 31670 points

    Victor,

    Try sudo tar xzf omapl138-lcdk-fs.tar.gz -C omap-fs/

  • 0 in reply to Renjith Thomas
    Intellectual 625 points

    Renjith Thomas said:

    Victor,

    Try sudo tar xzf omapl138-lcdk-fs.tar.gz -C omap-fs/

    Same behavior, still getting the errors:

    tar: ./media/ram: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./media/union: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./media/hdd: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./media: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./mnt/.splash: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./opt/ltp/lib/libmm.a: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./opt/ltp/lib/libmem.a: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./opt/ltp/lib: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./opt/ltp/runltp: Cannot change ownership to uid 0, gid 0: Operation not permitted
    tar: ./opt/ltp/ver_linux: Cannot change ownership to uid 0, gid 0: Operation not permitted

    ......

  • 0 in reply to Victor Mayoral
    Guru 31670 points

    Victor,

    Can you try using the tar options --no-same-owner or --no-same-permissions?