linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Guillaume Dargaud" <dargaud@lpsc.in2p3.fr>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Booting a Xilinx board
Date: Tue, 8 Apr 2008 15:32:26 -0600	[thread overview]
Message-ID: <fa686aa40804081432k6b126485w289669a214cadeb9@mail.gmail.com> (raw)
In-Reply-To: <10fd01c89974$57a0c830$f52f9e86@LPSC0173W>

On Tue, Apr 8, 2008 at 6:30 AM, Guillaume Dargaud <dargaud@lpsc.in2p3.fr> wrote:
> I'm making progress, thanks in no small part to this list, but I still need
> coaching, if you don't mind. The current boot is currently going as such:
>
>
>  loaded at:     00400000 005A819C
>  board data at: 005A6120 005A619C
<snip>
>  [    4.897987] RPC: Registered udp transport module.
>  [    4.953147] RPC: Registered tcp transport module.
>  [    5.011138] RAMDISK: Compressed image found at block 0
>  [    5.905538] VFS: Mounted root (ext2 filesystem).
>  [    5.945703] Freeing unused kernel memormdev: /etc/mdev.conf: No such
> file
>  or directory
>  mdev: /etc/mdev.conf: No such file or directory
<snip>
>  mdev: /etc/mdev.conf: No such file or directory
>  mdev: /etc/mdev.conf: No such file or directory
>  mount: mounting configfs on /config failed: No such device
>  Initializing random number generator... done.
>  Starting network...
>  ip: RTNETLINK answers: File exists
>
>
>  And then it stops, although I still have echo when I type.
>  Now there's no /etc/mdev.conf file in my root fylesystem and I understand I
> need to create the devices.
>  I've been reading docs/mdev.txt and
> http://www.lfs-matrix.org/clfs/view/clfs-embedded/mips/bootscripts/mdev.html
> and I'm a bit confused.

Congratulations, your kernel is in good shape.  Now you're dealing
with userspace issues.  You can try bypassing most of the init process
to see if you can get a prompt.  Add init=/bin/sh to the kernel
command line.

>
>  - do the devices need to be created in the FS before building the ramdisk
> and subsequent ACE file ?

Yes, you can statically create the device files.  MAKEDEV will do this
for you.  You can even just copy them from a working Linux system (any
arch).

>  - are they created dynamically by /bin/mdev on boot based on a manually
> written /etc/mdev.conf table as the error messages seem to imply ?

That depends on your rootfs.  Where did you get your rootfs image?

>  - can they be generated automagically by a MAKEDEV script ?
>
>  In the second case, how do I know which devices and what names I'm supposed
> to define ?

Easiest way: copy from the /dev tree in a running Linux machine.

Cheers,
g.

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

      reply	other threads:[~2008-04-08 21:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-07 15:33 Booting a Xilinx board Guillaume Dargaud
2008-04-07 16:44 ` Stephen Neuendorffer
2008-04-07 16:59   ` John Linn
2008-04-08  3:55 ` Grant Likely
2008-04-08  9:22   ` Guillaume Dargaud
2008-04-08 12:30     ` Guillaume Dargaud
2008-04-08 21:32       ` Grant Likely [this message]

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=fa686aa40804081432k6b126485w289669a214cadeb9@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=dargaud@lpsc.in2p3.fr \
    --cc=linuxppc-dev@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).