Hi,

Am 2. Januar 2022 02:40:16 MEZ schrieb "David J. Ring, Jr." <n1ea@arrl.net>:
As I already wrote:
my best guess for this one would be
https://www.debian.org/releases/stable/debian-installer/#errata


Holger

Holger,

So is this fixed? Does the daily our weekly installer with firmware allow
speech to be heard during installation?

Thank you,
David

Hi,

"D.J.J. Ring, Jr." <n1ea@arrl.net> wrote (Sun, 2 Jan 2022 07:56:46 -0500):

Please read the above mentioned site!

There is a link to "the umbrella bug report", which tracks the current status
of this issue.

I'd like to emphasize this:

john doe, le lun. 03 janv. 2022 09:39:41 +0100, a ecrit:

Yes, please do this, that should be extremely informative.

Any error message from the kernel will be visible in there.

Possibly there are some error messages from alsa itself, which may not
be there. Possibly you could use a smartphone to make a recording of the
screen while you are booting the bullseye installer, so we can see which
error messages you get there?

Samuel

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

Boot method: USB
Image version: firmware-testing-amd64-DVD-1_20220104.iso
Date: <Date and time of the install>

Machine: Intense-PC2-BRW (IPC2) serial: 1191205-03032
Partitions: <df -Tl will do; the raw partition table is preferred>


Base System Installation Checklist:
[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it

Initial boot:           [ ]
Detect network card:    [ ]
Configure network:      [ ]
Detect media:           [ ]
Load installer modules: [ ]
Clock/timezone setup:   [ ]
User/password setup:    [ ]
Detect hard drives:     [ ]
Partition hard drives:  [ ]
Install base system:    [ ]
Install tasks:          [ ]
Install boot loader:    [ ]
Overall install:        [ ]

Comments/Problems:

<Description of the install, in prose, and any thoughts, comments
      and ideas you had during the initial install.>


Please make sure that any installation logs that you think would
be useful are attached to this report. Please compress large
files using gzip.

Hello,

David J. Ring, Jr., le lun. 03 janv. 2022 14:18:39 -0500, a ecrit:
[-- Attachement #2: installer.tar.gz --]
[-- Type: application/gzip, Encoding: base64, Size: 6,4M --]

Could you do the same with a Buster installer, so we can spot the
differences?

Samuel

One thing possibly worth noting is this:

Jan  3 12:58:44 kernel: [    1.769085] snd_hda_codec_realtek hdaudioC1D0: ALC888: SKU not ready 0x00000100
Jan  3 12:58:44 kernel: [    1.769627] snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC888: line_outs=4 (0x14/0x16/0x15/0x17/0x0) type:line
Jan  3 12:58:44 kernel: [    1.769631] snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Jan  3 12:58:44 kernel: [    1.769633] snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Jan  3 12:58:44 kernel: [    1.769634] snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Jan  3 12:58:44 kernel: [    1.769636] snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x1e/0x0
Jan  3 12:58:44 kernel: [    1.769637] snd_hda_codec_realtek hdaudioC1D0:    inputs:
Jan  3 12:58:44 kernel: [    1.769638] snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
Jan  3 12:58:44 kernel: [    1.769640] snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
Jan  3 12:58:44 kernel: [    1.769641] snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
Jan  3 12:58:44 kernel: [    1.769642] snd_hda_codec_realtek hdaudioC1D0:      CD=0x1c

I don't know what this really means, though.

Samuel

Samuel,

You mean take a video of the screen when I am trying to install Bullseye?

I don't get any error messages at all, it just doesn't speak to me.

Regards,

David

D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:26:54 -0500, a ecrit:

Yes.

At some point you mentioned some errors:

“the errors precede writing to disk.”

Samuel

Yes Samuel, I just installed Debian Buster.  Everything just worked, even
got the right sound card!

Same hardware, nothing has changed. I tried to do the advanced install, the
instructions I had weren't accurate, but I did get to the Advanced menu and
was able to make a web server and save the files to another computer on my
network.

Here's the files from the Buster installation from /var/log/installer -
attached.

Also the files from the web server.
I compressed the files and put them inside buster_logs.tar.gz so you
wouldn't get them confused.

Best wishes to all,

David

Yes, I said that, but I am under the impression that whatever went wrong
happened before partitions were mounted.

I remembered using that advance menu configuration which I was unable to
find in Bullseye  - at least the same exact thing with the ability of
obtaining an IP address and downloading files.  I thought these files were
lost if the logs weren't sent to a web server or written during
installation to a mounted hard drive.

No errors are ever seen or heard - except that there is no sound after the
installer probes for sound card (press enter if this is your sound card,
etc.).

I'm going to install Bullseye once again because right now I have Buster -
but the sound is working in Buster and the screen readers orca and console
are both working. and sound from videos in the browser are all working.
Now if I can only get this in Bullseye.

Is there anything I can run while I have this installed?  I'm going to wait
for your response, it's past midnight on the Continent and 2000 hours here
on the east coast USA.  Also any suggestion of what to install thjat might
be more helpful?  Maybe the daily SID installer?

Best wishes,
David

Thanks, Phil.

I tried the daily Sid unstable and it also has no working sound screen
reader during but once finished it's there.

I'll believe you about the files because I cannot find an advanced menu
that installs the screen reader like Buster.had. Buster is much easier to
install.

I'm going to try another installer tomorrow.

David

Hello,

As already mentioned, please do this:

install with the Buster image, and use reportbug to send the
installation information, just like you did with Bullseye on Mon, 3 Jan
2022 14:18:39 -0500.

Really, do please do that.

Samuel

I have already done that, did it not go through? I did receive a message
saying that the message I sent because it didn't mention a package would be
disregarded.
It would have been sent from n1ea@arrll.net - any way of checking further?
Darn it,  I should have BCC it to you, Samuel.

Thanks,

David

Hello,

D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:47:17 -0500, a ecrit:

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)

Samuel

Hello,

D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:47:17 -0500, a ecrit:

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)

Samuel

Is there anything else I can do to help solve this problem?

I just tried the last daily iso with firmware with no luck.

Also I've discussed the problem with GRUB inserting an entry in the EFI
boot automatically which overrides user setting in BIOS.  That means if I
last booted into Debian I will go directly to Debian without having the
ability to press F2 (or whatever key is needed to access BIOS settings)..
I mentioned that this caused a problem on a multi system boot, especially
for those of us who cannot see well, but  also for everyone because the
only way to change this is either to open up the computer or laptop and
reset the BIOS by pressing a rubber domed switch which I suppose grounds
the capacitor is there to  holds a voltage on the computer CMOS to keep
settings, pushing the little switch puts the voltage to zero and restore
the factory settings.

There is a problem and I'm trying to get someone to fix it.   It's probably
an unfortunate consequence of this "feature" - GRUB would work just right
without this feature, and I cannot think of any reason that this "feature"
exists. It appears to be a bug.  It's certainly understandable to those who
who must  now take extraordinary measures to reset their BIOS by resetting
the CMOS. For blind persons who have already obtained sighted help to et up
their BIOS the way they want it, to boot from USB HD - a USB stick, it's
totally unwanted and very inconvenient. I have no idea if GRUB is aware of
this bug.

I believe even if GRUB is intended to do this, it shouldn't, it seems to be
be an unfortunate consequence of their work.   Even if it can be
overridden, it is much too complicated for the average computer user.
(Some kind member of this list sent me instructions to override this new
behavior of GRUB, but they are extremely complicated. If anything this
"feature" should be enabled only as an option.  I've just subscribed to
GRUB bugs list to tell them of this, hopefully it can be fixed because it
overrides the user's BIOS settings.

Best wishes to all,
David

Just FYI (1).

1)  https://lists.debian.org/debian-user/2022/01/msg00429.html

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

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

The gall here is to provide the missing sound drivers in the installer,
making internet irrelevent!

So the bottom line is that, the 'mini.iso' provided by Samuel is still
not working.
If this is the case, please do:
- Install Debian with the iso that Samuel has provided
- After installation tar up '/var/log/installer' (see below)
- Attached that tarball to your next reply

No -- the log that we need will always be available.

It is media dependent if Debian is installed the logs are placed in
'/var/log/installer' (this is all documented in one of your threads or
online).

Please note that we are testing the sound card here and internet is not
required at all as d-i can install without a network connection.

How do I send the logs when if I send them the list will send me a
rejection notice?

Thanks

David

I do not know as I do not have that msg infront of me.
When you need help providing the errors you are getting is the only way
for us to help you.

No, luck.

First, the mini.iso tried over and over to detect my soundcard, I currently
have 3, first one is usually digital, next is PCH analog, I use that, and I
had my USB camera plugged in.  It kept repeating in a loop for 5 minutes,
then I finally chose soundcard #1 then it went to ask if I had a USB stick
with Debian on it, so I just pressed enter, thinking it was talking about
the mini.iso.  It went around and around for a good 10 minutes before I had
decided it wasn't going to work.

So again, no luck with the mini.iso.

Best wishes,
David

D.J.J. Ring, Jr., le sam. 08 janv. 2022 20:38:43 -0500, a ecrit:

over and over, what do you mean? Was it failing to emit any sound at
all?

didn't it first ask for the language?

Did you try to press alt-f2 to get to the second console?

Samuel

It might have asked for the language, but I had no sound.  I know I didn't
get as far as networking, but I probably got as far as language and
keyboard, I've done installs so much recently I just didn't notice.

I'll try it again, I thought it was too soon to have logs. Usually when I
go to the other console, I just have busybox and I don't know how to mount
a CD stick with busy box.

I'll try it again.

David

D.J.J. Ring, Jr., le sam. 08 janv. 2022 21:04:13 -0500, a ecrit:

It's just exactly the same as with bash.

Samuel

Hello,

D.J.J. Ring, Jr., le dim. 16 janv. 2022 00:56:17 -0500, a ecrit:

The way to do this is to keep 1002976@bugs.debian.org in the Cc of your
mails. Otherwise the information you are providing is scattered in
various mails in various mailing lists, there is no way we can fix the
bug if the needed information has to be collected tediously. Creating
yet another thread on yet another mailing list cannot help fixing the
issue.

So, as already wrote:

Samuel wrote:

So please proceed to the language question, then switch to console 2,
and there mount a vfat-formatted USB stick and copy /var/log/syslog onto
it. For instance:

mkdir /usb
mount /dev/sda1 /usb
cp /var/log/syslog /usb/
umount /usb

Possibly it's not sda1 but sda, or sda2, or sdb, or sdb1, or sdb2,
depending how your disk and USB stick get detected. You can for instance
use

cat /proc/partitions

to see how big the disks are, and thus identify which one is the USB
stick.

Samuel

D.J.J. Ring, Jr., le ven. 14 janv. 2022 07:08:15 -0500, a ecrit:

Unless we manage to find out exactly what is happening, the bug won't
solve itself magically.

That being said, the daily build now has the newer upstream alsa-lib
version 1.2.6.1, possibly that could include a fix.

Samuel

D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:55:16 -0500, a ecrit:

Yes, but that error should have been vocalized already. There is no need
to have the network to get speech output.

Samuel

Sorry, Samuel, you misunderstand me.

You gave me a mini.iso to try but when I booted from it, it gave me an
error that firmware for my WiFi was needed. I do not have access to
Ethernet, our housing has WiFi supplied to us only.

So I could not test your mini.iso.

Is there a way I can put the needed wifi firmware into the iso, or somehow
be able to try your iso?

Best wishes,

David

D.J.J. Ring, Jr., le ven. 14 janv. 2022 08:55:16 -0500, a ecrit:

Just to make sure, when was this error precisely? Before or after the
installer language question?

Samuel

Here's the message, i didn't include the bug address.

I'm new

David


I'll try it again John, if this goes through, I must have done something
wrong before.

If it doesn't go through, I'll send the files to you and Samuel Thibault by
direct email.

Here are the files - for some reason, I couldn't mount the second USB stick
so I futzed around with it a few times, rebooted, rebooted again, then I
read up on how to put a firmware folder on a USB stick in /firmware folder
and the last time, I could mount the second USB stick and save the files.
So who knows maybe firmware was needed to mount the USB stick.  I don't
care, I got the job done.

Here goes!

David

D.J.J. Ring, Jr., le dim. 16 janv. 2022 19:13:18 -0500, a ecrit:

Thanks, that helps a lot to record all information in the bug.

So the syslog says that the binding with i915 went fine. But you said
you didn't have sound, so that's not the problem. The next thing I can
think of is dumping the output of these commands on a USB stick:

cat /proc/asound/cards
amixer -c 0 scontents
amixer -c 1 scontents

and doing so both when booting from the buster ISO image (so we can see
how it looks like when things work), and when booting from the bullseye
ISO image (so we can see how it looks like when things don't work).

Samuel

The mini iso just gave me an error that firmware was missing for my wifi -
I found the instructions on how to load firmware and put it in a FAT
partition on USB stick in a directory named /firmware.  No more error.

Thanks you.

David

Samuel,

It was just an error that I needed firmware for my WiFi.  I put
firmware-iwlwifi_20210818-1_all.deb in a FAT formatted USB stick in
/firmware and everything was happy.

Thanks,
David

Samuel,

Here is the information that you asked for.  I already noticed something,
in Buster, my digital card isn't listed with the cat /proc/asound/cards
command.

The attached files that say mini are from the mini.iso you provided of
Bullseye.

## Output of cat /proc/asound/cards command
mini_cards
firmware-10.11.0-amd-netinst_cards

## syslog of Bullseye mini iso and syslog
of firmware-10.11.0-amd-netinst.iso
syslog_mini
syslog_10.11.0

## Output of amixer -c 0 scontents and amixer -c 1 scontents for the
Bullseys mini.iso
mini_amixer0contents
mini_amixer1contents


## Output of amixer -c 0 scontents  amixer -c 1 scontents and amixer -c 1
scontents for the Buster 10.11.0 iso
10.11.0_amixer0contents  (There was no 0 card detected in Buster 10.11.0,
so the file is blank.)
10.11.0_amixer1contents
10.11.0_amixer2contents

I hope I did OK on this.

Thanks again for your help.

BRGDS,
David

We've all been there!!! :)

Please understand that it is as frustrated for you as it is for us.

P.S.

Apologies for the crossposting, from now on I will only send to this bug
report.

D.J.J. Ring, Jr., le dim. 16 janv. 2022 21:44:55 -0500, a ecrit:

That was not the question. Please *exactly* answer the question I am asking:

*When* was this error precisely? Before or after the installer language
question?

That's the information I need, if you don't provide it we'll be unused
what works and what doesn't work, and won't be able to fix the bug.

Samuel

Hello,

Thanks for the information.

D.J.J. Ring, Jr., le dim. 16 janv. 2022 22:12:29 -0500, a ecrit:

Yes, that's because in the bullseye case you have used the mini.iso. As
I wrote, please rather use the netinst bullseye iso image. The mini.iso
image was only to check whether the presence of the i915 driver would
help.

One thing I notice is this:

Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]

It's off in the Buster case and on in the Bullseye case. I guess you are
not using the IEC958 output.

Could you try running this inside the bullseye installer:

amixer -c 0 sset IEC958,0 off

samuel

I'm trying to be very careful to do whatever you tell me, but I will
probably make a mistake, but not on purpose, just because I misunderstood.

Here's what I did.

Using firmware-10.11.0-amd64 installer, I gave this command:

amixer -c 0 set IEC958,0 off

I didn't get a response because my sound cards were renumbered.

So I changed the command to:
amixer -c 1 set IEC958,0 off

This is the response I received.

Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]

About the firmware error, it's right after language selection saying that
some of my hardware requires firmware and that I should insert a disk with
firmware on it.   That looks normal to me.

While my computer has a digital sound output, I don't use it, I use the
small speaker 3.5mm TRS (tip, ring, sleeve) plug like music players use to
go to an amplified speaker.

Regards,
David

I just tried the mini iso again, the error about firmware was about the
installer language question, it then asked me if I had a disk with firmware
and if so to install it.

This looks normal to me.

I have since learned hot to download all the firmware and put it on my usb
stick in a folder named 'firmware", when I do this, the mini.iso is able to
see my wifi card and asks me the network ID number and password for my wifi
and it will connect.

Best regards,
David

D.J.J. Ring, Jr., le lun. 17 janv. 2022 22:01:59 -0500, a ecrit:

Ah, yes, sure.

And that didn't make espeakup start speaking?

Samuel

No, because the installer still might be selecting the wrong sound card,
it's usually the second choice, so even without sound I press enter to at
least choose something.

How can I chose the sound card, I'll chose them one by one and try.

David

D.J.J. Ring, Jr., le mar. 18 janv. 2022 03:28:07 -0500, a ecrit:

Ah right. You can check what you ended up selecting with

cat /var/run/espeakup.card

Samuel