Hi Sêrgio, I probably resolved the problem too:
On Thu, Nov 15, 2007 at 06:51:26PM -0000, Sérgio Neves wrote: > Is your braille display connected by usb? Yes it is. > I had this problem one or two months ago with a focus braille display > (connected by usb), and I think when ubuntu starts, it renames brltty.conf > to brltty.conf.orig and replaces the brltty.conf you made with a version > that is copied from a place I don't know. That's correct. But until know I still wasn't able to understand which blrtty.conf template(/defaults) it copies from /mmm/??? to /etc > To solve this problem, I edited the /etc/init.d/brltty and I commented the > lines that say to rename brltty.conf to brltty.conf.orig and copy the > brltty.conf form a place I don't know to /etc. I first tried to add "-t de" to the apropriate Alva line in /etc/udev/rules.d/85-brltty.rules but it doesn't worked: each time I rebooted I heard twice the blip blip, and saw that the first brltty startup was correct, then after the 2nd blip it returns again in us text-table. So I simply renamed now /etc/udev/rules.d/85-brltty.rules to /etc/udev/rules.d/.saf.85-brltty.rules and I finally added by hand "text-table de" to /etc/brltty.conf (where the brltty.sh script was only providing the driver and device raws) Now I hear 1 time blip and I see no "1 startup problem"; and I immediately see that the text-table is the good one. Also if I do now ps ax |grep brltty I see the brltty process once: 4169 ? ssl 0:00 /sbin/brltty -P /var/run/brltty.pid > After this step, it may happen that brltty no longer starts up > automatically. > To solve this, I edited the file that controls the usb startup of brltty and > I think it's on /udev/rules.. And when it appears one path for brltty > executable, I replace this path with /bin/brltty. > Maybe you don't need to do this second step, depending on whether brltty > starts up automatically or not. I will tell you if it refuses to start-up, but I hope it won't; it seems to work. > Sorry for not being much rigorous, but I don't remember very well this > second step because I didn't discover it alone and I don't have yet the > knowledge enough to understand the startup process. > After that, you can change brltty.conf and it will never be overwritten when > you restart ubuntu. That was the goal, impeaching the renaming and overriding of /etc/brltty.conf > I hope this helps. It seems it does, it inspires me; hope my "hack" is quite okay. Aldo. _______________________________________________ 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://mielke.cc/mailman/listinfo/brltty
