From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: modprobe speakupmain hangs
Date: Wed, 1 Nov 2006 16:57:58 -0700 [thread overview]
Message-ID: <20061101235758.GA30876@localhost.localdomain> (raw)
In-Reply-To: <Pine.BSF.4.64.0611011648180.38567@freire2.furyyjbeyq.arg>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've always had speakup_main built into the kernel, so I can't confirm
anything on that. However, I did report a while back having issues
when switching between combinations of none/bns/dtlk/sftsyn on one of
my machines. At the time, since the machine was running an outdated
version of slackware, I theorized that the problem may have to do with
an older version of gcc. Since then however, I've installed debian
testing on this box, and the version of gcc hasn't made a difference
as far as this speakup issue is concerned. Yes, I did build binaries
of the kernel and modules from scratch after upgrading from slackware
to debian.
Greg
On Wed, Nov 01, 2006 at 04:53:59PM -0600, luke wrote:
> I reported this problem 3 or 4 weeks ago. Gregory Nowak was able to
> confirm that it was happening.
>
> I was not able to get speakup running after the fact as you describe,
> although I can't say for certain that I tried that exact method.
> Greg did not report getting it to work after the fact either.
>
> I solved it by simply having speakup main compile as builtin, instead of
> as a module.
>
> While this is untested in regards to modprobe, it would be better to use:
>
> kill -9 $!
>
> Than it is to use:
>
> killall modprobe
>
> because if any concurrent modprobes happened to be running at that time,
> you could get yourself into some trouble.
>
> Regards,
>
> Luke
>
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
iD8DBQFFSTSG7s9z/XlyUyARAlU6AKCDTuxXn9Rq3G+8qLEMi5PrgJzsNACdEXvw
pTalCjQgUYJ4hFqDnPUUMi8=
=Zgay
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Hynek Hanke
` luke
` Gregory Nowak [this message]
` luke
` Hynek Hanke
` luke
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=20061101235758.GA30876@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).