Bug#1005693: Installation of sid failed because of network configuration failure
Package: installation-reports Boot method: Network PXE Boot Image version: PXE Boot with daily: > https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/initrd.gz > https://d-i.debian.org/daily-images/amd64/daily/netboot/debian-installer/amd64/linux Date: 2022-02-13 Machine: Asus Zenbook Pro UX501J Processor: Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz Memory: 16GB Partitions: - Output of lspci -knn: > 00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor DRAM Controller [8086:0c04] (rev 06) > Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor > DRAM Controller [1043:18dd] > Kernel modules: ie31200_edac > 00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor PCI Express x16 Controller [8086:0c01] (rev 06) > Kernel driver in use: pcieport > 00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core > Processor Integrated Graphics Controller [8086:0416] (rev 06) > Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated > Graphics Controller [1043:18dd] > Kernel driver in use: i915 > Kernel modules: i915 > 00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core > Processor HD Audio Controller [8086:0c0c] (rev 06) > Subsystem: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD > Audio Controller [8086:2010] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB xHCI [8086:8c31] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB xHCI [1043:18dd] > Kernel driver in use: xhci_hcd > Kernel modules: xhci_pci > 00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 > Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > MEI Controller [1043:18dd] > Kernel driver in use: mei_me > Kernel modules: mei_me > 00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #2 [8086:8c2d] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB EHCI [1043:18dd] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset > High Definition Audio Controller [8086:8c20] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset High > Definition Audio Controller [1043:18dd] > Kernel driver in use: snd_hda_intel > Kernel modules: snd_hda_intel > 00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #1 [8086:8c10] (rev d5) > Kernel driver in use: pcieport > 00:1c.2 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #3 [8086:8c14] (rev d5) > Kernel driver in use: pcieport > 00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset > Family PCI Express Root Port #4 [8086:8c16] (rev d5) > Kernel driver in use: pcieport > 00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset > Family USB EHCI #1 [8086:8c26] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > USB EHCI [1043:18dd] > Kernel driver in use: ehci-pci > Kernel modules: ehci_pci > 00:1f.0 ISA bridge [0601]: Intel Corporation HM87 Express LPC Controller > [8086:8c4b] (rev 05) > Subsystem: ASUSTeK Computer Inc. HM87 Express LPC Controller [1043:18dd] > Kernel driver in use: lpc_ich > Kernel modules: lpc_ich > 00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series > Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c03] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > 6-port SATA Controller 1 [AHCI mode] [1043:18dd] > Kernel driver in use: ahci > Kernel modules: ahci > 00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family > SMBus Controller [8086:8c22] (rev 05) > Subsystem: ASUSTeK Computer Inc. 8 Series/C220 Series Chipset Family > SMBus Controller [1043:18dd] > Kernel driver in use: i801_smbus > Kernel modules: i2c_i801 > 01:00.0 3D controller [0302]: NVIDIA Corporation GM107M [GeForce GTX 960M] > [10de:139b] (rev a2) > Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:18dd] > Kernel driver in use: nouveau > Kernel modules: nouveau > 3b:00.0 Network controller [0280]: Intel Corporation Wireless 7260 > [8086:08b1] (rev bb) > Subsystem: Intel Corporation Dual Band Wireless-AC 7260 [8086:4170] > Kernel driver in use: iwlwifi > Kernel modules: iwlwifi > 3c:00.0 Unassigned class [ff00]: Realtek Semi
Bug#992699: debian-installer: Firmwares required for some sound cards
Control: reassign -1 debian-cd Hello, Cyril Brulebois, le dim. 22 août 2021 16:02:20 +0200, a ecrit: > Samuel Thibault (2021-08-22): > > As mentioned in the Bullseye errata, there seems to be a number of > > sound cards that require loading a firmware to be able to emit sound > > (e.g. Intel SOF). Unfortunately currently the installer loads firmware > > after loading the ISO image, while speech synthesis is needed at the > > very first interaction with the user, which is usually before that. We'd > > thus want (for the firmware-enabled image) to include firmware in the > > initrd somehow. > > For context, that's sof I was fighting with: > > https://tracker.debian.org/news/1245087/accepted-hw-detect-1147-source-into-unstable/ > > > We discussed a bit on IRC, possibly we could just, at debian-cd step, > > catenate the cpio archives, or unpack/assemble/repack, or ship several > > initrds. > > And once booted on my sof-enabled laptop, it starts speaking, so I > suppose that's a successful PoC; next step is to confirm whether > tweaking debian-cd to do the cat dance looks good to Steve as well. I had a try at adding support to debian-cd, I can up with this: https://salsa.debian.org/images-team/debian-cd/-/merge_requests/23 It actually follows the debian-edu way which uses cpio -oA to append content. That makes it simpler for anybody who would be trying to gunzip the initrd.gz Cyril, could you try on the actual hardware the resulting image: https://people.debian.org/~sthibault/tmp/debian-sid-amd64-NETINST-1.iso debian-cd people, could you have a look? It would be also very worth applying to the bullseye images. Samuel
Processed: Re: Bug#992699: debian-installer: Firmwares required for some sound cards
Processing control commands: > reassign -1 debian-cd Bug #992699 [debian-installer] debian-installer: Firmwares required for some sound cards Bug #985696 [debian-installer] debian-installer: Speech synthesis and Intel SOF firmware Bug reassigned from package 'debian-installer' to 'debian-cd'. Bug reassigned from package 'debian-installer' to 'debian-cd'. No longer marked as found in versions debian-installer/20210731. No longer marked as found in versions debian-installer/20210731. Ignoring request to alter fixed versions of bug #992699 to the same values previously set Ignoring request to alter fixed versions of bug #985696 to the same values previously set -- 985696: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=985696 992699: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992699 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
arm64/d-i: esp: not enough or too many clusters for filesystem
Hello, I modified the daily build of d-i to include custom kernel modueles for the m1. I boot using m1n1/dtb/u-boot > usb stick with fat32 > grub the the Debian installer in the expert mode. When I try to autopartition it fails because it creates a ESP partition which is too large. I tried 512M and 1G both failed, but with 256M it works. See the following video: https://tg.st/u/d-i-esp-cluster-size-vfat.mp4 These are the scripts that I used to modify the d-i for the m1: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian See bootstrap.sh. Also I would like to know where I can file bug reports for d-i? Cheers, Thomas
arm64 d-i for apple m1 machines
Hello, I modified the daily build of d-i to be able to install it on m1. Currently I have the following problems: - I need to extract some wifi firmware from a usb stick - I need to tell grub to use the removable media path and not try to update the nvram - The signed grub binary should not be installed because u-boot hangs when it tries to load the same. - I need to install a custom kernel I tried three things: - Create a preseed.cfg in the root of the initramfs with the following options: d-i base-installer/kernel/image string none d-i preseed/early_command /wifi.sh d-i preseed/late_command /kernel.sh grub-efi-arm64 grub2/update_nvram boolean false grub-efi-arm64 grub2/force_efi_extra_removable boolean true When I do that the debian installer does not start on vt0, I have to go to vt1 and attach to a screen session with a basic d-i in it. I want the regular one. - Tried the hooks here: https://d-i.debian.org/doc/internals/apb.html /usr/lib/debian-installer-startup.d/ This directory did not exist, I created it, but the script was not executed. /usr/lib/post-base-installer.d/* This is the only hook that worked for me. But I tried to use it to set the following two options in /target system which were ignored when installing grub: grub-efi-arm64 grub2/update_nvram boolean false grub-efi-arm64 grub2/force_efi_extra_removable boolean true /usr/lib/finish-install.d/* [finish-install] This script was not executed. - So what I now did is write two scripts which are being executed by the user on a shell on the first installer page to load the wifi firmware. And when grub installation failed to install grub and install a kernel. See also: https://git.zerfleddert.de/cgi-bin/gitweb.cgi/m1-debian bootstrap.sh https://tg.st/u/m1-d-i.mp4 https://github.com/AsahiLinux/docs/wiki/Debian If you have any advise for me how to improve the procedure, so that the user does not need to install the scripts manually, please let me know. Cheers, Thomas
Bug#1005729: Automatic partitioning fails on arm64 d-i with error message partman: mkfs.vfat: Not enough or too many clusters for filesystem
Source: partman-efi
X-Debbugs-Cc: tho...@glanzmann.de
Version: 94
Severity: normal
Tags: d-i patch
Hello,
when installing Debian on an arm64 m1 machine, I get the following error during
auto partitioning or when creating a EFI System Partition with more than 256 MB:
partman: mkfs.vfat: Not enough or too many clusters for filesystem - try less
or more sectors per cluster
When I try to manually create mkfs.vfat on the same system it works:
(air) [~] lsblk
NAMEMAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
nvme0n1 259:00 465.9G 0 disk
├─nvme0n1p1 259:10 500M 0 part
├─nvme0n1p2 259:20 371.6G 0 part
├─nvme0n1p3 259:30 2.3G 0 part
├─nvme0n1p4 259:40 1G 0 part /boot/efi
├─nvme0n1p5 259:50 85.5G 0 part /
└─nvme0n1p6 259:60 5G 0 part
nvme0n2 259:70 3M 0 disk
nvme0n3 259:80 128M 0 disk
(air) [~] umount /boot/efi
(air) [~] mkfs.vfat /dev/nvme0n1p4
mkfs.fat 4.2 (2021-01-31)
(air) [~] mkfs.vfat -F 16 /dev/nvme0n1p4
mkfs.fat 4.2 (2021-01-31)
The sector size is report as 4096:
(air) [~] blockdev --getss /dev/nvme0n1
4096
The issue seems to be related to:
https://sources.debian.org/src/partman-efi/94/commit.d/format_efi/?hl=15#L66
Since mkfs.vfat don't have issue with creating file systems on block devices
with a sector size other than 4096, it is probably best to remove the whole code
block that sets the sectors per cluster and sector size. Find attached a patch.
-- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: arm64 (aarch64)
Kernel: Linux 5.16.0-asahi-next-20220118-g5fa3c85b5f14 (SMP w/8 CPU threads;
PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC
Locale: LANG=C, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Report will be sent to Debian Bug Tracking System
--- ./wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml.orig 2022-02-13
09:33:30.099608502 +0100
+++ ./wpa_supplicant/doc/docbook/wpa_supplicant.conf.sgml 2022-02-13
09:33:51.187037059 +0100
@@ -45,8 +45,8 @@
EAP-TLS as work network.
-# allow frontend (e.g., wpa_cli) to be used by all users in 'wheel' group
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+# allow frontend (e.g., wpa_cli) to be used by all users in 'root' group
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
#
# home network; allow all valid ciphers
network={
@@ -79,7 +79,7 @@
Aegis, Interlink RAD-Series)
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="example"
scan_ssid=1
@@ -101,7 +101,7 @@
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="example"
scan_ssid=1
@@ -123,7 +123,7 @@
authentication
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="1x-test"
scan_ssid=1
@@ -148,7 +148,7 @@
use.
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
network={
ssid="example"
scan_ssid=1
@@ -178,7 +178,7 @@
(-Dwired or -Droboswitch on command line).
-ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=wheel
+ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=root
ap_scan=0
network={
key_mgmt=IEEE8021X
--- format_efi.orig 2022-02-14 04:42:29.023205868 +0100
+++ format_efi 2022-02-14 04:46:31.407838463 +0100
@@ -62,22 +62,8 @@
db_progress START 0 3 partman/text/formatting
db_progress INFO $template
db_progress SET 1
- log_sector_size="$(blockdev --getss "$(cat device)")"
- if [ "$log_sector_size" = 512 ]; then
- mkdosfs_opts=
- else
- # mkdosfs has trouble handling cluster
- # calculations for non-512-byte logical
- # sectors. Forcing one sector per cluster
- # avoids this as long as the filesystem
- # isn't too large, but that shouldn't be a
- # problem for EFI System Partitions.
- mkdosfs_opts='-s 1'
- fi
if log-output -t partman --pass-stdout \
$MKFS_FAT -F "${new_efi_fs#fat}" \
--S "$log_sector_size" \
-$mkdosfs_opts \
"$device" >/dev/null; then
sync
status=OK
