Re: Skipping disk erase on Debian text-based installation (fwd)

[Nick Gawronski]

Hi, I think that some type of message should be written in the installer 
that is used with speech telling the user that if you don't need to wipe 
the disk like if it is already encrypted then you can press control and 
c to abort the process so that the message is clear and so that it is 
known to the user that they don't have to wait until the entire wiping 
process is completed if they don't want to.  Nick Gawronski


On 5/2/2022 7:39 AM, Holger Wansing wrote:


Am 2. Mai 2022 13:58:54 MESZ schrieb Samuel Thibault :

Holger Wansing, le lun. 02 mai 2022 13:52:36 +0200, a ecrit:

Nick is right, if you perform an install with speech output, there is no
interactive possibility to cancel the full disk wipe action in the text
frontend used for speech!
In the newt frontend or graphical installer there is the Cancel button,
but not in the text frontend, sadly.

That was fixed in cdebconf 0.261, one can just press control-C.

Uups.
Yes, I used an outdated image for testing, my bad...


Holger

Re: Skipping disk erase on Debian text-based installation (fwd)

[Nick Gawronski]

Hi, I am totally blind and use the s option at boot to start the 
installer with speech output.  If I wish to add this kernel command line 
option yet still run the installation using software speech output would 
pressing s then tab and then entering in the command line switches then 
pressing enter work as control and c does not do the canceling operation 
like it should and I had to wait until the entire disk was wiped?  Nick 
Gawronski


On 5/1/2022 5:54 AM, Philip Hands wrote:

Nick Gawronski  writes:


Hi, I had to reinstall debian and like to encrypt my installations.
Regardless of what installation image I use I find that no choice exists
to not do the complete wiping of the disk before the LVM manager is
setup.  I get that it will be possible to press control and c to stop
the process but having an option like a choice in the last step asking
if you wish to do this complete wipe would be better.  If the system was
already encrypted and all you were doing was doing a reinstallation then
going threw that process again to     me is pointless.  Is this
something that could possibly be looked at for a future release? Nick
Gawronski

If you're doing an interactive install, the expectation is that you
cancel it if you don't want to wait for it, since that seems the way to
ensure that people that don't know what they're doing still get a safe
result.

It's been possible to override this via preseeding (since 2017[1]),
either in a preseed.cfg, thus:

   d-i partman-auto-crypto/erase_disks boolean false

or on the kernel command line:

   partman-auto-crypto/erase_disks=false

which you could do in an otherwise interactive install, if that's what
you wanted.

For more such preseeding hints, check out the example preseed.cfg:

   https://d-i.debian.org/manual/example-preseed.txt

which is linked to from here:

   https://d-i.debian.org/manual/en.amd64/apbs02.html

HTH

Cheers, Phil.

[1]  https://bugs.debian.org/476388

Re: Skipping disk erase on Debian text-based installation (fwd)

[Nick Gawronski]

Hi, I had to reinstall debian and like to encrypt my installations.  
Regardless of what installation image I use I find that no choice exists 
to not do the complete wiping of the disk before the LVM manager is 
setup.  I get that it will be possible to press control and c to stop 
the process but having an option like a choice in the last step asking 
if you wish to do this complete wipe would be better.  If the system was 
already encrypted and all you were doing was doing a reinstallation then 
going threw that process again to     me is pointless.  Is this 
something that could possibly be looked at for a future release? Nick 
Gawronski


On 11/17/2021 3:34 PM, Samuel Thibault wrote:

john doe, le mer. 17 nov. 2021 21:58:00 +0100, a ecrit:

Unless I'm missing something, one could preseed this question as kernel
boot parameter:

# When disk encryption is enabled, skip wiping the partitions beforehand.
#d-i partman-auto-crypto/erase_disks boolean false

Yes, but that's way easier to just interrupt the step than finding out
how to preseed a parameter

Samuel

Re: not loading non-free firmware in 11.00 network installation debian-installer

[Nick Gawronski]

Hi, Here is the syslog file from the working installed system. Possibly 
someone can look at it and find out what is different and why the newer 
installers are not loading the needed firmware. Nick Gawronski


On 9/25/2021 2:40 PM, Holger Wansing wrote:

Hi,

Nick Gawronski  wrote (Sat, 25 Sep 2021 12:47:25 -0500):

Hi, I just tried this same process with the debian non-free DVD and
educational versions with the same results.  My system was installed
with an earlier version of debian-installer so where can I locate the
installation report on my system as sending this to you might help?

That's under /var/log/installer/

Holger



syslog.xz
Description: Binary data

Re: not loading non-free firmware in 11.00 network installation debian-installer

[Nick Gawronski]

Hi, I just tried this same process with the debian non-free DVD and 
educational versions with the same results.  My system was installed 
with an earlier version of debian-installer so where can I locate the 
installation report on my system as sending this to you might help?  
Nick Gawronski


On 9/15/2021 1:43 PM, Holger Wansing wrote:

Hi,

"Andrew M.A. Cater"  wrote (Wed, 15 Sep 2021 17:25:52 
+):

On Wed, Sep 15, 2021 at 11:47:29AM -0500, Nick Gawronski wrote:


Feb 25 15:44:03 cdrom-detect: Detected CD 'Debian GNU/Linux 11.0.0 "Bullseye" - 
Unofficial amd64 NETINST with firmware 20210814-10:09'
Feb 25 15:44:04 cdrom-detect: Detected CD with 'stable' (bullseye) distribution

This is the official Debian media installer

Try the unofficial non-free CD : from the lines I've selected, it looks as
if you might be able to install via wired interface without loading firmware.

The lines you quoted above show, that Nick already used the unofficial image
with firmware included.

I guess this lines are related:


Feb 25 15:44:42 kernel: [   87.777956] iwlwifi :02:00.0: firmware: failed 
to load iwlwifi-6000g2b-6.ucode (-2)
Feb 25 15:44:42 kernel: [   87.777957] firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Feb 25 15:44:42 kernel: [   87.777958] iwlwifi :02:00.0: Direct firmware 
load for iwlwifi-6000g2b-6.ucode failed with error -2
Feb 25 15:44:42 kernel: [   87.777969] iwlwifi :02:00.0: firmware: failed 
to load iwlwifi-6000g2b-5.ucode (-2)
Feb 25 15:44:42 kernel: [   87.777970] iwlwifi :02:00.0: Direct firmware 
load for iwlwifi-6000g2b-5.ucode failed with error -2
Feb 25 15:44:42 kernel: [   87.777971] iwlwifi :02:00.0: minimum version 
required: iwlwifi-6000g2b-5
Feb 25 15:44:42 kernel: [   87.777972] iwlwifi :02:00.0: maximum version 
supported: iwlwifi-6000g2b-6

However, I have no clue what happens here...
The iwlwifi-6000g2b-6.ucode file is included in firmware-iwlwifi package, so
should also be available on the image in question.


Holger

Re: not loading non-free firmware in 11.00 network installation debian-installer

[Nick Gawronski]

Hi, Yes as I looked and it appears as if the firmware package is on the 
network installation image.  This system has debian already installed on 
it is there a way I could send you the installation report from this 
system so you could take a look at it like where is it stored on the 
system?  Nick Gawronski


On 9/15/2021 1:43 PM, Holger Wansing wrote:

Hi,

"Andrew M.A. Cater"  wrote (Wed, 15 Sep 2021 17:25:52 
+):

On Wed, Sep 15, 2021 at 11:47:29AM -0500, Nick Gawronski wrote:


Feb 25 15:44:03 cdrom-detect: Detected CD 'Debian GNU/Linux 11.0.0 "Bullseye" - 
Unofficial amd64 NETINST with firmware 20210814-10:09'
Feb 25 15:44:04 cdrom-detect: Detected CD with 'stable' (bullseye) distribution

This is the official Debian media installer

