public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Rob Hudson" <captinlogic@gmail.com>
To: "Speakup is a screen review system for Linux."
	<speakup@linux-speakup.org>
Subject: Re: slackware on a very fast machine
Date: Thu, 26 Jun 2014 15:02:41 -0500	[thread overview]
Message-ID: <F5E8CAF9DC074ACDB39882E7FDB5EA4B@train> (raw)
In-Reply-To: <53AC736D.3050405@math.wisc.edu>

I don't understand why the kernel has serial bugs. Many many many companies 
still use serial consoles, and in fact, as faras I know, it is still the 
most common way of interacting directly with rack-mounted computers and some 
high end routers. What's the deal?
----- Original Message ----- 
From: "John G. Heim" <jheim@math.wisc.edu>
To: "Speakup is a screen review system for Linux." 
<speakup@linux-speakup.org>
Sent: Thursday, June 26, 2014 2:24 PM
Subject: Re: slackware on a very fast machine


> The syntax is "modprobe speakup_ltlk".
>
> But it isn't going to help unless  slackware hacked the kernel clode to 
> fix the serial port bug.  If they used the speakup code as it is in the 
> kernel, your litetalk won't work.
> I started trying to make a fork of grml with a patched kernel but never 
> had the time to really get into it. Instead I've been using an FAI disk. 
> FAI is actually an installer system. FAI stands for fully automated 
> install. But they make it real easy to create a live CD.
> On 06/26/14 14:12, Jude DaShiell wrote:
>> I can't determine when the 10 seconds starts or ends with
>> slackware-Current on this machine since the machine appears to be running
>> too fast to get any usable audible indicators from it any longer.  What 
>> is
>> the correct syntax to modprobe speakup and have speakup come up on a
>> litetalk synthesizer on ttyS0?  I might be able to get slackware to run
>> the speakup.s kernel and if I can do that, I ought to be able to key the
>> modprobe line in once I get in as root.
>>
>>
>>
>> jude <jdashiel@shellworld.net>
>>
>> _______________________________________________
>> Speakup mailing list
>> Speakup@linux-speakup.org
>> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
>>
>
> -- 
> ---
> John G. Heim, 608-263-4189, jheim@math.wisc.edu
> _______________________________________________
> Speakup mailing list
> Speakup@linux-speakup.org
> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
> 


  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Jude DaShiell
 ` John G. Heim
   ` Rob Hudson [this message]
     ` covici
       ` John G. Heim
     ` John G. Heim
       ` covici
       ` Trevor Astrope

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=F5E8CAF9DC074ACDB39882E7FDB5EA4B@train \
    --to=captinlogic@gmail.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).