[BRLTTY] Brltty woes on Centos 7

[Keith Wessel]

Dave,

No, I get a text console on virtual TTY1 when in runlevel 3, so it seems to
be acting sane there.

I figured out why the service unit script that you packaged with brltty
wasn't working, and that was my fault. I was adding to (replacing) the
ExecStart line to add a -q to the start-up. That didn't work since your unit
uses the wrapper setup. I see now, if I want to do that, that I need to add
it to the environment variable that your wrapper uses for the executable
args which need to include the -n switch.

So, now I have my basic service script and your service script ending up at
the same result: they both end up with "screen not in text mode" even when
GDM is not running. And even if I do an alt-F2 to switch to another VT, that
doesn't change. Only way to get it to change is to restart the service.

I did make one change to your system unit script: instead of
Before=sysinit.target, I have After=alsa-restore.service. Otherwise, I don't
have Alsa available when brltty starts it, and it falls back on the beeper
device.

I'm happy to add logging. I notice that, with my basic unit script without
your wrapper, the brltty output all gets captured by journalctl. With the
wrapper, I only get lines about the service starting and stopping. Is there
a way to get the wrapper to send the brltty output to a log of some sort? If
not, I can go back to my simpler service unit script and send you what I'm
seeing in journalctl. If there's any way to get brltty to send more verbose
messages to the console for system to log, I'd also appreciate knowing that.

Given that, I'll collect some info, and we'll see if we can catch this
problem red-handed.

Keith


-----Original Message-----
From: BRLTTY [mailto:brltty-bounces at brltty.com] On Behalf Of Dave Mielke
Sent: Wednesday, March 01, 2017 3:37 PM
To: Informal discussion between users and developers of BRLTTY.
<brltty at brltty.com>
Subject: Re: [BRLTTY] Brltty woes on Centos 7

[quoted lines by Keith Wessel on 2017/03/01 at 15:17 -0600]

>Alright, I've made a much simpler brltty.service to try and simplify
things,
>and I'm getting this down to a console error. I've changed my system to
only
>boot to runlevel 3 to get Gnome out of the mix. But, when brltty starts at
>boot, it still reports "screen not in text mode" on the braille display. 

Does CentOS 7 put X on tty1? If so, I bet it still reserves tty1 for that
even 
when at run level 3.

>The journalctl output from brltty.service tells me that brltty is
reporting: 
>control[console] error 5: Input/output error.

Please add brltty logging options in your service unit so that we can find
out 
what the problem is from "the horse's mouth".

>Is this a funky permissions issue with system not allowing console access
for 
>some reason? 

I doubt it, but who knows. I hate guessing, and much prefer just facts.

-- 
Dave Mielke           | 2213 Fox Crescent | The Bible is the very Word of
God.
Phone: 1-613-726-0014 | Ottawa, Ontario   | http://Mielke.cc/bible/
EMail: Dave at Mielke.cc | Canada  K2A 1H7   | http://FamilyRadio.org/
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY at brltty.com
For general information, go to: http://brltty.com/mailman/listinfo/brltty