Did you do: sysctl enable espeakup.service -- Jude <jdashiel at panix dot com> "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." Ed Howdershelt 1940. On Tue, 19 Mar 2024, Martin McCormick wrote: > I put debian bookworm on a Raspberry Pi 2b Rev 1 and it is > trying to start but can't seem to find it's way. > > Here are syslog lines from the attempt to start with the time > stamps removed but everything else present: > > rpi1 systemd[1]: Starting espeakup.service - Software speech output for Speakup... > rpi1 systemd[1]: espeakup.service: Control process exited, code=exited, status=2/INVALIDARGUMENT > rpi1 systemd[1]: espeakup.service: Failed with result 'exit-code'. > rpi1 systemd[1]: Failed to start espeakup.service - Software speech output for Speakup. > rpi1 systemd[1]: espeakup.service: Scheduled restart job, restart counter is at 5. > rpi1 systemd[1]: Stopped espeakup.service - Software speech output for Speakup. > rpi1 systemd[1]: espeakup.service: Start request repeated too quickly. > rpi1 systemd[1]: espeakup.service: Failed with result 'exit-code'. > rpi1 systemd[1]: Failed to start espeakup.service - Software speech output for Speakup. > > I know, for sure, that the sound interface which is a > playback-only device works fine. I have used aplay to send .wav > files to it and they are heard loud and clear. > > The installation of speakup was done on the raspberry pi > by the following actions: > > apt-get -y install espeakup speakup-tools speakup-doc > and, based on a message from those installations: > apt-get -y install speechd-up > > Is there something I can look at that shows what invalid > argument was sent which is probably what is killing the whole > startup procedure? > > I also wonder if I need pulseaudio running since libpulse > was one of the libraries downloaded when I gave the apt install > commands. > > I think I may have missed some step or something because > it certainly does try to start and amixer shows the sound > interface on. > > I will be using this older Raspberry Pi as a talking > terminal for command-line work since I do have an image based on > debian 8 or jessie from around 2017 that actually does talk with > speakup but can't be used any more because such things as ssh > keys and other security features aren't compatible with todays > ssh world. > > I did look at espeak.conf and see that espeak keeps a log > in /var/log but there is no espeak or anything with the word > speak in that file tree so it appears to have never gotten that > far. > > I asked this question on a raspberry Pi list and got a > number of helpful answers but so far, I am not sure how to trace > what is happening that shouldn't be happening. > > Thanks for all constructive solutions since I don't think this is > too far gone but obviously needs some adjustment. > > amartin > >