Try the unofficial non-free CD : from the lines I've selected, it looks as
if you might be able to install via wired interface without loading firmware.

The lines you quoted above show, that Nick already used the unofficial image
with firmware included.

I guess this lines are related:


Feb 25 15:44:42 kernel: [   87.777956] iwlwifi :02:00.0: firmware: failed 
to load iwlwifi-6000g2b-6.ucode (-2)
Feb 25 15:44:42 kernel: [   87.777957] firmware_class: See 
https://wiki.debian.org/Firmware for information about missing firmware
Feb 25 15:44:42 kernel: [   87.777958] iwlwifi :02:00.0: Direct firmware 
load for iwlwifi-6000g2b-6.ucode failed with error -2
Feb 25 15:44:42 kernel: [   87.777969] iwlwifi :02:00.0: firmware: failed 
to load iwlwifi-6000g2b-5.ucode (-2)
Feb 25 15:44:42 kernel: [   87.777970] iwlwifi :02:00.0: Direct firmware 
load for iwlwifi-6000g2b-5.ucode failed with error -2
Feb 25 15:44:42 kernel: [   87.777971] iwlwifi :02:00.0: minimum version 
required: iwlwifi-6000g2b-5
Feb 25 15:44:42 kernel: [   87.777972] iwlwifi :02:00.0: maximum version 
supported: iwlwifi-6000g2b-6

However, I have no clue what happens here...
The iwlwifi-6000g2b-6.ucode file is included in firmware-iwlwifi package, so
should also be available on the image in question.


Holger

not loading non-free firmware in 11.00 network installation debian-installer

[Nick Gawronski]

Hi, I was going to see if the network installation image would work 
successfully to reinstall debian 11.00 with non-free firmware needed for 
my network cards.  When I ran the installer at low priority so everything 
would work as expected and so I would have full control of the 
installation when it got to the firmware loading it fails to load the 
firmware for any of my network cards when before on this same system in 
earlier versions of debian it worked just fine.  Attached is the syslog 
from the installer.  Can someone please tell me what is going on with this 
installation image?  Nick GawronskiFeb 25 15:43:19 syslogd started: BusyBox v1.30.1
Feb 25 15:43:19 kernel: klogd started: BusyBox v1.30.1 (Debian 1:1.30.1-6+b3)
Feb 25 15:43:19 kernel: [0.00] Linux version 5.10.0-8-amd64 
(debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, GNU 
ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.46-3 (2021-07-28)
Feb 25 15:43:19 kernel: [0.00] Command line: 
BOOT_IMAGE=/install.amd/vmlinuz vga=788 initrd=/install.amd/gtk/initrd.gz 
speakup.synth=soft --- quiet 
Feb 25 15:43:19 kernel: [0.00] Disabled fast string operations
Feb 25 15:43:19 kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x001: 
'x87 floating point registers'
Feb 25 15:43:19 kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x002: 
'SSE registers'
Feb 25 15:43:19 kernel: [0.00] x86/fpu: Supporting XSAVE feature 0x004: 
'AVX registers'
Feb 25 15:43:19 kernel: [0.00] x86/fpu: xstate_offset[2]:  576, 
xstate_sizes[2]:  256
Feb 25 15:43:19 kernel: [0.00] x86/fpu: Enabled xstate features 0x7, 
context size is 832 bytes, using 'standard' format.
Feb 25 15:43:19 kernel: [0.00] BIOS-provided physical RAM map:
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x-0x0009d7ff] usable
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x0009d800-0x0009] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x000e-0x000f] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x0010-0x9abeefff] usable
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x9abef000-0x9aeeefff] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x9aeef000-0x9af9efff] ACPI NVS
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x9af9f000-0x9affefff] ACPI data
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x9afff000-0x9aff] usable
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x9b00-0x9f9f] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xf800-0xfbff] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xfec0-0xfec00fff] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xfed08000-0xfed08fff] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xfed1-0xfed19fff] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xfed1c000-0xfed1] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xfee0-0xfee00fff] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0xffd8-0x] reserved
Feb 25 15:43:19 kernel: [0.00] BIOS-e820: [mem 
0x0001-0x00025fdf] usable
Feb 25 15:43:19 kernel: [0.00] NX (Execute Disable) protection: active
Feb 25 15:43:19 kernel: [0.00] SMBIOS 2.6 present.
Feb 25 15:43:19 kernel: [0.00] DMI: SAMSUNG ELECTRONICS CO., LTD. 
700Z3A/700Z4A/700Z5A/700Z5B/700Z3A/700Z4A/700Z5A/700Z5B, BIOS 10FD 11/21/2011
Feb 25 15:43:19 kernel: [0.00] tsc: Fast TSC calibration using PIT
Feb 25 15:43:19 kernel: [0.00] tsc: Detected 2194.756 MHz processor
Feb 25 15:43:19 kernel: [0.000871] e820: update [mem 0x-0x0fff] 
usable ==> reserved
Feb 25 15:43:19 kernel: [0.000874] e820: remove [mem 0x000a-0x000f] 
usable
Feb 25 15:43:19 kernel: [0.000882] last_pfn = 0x25fe00 max_arch_pfn = 
0x4
Feb 25 15:43:19 kernel: [0.000887] MTRR default type: uncachable
Feb 25 15:43:19 kernel: [0.000888] MTRR fixed ranges enabled:
Feb 25 15:43:19 kernel: [0.000890]   0-9 write-back
Feb 25 15:43:19 kernel: [0.000891]   A-B uncachable
Feb 25 15:43:19 kernel: [0.000892]   C-F write-protect
Feb 25 15:43:19 kernel: [0.000893] MTRR variable ranges enabled:
Feb 25 15:43:19 kernel: [0.000895]   0 base 0FFC0 mask FFFC0 
write-protect
Feb 25 15:43:19 kernel: [0.000896]   1 base 0 mask F8000 
write-back
Feb 25 15:43:19 kernel: [0.000897]   2 base 08000 mask FE000 
write-back
Feb 25 15:43:19 kernel: [0.000898]   3 base 09C00 mask 

Bug#986491: Acknowledgement (fails to fully configure with debconf low priority)

[Nick Gawronski]

My main reason for running installs at low priority both at the main 
debian-installer screen and wanting to do so after the base system is 
installed is so I can have a fully configured system and not have to go 
back and reconfigure everything after the installation is finished.  If 
the debconf priority of the installation would be transfered over to the 
installed system when the base system was being installed then I could 
have an installation where I was asked about all configuration questions 
the first time the system was fully installed and when it came up at the 
end of the installation everything would be ready to go. My question is 
why is the debconf priority not carried over from the debian-installer 
to the installed system after the base system is installed as if a user 
chose expert mode or just low priority I would have thought this would 
have been the case?


On 4/6/2021 5:03 PM, Debian Bug Tracking System wrote:

Thank you for filing a new Bug report with Debian.

You can follow progress on this Bug here: 986491: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986491.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

As you requested using X-Debbugs-CC, your message was also forwarded to
   n...@nickgawronski.com
(after having been given a Bug report number, if it did not have one).

Your message has been sent to the package maintainer(s):
  Debian Install System Team 

If you wish to submit further information on this problem, please
send it to 986...@bugs.debian.org.

Please do not send mail to ow...@bugs.debian.org unless you wish
to report a problem with the Bug-tracking system.

Bug#986491: fails to fully configure with debconf low priority

[Nick Gawronski]

Package: debian-installer
Severity: important
Tags: d-i a11y
X-Debbugs-Cc: n...@nickgawronski.com



-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 5.10.0-5-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

issue with configuring a debian installation with debconf set to low priority both at the beginning and after the base system is installed

[Nick Gawronski]

