All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Caulfield <pcaulfie@redhat.com>
To: xen-devel@lists.sourceforge.net
Subject: Serial console funnies
Date: Tue, 25 Jan 2005 11:11:34 +0000	[thread overview]
Message-ID: <20050125111134.GD18925@tykepenguin.com> (raw)

I have a dual-processor machine with no keyboard/monitor on it that I would like
to use for Xen but I'm having problems getting the serial console to work
properly.

I can see the system boot up into dom0 and I get the login prompt so it all
looks setup correctly, but it won't take keyboard input - at least not into the
login process on dom0. if I ssh into the box and try to read from the serial
port I still get nothing.

However, if I do ^a^a^a I can interact with the Xen code, so the serial port
itself is working, it just seems like it's not getting passed down to dom0.

I've had this from 2.0->2.0.3 and also with the latest unstable bk.

FWIW this is my grub entry:

title Xen (2.0/Linux 2.6.10)
        root (hd0,0)
        kernel /xen.gz com1=57600,8n1 dom0_mem=131072
        module /vmlinuz-2.6.10-xen0 ro root=/dev/sda5 console=ttyS0

-- 

patrick


-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

             reply	other threads:[~2005-01-25 11:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-25 11:11 Patrick Caulfield [this message]
2005-01-25 17:05 ` Serial console funnies Ian Pratt
2005-01-25 17:26   ` Patrick Caulfield
2005-01-25 21:37 ` Chris Andrews
2005-01-26  8:58   ` Patrick Caulfield
2005-01-28 10:59     ` Chris Andrews

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=20050125111134.GD18925@tykepenguin.com \
    --to=pcaulfie@redhat.com \
    --cc=xen-devel@lists.sourceforge.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 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.