On Mon, Feb 27, 2017 at 04:55:37PM -0500, Dave Mielke wrote:
> [quoted lines by Adrian van Bloois on 2017/02/27 at 22:46 +0100]
>
> Brltty isn't seeing your Alva. When you log with -lusb, you'll see lines like
> this one (taken from your log):
>
>USB: testing device: vendor=1D6B product=0003
[quoted lines by Adrian van Bloois on 2017/02/27 at 22:46 +0100]
Brltty isn't seeing your Alva. When you log with -lusb, you'll see lines like
this one (taken from your log):
USB: testing device: vendor=1D6B product=0003
For an Alva BC680, the vendor ID is 0798 and the product ID is 0680. Pe
On Mon, Feb 27, 2017 at 04:30:33PM -0500, Dave Mielke wrote:
> [quoted lines by Adrian van Bloois on 2017/02/27 at 21:50 +0100]
>
> >What flags should I put in the-ldebug???
>
> For this kind of problem, -ldebug should be good enough. You could, though,
> always add usb just in case it gets furt
[quoted lines by Adrian van Bloois on 2017/02/27 at 21:58 +0100]
Are you perhaps specifying the drivers directory in your brltty.conf file? If
so, maybe it isn't correct.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God.
Phone: 1-613-726-0014 | Ottawa, Ontario
[quoted lines by Adrian van Bloois on 2017/02/27 at 21:50 +0100]
>What flags should I put in the-ldebug???
For this kind of problem, -ldebug should be good enough. You could, though,
always add usb just in case it gets further.
--
Dave Mielke | 2213 Fox Crescent | The Bible is the ve
On Mon, Feb 27, 2017 at 03:45:33PM -0500, Dave Mielke wrote:
> [quoted lines by Adrian van Bloois on 2017/02/27 at 21:37 +0100]
>
> It looks right, but maybe there's somethign subtle that I, too, am not
> spotting. Is there any reason that you're over-configuring? Have you tried
> just
> --pref
On Mon, Feb 27, 2017 at 03:45:33PM -0500, Dave Mielke wrote:
> [quoted lines by Adrian van Bloois on 2017/02/27 at 21:37 +0100]
>
> It looks right, but maybe there's somethign subtle that I, too, am not
> spotting. Is there any reason that you're over-configuring? Have you tried
> just
> --pref
[quoted lines by Adrian van Bloois on 2017/02/27 at 21:37 +0100]
It looks right, but maybe there's somethign subtle that I, too, am not
spotting. Is there any reason that you're over-configuring? Have you tried just
--prefix=/usr/local?
A debug log would confirm wehre brltty is looking for its
Hi Dave,
I've got everything placed in the right directories, the librltty???.so
files are all in /usr/local/lib64/brltty as configured.
But brltty is still unable to find the al braille-driver.
When set to auto it sees that the al driver is needen, but not able to
find it.
I configured the whole t
