From: "Tyler Spivey" <tspivey8@softhome.net>
To: speakup@braille.uwo.ca
Subject: Re: brltty and red hat 9
Date: Thu, 12 Jun 2003 10:10:53 -0700 [thread overview]
Message-ID: <000901c33105$a4162ca0$691817cf@130SetBC01> (raw)
In-Reply-To: <20030612144822.GA16304@localhost.localdomain>
i'm just speaking from past postings here, i'm probably wrong so take mya
dvice with a grain of salt.
i believe that red hat uses something called kudzu. the spelling's wrong,
but it detects any new hardware and tries to configure it.
i'm not sure how to shut it off, but that's probably your problem.
again, i'm not sure, i'm just going on a lim here.
----- Original Message -----
From: <jacobs@surferie.net>
To: <speakup@braille.uwo.ca>
Sent: Thursday, June 12, 2003 7:48 AM
Subject: brltty and red hat 9
> Hi listers
> I dug out my powerbraille 80 yesterday and decided to put it to use. So I
> installed the brltty 3.2 RPM, editted the configuration file, and launched
> brltty. All was well... for about 5 seconds. Then my display showed what
> looks like computer braille question marks (dots 1-4-5-6). Moving around
the
> screen with my braille display revealed nothing but computer braille
> questionmarks on the bottom half, and grade II braille questionmarks (dots
> 2-3-6) on the top half of the screen. When starting brltty in rc.sysinit,
> things go better up until right before it goes multiuser. Then my display
> goes back to the questionmarks. I'm assuming it's something RH does in the
> boot scripts, but for the life of me, I can't find it. This does not
happen
> when I connect the display to my laptop running slackware 9.
> Any brltty/redhat users know what's going on here? Yes, I know this is the
> speakup list.
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
jacobs
` Tyler Spivey [this message]
` Thomas D. Ward
` jacobs
` Lorenzo Prince
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='000901c33105$a4162ca0$691817cf@130SetBC01' \
--to=tspivey8@softhome.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).