I do have all your rules, but I don't think udev is starting brltty, not sure why -- maybe because of that modprobe failing -- not sure which module it is looking for.
Sorry for my immediately previous message, did not see this one first. On Sun, 21 Feb 2021 22:35:18 -0500, Dave Mielke wrote: > > [quoted lines by John Covici on 2021/02/21 at 15:58 -0500] > > >Also, looking at the only service unit, it says RefuseManualStart=true > >so I seem to have no way to just say systemctl start brltty > > Okay, I understand your question, now. If you really want to just start brltty > then start the brltty.path unit. > > Just starting brltty, these days, isn't necessarily the right thing to do. > This > is because udev also starts brltty. If you don't have brltty's udev rules then > just starting brltty is okay. If, however, you do have them then you should > configure the general brltty to not look for USB devices. An easy way to do > this would be to have this line in brltty.conf: > > braille-device bluetooth: > > By the way: It's often handy to check the description within a systemd unit > file. The brltty.path unit contains this line: > > Description=Default BRLTTY Instance > > -- > I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ > Dave Mielke | 2213 Fox Crescent | WebHome: http://Mielke.cc/ > EMail: [email protected] | Ottawa, Ontario | Twitter: @Dave_Mielke > Phone: +1 613 726 0014 | Canada K2A 1H7 | > -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici wb2una [email protected] _______________________________________________ This message was sent via the BRLTTY mailing list. To post a message, send an e-mail to: [email protected] For general information, go to: http://brltty.app/mailman/listinfo/brltty
