From: Darren Hart <dvhart@linux.intel.com>
To: jfabernathy <jfabernathy@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: meta-cedartrail - serial console
Date: Thu, 31 May 2012 11:13:55 -0700 [thread overview]
Message-ID: <4FC7B4E3.1010401@linux.intel.com> (raw)
In-Reply-To: <4FC79837.2070309@gmail.com>
On 05/31/2012 09:11 AM, jfabernathy wrote:
> Using a DN2800MT (Marshalltown) Intel board, I'm testing the
> meta-cedartrail using edison branch and noticed an issues with the
> serial console.
>
> The cedartrail.conf in the machine directory has the following statements:
>
> SYSLINUX_OPTS = "serial 0 115200"
> SERIAL_CONSOLE = "115200 ttyS0"
> APPEND += "console=ttyS0,115200 console=tty0"
>
> However, when the image booted, I had no serial console on ttyS0. I
> checked /etc/inittab and noticed that the following line existed:
>
> S:2345:respawn:/sbin/getty 115200 ttyS3
>
> I changed the ttyS3 to ttyS0 and then I have a serial console on the
> next reboot. So it appears the override in the .conf file is not
> working. Also I only have the console from getty, and not the kernel
> logging console.
>
> Anyone have a solution??
>
> If this is considered a bug I can put it on bugzilla.
Lets make sure your environment is what we expect. Please provide the
output of:
$ bitbake core-image-minimal -e | grep SERIAL_CONSOLE=
If it is not "115200 ttyS0" then it is getting overwritten somewhere
either in your config, or possibly by an inappropriate selection of an
assignment operator (=, ?=, etc.) in edison.
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2012-05-31 18:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-31 16:11 meta-cedartrail - serial console jfabernathy
2012-05-31 18:13 ` Darren Hart [this message]
2012-05-31 18:54 ` jfabernathy
2012-05-31 19:41 ` Darren Hart
2012-06-01 15:45 ` jfabernathy
2012-06-01 17:01 ` Darren Hart
2012-06-01 17:39 ` jfabernathy
2012-06-01 17:44 ` Darren Hart
2012-06-01 17:53 ` jfabernathy
2012-06-01 17:55 ` Darren Hart
2012-06-01 19:14 ` jfabernathy
2012-06-01 20:02 ` Darren Hart
2012-06-01 20:07 ` jfabernathy
2012-06-01 20:10 ` Darren Hart
2012-06-01 20:31 ` jfabernathy
2012-06-01 21:19 ` Darren Hart
2012-06-01 20:08 ` jfabernathy
2012-06-01 20:12 ` Darren Hart
2012-05-31 18:18 ` Bodke, Kishore K
2012-05-31 18:36 ` jfabernathy
2012-05-31 19:32 ` jfabernathy
2012-05-31 19:43 ` Darren Hart
2012-06-01 18:03 ` Bodke, Kishore K
2012-06-01 18:12 ` Darren Hart
2012-06-01 21:02 ` Bodke, Kishore K
2012-06-01 21:16 ` Darren Hart
2012-06-02 0:51 ` Bodke, Kishore K
2012-06-04 16:32 ` Darren Hart
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=4FC7B4E3.1010401@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=jfabernathy@gmail.com \
--cc=yocto@yoctoproject.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.