Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread D.J.J. Ring, Jr.
On Tue, Jan 4, 2022, 01:09 Philip Hands wrote: > "D.J.J. Ring, Jr." writes: > > > 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 Bul

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread Philip Hands
"D.J.J. Ring, Jr." writes: > 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 > o

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread D.J.J. Ring, Jr.
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 f

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread Samuel Thibault
D.J.J. Ring, Jr., le lun. 03 janv. 2022 20:26:54 -0500, a ecrit: > You mean take a video of the screen when I am trying to install Bullseye? Yes. > I don't get any error messages at all, it just doesn't speak to me. At some point you mentioned some errors: “the errors precede writing to disk.”

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread D.J.J. Ring, Jr.
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 On Mon, Jan 3, 2022 at 7:03 PM Samuel Thibault wrote: > I'd like to emphasize this: > > john doe, le lun. 03 janv. 2022 09:39:4

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

2022-01-03 Thread Samuel Thibault
One thing possibly worth noting is this: Jan 3 12:58:44 kernel: [1.769085] snd_hda_codec_realtek hdaudioC1D0: ALC888: SKU not ready 0x0100 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

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

2022-01-03 Thread Samuel Thibault
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

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread Samuel Thibault
I'd like to emphasize this: john doe, le lun. 03 janv. 2022 09:39:41 +0100, a ecrit: > - As far as I understand it, everything is working fine on Buster but > not on Bullseye, tarring the logs from a Buster installation and from > Bullseye might give us some clues on where this is failing. Yes, p

Re: realtek usb wifi

2022-01-03 Thread Andrew M.A. Cater
On Wed, Dec 29, 2021 at 03:41:28AM +, oppdalloen wrote: > Hello i thought i could try asking if you guys have knowledge about the about > usb wifi driver, i've tried to locate evrywhere and no luck > below is the usb wifi information > > Bus 002 Device 002: ID 0bda:b812 Realtek Semiconductor

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread D.J.J. Ring, Jr.
No, John, it doesn't. The errors are being made prior to installation. I previously used something to copy these logs to a pastebin while I was installing, this was done somewhere around the time of package selection because networking was running. There was some screen where I could get these

Re: installation-guide: secure boot vs. boothole

2022-01-03 Thread Steve McIntyre
Hi Holger! Happy New Year! On Sun, Dec 26, 2021 at 02:50:32PM +0100, Holger Wansing wrote: > >on the german l10n mailinglist a topic came up regarding the 'secure boot' >chapter in the installation-guide: >https://d-i.debian.org/manual/en.amd64/ch03s06.html#secure-boot > > >It was stated, that the

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread john doe
On 1/3/2022 9:59 AM, D.J.J. Ring, Jr. wrote: John Doe, Someone told me of a method of saving log files from the installer before it writes to the hard drive it's going to install to. The error occurs prior to writing to any partition. If these errors are kept in system RAM until the partitions

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread D.J.J. Ring, Jr.
John Doe, Someone told me of a method of saving log files from the installer before it writes to the hard drive it's going to install to. The error occurs prior to writing to any partition. If these errors are kept in system RAM until the partitions are formatted and then written to that partiti

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread john doe
On 1/3/2022 9:06 AM, D.J.J. Ring, Jr. wrote: On Mon, Jan 3, 2022, 02:09 john doe wrote: On 1/3/2022 12:18 AM, D.J.J. Ring, Jr. wrote: On Sun, Jan 2, 2022 at 8:25 AM john doe wrote: On 1/2/2022 1:56 PM, D.J.J. Ring, Jr. wrote: On Sun, Jan 2, 2022, 03:59 Holger Wansing wrote: Hi, Am 2

Re: Bug#1002976: installation-reports: Installer Fault Accessibility No Screen Reader Heard

2022-01-03 Thread D.J.J. Ring, Jr.
On Mon, Jan 3, 2022, 02:09 john doe wrote: > On 1/3/2022 12:18 AM, D.J.J. Ring, Jr. wrote: > > On Sun, Jan 2, 2022 at 8:25 AM john doe wrote: > > > >> On 1/2/2022 1:56 PM, D.J.J. Ring, Jr. wrote: > >>> On Sun, Jan 2, 2022, 03:59 Holger Wansing > wrote: > >>> > Hi, > > Am 2. Janua