public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Jacob Schmude <jacobs@ncinter.net>
To: speakup@braille.uwo.ca
Subject: CVS speakup with 2.4.0-test9 (was Re: emacs terminal devices)
Date: Wed, 18 Oct 2000 18:38:10 -0400	[thread overview]
Message-ID: <E13m1qb-0000BS-00@jscp> (raw)
In-Reply-To: <x7aec1ga81.fsf@speech.braille.uwo.ca> (message from Kirk Reiser on 18 Oct 2000 16:34:06 -0400)

HI
     Well Kirk, no luck. It compiles fine, but as soon as I attempt to boot the new kernel, the system hangs. Yes, I did start with a clean source, I did specify the synth properly, and I did make sure lilo was run. This is kernel v 2.4.0-test9. At first I thought it might be a problem with device probing, so I went in and changed the synth_portlist array in speakup_dtlk.c to only look on 0x29e. Still no luck. Here's what I get when I boot:
LILO boot: linux
uncompressing linux...ok, booting the kernel.
     Then, the system hangs. Not even control-alt-delete will reboot. I have to power the system down.

Got any ideas? I'd really like to get speakup working with this kernel. And no, I won't go back to 2.2, I've made the 2.4 system upgrades already.    Oh well, that's what happens to someone who beta tests devel kernels.



  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Jacob Schmude's message of "Wed, 18 Oct 2000 15:37:01 -0400">
 ` emacs terminal devices Jacob Schmude <Jacob Schmude
   ` Kirk Reiser
     ` Jacob Schmude
       ` Kirk Reiser
         ` Jacob Schmude [this message]
           ` CVS speakup with 2.4.0-test9 (was Re: emacs terminal devices) Kirk Reiser
             ` Jacob Schmude
             ` Brent Harding
               ` Jason Custer
         ` emacs terminal devices Brent Harding
           ` Kirk Reiser

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=E13m1qb-0000BS-00@jscp \
    --to=jacobs@ncinter.net \
    --cc=speakup@braille.uwo.ca \
    /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).