[quoted lines by Keith Wessel on 2017/03/02 at 22:33 -0600] >With the screen driver logging patch in place, the error I now get looks >like this: > >Mar 02 22:28:23 brltty[982]: console control error 5: fd=10 vt=1 op=0X5603: >Input/output error > >Does that help at all?
Yes, very much so. Starting in brltty 5, the event loop (which is no longer a loop) is interrupt driven. In your case, brltty is starting so early that the Linux screen driver isn't able to find anything to grab onto in order to monitor for changes to the screen. This is nothing that a simple scheduled retry can't fix, so I'll definitely be looking into it. It's just an unanticiapated situation. As I recall, though, you were having a second problem, as well, which had something to do with braille display communication. Would you mind to please describe it again, and is your braille display connected via serial or USB? -- 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: d...@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@brltty.com For general information, go to: http://brltty.com/mailman/listinfo/brltty