From: "Keith Wessel" <keith@wessel.com>
To: <gentoo-accessibility@lists.gentoo.org>
Subject: [gentoo-accessibility] Advice on serial console configurations?
Date: Wed, 18 Feb 2015 16:56:14 -0600 [thread overview]
Message-ID: <007301d04bce$197b94e0$4c72bea0$@wessel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1671 bytes --]
Hi, all,
Hoping someone has more insight into serial console setup than me.
My current system has no on-board serial ports. I've been without Speakup
since I moved to it. Not even headers for one. I'm looking for an excuse to
by a new mother board.
In the meantime, I've got a SIIG PCI board in there that works fine. It's
driving my braille display with brltty just fine. Of course, it uses
non-standard I/O addrs and IRQs. But brltty doesn't care about that.
I recently got a docking station for my work Windows laptop that has a
serial port, and this was my nudge to use the other port on my PCI serial
card to set up a serial console that I can access from Windows. Keeps me
from having to get my wife to read the screen to me every time my system
won't boot far enough for brltty.
When I add:
console=ttyS0,9600n8 console=tty0
to my kernel command-line, I get nothing in my terminal program on the
laptop. I know the connection's working because agetty gives me a login
prompt and allows me to log in once the system is booting.
What does happen with the console parameters added to the kernel
command-line different from without them is that the system boots very
slowly. Takes more like 10 minutes instead of the usual 1 minute to get to a
login prompt.
Is this because my serial ports are using non-standard I/O ports and IRQs?
Or is Linux smart enough to not assume anything about those? Clearly
something's getting it right since the right parameters are getting set once
the system has booted and brltty starts.
Can anyone think of any other explanations? Or is it time to buy a new
mother board?
Thanks,
Keith
[-- Attachment #2: Type: text/html, Size: 4163 bytes --]
reply other threads:[~2015-02-18 22:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='007301d04bce$197b94e0$4c72bea0$@wessel.com' \
--to=keith@wessel.com \
--cc=gentoo-accessibility@lists.gentoo.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