I investigated this further. The problem is that while building the
Dracut image, it's looking for keytab and other data files under
/etc/brltty, whereas in the Arch Linux package, they're located under
/usr/share/brltty. The directory is hard-coded in the shell script.
Here are the error messages for reference.
-> Building initrd image linux (6.7.1-arch1-1)
brltty-lsinc: cannot open file: /etc/brltty/Input/al/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/bm/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/bn/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/cn/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/dp/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/eu/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/fs/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hd/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hm/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/ht/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/hw/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/ic/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/mt/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/pg/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/pm/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/sk/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/vo/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/md/*.ktb: No such file
or directory
brltty-lsinc: cannot open file: /etc/brltty/Input/mm/*.ktb: No such file
or directory
-> Ukify image linux (6.7.1-arch1-1)
On 26/1/24 08:29, Jason J.G. White wrote:
Dear BRLTTY community,
I recently switched to using a Unified Kernel Image to boot my laptop.
I'm using Dracut to generate the image, following guidance on the Arch
Linux wiki. During image generation, errors are reported regarding
BRLTTY-related devices not being found.
I can capture the error messages if this is not a known issue.
After the system boots to a graphical login manager, BRLTTY is running
but it reports "no key bindings" on the display. The work-around is to
restart BRLTTY by shutting down the braille display and then
re-enablig it.
Has anyone been here before, and is there a known solution?
The unified kenrel image is executed directly by the UEFI firmware, so
there is no boot loader anymore.
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
_______________________________________________
This message was sent via the BRLTTY mailing list.
To post a message, send an e-mail to: BRLTTY@brltty.app
For general information, go to: http://brltty.app/mailman/listinfo/brltty
