[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation



John, 

Missing from this is the information that:

The mini.iso that Samuel provided did not produce sound, unfortunately, I could not access Internet with this iso as I needed firmware to do so.

Samuel said that he had the files he needed, and that ALSA might be working on a fix. 

As I understand it, I need to install files from the Internet to have a working system that is capable of furnishing logs. I'm willing to try again, but I have no Ethernet where I live, we have collective WiFi in this location and the WiFi needs firmware.

Best wishes,

David


On Sun, Jan 16, 2022, 01:24 john doe <johndoe65534@mail.com> wrote:
Please read this e-mail to the bottom, in particular, Samuel's answer.


On 1/16/2022 6:56 AM, D.J.J. Ring, Jr. wrote:
> I'm just trying to make sure I notify everyone that should know about this,
> John.
> Thanks for all of your efforts.
>
> I've also joined the GRUB bug mailing list because now GRUB it seems is
> inserting a UEFI boot entry into my BIOS entry, forcing my computer to
> always boot into the last used operating system.
>
> This requires me to open up the computer case and push the reset button on
> the motherboard.
>
> I've been given instructions on how to change this by a friend but the
> instructions are so complicated, that I cannot figure them out.
>
> The same friend told me that this is what GRUB does now, but it's terribly
> inconvenient, especially for visually impaired users, both by having to
> open up the computer case but also changing the BIOS settings to what they
> were set to do the computer will boot from USB (or CD/DVD).  It doesn't
> make sense to me that GRUB would override a user's BIOS settings.
>
> If there's anything I can do to help, let me know.
>
> Samuel said ALSA may have fixed the problem but I tried the latest daily
> firmware CD and I still don't get screen reader.
>
> I just don't understand how Buster could work so well but Bullseye not work
> at all.
>
> Best wishes to all and thanks for your combined efforts,
>
> David
>
> On Sat, Jan 15, 2022, 04:11 john doe <johndoe65534@mail.com> wrote:
>
>> On 1/8/2022 9:50 PM, Samuel Thibault wrote:
>>> Hello,
>>>
>>> D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:47:17 -0500, a ecrit:
>>>> Here's the files from the Buster installation from /var/log/installer -
>>>> attached.
>>>
>>> Ok, thanks!
>>>
>>> So the "ALC888: SKU not ready 0x00000100" message was already there at
>>> the time. What's new in bullseye is
>>>
>>> snd_hda_intel 0000:00:03.0: couldn't bind with audio component
>>> snd_hda_intel 0000:00:03.0: HSW/BDW HD-audio HDMI/DP requires binding
>> with gfx driver
>>>
>>> I remember having troubles with hda intel and the i915 graphic driver
>>> missing. Could you try this image which includes the i915 driver:
>>>
>>> https://people.debian.org/~sthibault/tmp/mini.iso
>>>
>>> (again all the logs are useful to provide since we don't know precisely
>>> what we want to look at)
>>>
>>
>> Just FYI (1).
>>
>> 1)  https://lists.debian.org/debian-user/2022/01/msg00429.html
>>
>> --
>> John Doe
>>
>>
>


--
John Doe


Reply to: