Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
D.J.J. Ring, Jr., le mar. 18 janv. 2022 03:28:07 -0500, a ecrit: > 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. Ah right. You can check what you ended up selecting with cat /var/run/espeakup.card Samuel
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
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 On Tue, Jan 18, 2022, 03:21 Samuel Thibault wrote: > D.J.J. Ring, Jr., le lun. 17 janv. 2022 22:01:59 -0500, a ecrit: > > 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. > > Ah, yes, sure. > > > 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] > > And that didn't make espeakup start speaking? > > Samuel >
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
D.J.J. Ring, Jr., le lun. 17 janv. 2022 22:01:59 -0500, a ecrit: > 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. Ah, yes, sure. > 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] And that didn't make espeakup start speaking? Samuel
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
On Mon, Jan 17, 2022 at 4:55 AM Samuel Thibault wrote: > Hello, > > Thanks for the information. > > D.J.J. Ring, Jr., le dim. 16 janv. 2022 22:12:29 -0500, a ecrit: > > I already noticed something, in Buster, my digital card isn't listed > > with the cat /proc/asound/cards command. > > 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. > > > ## Output of amixer -c 0 scontents and amixer -c 1 scontents for the > Bullseys > > mini_amixer1contents > > > > > > ## Output of amixer -c 0 scontents amixer -c 1 scontents and amixer -c 1 > > 10.11.0_amixer1contents > > 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 > Hello 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
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
Hello, Thanks for the information. D.J.J. Ring, Jr., le dim. 16 janv. 2022 22:12:29 -0500, a ecrit: > I already noticed something, in Buster, my digital card isn't listed > with the cat /proc/asound/cards command. 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. > ## Output of amixer -c 0 scontents and amixer -c 1 scontents for the Bullseys > mini_amixer1contents > > > ## Output of amixer -c 0 scontents amixer -c 1 scontents and amixer -c 1 > 10.11.0_amixer1contents 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
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
On 1/17/2022 1:13 AM, D.J.J. Ring, Jr. wrote: Here's the message, i didn't include the bug address. I'm new 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. -- John Doe
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
D.J.J. Ring, Jr., le dim. 16 janv. 2022 19:13:18 -0500, a ecrit: > Here's the message, i didn't include the bug address. 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
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
Hello, D.J.J. Ring, Jr., le dim. 16 janv. 2022 00:56:17 -0500, a ecrit: > I'm just trying to make sure I notify everyone that should know about this, > John. The way to do this is to keep 1002...@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: > > D.J.J. Ring, Jr., le sam. 08 janv. 2022 21:33:12 -0500, a ecrit: > > I tried console 2 but nothing is there. The soundcard detection just goes > > in a > > loop, over and over asking me to select a soundcard but no sound. > > That's on purpose. As I wrote previously, proceed to the language > question, and then you'll have the busybox shell available on console 2. 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
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
D.J.J. Ring, Jr., le sam. 08 janv. 2022 21:04:13 -0500, a ecrit: > I don't know how to mount a CD stick with busy box. It's just exactly the same as with bash. Samuel
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
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 On Sat, Jan 8, 2022 at 8:53 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le sam. 08 janv. 2022 20:38:43 -0500, a ecrit: > > First, the mini.iso tried over and over to detect my soundcard, > > over and over, what do you mean? Was it failing to emit any sound at > all? > > > then it went to ask if I had a USB stick with Debian on it, > > didn't it first ask for the language? > > Did you try to press alt-f2 to get to the second console? > > Samuel >
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
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 On Sat, Jan 8, 2022 at 5:22 PM Samuel Thibault wrote: > D.J.J. Ring, Jr., le sam. 08 janv. 2022 16:34:09 -0500, a ecrit: > > This is in bash, not busy box, right? I can't figure out busybox! > > busybox is mostly like bash. > > > At what time do I mount a USB stick, > > The main menu will be fine. > > > and where is the command to save installer logs to it? > > The syslog is already in /var/log/syslog > > Samuel >
Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
D.J.J. Ring, Jr., le sam. 08 janv. 2022 20:38:43 -0500, a ecrit: > First, the mini.iso tried over and over to detect my soundcard, over and over, what do you mean? Was it failing to emit any sound at all? > then it went to ask if I had a USB stick with Debian on it, didn't it first ask for the language? Did you try to press alt-f2 to get to the second console? Samuel
Re: Bug#1002976: installation-reports: Installer Does Not Provide Screen Reader in Accessible Installation
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 0x0100" message was already there at the time. What's new in bullseye is snd_hda_intel :00:03.0: couldn't bind with audio component snd_hda_intel :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
