public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Loading speakup modules strange problem.
Date: Sun, 11 Jan 2009 21:29:39 -0700	[thread overview]
Message-ID: <C2A9214501DD420383CE740320B11FD4@tdsdev> (raw)
In-Reply-To: <1231734220.70533953@192.168.1.70>

hello,
I'm not sure what the deal could be, but have you checked the panic, dmesg, 
and syslog logs for any type of output after it locks up?


Thanks,
Tyler Littlefield
http://tysdomain.com

----- Original Message ----- 
From: "Joe Kamphaus" <joe@joekamphaus.net>
To: <speakup@braille.uwo.ca>
Sent: Sunday, January 11, 2009 9:23 PM
Subject: Loading speakup modules strange problem.


>I am using debian lenny with kernel 2.6.26-1-686 with the speakup modules 
>package for the same.
> I am using the software synthesizer with speech-dispatcher and speechd-up.
> My system crashes causing keyboard to lock up when I use modprobe to load 
> them from the command line.
>
> The strange thing is... I can open X-Windows and load the modules in xterm 
> or rxvt and exit X-Windows and speakup works great.  I have tried init 
> script to no avail either.  Seems that the only way I can get speakup to 
> work is by loading them from xterm.
>
> What can I do?
>
> Joe Kamphaus of LinuxSpeaks
> [http://www.joekamphaus.net] www.joekamphaus.net
> [http://www.joeandwilma.com]
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> __________ NOD32 3757 (20090111) Information __________
>
> This message was checked by NOD32 antivirus system.
> http://www.eset.com
>
> 


  reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Joe Kamphaus
 ` Tyler Littlefield [this message]
 ` 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=C2A9214501DD420383CE740320B11FD4@tdsdev \
    --to=tyler@tysdomain.com \
    --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).