Hi, I had written about this to mailing lists several years ago but 
never got the proper bug number as I think the bug was reported.  I 
often like to run the installation at low priority so I can configure 
everything correctly at the start of the installation process and so 
that when the system reboots into the newly installed system things are 
all setup and ready to go. After the base system is installed I then 
exicute a shell and chroot into /target and run dpkg-reconfigure adduser 
to tell it not to have system readable home directories.  If I then do 
dpkg-reconfigure debconf still in the chroot and set it to low priority 
the installation continues up until it gets to the pam profiles 
selection screen.  No matter what I select here even when everything is 
selected the system tells me that no pam profiles are enabled for the 
system and would grant all users access with authenticating which is not 
allowed.  I can not preceed past this screen as even trying to go to 
another shell and change the priority back to medium will not work as I 
am still stuck at that screen when I return to the console.  I also 
think that if a user sets the priority to low in the installation 
process that at least for the installation even in the target the 
priority remain at that setting and if a user wants to change it back to 
medium they could do this after the installation.  How would I be able 
to submit further information on how to get the proper information to 
someone so it could be looked into and get fixed?  Nick Gawronski

Re: instructions for building the non-free debian installation images with the latest gtk network installation for testing the latest espeakup changes

[Nick Gawronski]

Hi, I have uncommented that setting and so if I were interested in 
building the latest CD image with non-free firmware and having this 
image after about 4 seconds automatically launch the talking installer 
what files would I change?  I am also interested in after the installer 
starts having it automatically set debconf priority to low and put me at 
the main menu is this possible? Nick Gawronski


On 4/4/2021 5:11 PM, Daniel Leidert wrote:

Am Sonntag, dem 04.04.2021 um 16:19 -0500 schrieb Nick Gawronski:

[..]

What would I need to do to build using
debian-cd the non-free network installer or include custom packages on
it?

Not sure if that already helps you, but you can use the FORCE_FIRMWARE
environment variable. Check out all the variables in /usr/share/debian-
cd/CONF.sh.

Personally I use simple-cdd to build custom installer CDs.

Regards, Daniel

instructions for building the non-free debian installation images with the latest gtk network installation for testing the latest espeakup changes

[Nick Gawronski]

Hi, I was testing out the latest network gtk debian-installer build 
target and was wondering as searching the wiki does not provide any 
directions on how to build the non-free installer image for systems that 
require it.  I was wanting to test out the latest espeakup changes on a 
real system but wanted to build the non-free version and the 
debian-accessibility list told me that they did not know how to use 
debian-cd to build the non-free images.  The wiki pages are very old in 
some places talking about etch and don't really apply to the latest 
version of the debian-installer.  What would I need to do to build using 
debian-cd the non-free network installer or include custom packages on 
it?  Nick Gawronski

Re: software speech works with vmware player 16 but not after installation of Debian testing

[Nick Gawronski]

Hi, Here is that file.  Nick Gawronski

# To choose the default voice of the espeakup daemon, define VOICE here.
# See /usr/lib/*/espeak-data/lang/ for a list of possible voices.

VOICE=en

# To choose audio output on another sound card, uncomment this and set as
# appropriate (either a card number or a card name as seen in CARD= alsa
# output).
#
ALSA_CARD="AudioPCI"

On 3/17/2021 7:43 PM, Samuel Thibault wrote:

Nick Gawronski, le mer. 17 mars 2021 19:34:24 -0500, a ecrit:

Hi, Here is that output.  Nick Gawronski

Ok, it doesn't seem muted...

What does

   cat /etc/default/espeakup

have to say?

Samuel

Re: software speech works with vmware player 16 but not after installation of Debian testing

[Nick Gawronski]

Hi, Here is that output.  Nick Gawronski

Script started on 2021-03-17 19:32:18-05:00 [TERM="xterm-256color" 
TTY="/dev/pts/0" COLUMNS="120" LINES="30"]

[?2004hroot@debian641:~# amixer -c 0 scontents
[?2004l
Simple mixer control 'Master',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Mono:
  Front Left: Playback 49 [78%] [-21.00dB] [on]
  Front Right: Playback 49 [78%] [-21.00dB] [on]
Simple mixer control 'PCM',0
  Capabilities: pvolume pswitch pswitch-joined
  Playback channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Mono:
  Front Left: Playback 23 [37%] [0.00dB] [on]
  Front Right: Playback 23 [37%] [0.00dB] [on]
Simple mixer control 'Line',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]
Simple mixer control 'CD',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]
Simple mixer control 'Mic',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [on]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [on]
Simple mixer control 'Mic Boost (+20dB)',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'Video',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]
Simple mixer control 'Phone',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]
Simple mixer control 'IEC958',0
  Capabilities: pswitch pswitch-joined
  Playback channels: Mono
  Mono: Playback [off]
Simple mixer control 'Aux',0
  Capabilities: pvolume pswitch pswitch-joined cswitch cswitch-exclusive
  Capture exclusive group: 0
  Playback channels: Front Left - Front Right
  Capture channels: Front Left - Front Right
  Limits: Playback 0 - 63
  Front Left: Playback 0 [0%] [-34.50dB] [off] Capture [off]
  Front Right: Playback 0 [0%] [-34.50dB] [off] Capture [off]
Simple mixer control 'Capture',0
  Capabilities: cvolume cswitch cswitch-joined
  Capture channels: Front Left - Front Right
  Limits: Capture 0 - 15
  Front Left: Capture 8 [53%] [12.00dB] [on]
  Front Right: Capture 8 [53%] [12.00dB] [on]
Simple mixer control 'Mix',0
  Capabilities: cswitch cswitch-exclusive
  Capture exclusive group: 0
  Capture channels: Front Left - Front Right
  Front Left: Capture [off]
  Front Right: Capture [off]
Simple mixer control 'Mix Mono',0
  Capabilities: cswitch cswitch-exclusive
  Capture exclusive group: 0
  Capture channels: Front Left - Front Right
  Front Left: Capture [off]
  Front Right: Capture [off]
