public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Samuel Thibault <sthibault@debian.org>
To: Didier Spaier <didier@slint.fr>
Cc: debian-accessibility@lists.debian.org, speakup@linux-speakup.org
Subject: Re: Debian Buster installer and speech issues
Date: Wed, 24 Apr 2019 10:35:46 +0200	[thread overview]
Message-ID: <20190424083546.uoyxd3wcxx3dn7re@function> (raw)
In-Reply-To: <c0d52d19-1119-383a-3774-d1261c3681ee@slint.fr>

Didier Spaier, le mer. 24 avril 2019 12:20:08 +0200, a ecrit:
> On 23/04/2019 23:40, Didier Spaier wrote:
> > On bare metal, no luck: the installer could not detect
> > my sound card, so no  speech in the installer.
> > 
> > It made 9 unsuccessful attempts, told it would tried
> > other cards, seemed to gave up.

What do you mean by "told it would tried other cards"? What _exactly_
did it write? Otherwise I'm not sure what exactly you refer to, that's
how a way for me to be able to debug anything.

> > I have only one sound card.
> > 
> > That's weird as I have no issue with Slint's installer,
> > also using espeakup.
> 
> My assumption is that' there is an issue with S38espeakup.
> 
> If I understand well, you modified it to wait that
> /sys/class/sound/card*/id be populated.

Yes, because as commented there it seems that the Buster audio drivers
take _ages_ to initialize...

> I thought, maybe there's an issue with this modification.

Possibly, but I need precise information to be able to guess what is
going wrong. Please really post what is asked on 

https://wiki.debian.org/accessibility#Debian_installer_accessibility

from *within the installer* because that is what the script uses. The
alsa-info output from an installed system can be useful, but much less
than the precise information of what is _actually_ happening.

> PS FYI I attach the script used for card detection in the
> current Slint installer. Obviously it is a modification of
> S38espeakup (but a former version).

And it'll just fail the same way as Buster in case Slint happens to meet
the same driver initialization time.

Samuel

  reply	other threads:[~ UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Samuel Thibault
 ` Jude DaShiell
   ` Samuel Thibault
     ` Didier Spaier
 ` Didier Spaier
   ` Jude DaShiell
   ` Samuel Thibault
     ` Didier Spaier
       ` Samuel Thibault
   ` Didier Spaier
     ` Samuel Thibault [this message]
       ` Jude DaShiell
         ` Didier Spaier
           ` Jude DaShiell
       ` Didier Spaier
         ` Samuel Thibault
           ` Didier Spaier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190424083546.uoyxd3wcxx3dn7re@function \
    --to=sthibault@debian.org \
    --cc=debian-accessibility@lists.debian.org \
    --cc=didier@slint.fr \
    --cc=speakup@linux-speakup.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).