linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Joachim Meyer" <Jogi95@web.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ml310 kernel2.6 booting problems
Date: Wed, 16 Jan 2008 13:30:49 -0700	[thread overview]
Message-ID: <fa686aa40801161230q2308188djf1f6c756412051dc@mail.gmail.com> (raw)
In-Reply-To: <538215286@web.de>

On 1/16/08, Joachim Meyer <Jogi95@web.de> wrote:
> Thx for the answer
>
> It's right, there is no /dev/console, but the MontaVista-Linux-kernel can fully boot with this rootFS, how comes?

hmmm, I don't know.  The montavista kernel might be running a
different binary as the init process.  Compare the kernel parameter
lines between the two.

> Doesn't matter, I was going to make my own RootFS anyway, so can you give me an hint how I would
> do this best?
> I tried the Klingauf-Script (www.klingauf.com) with busybox, but I still have no console in my /dev/ and it doesn't work.

Creating a console device is easy:

$ mknod /dev/console c 5 1

> I tried out buildroot, but I was a little overstrained with the configuration and when I did "make" it aborted with an error message
> after a long time of working
> Then I tried ELDK. I read that I could use the Directory "<install-dir>/ppc_4xx/" as rootfs but when I go there and look inside
> /dev I find only one entry:
> prw------- 1 jogi jogi 0 2007-01-20 04:58 initctl
> So this won't work, would it?

Looks like you haven't installed ELDK correctly.  I recommend
rereading the instructions and giving it another try.  ELDK is a great
starting point.

>
> Which way would be the best for me to get an good RootFS easily?
> If the answer would be buildroot can you give me a short summary which settings are importent?

Personally, I use buildroot, but you should start with ELDK to get things going.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  reply	other threads:[~2008-01-16 20:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-16 20:02 ml310 kernel2.6 booting problems Joachim Meyer
2008-01-16 20:30 ` Grant Likely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-18  2:49 Jean-Samuel Chenard
2008-01-19  0:11 ` Ron Sass
2008-01-19  0:35   ` Stephen Neuendorffer
2008-01-19  1:21     ` Ron Sass
2008-01-19  1:23   ` Grant Likely
2008-01-17 20:19 Joachim Meyer
2008-01-16 13:25 Joachim Meyer
2008-01-16 14:50 ` Grant Likely
2008-01-25 13:04   ` greenlean
2008-01-25 15:17     ` Grant Likely

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=fa686aa40801161230q2308188djf1f6c756412051dc@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=Jogi95@web.de \
    --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).