[?2004hroot@debian641:~# [?2004l

exit

Script done on 2021-03-17 19:32:47-05:00 [COMMAND_EXIT_CODE="0"]

On 3/17/2021 4:14 PM, Samuel Thibault wrote:

Hello,

Nick Gawronski, le mar. 16 mars 2021 21:32:51 -0500, a ecrit:

[?2004hroot@debian641:~# amixer -c 0 contents

Could you pass scontents rather than contents?

Samuel

Re: software speech works with vmware player 16 but not after installation of Debian testing

[Nick Gawronski]

Hi, Here is all of those commands that had output the first sound card 
as I only had one in the virtual machine.  Based on this what can you 
tell about this virtual machine as I am able to ssh into it?  Nick Gawronski


Script started on 2021-03-16 21:26:28-05:00 [TERM="xterm-256color" 
TTY="/dev/pts/1" COLUMNS="120" LINES="30"]
[?2004hroot@debian641:~# amixer -c 0 
controlscontrols

[?2004l
Simple mixer control 'Master',0
Simple mixer control 'PCM',0
Simple mixer control 'Line',0
Simple mixer control 'CD',0
Simple mixer control 'Mic',0
Simple mixer control 'Mic Boost (+20dB)',0
Simple mixer control 'Video',0
Simple mixer control 'Phone',0
Simple mixer control 'IEC958',0
Simple mixer control 'Aux',0
Simple mixer control 'Capture',0
Simple mixer control 'Mix',0
Simple mixer control 'Mix Mono',0
[?2004hroot@debian641:~# amixer -c 0 contents
[?2004l
numid=1,iface=MIXER,name='Master Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on
numid=2,iface=MIXER,name='Master Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=49,49
  | dBscale-min=-94.50dB,step=1.50dB,mute=0
numid=16,iface=MIXER,name='PCM Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on
numid=17,iface=MIXER,name='PCM Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=23,23
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=8,iface=MIXER,name='Line Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=9,iface=MIXER,name='Line Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=0,0
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=10,iface=MIXER,name='CD Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=11,iface=MIXER,name='CD Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=0,0
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=7,iface=MIXER,name='Mic Boost (+20dB)'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=5,iface=MIXER,name='Mic Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=6,iface=MIXER,name='Mic Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=0,0
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=3,iface=MIXER,name='Phone Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=4,iface=MIXER,name='Phone Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=0,0
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=12,iface=MIXER,name='Video Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=13,iface=MIXER,name='Video Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=0,0
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=14,iface=MIXER,name='Aux Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=15,iface=MIXER,name='Aux Playback Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=63,step=0
  : values=0,0
  | dBscale-min=-34.50dB,step=1.50dB,mute=0
numid=18,iface=MIXER,name='Capture Source'
  ; type=ENUMERATED,access=rw--,values=2,items=8
  ; Item #0 'Mic'
  ; Item #1 'CD'
  ; Item #2 'Video'
  ; Item #3 'Aux'
  ; Item #4 'Line'
  ; Item #5 'Mix'
  ; Item #6 'Mix Mono'
  ; Item #7 'Phone'
  : values=0,0
numid=19,iface=MIXER,name='Capture Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=on
numid=20,iface=MIXER,name='Capture Volume'
  ; type=INTEGER,access=rw---R--,values=2,min=0,max=15,step=0
  : values=8,8
  | dBscale-min=0.00dB,step=1.50dB,mute=0
numid=21,iface=MIXER,name='IEC958 Playback Con Mask'
  ; type=IEC958,access=r---,values=1
  : values=[AES0=0x0f AES1=0xff AES2=0x00 AES3=0x0f]
numid=22,iface=MIXER,name='IEC958 Playback Pro Mask'
  ; type=IEC958,access=r---,values=1
  : values=[AES0=0xcf AES1=0x00 AES2=0x00 AES3=0x00]
numid=23,iface=MIXER,name='IEC958 Playback Default'
  ; type=IEC958,access=rw--,values=1
  : values=[AES0=0x00 AES1=0x82 AES2=0x00 AES3=0x02]
numid=24,iface=MIXER,name='IEC958 Playback Switch'
  ; type=BOOLEAN,access=rw--,values=1
  : values=off
numid=25,iface=PCM,name='Playback Channel Map'
  ; type=INTEGER,access=rR--,values=2,min=0,max=36,step=0
  : values=3,4
  | container
    | chmap-fixed=MONO
    | chmap-fixed=FL,FR
numid=26,iface=PCM,name='Playback Channel Map',device=1
  ; type=INTEGER,access=rR--,values=2,min=0,max=36,step=0
  : values=0,0
  | container
    | chmap-fixed=MONO
    | chmap-fixed=RL,RR
[?2004hroot@debian641:~# cat /proc/asound/cards
[?2004l
 0 [AudioPCI   ]: ENS1371 - Ensoniq AudioPCI
  Ensoniq AudioPCI ENS1371 at 0x2040, irq 16
[?2004hroot@debian641:~# cat /sys//class/sound//card0/id
[?2004l
AudioPCI
[?2004hroot@debian641:~# cat /var/run/espeakup.c

Re: software speech works with vmware player 16 but not after installation of Debian testing

[Nick Gawronski]

Hi, The system I am using for my host is a windows 10 pro 64 bits system 
and with vmware player I have it set as Debian 10 64 bits as there is no 
version 11.  If I install the ssh server task along with the rest of the 
system during the installation on the host system should I be able to 
ssh into the guest with the networking in vmware player set to nat?  
When I hit backspace in the virtual machine logd in as root or a normal 
user I do get the pc speaker beeps.  If I can login as root on the 
virtual machine what command can I use to unmute the sound card?  Nick 
Gawronski


On 3/16/2021 1:32 PM, Samuel Thibault wrote:

Hello,

Nick Gawronski, le lun. 15 mars 2021 23:11:26 -0500, a ecrit:

I however get no software speech either in the mate desktop or in the
console

I don't have vmware player, so I cannot test this myself. When I try it
with qemu I do get speech both during installation and in the installed
system. So I cannot debug the issue myself.


If I try to use espeak and enter text I get no sound.

Could it be that (for whatever reason) the sound driver on the
installed system does not take care of unmuting the card?


rather then auto detecting or using the system sound card as if I do
this the installation freezes at random points where I suddenly lose
speech.

It would be useful to debunk this as well actually.

Samuel

software speech works with vmware player 16 but not after installation of Debian testing

[Nick Gawronski]

Hi, I used the s option to start speech as I am totally blind using this 
image.


https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/weekly-builds/amd64/iso-cd/firmware-testing-amd64-netinst.iso

Speech worked fine and I liked the fact that the volume was of a highor 
level then in stable.  I then installed the system making sure that 
vmware player 16 was set to use the Realtek sound card by default rather 
then auto detecting or using the system sound card as if I do this the 
installation freezes at random points where I suddenly lose speech.  I 
find that if I tell vmware player the sound card to use it works fine.  
Once the installation is complete I do the reboot and the virtual 
machine beeps at the boot prompt.  I however get no software speech 
either in the mate desktop or in the console but the navigation keys for 
speakup do beep when I go to the top of the screen so I know it is 
installed and running.  If I try to use espeak and enter text I get no 
sound.  My question is why does the installer work successfully with all 
of the default software installed but not talk when it comes up after 
the installation completes?  This same issue works with the stable 
network installer.  I used the non-free image just so if vmware player 
needed anything it would have it and the normal iso image does the same 
thing.  Nick Gawronski

Re: building a custon talking debian installation image with build essential and other packages on the disc as well as the mate accessible desktop

[Nick Gawronski]

Hi, I agree as most hardware now requires firmware to use.  Is there a 
document on how to remaster and add packages to the disc either for 
download or as normal debs that are on the disc?  Nick Gawronski
On Mon, 27 
Apr 2020, D.J.J. Ring, Jr. wrote:



Date: Mon, 27 Apr 2020 00:38:15 -0400
From: "D.J.J. Ring, Jr." 
To: Nick Gawronski 
Cc: debian-accessibil...@lists.debian.org, debian-boot@lists.debian.org
Subject: Re: building a custon talking debian installation image with build
essential and other packages on the disc as well as the mate accessible
desktop

Nick,
Please use the non free images because many blind people are connecting by 
Wi-Fi and the drivers are only on the non free images. Also add the Unofficial 
multimedia sources so blind people can use
the non free codecs.

It takes a lot of work to make Debian normal.

But Debian still is the best, I just wish they'd stop the non free prohibition 
and put printer and multimedia and Firefox in their ISO.

Best wishes,

David

On Fri, Apr 24, 2020, 15:29 Nick Gawronski  wrote:
  Hi, I am totally blind and know about pressing s to start the installer
  with speech as I do this then go back to the main menu and set debconf
  priority to low so I have the most control during the installation
  process.  I looked into the simple-cdd package for building a debian
  installation image but could not find out how to include the full mate
  debian desktop with orca the screen reader setup for speech as well as
  build-essential and other development packages.  What would be the best
  process for building such an image that starts automatically at low
  priority with speech running and a highor volume level then normal for
  systems where you would like speech to be not so soft during the
  installation process?  Nick Gawronski

building a custon talking debian installation image with build essential and other packages on the disc as well as the mate accessible desktop

[Nick Gawronski]

Hi, I am totally blind and know about pressing s to start the installer 
with speech as I do this then go back to the main menu and set debconf 
priority to low so I have the most control during the installation 
process.  I looked into the simple-cdd package for building a debian 
installation image but could not find out how to include the full mate 
debian desktop with orca the screen reader setup for speech as well as 
build-essential and other development packages.  What would be the best 
process for building such an image that starts automatically at low 
priority with speech running and a highor volume level then normal for 
systems where you would like speech to be not so soft during the 
installation process?  Nick Gawronski

Re: speech-enabled expert/rescue/autoinstall keyboard shortcuts

[Nick Gawronski]

On 3/21/2017 7:40 PM, Samuel Thibault wrote:

Hello,

Somehow somebody managed to raise that there is no menu entry for
starting the rescue mode with speech synthesis enabled.  That actually
also raises the question of doing the same for expert install andHi, One issue 
with that is how do we know if we are totally blind what menu we are in and 
also if an option is selected properly or not?  I know the option to start the 
installation with software speech but when there are other menus to go threw 
with no speech how fast do they come up?  Why not add shortcuts to the main 
menu for speech or can one not just type in the shortcut then add 
speakup.synth=soft to start software speech as I tried that once but got 
nowhere?  Nick Gawronski
automated install.

It's really a matter of adding the menu entry: just copy/paste the
existing expert/rescue/automated entries, and append speakup.synth=soft
to it.

Now the question is: which keyboard shortcut to use?

For now, the only documented accessible keyboard shortcut is "s" to
start a speech-enabled installation.  I guess we don't want to add yet
other entries to the main menu, so we'd put these additional entries
under the "advanced options" submenu, which already has shortcut "a".
However, the natural "e", "r" and "a" shortcuts are already taken for
the non-speech versions.

Would it really be a problem to change the meaning of those shortcuts,
to make them start the speech versions instead of the non-speech
version?  I have to say I myself never used those shortcuts, since it's
so fast to just move down a few times when one is sighted :)

Samuel

targets used to build the debian-installer for use with the network installation iso images

[Nick Gawronski]

Hi, I was wanting to do some testing on the debian-installer and was 
wondering what build target is used for the official network 
installations and if I wanted to change the default target from the 
default installation method to the software speech what file should I 
edit as I have both an i386 and an amd64 based system?  I have installed 
the build dependencies using apt-get build-dep debian-installer and also 
have checked out the debian-installer using the svn and mr method talked 
about on the checking out the debian-installer page is this the proper 
method?  Nick Gawronski

proper method for getting the source for the debian-installer for building my own test images

[Nick Gawronski]

Hi, I did apt-get source debian-installer and was told to download the 
debian-installer from git so I did this.  Then I tried to do a demo 
build of the GTK target and it failed with unable to create directories 
in /tmp and things not existing.  I then went to the debian-installer 
wiki pages and was told there to checkout the subversion sources then 
use mr to murge in the git changes.  My question is what is the correct 
method for checking out and building the debian-installer after 
installing the build dependencies using apt-get build-dep 
debian-installer as I think the README file and the wiki pages should 
all have the the same information and not two different sets of 
directions on two different pages?  Nick Gawronski

Re: Debian Installer Stretch Alpha 6 release

[Nick Gawronski]

Hi, Another issue I found is of course backports did not work even when 
I selected it for installation as there are no backports yet for 
testing.  The installer just told me that the repository was commented 
out but it gave the URL instead of the backports information.  What 
would it take for the message to say something like backports could not 
be verified there for this repository is commented out as currently it 
looks like it could not download any information from the repository 
when infact it was just one that failed?  Nick Gawronski



On 5/21/2016 4:13 PM, Cyril Brulebois wrote:

The Debian Installer team[1] is pleased to announce the sixth alpha
release of the installer for Debian 9 "Stretch".


Important changes in this release of the installer
==

  * This release fixes the package installation issue which appeared
lately with the previous alpha release (#814343).
  * Debian Pure Blends can now be enabled directly from the Software
selection screen. This might change in a later release though
(#758116).


Improvements in this release


  * brltty:
 - Install MATE desktop by default when brltty is used in d-i.
 - Disable auto-detection of Cebra, Albatross, and BrailleMemo
   devices in d-i, since they are rare and conflict with other
   devices (#782732).
 - prebaseconfig: Enable screen reader in KDE.
 - prebaseconfig: Support 4th bootline parameter.
 - brltty-udeb.udev.rules: Add new USB IDs.
  * cdebconf:
 - gtk: Auto-scroll when switching between entries.
 - text: Print one screen worth of choices, and use +/- to switch
   between choices screens (#809739).
  * debian-installer:
 - Bump linux kernel version from 4.3.0-1 to 4.5.0-2.
  * espeakup:
 - Add support for multiboard systems: request the user to press
   enter at the right time to select a given board.
 - Improve language/voice lookup.
 - Install MATE desktop by default when espeakup is used in d-i.
  * flash-kernel:
 - Avoid waiting for Ctrl-c when debconf is running (#791794).
  * net-retriever:
 - Concentrate on SHA256 now, following archive-side changes.
  * netcfg:
 - Improve behaviour when user-submitted input contains spaces
   (#818611).
 - Improve error checking in various places.
  * network-console:
 - Improve support for multiple addresses (#816600).
  * parted:
 - Fix problems with LVM and DASD devices (#814076).
  * partman-auto:
 - Bump space requirements for a lot of recipes (#725642).
  * partman-basicfilesystems:
 - Call mkfs.ext2 with -F to avoid hangs (#817174).
  * partman-ext3:
 - Call mkfs.ext[34] with -F to avoid hangs (#767682).
  * preseed:
 - Invert env-preseed and initrd-preseed so that the former
   overrides the latter (#805291).
 - url: correctly handle IPv6 addresses (#815166).
  * rootskel:
 - Add GNU/screen support, when it's available.
  * s390-zfcp:
 - New component to activate and configure FCP devices (#808041).
  * wget:
 - Add udeb support, for later user.
  * win32-loader:
 - Switch signature checking from MD5 to SHA256.
 - Improve support for new versions of Windows (#775055).


Hardware support changes


  * debian-installer:
 - Provide u-boot images for OpenRD.
 - Use marvell flavour for orion5x and kirkwood.
 - Include mtd-modules in various images.
 - Generate image for Seagate Personal Cloud and Seagate NAS.
 - Improve armel/orion5x and armel/kirkwood for many different
   Buffalo Linkstation devices.
 - Add support for Firefly-RK3288.
 - Add support for BeagleBoard-X15.
 - ARM: sunxi: Add support for the Olimex A20-SOM-EVB.
 - Add sata-modules for arm64.
  * grub-installer:
 - Install grub-xen when installing in a Xen PV guest.
  * hw-detect:
 - Improve and split harddrive detection into DASD and SCSI
   dependency on s390x (#818586).
  * libdebian-installer:
 - armel: Add various orion5x/kirkwood based Buffalo Linkstation
   devices supported by device-tree.
  * linux:
 - [armhf] usb-modules: Add modules required for BeagleBoard-X15
   (#815848).
 - [mips*/octeon] udeb: Add ahci_octeon and ahci_platform modules
   to sata-modules.
 - [arm64] udeb: Add leds-modules package containing leds-gpio
   driver.
 - [arm64] udeb: Add regulators and SoC modules to core-modules.
 - [x86] udeb: Move scsi_transport_fc to scsi-core-modules, since
   hv_storvsc now depends on it.
 - [armhf] core-modules: Include regulator drivers by default.
 - mmc-modules: Include MMC controller drivers by default.
 - mmc-modules: Depends on usb-modules.
 - usb-modules: Include USB PHY drivers by default.
 - udeb: Combine scsi-{common,extra}-modules with scsi-modules.
 - udeb: Use wildcards to include entire classes of drivers.
 - udeb: R

Re: Debian Installer Stretch Alpha 6 release

[Nick Gawronski]

Hi, One thing that would be nice to add in the next version of the 
debian-installer is brief descriptions of what tasks do for example in 
the alpha 6 screen select and install software lots of selections exists 
and as some are very good by their names like DebianMultimedia other 
ones are not so well explained by their names like Debian Astro.  The 
descriptions should take up probably no more then one or two lines at 
the most.  Nick Gawronski



On 5/21/2016 4:13 PM, Cyril Brulebois wrote:

The Debian Installer team[1] is pleased to announce the sixth alpha
release of the installer for Debian 9 "Stretch".


Important changes in this release of the installer
==

  * This release fixes the package installation issue which appeared
lately with the previous alpha release (#814343).
  * Debian Pure Blends can now be enabled directly from the Software
selection screen. This might change in a later release though
(#758116).


Improvements in this release


  * brltty:
 - Install MATE desktop by default when brltty is used in d-i.
 - Disable auto-detection of Cebra, Albatross, and BrailleMemo
   devices in d-i, since they are rare and conflict with other
   devices (#782732).
 - prebaseconfig: Enable screen reader in KDE.
 - prebaseconfig: Support 4th bootline parameter.
 - brltty-udeb.udev.rules: Add new USB IDs.
  * cdebconf:
 - gtk: Auto-scroll when switching between entries.
 - text: Print one screen worth of choices, and use +/- to switch
   between choices screens (#809739).
  * debian-installer:
 - Bump linux kernel version from 4.3.0-1 to 4.5.0-2.
  * espeakup:
 - Add support for multiboard systems: request the user to press
   enter at the right time to select a given board.
 - Improve language/voice lookup.
 - Install MATE desktop by default when espeakup is used in d-i.
  * flash-kernel:
 - Avoid waiting for Ctrl-c when debconf is running (#791794).
  * net-retriever:
 - Concentrate on SHA256 now, following archive-side changes.
  * netcfg:
 - Improve behaviour when user-submitted input contains spaces
   (#818611).
 - Improve error checking in various places.
  * network-console:
 - Improve support for multiple addresses (#816600).
  * parted:
 - Fix problems with LVM and DASD devices (#814076).
  * partman-auto:
 - Bump space requirements for a lot of recipes (#725642).
  * partman-basicfilesystems:
 - Call mkfs.ext2 with -F to avoid hangs (#817174).
  * partman-ext3:
 - Call mkfs.ext[34] with -F to avoid hangs (#767682).
  * preseed:
 - Invert env-preseed and initrd-preseed so that the former
   overrides the latter (#805291).
 - url: correctly handle IPv6 addresses (#815166).
  * rootskel:
 - Add GNU/screen support, when it's available.
  * s390-zfcp:
 - New component to activate and configure FCP devices (#808041).
  * wget:
 - Add udeb support, for later user.
  * win32-loader:
 - Switch signature checking from MD5 to SHA256.
 - Improve support for new versions of Windows (#775055).


Hardware support changes


  * debian-installer:
 - Provide u-boot images for OpenRD.
 - Use marvell flavour for orion5x and kirkwood.
 - Include mtd-modules in various images.
 - Generate image for Seagate Personal Cloud and Seagate NAS.
 - Improve armel/orion5x and armel/kirkwood for many different
   Buffalo Linkstation devices.
 - Add support for Firefly-RK3288.
 - Add support for BeagleBoard-X15.
 - ARM: sunxi: Add support for the Olimex A20-SOM-EVB.
 - Add sata-modules for arm64.
  * grub-installer:
 - Install grub-xen when installing in a Xen PV guest.
  * hw-detect:
 - Improve and split harddrive detection into DASD and SCSI
   dependency on s390x (#818586).
  * libdebian-installer:
 - armel: Add various orion5x/kirkwood based Buffalo Linkstation
   devices supported by device-tree.
  * linux:
 - [armhf] usb-modules: Add modules required for BeagleBoard-X15
   (#815848).
 - [mips*/octeon] udeb: Add ahci_octeon and ahci_platform modules
   to sata-modules.
 - [arm64] udeb: Add leds-modules package containing leds-gpio
   driver.
 - [arm64] udeb: Add regulators and SoC modules to core-modules.
 - [x86] udeb: Move scsi_transport_fc to scsi-core-modules, since
   hv_storvsc now depends on it.
 - [armhf] core-modules: Include regulator drivers by default.
 - mmc-modules: Include MMC controller drivers by default.
 - mmc-modules: Depends on usb-modules.
 - usb-modules: Include USB PHY drivers by default.
 - udeb: Combine scsi-{common,extra}-modules with scsi-modules.
 - udeb: Use wildcards to include entire classes of drivers.
 - udeb: Remove some obsolete drivers from nic-modules: Remove FDDI
   and HIPPI drivers, and inet_

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Nick Gawronski]

Hi, Here is the syslog file from my installed system compressed so it 
will go to the lists in gzip format.  Is this what file you want?  Nick 
Gawronski



On 5/20/2016 2:53 AM, Cyril Brulebois wrote:

Hi Nick,

Nick Gawronski <n...@nickgawronski.com> (2016-05-20):

Hi, The name of the iso I was using is firmware-8.0.0-amd64-netinst.iso

  and it is in the archive for the debian-installer.  I ran the installation
using this image as my network cards both wired and wireless require
firmware and I also ran the installation on low priority and choose to
install everything like non-free as well as backports.  For the main tasks
for this text based installation I selected just the standard system as I
want this system to be small.  Everything installed just fine and I was
connected to the installation over the network as I wanted to test out the
network console using my windows 10 system and was able to follow all
prompts but then once the Debian system rebooted no internet settings were
on the system in the /etc/network/interfaces or any other wifi packages that
were installed such as wpa_supplicant.  My question is why does the
installer not copy over the wireless networking settings from the installer
to the target system when doing a text only install with speech?  Nick
Gawronski

In the general case, the installer (through its netcfg component) should
be copying the network settings over from the installer system to the
installed system.

I'm not familiar with the firmware version of installer images, so I'm
adding the debian-cd@ list to the loop, so that people building those
images can comment on this. They might appreciate if you could extract
the following log file from your system and attach it to an email:

 /var/log/installer/syslog

We might have a missing integration bit to enable non-free packages on
the installation system (this might be by design because of freeness
issues, or maybe an oversight; no idea), or maybe a buggy behaviour.

The log file mentioned above might help them figure out what happened on
your system.


KiBi.




syslog.gz
Description: application/gzip

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Nick Gawronski]

Hi, I did not setup any desktop task but my system was installed using 
the wireless network and wpa_supplicant was installed on the target 
system but not sure why networking was not working as should the 
wireless networking settings if just a standard system is installed be 
also installed on to the target system I don't understand why this is 
not done or a question is added to the installer to ask the user about 
this?  Nick Gawronski



On 5/20/2016 1:12 PM, Brian Potkin wrote:

On Fri 20 May 2016 at 01:54:02 -0500, Nick Gawronski wrote:


prompts but then once the Debian system rebooted no internet settings were
on the system in the /etc/network/interfaces or any other wifi packages that
were installed such as wpa_supplicant.  My question is why does the

Are you certain wpa_supplicant was not on the system? If the machine has
no ethernet connection you now have problems.


installer not copy over the wireless networking settings from the installer
to the target system when doing a text only install with speech?  Nick
Gawronski

It happens with any install. The thinking appears to be:

You used a wired install without selecting a desktop task. That means
you wanted a wired connection after the install.

You used a wired or wireless connection and selected a desktop task.
That means you wanted to use networkmanager.

That's ok up to there. There is some practical sense in it. You will
have connectivity after the first boot and can change what you want.

If you used a wireless onnection and did not select a desktop task
that means you want to select and set up your connectivity software
after first boot. Basically - you were just kidding when you used
wireless to install Debian; you didn't want immediate connectivity
afterwards.

Setting up wireless all over again is good fun when your passphrase
has 63 characters. Copy and paste? You could download gpm but

That is one of the reasons I preseed.

Regards.

Brian.

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Nick Gawronski]

Hi, I used the S option to get speech during the installation then 
enabled the network console using the loading menu options and then 
entered in my password so had speech the entire installation and was 
mainly testing out the network console.  Are you saying even if I do 
that and have speech if I install using the network console speech will 
not be turned on after the installation even if it is used to start the 
network console? Nick Gawronski



On 5/20/2016 5:41 AM, Jude DaShiell wrote:
Windows 10 was probably why you didn't get speech post-install. 
Starting debian with the s boot parameter turns on speech that debian 
produces for the installation then by default keeps speech turned on 
post-install.  Use of a console with windows 10 enabled you to get the 
text over the console so I suspect you failed to enable debian speech 
during installation.  I hope this solves one of your problems.


On Fri, 20 May 2016, Nick Gawronski wrote:


Date: Fri, 20 May 2016 02:54:02
From: Nick Gawronski <n...@nickgawronski.com>
To: Alex ARNAUD <alexarn...@member.fsf.org>,
debian-accessibil...@lists.debian.org
Cc: debian-boot@lists.debian.org
Subject: Re: debian-installer issues with no wireless network 
connection after

 a text based Jessie installation
Resent-Date: Fri, 20 May 2016 06:54:31 + (UTC)
Resent-From: debian-accessibil...@lists.debian.org

Hi, The name of the iso I was using is firmware-8.0.0-amd64-netinst.iso

and it is in the archive for the debian-installer.  I ran the 
installation using this image as my network cards both wired and 
wireless require firmware and I also ran the installation on low 
priority and choose to install everything like non-free as well as 
backports.  For the main tasks for this text based installation I 
selected just the standard system as I want this system to be small.  
Everything installed just fine and I was connected to the 
installation over the network as I wanted to test out the network 
console using my windows 10 system and was able to follow all prompts 
but then once the Debian system rebooted no internet settings were on 
the system in the /etc/network/interfaces or any other wifi packages 
that were installed such as wpa_supplicant.  My question is why does 
the installer not copy over the wireless networking settings from the 
installer to the target system when doing a text only install with 
speech?  Nick Gawronski

On 5/20/2016 1:07 AM, Alex ARNAUD wrote:

Dear Nick

On 05/20/2016 06:52 AM, Nick Gawronski wrote:
Hi, I am using the net installer of Jessie version 8.0.0 that 
includes the firmware 

Could you give us the full name of the Jessie ISO?
as I am totally blind and found that the latest installer once it 
was installed I had no software speech after installing the system.
It depends on how you install your system. If you install you system 
in braille or in "normal" way it's the normal effect.
I was installing Debian Jessie on my laptop with just a text based 
system mainly for a rescue system for when X windows is down and 
for times when I don't wish to use X windows.  I found that during 
the installation I was able to connect to the internet and 
successfully install the system but once the system was rebooted I 
had no internet access over any network method. 

As I know, It seems there is no link with accessibility in this case.
What would it take for the debian installation to copy the network 
settings from the installer to the target system as it makes no 
sence why networking would be setup and working during a text based 
installation but not in the target system?  What file should I edit 
to add my wireless network as well as my wired network using DHCP 
so they both will work when my text based system boots?  Nick 
Gawronski

The tips I use is to install a new driver for your Debian system.
For doing something like that you need to follow some steps :
1) Find the model of your card and the related firmware package in 
Debian, if it's a Intel Wireless card it's the package 
firmware-iwlwifi 
<https://packages.debian.org/fr/jessie/firmware-iwlwifi>
2) Add the backports repo in your environment as explained in this 
page : http://backports.debian.org/Instructions/
3) Install the new package with a command like that : "apt-get 
install -t jessie-backports FIRMWARE_NAME"

--
Alex ARNAUD

Re: debian-installer issues with no wireless network connection after a text based Jessie installation

[Nick Gawronski]

Hi, The name of the iso I was using is firmware-8.0.0-amd64-netinst.iso

 and it is in the archive for the debian-installer.  I ran the 
installation using this image as my network cards both wired and 
wireless require firmware and I also ran the installation on low 
priority and choose to install everything like non-free as well as 
backports.  For the main tasks for this text based installation I 
selected just the standard system as I want this system to be small.  
Everything installed just fine and I was connected to the installation 
over the network as I wanted to test out the network console using my 
windows 10 system and was able to follow all prompts but then once the 
Debian system rebooted no internet settings were on the system in the 
/etc/network/interfaces or any other wifi packages that were installed 
such as wpa_supplicant.  My question is why does the installer not copy 
over the wireless networking settings from the installer to the target 
system when doing a text only install with speech?  Nick Gawronski

On 5/20/2016 1:07 AM, Alex ARNAUD wrote:

Dear Nick

On 05/20/2016 06:52 AM, Nick Gawronski wrote:
Hi, I am using the net installer of Jessie version 8.0.0 that 
includes the firmware 

Could you give us the full name of the Jessie ISO?
as I am totally blind and found that the latest installer once it was 
installed I had no software speech after installing the system.
It depends on how you install your system. If you install you system 
in braille or in "normal" way it's the normal effect.
I was installing Debian Jessie on my laptop with just a text based 
system mainly for a rescue system for when X windows is down and for 
times when I don't wish to use X windows.  I found that during the 
installation I was able to connect to the internet and successfully 
install the system but once the system was rebooted I had no internet 
access over any network method. 

As I know, It seems there is no link with accessibility in this case.
What would it take for the debian installation to copy the network 
settings from the installer to the target system as it makes no sence 
why networking would be setup and working during a text based 
installation but not in the target system?  What file should I edit 
to add my wireless network as well as my wired network using DHCP so 
they both will work when my text based system boots?  Nick Gawronski

The tips I use is to install a new driver for your Debian system.
For doing something like that you need to follow some steps :
1) Find the model of your card and the related firmware package in 
Debian, if it's a Intel Wireless card it's the package 
firmware-iwlwifi <https://packages.debian.org/fr/jessie/firmware-iwlwifi>
2) Add the backports repo in your environment as explained in this 
page : http://backports.debian.org/Instructions/
3) Install the new package with a command like that : "apt-get install 
-t jessie-backports FIRMWARE_NAME"

--
Alex ARNAUD

debian-installer issues with no wireless network connection after a text based Jessie installation

[Nick Gawronski]

Hi, I am using the net installer of Jessie version 8.0.0 that includes 
the firmware as I am totally blind and found that the latest installer 
once it was installed I had no software speech after installing the 
system.  I was installing Debian Jessie on my laptop with just a text 
based system mainly for a rescue system for when X windows is down and 
for times when I don't wish to use X windows.  I found that during the 
installation I was able to connect to the internet and successfully 
install the system but once the system was rebooted I had no internet 
access over any network method.  What would it take for the debian 
installation to copy the network settings from the installer to the 
target system as it makes no sence why networking would be setup and 
working during a text based installation but not in the target system?  
What file should I edit to add my wireless network as well as my wired 
network using DHCP so they both will work when my text based system 
boots?  Nick Gawronski

Re: Q: How to rebuild d-i or initrd?

[Nick Gawronski]

Hi, I am also wanting to rebuild the debian-installer as I am totally 
blind and would like to build a version that automatically starts 
speakup on boot rather then having to press a letter as sometimes I am 
not always sure when the drive stops spinning so most of the time I am 
successful but not all of the time.  Also having the ability to set the 
proper volume and speech rate as well as what language espeak uses by 
default would be a very nice thing to document.  On my desktop system 
that is 32 bit I like the feature where the pc speaker beeps but how in 
my local copy of the debian-installer can I just configure all of the 
targets to beep if a built in pc speaker is installed as I read about 
the configuration leaves or so they call it but to make a change across 
the entire local copy of the debian-installer so they all do the same 
thing I am not sure where to look.  On my 64 bit system there is no pc 
speaker that can beep but the sound card is detected properly so I do 
get speech and my next question is can I build a 32 and a 64 bit 
debian-installer on either system even if the 64 bit debian-installer 
won't run on the 32 bit system?  Nick Gawronski

On 12/28/2013 3:36 PM, Ozi Traveller wrote:
I made a replacement for rootskel-gtk, using the previous version 
rootskel-gtk_1.27_amd64.udeb as the source, with a higher version 
number. I've changed the theme and the logo.


I've been told that the way to have the d-i use this new version is to 
rebuild d-i (preferably) or

the initrd (at least).

My question is, how do I rebuild the d-i and then how do I incorporate 
the new d-i in my build?


Cheers

Bug#727740: installation-reports: wireless and wired network works in the installer but not transfered to the installed system

[Nick Gawronski]

Package: installation-reports
Severity: critical
Tags: d-i
Justification: breaks the whole system



-- Package-specific info:

Boot method: CD
Image version: 
http://cdimage.debian.org/debian-cd/7.2.0/and64/iso-cd/debian-7.2.0-amd64-netinst.iso
 2013-10-12 16:06
Date: Date and time of the install

Machine: asus laptop i7 as well as samsung laptop i7
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:   [O ]
Detect network card: [E worked during the installation but was not 
transfered to the installed system which should have been done ]
Configure network:  [E worked during the installation process but was not 
transfered to the installed system which should have been done]
Detect CD:  [O ]
Load installer modules: [O ]
Clock/timezone setup:   [O ]
User/password setup:[O ]
Detect hard drives: [O ]
Partition hard drives:  [O ]
Install base system:[O ]
Install tasks:  [O ]
Install boot loader:[O ]
Overall install:[E network configuration was not transfered to 
installed system so after I booted my system I had no internet access ]

Comments/Problems:
I managed to do the installation successfully but found that after the 
installation my network configuration settings were not transfered to my 
installed system so I had no internet access after the installation on a 
wireless network and had to restart the installation and go to the portion 
right after I was connected to the wireless network and copy over from the 
installer /etc/network/interfaces to my target system as I am totally blind and 
don't know of a nice user friendly tool for configuring wired or wireless 
networking after the installation is complete and am not using X windows
Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.
I think that over all the installation went ok but one thing that should be 
done is if more then one network interface is detected during the installation 
process like wired and wireless setup all of these network interfaces so they 
work during and after the installer and have these settings transfered to the 
installed system.  Also, have a package that uses your debconf frontend 
settings for setting up another network interface or for adding another 
wireless network or removing a wireless network for users who don't use X 
windows but like the method that the installer uses.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=7 (wheezy) - installer build 20130613+deb7u1
X_INSTALLATION_MEDIUM=cdrom

==
Installer hardware-summary:
==
uname -a: Linux chihuahual2 3.2.0-4-amd64 #1 SMP Debian 3.2.51-1 x86_64 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core 
Processor Family DRAM Controller [8086:0104] (rev 09)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200/2nd 
Generation Core Processor Family PCI Express Root Port [8086:0101] (rev 09)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd 
Generation Core Processor Family Integrated Graphics Controller [8086:0116] 
(rev 09)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: 00:16.0 Communication controller [0780]: Intel Corporation 6 
Series/C200 Series Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: 00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 
Series Chipset Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: Kernel driver in use: ehci_hcd
lspci -knn: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series 
Chipset Family High Definition Audio Controller [8086:1c20] (rev 04)
lspci -knn: Subsystem: Samsung Electronics Co Ltd Device [144d:c0b3]
lspci -knn: Kernel driver in use: snd_hda_intel
lspci -knn: 00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series 
Chipset Family PCI Express Root Port 1 [8086:1c10] (rev b4)
lspci -knn: Kernel driver in use: pcieport
lspci -knn: 00:1c.3 PCI bridge [0604]: Intel 

Bug#607338: installation-report: report of my debian installation and issues after initial install

[Nick Gawronski]

Package: installation-reports
Version: 2.43
Severity: important
Tags: d-i squeeze



-- Package-specific info:

Boot method: pressed tab and did debconf/priority=low speakup.synth=dectlk
Image version: 
http://people.debian.org/~joeyH/d-i/images/daily/netboot/gtk/mini.iso 
Date: 14th of December 2010 at around 11 PM Central time

Machine: custom built system with intel p4 processer 3.3 GHZ and 2 GB of ram 
and an 80 GB hard drive that is IDE and all hardware works under linux
Partitions: FilesystemType   1K-blocks  Used Available Use% Mounted on
/dev/sda2 ext476804136   3542952  72480888   5% /
tmpfstmpfs 1033296 0   1033296   0% /lib/init/rw
udev tmpfs 1028928   212   1028716   1% /dev
tmpfstmpfs 1033296 0   1033296   0% /dev/shm



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

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

Comments/Problems:

Description of the install, in prose, and any thoughts, comments
  and ideas you had during the initial install.
When I booted the installation from the CD I had set debconf/priority to low 
and after the base system I went into console two and chrooted into /target and 
set debconf/priority to low and also changed the adduser to not have system 
wide readible home directories.  When I tried to install X windows as well as 
the standard system I got the selection of what pam modules needed to be chosen 
and no matter which one or ones I selected the installation would not let me 
continue saying no pam profiles could be selected I put spaces in front of the 
numbers like with all of the other installation prompts that can be handled 
this way.  After the installation when running tasksel and installing all tasks 
on the system I still got this same issue and had to boot into single user mode 
as booting into normal mode caused the system to freeze as I could not just 
kill aptitude as there was a lock that would not go away.  When I rebooted into 
single user mode I ran dpkg --reconfigure -a and se
 lected unix authentication when the pam prompt came up and everything worked 
fine but still this should be fixed as I would have liked to install X windows 
as well as all other tasks during the initial installation and not have to 
reboot more then once to finish the installation.

-- 

Please make sure that the hardware-summary log file, and any other
installation logs that you think would be useful are attached to this
report. Please compress large files using gzip.

Once you have filled out this report, mail it to sub...@bugs.debian.org.

==
Installer lsb-release:
==
DISTRIB_ID=Debian
DISTRIB_DESCRIPTION=Debian GNU/Linux installer
DISTRIB_RELEASE=6.0 (squeeze) - installer build 20101214-21:57
X_INSTALLATION_MEDIUM=netboot-gtk

==
Installer hardware-summary:
==
uname -a: Linux chihuahuad1 2.6.32-5-486 #1 Fri Dec 10 15:32:53 UTC 2010 i686 
GNU/Linux
lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 82865G/PE/P DRAM 
Controller/Host-Hub Interface [8086:2570] (rev 02)
lspci -knn: Subsystem: Intel Corporation 82865G/PE/P DRAM 
Controller/Host-Hub Interface [8086:2570]
lspci -knn: Kernel driver in use: agpgart-intel
lspci -knn: 00:02.0 VGA compatible controller [0300]: Intel Corporation 82865G 
Integrated Graphics Controller [8086:2572] (rev 02)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:0370]
lspci -knn: 00:06.0 System peripheral [0880]: Intel Corporation 82865G/PE/P 
Processor to I/O Memory Interface [8086:2576] (rev 02)
lspci -knn: 00:1d.0 USB Controller [0c03]: Intel Corporation 82801EB/ER 
(ICH5/ICH5R) USB UHCI Controller #1 [8086:24d2] (rev 02)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:0370]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.1 USB Controller [0c03]: Intel Corporation 82801EB/ER 
(ICH5/ICH5R) USB UHCI Controller #2 [8086:24d4] (rev 02)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:0370]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.2 USB Controller [0c03]: Intel Corporation 82801EB/ER 
(ICH5/ICH5R) USB UHCI Controller #3 [8086:24d7] (rev 02)
lspci -knn: Subsystem: Micro-Star International Co., Ltd. Device [1462:0370]
lspci -knn: Kernel driver in use: uhci_hcd
lspci -knn: 00:1d.3 USB Controller [0c03]: Intel Corporation 82801EB/ER 
(ICH5/ICH5R) USB UHCI Controller #4