All of lore.kernel.org
 help / color / mirror / Atom feed
From: btuch@usa.net (Brian T.)
To: linux-mtd@lists.infradead.org
Subject: Unable to open console /start init - more info (jffs2)
Date: Wed, 12 Mar 2003 12:27:04 -0600	[thread overview]
Message-ID: <001501c2e8c4$fbadca60$150a0ac0@jbmsoft.com> (raw)
In-Reply-To: 200303120954.55244.tglx@linutronix.de

Thanks for the reply.

> - The kernel was compiled without support for virtual terminals.
I tried adding in virtual console support, and I just get a bunch of
pc_keyb: controller jammed (0x17) errors, and then it times out
and keeps booting, eventually with the same end result.

> - /dev/ttyX is not there
 /dev/console and /dev/ttyS0 *should* be there.  I haven't changed anything
with the that part of the Makefile which creates those files, all though
maybe thats
part of the problem; maybe this newer version of JFFS2 doesn't like the way
they
are created.  All the /dev/ files are created with example: "touch
./somedir/dev/@console,c,5,1"
which worked fine with the older distro I'm using. The jffs2 images is then
made
on ./somedir/.

> - Wrong root partition
My root partition is MTD partition #1.  When the kernel comes up, so I need
to specify which partition to use as root?  Or does it scan them and use the
first one it finds?  If I need to specify which one is to be mounted as the
root partition, any idea how I do that?

If I removed /sbin/init from the build and put my flash image on the ROMFS,
then main.c gets past the first init trial, and attempts the others, and
then fails.  If I
leave it there, then it stops at /sbin/init, which I believe proves that it
is mounting the right MTD partition; but am still unsure.

Kind regards,

-Brian

  reply	other threads:[~2003-03-12 18:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11 16:58 Unable to open console /start init Brian T.
2003-03-11 19:30 ` Unable to open console /start init - more info (jffs2) Brian T.
2003-03-12  8:54   ` Thomas Gleixner
2003-03-12 18:27     ` Brian T. [this message]
2003-03-13 13:06       ` Brian T.
2003-03-13 12:32   ` Bob Chiodini

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='001501c2e8c4$fbadca60$150a0ac0@jbmsoft.com' \
    --to=btuch@usa.net \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.