linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jean-Samuel Chenard" <jsamch@macs.ece.mcgill.ca>
To: linuxppc-embedded@ozlabs.org, kernelppc@gmail.com
Subject: RE: File system problem
Date: Thu, 3 Jan 2008 18:57:43 -0500	[thread overview]
Message-ID: <169c03cb0801031557r1efbd89fsd971533e04477daa@mail.gmail.com> (raw)

> Message: 9
> Date: Thu, 3 Jan 2008 18:00:14 +0100
> From: "mojtaba"
>
> Actually, I removed the console and null created by buildroot and create
> them manually using make node. This time the system freezes at this point=
.
> "Freeing unused kernel memory: 76k init"

Hi Mojtaba,

I just want to comment on your observation that the file size in /dev
was zero.  This is normal as the device files are 'special' since they
are a mean of abstracting the interface to the kernel.  I had to read
the online book listed below before I could understand the inner
workings of those special files.  If you plan on interfacing your FPGA
with the Linux Kernel, I suggest you read it too, as it is a very
insightful book:
http://lwn.net/Kernel/LDD3/

At this point, your system is not frozen, but your init script and
configuration files are probably not all correctly set.  You might
need to read some documentation about buildroot to see what its init
scripts are trying to do.

You might be missing a library or symlink (I got that problem in my
attempt to build the BusyBox root filesystem from scratch).  One way
to go at the problem is to pass the init=3D/bin/ash or something like
that to your kernel at the boot prompt (you could even make some
trivial 'hello world' program and pass it to the kernel as the init
process).  This way, you can dive right into a shell or your program
and avoid init and its configuration.

After some copying of required libraries in /lib (I'm using uClibc)
and the creation of the required symbolic links, I got my Busybox root
filesystem working on my ML-310 board.

Good luck!

Regards,

Jean-Samuel
--=20
Ph.D. candidate
Integrated Microsystems Laboratory
McGill University, Montr=E9al, QC, CANADA
Web Page: http://chaos.ece.mcgill.ca

             reply	other threads:[~2008-01-03 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-03 23:57 Jean-Samuel Chenard [this message]
2008-01-04 11:57 ` File system problem mojtaba
  -- strict thread matches above, loose matches on Subject: below --
2008-01-03  3:32 Jean-Samuel Chenard
2008-01-03 15:57 ` mojtaba
2008-01-03 17:27   ` Grant Likely
2008-01-03 17:00 ` mojtaba
2008-01-03 17:33   ` Grant Likely
2008-01-02 18:50 mojtaba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=169c03cb0801031557r1efbd89fsd971533e04477daa@mail.gmail.com \
    --to=jsamch@macs.ece.mcgill.ca \
    --cc=kernelppc@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).