[BRLTTY] brltty and voyager 44 USB-HUB

[Dietmar Segbert]

Hello Dave,
now i have created a debug file with the command:
brltty -b vo -l7 -e 2>/tmp/brltty.log

The voyager 44 ist connected to a usb 2.0 hub with power-adapter

The log ist:

BRLTTY 4.2 [http://mielke.cc/brltty/]
brltty: Working Directory: /root
brltty: Writable Directory: /lib/brltty/rw
brltty: Configuration File: /etc/brltty.conf
brltty: Data Directory: /etc/brltty
brltty: Library Directory: /lib/brltty
brltty: Tables Directory: /etc/brltty
brltty: file opened: /etc/brltty/de.ttb fd=3
brltty: including data file: /etc/brltty/de.ttb
brltty: file opened: /etc/brltty/letters-latin.tti fd=5
brltty: including data file: /etc/brltty/letters-latin.tti
brltty: file opened: /etc/brltty/control-latin.tti fd=5
brltty: including data file: /etc/brltty/control-latin.tti
brltty: file opened: /etc/brltty/numbers-dot6.tti fd=5
brltty: including data file: /etc/brltty/numbers-dot6.tti
brltty: file opened: /etc/brltty/common.tti fd=5
brltty: including data file: /etc/brltty/common.tti
brltty: file opened: /etc/brltty/spaces.tti fd=6
brltty: including data file: /etc/brltty/spaces.tti
brltty: file opened: /etc/brltty/boxes.tti fd=6
brltty: including data file: /etc/brltty/boxes.tti
brltty: Text Table: de
brltty: Attributes Table: attributes
brltty: Contraction Table: none
brltty: Key Table: none
brltty: Keyboard Property: type=
brltty: Keyboard Property: vendor=
brltty: Keyboard Property: product=
brltty: checking for screen driver: lx
brltty: initializing screen driver: lx
brltty: device directory: /dev
brltty: checking screen device: /dev/vcsa
brltty: screen device: vcsa
brltty: checking console device: /dev/tty0
brltty: console device: tty0
brltty: device opened: /dev/vcsa: fd=3
brltty: screen opened: vcsa: fd=3
brltty: device opened: /dev/tty0: fd=5
brltty: console opened: tty0: fd=5
brltty: Screen Font Map Size: 303
brltty: VGA Character Count: 256(small)
brltty: attributes masks: font=0000 unshifted=FF00 shifted=0000
brltty: Screen Driver: lx [Linux]
brltty: Linux Screen Driver:
brltty: Screen Parameter: charset=
brltty: Screen Parameter: hfb=
brltty: Screen Parameter: debugsfm=
brltty: BrlAPI Server: release 0.5.5
brltty: API Parameter: auth=
brltty: API Parameter: host=
brltty: API Parameter: stacksize=
brltty: linking local socket lock: Die Datei existiert bereits
brltty: socket 0 established (fd 6)
brltty: socket 1 established (fd 7)
brltty: exit status: 0
brltty: Console opened: fd=8
brltty: regions: text=0.0 status=0.0
brltty: shifts: full=1 half=0 vertical=5
brltty: checking braille device: usb:
brltty: checking for braille driver: vo
brltty: unsupported parameter: InputMode=yes
brltty: unsupported parameter: StatusCells=5
brltty: initializing braille driver: vo -> usb:
brltty: verifying file system path: usbfs: /dev/bus/usb
brltty: USBFS Root: /dev/bus/usb
brltty: USB: testing: vendor=1D6B product=0001
brltty: USB: testing: vendor=1D6B product=0001
brltty: USB: testing: vendor=1D6B product=0001
brltty: USB: testing: vendor=1D6B product=0001
brltty: USB: testing: vendor=0798 product=0001
brltty: USB: no serial operations: vendor=0798 product=0001
brltty: USB: ept=81 dir=in xfr=int pkt=8 ivl=10ms
brltty: USB Language: 409
brltty: USB: Manufacturer Name: F.J. Tieman BV
brltty: USB: Product Description: Braille Voyager
brltty: USB: Serial Number: 01AB92D707000050
brltty: Voyager Cell Count: 44
brltty: Voyager Serial Number: 01AB92D707000050
brltty: Voyager Hardware: 196.0
brltty: Voyager Firmware: $Revision: 1.12 $$Date: 2002/06/13 07:57:31 $$Author: cvs $
brltty: Braille Display Dimensions: 1 row, 44 columns
brltty: regions: text=0.44 status=0.0
brltty: shifts: full=44 half=22 vertical=5
brltty: Key Bindings: all
brltty: file opened: /etc/brltty/brl-vo-all.ktb fd=10
brltty: including data file: /etc/brltty/brl-vo-all.ktb
brltty: Key Table: /etc/brltty/brl-vo-all.ktb
brltty: api link
brltty: Braille Driver: vo [Voyager]
brltty: Voyager Braille Driver: version 0.3 (June 2009)
brltty: Braille Device: usb:
brltty: Preferences File: /etc/brltty-vo.prefs
brltty: cannot open file: /etc/brltty-vo.prefs: Datei oder Verzeichnis nicht gefunden
brltty: regions: text=0.40 status=41.3
brltty: shifts: full=40 half=20 vertical=5
brltty: Setting voltage: 80
brltty: Setting voltage: 80
brltty: beeper enabled
brltty: tone: msec=60 note=64
brltty: tone: msec=100 note=69
brltty: api unlink
brltty: USB URB status error 32: Daten├╝bergabe unterbrochen (broken pipe).
brltty: USB URB status error 32: Daten├╝bergabe unterbrochen (broken pipe).


Regards

Dietmar

> dave at mielke.cc schrieb am 13.01.12:

> [quoted lines by Dietmar Segbert on 2012/01/08 at 21:35 +0100]

>> I have done the following:
>> deleting /var/log/messages
>> deleted /var/log/syslog
>> unplug the voyager 44
>> plug in the voyager 44 in a usb-hub (usb 2.0) with poweradapter
>> pressing the keys of the voyager 44
>>
>> looking vor messages and syslog, but there are no new entrys in
>> the files.

> Removing those files was the wrong thing to do. Your system is
> probably still continuing to write to those now deleted files. This
> is okay because a file isn't actually deleted from the disk until
> it's been closed by all applications using it, but it means that
> you can no longer access it.

> This problem may self-correct because many distributions these days
> open new versions of these files each week or so. I think, though,
> that the best thing to do to make sure your system is back to
> normal is to reboot it.

>> Can i make debug-file of brltty?

> I was actually wanting to know what your system log is reporting,
> but, yes, you could also send us a log from brltty itself. To do
> this, please add two options when rtunning brltty. The first is
> -ldebug and the second is -L/path/to/logfile (the -L here is
> uppercase).

> --
> Dave Mielke           | 2213 Fox Crescent | The Bible is the very
> Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario   | 2011 May
> 21 is the End of Salvation. EMail: dave at mielke.cc | Canada  K2A 1H7
>   | http://Mielke.cc/now.html http://FamilyRadio.com/
>     | http://Mielke.cc/bible/ _____________________________________
> __________ This message was sent via the BRLTTY mailing list.
> To post a message, send an e-mail to: BRLTTY at mielke.cc
> For general information, go to: http://mielke.cc/mailman/listinfo/b
> rltty