From: "Pat O'Rourke" <orourke@missioncriticallinux.com>
To: ultralinux@vger.kernel.org
Subject: Re: serial console
Date: Fri, 11 Feb 2000 21:21:38 +0000 [thread overview]
Message-ID: <marc-linux-ultrasparc-95032461205045@msgid-missing> (raw)
In-Reply-To: <marc-linux-ultrasparc-95030299721929@msgid-missing>
Matthew Jacob wrote:
> define 'not work'? I've had the serial console just be 'strange' when running
> it in a screen session so I just type 'reset'.
It receives no output (kernel printk's don't show up) and does not accept
input. I've been using minicom and the status bar shows 'offline' right
after the message 'Booting Linux...' appears (note this is a prom_printf
as opposed to a printk).
Pat
--
Patrick O'Rourke
orourke@missioncriticallinux.com
prev parent reply other threads:[~2000-02-11 21:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-11 17:08 serial console Pat O'Rourke
2000-02-11 21:04 ` Matthew Jacob
2000-02-11 21:21 ` Pat O'Rourke [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=marc-linux-ultrasparc-95032461205045@msgid-missing \
--to=orourke@missioncriticallinux.com \
--cc=ultralinux@vger.kernel.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