The one thing I can think of is that you probably
once started brltty not with the init.d script but
directly. If you just run "brltty" to start brltty, it
will not create the /var/run/brltty.pid file, and
"/etc/init.d/brltty start" will not recognize that brltty
is already running. Aldo, could this be the problem?
If so, we should probably look at some kind of device locking
mechanism for brltty, so that it doesnt murder itself if
started twice. I know the effect as well, what happens
is that two daemons are accessing the same device, and producing garbage...
BRLTTY should really not disable itself.