public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Mitchell D. Lynn" <mlynn@kc.rr.com>
To: "'Speakup is a screen review system for Linux.'"
	<speakup@linux-speakup.org>
Subject: RE: Slack 13.37 and 14.0
Date: Wed, 15 May 2013 20:38:18 -0500	[thread overview]
Message-ID: <1FE7DAD9E5CD4A86A60DA427B9B3C72F@mdlynn> (raw)
In-Reply-To: <22596.1368664945@ccs.covici.com>

The shops I visited had systems built with those boards, and we checked CMOS
to see if they were listed there as well as in manuals. They also looked at
the board, and nothing indicated there were serial connections at all. It's
something I will keep in mind in the future. Usually buy my stuff online;
looks like I will again have to face those odious PDF files. 

 

-----Original Message-----
From: Speakup [mailto:speakup-bounces@linux-speakup.org] On Behalf Of
covici@ccs.covici.com
Sent: Wednesday, May 15, 2013 7:42 PM
To: Speakup is a screen review system for Linux.
Subject: Re: Slack 13.37 and 14.0

Did you look at the specs to see if they had the headers -- what they seem
to be doing these days is have the headers without a cable or bracket, so
you have to bring it out to a slot on the back of the unit.

Mitchell D. Lynn <mlynn@kc.rr.com> wrote:

> I don't know about "most mainboards," but none of those I have looked 
> at in the flesh over the past 12-months or so have had any serial 
> connections at all.
> 
> -----Original Message-----
> From: Speakup [mailto:speakup-bounces@linux-speakup.org] On Behalf Of 
> covici@ccs.covici.com
> Sent: Wednesday, May 15, 2013 11:40 AM
> To: Speakup is a screen review system for Linux.
> Subject: Re: Slack 13.37 and 14.0
> 
> Most motherboards have the serial headers, just not brought out to the
back.
> 
> Tony Baechler <tony@baechler.net> wrote:
> 
> > No, you're still not understanding.  Debian Wheezy has the 3.2 
> > kernel, so no serial support.  That's why I suggested installing 
> > Squeeze and upgrading to Wheezy.  That way you can run the 2.6.32 
> > kernel with newer packages and still have serial support.  No, you 
> > won't get most boot messages with software speech because it takes a 
> > while for sound drivers to load.  I have both kernels installed here 
> > so I can get hardware speech if my system becomes unbootable.  I had 
> > no problem finding a motherboard with a serial port last August.  
> > You have to look for server motherboards, but they're not that hard to
find.
> > 
> > On 5/15/2013 7:15 AM, Mitchell D. Lynn wrote:
> > > Thanks for the info on the 3.2 kernels. That, then, is the issue.
> > > 
> > > RE Debian: Looks like there has been a new release since I last 
> > > looked. Grabbed the Wheezy release and installed on a test system 
> > > last night. Software synth works fine on that machine. No serial 
> > > port on this system to test with DEC. I will see how it does on 
> > > the main server later this week when I can have it down for an 
> > > extended period. I can live with a software synth as long as I can 
> > > get boot messages, and serial ports are getting harder to find on 
> > > modern
> mainboards.
> > _______________________________________________
> > Speakup mailing list
> > Speakup@linux-speakup.org
> > http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> --
> Your life is like a penny.  You're going to lose it.  The question is:
> How do
> you spend it?
> 
>          John Covici
>          covici@ccs.covici.com
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup

--
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com
_______________________________________________
Speakup mailing list
Speakup@linux-speakup.org
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup


  reply	other threads:[~ UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Mitchell D. Lynn
 ` Tony Baechler
   ` Mitchell D. Lynn
     ` Tony Baechler
       ` Mitchell D. Lynn
         ` Tony Baechler
           ` Mitchell D. Lynn
           ` covici
             ` Mitchell D. Lynn
               ` covici
                 ` Mitchell D. Lynn [this message]
                   ` Onboard serial ports Tony Baechler
                     ` John G. Heim
                       ` Mitchell D. Lynn
                       ` Jason White
                   ` Slack 13.37 and 14.0 John G. Heim
             ` Adam Myrow
               ` Mitchell D. Lynn
               ` Serial ports with 32-bit vs. 64-bit processors Tony Baechler
                 ` Kitty Litter
                 ` John G. Heim
                   ` Ryan Hutchings
                     ` John G. Heim
                   ` Tony Baechler
                 ` covici
                   ` Keith Wessel
           ` Slack 13.37 and 14.0 Gregory Nowak
             ` Tony Baechler
   ` Ryan Hutchings
     ` Debian Squeeze CDs Tony Baechler
       ` Ryan Hutchings
   ` Slack 13.37 and 14.0 Alex Snow
     ` Mitchell D. Lynn

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=1FE7DAD9E5CD4A86A60DA427B9B3C72F@mdlynn \
    --to=mlynn@kc.rr.com \
    --cc=speakup@linux-speakup.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).