<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Dave,</p>
<p><br>
</p>
<p>I tryed with you wrote, but not worked unfortunatelly.</p>
<p>In syslog I see now following error message, translate to english
for you in Ubuntu 20.04, BRLTTY 6.5:</p>
<p>Dec 22 14:01:56 hammera-pc brltty[1410]: unable to connect to
polkit: g-io-error-quark (159) Error initializing authority: Could
not connect: No such file or directory (1)</p>
<p>What file missing for BRLTTY and polkit related? When I used the
my Alva display with USB connection, I not see similar error
messages.</p>
<p>Another interesting error messages:</p>
<p>Dec 22 14:01:59 hammera-pc brltty[3886]: can't isolate namespaces</p>
<p>Dec 22 14:01:59 hammera-pc brltty[3886]: required capability not
granted: cap_sys_admin (for injecting input characters typed on a
braille device)<br>
Dec 22 14:01:59 hammera-pc brltty[3886]: required capability not
granted: cap_sys_tty_config (for playing alert tunes via the
built-in PC speaker)<br>
Dec 22 14:01:59 hammera-pc brltty[3886]: required capability not
granted: cap_mknod (for creating needed but missing special device
files)<br>
Dec 22 14:01:59 hammera-pc dbus-daemon[3210]: [session uid=1000
pid=3210] Activating via systemd: service name='org.a11y.Bus'
unit='at-spi-dbus-bus.service' requested by ':1.154' (uid=1000
pid=3887 comm="/bin/brltty -b ba -s no -x a2 -N "
label="unconfined")<br>
Dec 22 14:01:59 hammera-pc at-spi-bus-launcher[3901]:
dbus-daemon[3901]: Activating service
name='org.a11y.atspi.Registry' requested by ':1.0' (uid=1000
pid=3887 comm="/bin/brltty -b ba -s no -x a2 -N "
label="unconfined")<br>
Dec 22 14:01:59 hammera-pc brltty[3887]: Screen Driver: a2
[AtSpi2]<br>
Dec 22 14:01:59 hammera-pc brltty[3887]: Braille Driver: ba
[BrlAPI] Version:0.1, 2005<br>
Dec 22 14:01:59 hammera-pc brltty[3887]: Speech Driver: no
[NoSpeech]<br>
</p>
<p>Dec 22 14:01:59 hammera-pc brltty[3887]: ioctl[KDMKTONE] error 1:
Operation not permitted</p>
<p><br>
</p>
<p>Me not have other ydea. USB to serial adapter connection is Ok,
/dev/ttyACM0 device correct existing, the /etc/brltty.conf file
correct setted fs driver parameter and the serial device line.</p>
<p>My Asus B550 motherboard based the tech specs supports one serial
port connector, but not have back panel connector connected the
motherboard.</p>
<p>Perhaps me need trying buying a 9 pin serial connector cable to
the motherboard connector if not have better ydea.</p>
<p>General 9 pin serial to serial cable an another machine the
display works correct the /dev/ttyS0 device, so the display is not
bad and the serial port in the display is not bad.</p>
<p>Unfortunatelly the display USB port with usb cable is unusable
the BRLTTY 6.5 and higher version, because shows following error
message the log file:</p>
<p> [brltty] USB URB status error 75: The value is too large for the
specified data type<br>
<a class="moz-txt-link-abbreviated moz-txt-link-freetext"
href="mailto:2024-03-31@14:28:26.852">2024-03-31@14:28:26.852</a>
[brltty] USB: endpoint descriptor not found: 00<br>
<br>
</p>
<p>Attila<br>
2024. 12. 21. 20:55 keltezéssel, Dave Mielke írta:</p>
<blockquote type="cite"
cite="mid:Z2cdTH2nGvkKG4U4@beta.private.mielke.cc">
<pre class="moz-quote-pre" wrap="">[quoted lines by Hammer Attila on 2024/12/21 at 15:49 +0100]
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">so I buied a Genbird USB to serial 9 pin cable.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
That should work.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Both Ubuntu 20.04 and Debian 12 are correct detected my usb to serial cable,
and created correct the /dev/ttyACM0 device.
In /etc/brltty.conf file I set braille driver related config key, and added
following line into the config file:
braille-device serial:ttyACM0 # First serial device.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
Yes, that's correct.
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Because the display shows only the focus 70 related status message and not
the actual braille output, I restarted BRLTTY with sudo brltty -d
/dev/ttyACM0 and -D fs command,
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
-D (uppercase D) is the wrong option. It tells brltty where to find the drivers, and I think that's what your problem is. To tell brltty which braille driver to use, please specify the -b (lowercase b) option.
</pre>
</blockquote>
</body>
</html>