Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: <bogus@does.not.exist.com>
To: buildroot@busybox.net
Subject: No subject
Date: Mon, 14 Jul 2008 13:16:20 -0000	[thread overview]
Message-ID: <mailman.4.1219477498.1340.buildroot@uclibc.org> (raw)

ttymxc0 device. If so, then the reason why you cannot login is that
you don't have ttymxc0 listed in /etc/securetty.

The file comes from target/generic/target_skeleton/etc, but you can
simply edit it under project_build_arm/uclibc/root/etc and rerun make
to regenerate your filesystem image.

I don't see any mention of /dev/ttymxcN in Documentation/devices.txt
in the kernel sources? I take it that the serial driver isn't in the
mainline kernel?

 > THe other thing I tried to do was pass init=/dev/sh and
 > init=/dev/bash to try to get a direct shell prompt. I don't think
 > it was connecting to the MX31's serial port because I never saw any
 > outputs after the filesystem was mounted. Is there a recommended
 > way to force /dev/sh to appear on a ttyS0 (or actually ttymxc0 for
 > the MX31)

I take it you mean /bin/sh not /dev/sh?

Strange. And you do get output from init and login with the same
filesystem if you boot without init=/bin/sh?

-- 
Bye, Peter Korsgaard

             reply	other threads:[~2008-07-14 13:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 13:16 bogus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-12-07 21:22 No subject bogus
2008-11-21  1:22 bogus
2008-10-23 17:17 bogus
2008-10-23 17:17 bogus
2008-10-23 17:17 bogus
2008-09-15 17:22 bogus
2008-09-15 17:22 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-07-14 13:16 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-04-23 14:39 bogus
2008-03-17 22:01 bogus
2007-12-01  7:52 bogus
2007-12-01  7:52 bogus
2007-10-06 20:13 bogus
2007-10-06 20:13 bogus
2007-10-06 20:13 bogus
2007-07-23 18:04 bogus
2007-07-23 18:04 bogus
2007-06-23 20:07 bogus
2007-02-14  8:32 bogus
2007-02-14  8:32 bogus
2007-02-14  8:32 bogus
2007-02-14  8:32 bogus
2007-02-06  7:08 bogus
2007-02-06  7:08 bogus
2007-02-06  7:08 bogus
2007-02-06  7:08 bogus
2006-08-17  1:58 bogus
2006-08-17  1:58 bogus
2006-08-17  1:58 bogus
2006-08-17  1:58 bogus
2006-08-17  1:58 bogus
2006-08-17  1:58 bogus
2006-08-17  1:58 bogus

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=mailman.4.1219477498.1340.buildroot@uclibc.org \
    --to=bogus@does.not.exist.com \
    --cc=buildroot@busybox.net \
    /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