Bug#985853: debian-installer: Whitespace before a commented line in preseed file causes line to be parsed
On Thu, Mar 25, 2021 at 09:45:17AM +1030, Andrew McDonnell wrote: > Package: debian-installer > Version: 20190702+deb10u8 > Severity: important > Tags: d-i > > In a preseed file I accidentally had a space before a comment character, which > caused my preseed to fail in unexpected ways. I could not find anythying that > stood out in the documentation (e.g. > https://www.debian.org/releases/buster/amd64/apbs04.en.html or > https://www.debian.org/releases/stable/amd64/apbs03.en.html) stating that this > would occur. > > The specific example in my case looked like this: > > #_preseed_V1 > d-i debian-installer/locale string en_AU > d-i keyboard-configuration/xkb-keymap select us > d-i keymap select us > ... etc ... > # Example of fetching a script to run > #d-i preseed/run string http://10.1.2.3/my-script.sh > > > My install was hanging and when I entered a console and looked in the syslog, > it was attempting to access that script for which the IP address does not > exist > on my network. I finally started to understand the problem when I did this, > the > latter finally triggered a parse error in the installer console: > > #d-iWHATpreseed/run string http://10.1.2.3/my-script.sh > > > #d-iWHATpreseed/runISstringHAPPENINGhttp://10.1.2.3/my-script.sh > > at this point I saw the white space, removed it and the problem went away. > > (I am also unsure whether "d-iWHAT" is also a bug or just some default > applying > if the item owner is not found) > > So I guess that either > - whitespace is disallowed before a comment character and this should be added > to https://www.debian.org/releases/stable/amd64/apbs03.en.html - it mentioned > whitespace between fields but not at the start of a line > - this is a bug Well none of the examples ever have spaces before # for comments. The documentation page you linked to doesn't even mention comments at all. I would agree that perhaps it should. I have certainly encountered file types before where comments had to have # at the start of the line. -- Len Sorensen
Bug#985904: installation-reports: partman defaults to use existing ESP partitions on LVM volumes
Package: installation-reports Severity: normal X-Debbugs-Cc: vagr...@debian.org Boot method: network Image version: https://d-i.debian.org/daily-images/arm64/20210325-02:16/netboot/netboot.tar.gz Date: 2021-03-25 ~17:00 UTC Machine: apm mustang Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udev devtmpfs 16359696 0 16359696 0% /dev tmpfs tmpfs 3281996 524 3281472 1% /run /dev/mapper/mst0vg-mst00--root ext4 4721184 1233016 3227664 28% / tmpfs tmpfs 16409976 0 16409976 0% /dev/shm tmpfs tmpfs 5120 0 5120 0% /run/lock /dev/sda1 vfat5117204352507368 1% /boot/efi tmpfs tmpfs 3281992 0 3281992 0% /run/user/1000 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 media: [ ] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [E] Install base system:[E] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: I was performing an installation with existing LVM volumes of several virtual machines, and partman defaulted to selecting the ESP partitions that were present inside the LVM volumes of the virtual machines, but would fail to proceed during the installation. Going back to the partitioning menu and setting each of the undesired ESP partitions to "do not use this partition" eventually allowed the install to proceed. Similar issue with swap partitions, though I'm sure it would have happily proceeded to re-initialize all the swap partitions in the virtual machine images... not sure how to handle that sanely; other than potentially suspend-to-disk images, it is fairly easy to recover from having the swap signature rewritten. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20210325-02:07:18" X_INSTALLATION_MEDIUM=netboot == Installer hardware-summary: == uname -a: Linux mst00 5.10.0-5-arm64 #1 SMP Debian 5.10.24-1 (2021-03-19) aarch64 GNU/Linux usb-list: usb-list: Bus 01 Device 01: xHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 5.10.0-5-arm64 xhci-hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 02 Device 01: xHCI Host Controller [1d6b:0003] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 03 usb-list:Manufacturer: Linux 5.10.0-5-arm64 xhci-hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 03 Device 01: xHCI Host Controller [1d6b:0002] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 01 usb-list:Manufacturer: Linux 5.10.0-5-arm64 xhci-hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub usb-list: usb-list: Bus 04 Device 01: xHCI Host Controller [1d6b:0003] usb-list:Level 00 Parent 00 Port 00 Class 09(hub ) Subclass 00 Protocol 03 usb-list:Manufacturer: Linux 5.10.0-5-arm64 xhci-hcd usb-list:Interface 00: Class 09(hub ) Subclass 00 Protocol 00 Driver hub lsmod: Module Size Used by lsmod: ufs81920 0 lsmod: qnx4 24576 0 lsmod: hfsplus 110592 0 lsmod: hfs65536 0 lsmod: cdrom 61440 2 hfsplus,hfs lsmod: minix 40960 0 lsmod: msdos 24576 0 lsmod: fuse 155648 0 lsmod: nls_ascii 16384 1 lsmod: nls_cp437 20480 1 lsmod: efivarfs 20480 1 lsmod: dm_mod135168 36 lsmod: raid1 57344 1 lsmod: md_mod172032 2 raid1 lsmod: xfs 1359872 0 lsmod: jfs 192512 0 lsmod: btrfs1388544 0 lsmod: xor20480 1 btrfs lsmod: xor_neon 16384 1 xor lsmod: raid6_pq 106496 1 btrfs lsmod: libcrc32c 16384 2 btrfs,xfs lsmod: vfat 28672 1 lsmod: fat81920 2 msdos,vfat lsmod: ext4 765952 1 lsmod: crc16 16384 1 ext4 lsmod: mbcache24576 1 ext4 lsmod: jb
Re: Bug#985853: debian-installer: Whitespace before a commented line in preseed file causes line to be parsed
On Thu, 25 Mar 2021 10:49:06 -0400
lsore...@csclub.uwaterloo.ca (Lennart Sorensen) wrote:
> Well none of the examples ever have spaces before # for comments.
> The documentation page you linked to doesn't even mention comments at
> all. I would agree that perhaps it should. I have certainly
> encountered file types before where comments had to have # at the
> start of the line.
May I suggest inserting the following as the last bullet point item at
the top of "B.3. Creating a preconfiguration file" the following:
A comment consist of a line which *starts* with a sharp character ("#")
and extends the length of that line.
https://www.debian.org/releases/stable/i386/apbs03.en.html
The emphasis on the word "starts" should probably be italics, or, in
HTML, .
--
Does anybody read signatures any more?
https://charlescurley.com
https://charlescurley.com/blog/
Bug#985755: Modprobe tried to load incorrect module
I noticed in the "syslog" that modprobe couldn't find the module "rtw_8723de" that was not listed on the provided "hardware-summary"; instead, lsmod shows "rtw88_8723de". Then, the module "r8169" tried to load the firmware, but that module belongs to the GbE card. hardware-summary: lspci -knn: 02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15) ... lspci -knn: Kernel driver in use: r8169 lspci -knn: Kernel modules: r8169 lspci -knn: 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8723DE 802.11b/g/n PCIe Adapter [10ec:d723] ... lspci -knn: Kernel modules: rtw88_8723de syslog: Mar 25 20:35:04 main-menu[262]: (process:3599): modprobe: FATAL: Module rtw_8723de not found. Mar 25 20:35:04 main-menu[262]: (process:3599): modprobe: FATAL: Module rtw_8723de not found in directory /lib/modules/5.10.0-4-amd64 ... Mar 25 20:35:10 kernel: [ 133.234274] r8169 :02:00.0: firmware: failed to load rtl_nic/rtl8168h-2.fw (-2) Mar 25 20:35:10 kernel: [ 133.234278] r8169 :02:00.0: Direct firmware load for rtl_nic/rtl8168h-2.fw failed with error -2 Mar 25 20:35:10 kernel: [ 133.234281] r8169 :02:00.0: Unable to load firmware rtl_nic/rtl8168h-2.fw (-2)
Bug#985917: installation-reports: Bullseye Alpha 3 successful on GNOME Boxes in Mint 20
Package: installation-reports Severity: wishlist X-Debbugs-Cc: cdpa...@hotmail.com (Please provide enough information to help the Debian maintainers evaluate the report efficiently - e.g., by filling in the sections below.) Boot method: GNOME Boxes, presented ISO to hypervisor as DVD. Image version: debian-bullseye-DI-alpha3-amd64-netinst.iso Date: Thu, Mar 25, 2021, approximately 5:30pm US-EDT Machine: Lenovo H30-50 desktop, Linux Mint 20 Ulyanna Cinnamon host system (fully updated prior to guest installation), Intel Pentium G3260 processor, 4GB DDR3 memory. Partitions: Filesystem Type 1K-blocksUsed Available Use% Mounted on udev devtmpfs669692 0669692 0% /dev tmpfs tmpfs 138516 884137632 1% /run /dev/sda1 ext4 19525456 3812848 14697724 21% / tmpfs tmpfs 692576 26792665784 4% /dev/shm tmpfs tmpfs 5120 4 5116 1% /run/lock tmpfs tmpfs 138512 52138460 1% /run/user/1000 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 media: [O] Load installer modules: [O] Clock/timezone setup: [O] User/password setup:[O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Chose defaults for all options except mirror, where I chose ftp.us.debian.org and got an error message. However, it then seemed to proceed normally. All other aspects of installation were clean, guest rebooted and installed system is normal. Chose Xfce instead of GNOME as the DE. Installation was smooth and pleasant. Please make sure that any installation logs that you think would be useful are attached to this report. Please compress large files using gzip. -- Package-specific info: == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="11 (bullseye) - installer build 20201202" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == uname -a: Linux bullseye-testing-alpha3 5.9.0-4-amd64 #1 SMP Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux lspci -knn: 00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02) lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: 00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000] lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: 00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010] lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: Kernel driver in use: ata_piix lspci -knn: Kernel modules: ata_piix, ata_generic lspci -knn: 00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03) lspci -knn: Subsystem: Red Hat, Inc. Qemu virtual machine [1af4:1100] lspci -knn: 00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04) lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: 00:03.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter [10ec:8139] (rev 20) lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: Kernel driver in use: 8139cp lspci -knn: Kernel modules: 8139cp, 8139too lspci -knn: 00:04.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 01) lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: Kernel driver in use: snd_hda_intel lspci -knn: Kernel modules: snd_hda_intel lspci -knn: 00:05.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03) lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci_hcd lspci -knn: 00:05.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03) lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: Kernel driver in use: uhci_hcd lspci -knn: Kernel modules: uhci_hcd lspci -knn: 00:05.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03) lspci -knn: Subsystem: Red Hat, Inc. QEMU Virtual Machine [1af4:1100] lspci -knn: Kernel driver in us
Bug#985922: unblock: u-boot/2021.01+dfsg-4
Package: release.debian.org User: release.debian@packages.debian.org Usertags: unblock X-Debbugs-Cc: vagr...@debian.org, debian-boot@lists.debian.org Severity: normal Please unblock package u-boot [ Reason ] This version adds support for the pinetab platform and fixes a bug that fails to detect some pinephone platforms. This also re-adds debugging symbols that were lost late in the bullseye release cycle due to upstream buildsystem changes. [ Impact ] Hardware support for another platform (pinetab) and working installation process for another platform (pinephone). Ability to debug u-boot using debugging symbols. [ Tests ] None. [ Risks ] Very low risk to existing platforms as this involves no code changes to u-boot itself. Increases the installed size (~2MB) and .deb size nominally for the u-boot-sunxi:arm64 package. [ Checklist ] [x] all changes are documented in the d/changelog [x] I reviewed all changes and I approve them [x] attach debdiff against the package in testing [ Other info ] This is depended on by debian-installer for the arm64/armhf images, so leaving this in a blocked state could impact debian-installer update process. unblock u-boot/2021.01+dfsg-4 Thanks for your work managing the release! live well, vagrant diff -Nru u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi --- u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi 2021-02-28 18:14:48.0 -0800 +++ u-boot-2021.01+dfsg/debian/bin/u-boot-install-sunxi 2021-03-12 11:10:45.0 -0800 @@ -38,7 +38,9 @@ "OrangePi Zero Plus2") TARGET="/usr/lib/u-boot/orangepi_zero_plus2/" ;; "OrangePi One Plus") TARGET="/usr/lib/u-boot/orangepi_one_plus/" ;; "Pinebook") TARGET="/usr/lib/u-boot/pinebook" ;; - "Pine64 PinePhone (1."[12]")") TARGET='/usr/lib/u-boot/pinephone' ;; + "Pine64 PinePhone Braveheart (1.1)") TARGET='/usr/lib/u-boot/pinephone' ;; + "Pine64 PinePhone (1.2)") TARGET='/usr/lib/u-boot/pinephone' ;; + "PineTab") TARGET="/usr/lib/u-boot/pinetab" ;; "Pine64+") TARGET="/usr/lib/u-boot/pine64_plus" ;; "Pine64 LTS") TARGET="/usr/lib/u-boot/pine64-lts" ;; "PineRiver Mini X-Plus") TARGET="/usr/lib/u-boot/Mini-X" ;; diff -Nru u-boot-2021.01+dfsg/debian/changelog u-boot-2021.01+dfsg/debian/changelog --- u-boot-2021.01+dfsg/debian/changelog2021-03-01 00:00:18.0 -0800 +++ u-boot-2021.01+dfsg/debian/changelog2021-03-12 15:00:43.0 -0800 @@ -1,3 +1,18 @@ +u-boot (2021.01+dfsg-4) unstable; urgency=medium + + [ Arnaud Ferraris ] + * Add support for the pinetab platform (Closes: #982982) + * u-boot-install-sunxi: fix device tree model for PinePhone 1.1 +(Closes: #984704) + + [ Vagrant Cascadian ] + * debian/patches: Update PineTab patch use default bootdelay. + * debian/patches: Add Forwarded link to PineTab patch. + * debian/rules: Ensure debugging symbols are enabled. + * debian/rules: Pass argument to remove build path from debug symbols. + + -- Vagrant Cascadian Fri, 12 Mar 2021 15:00:43 -0800 + u-boot (2021.01+dfsg-3) unstable; urgency=medium [ Domenico Andreoli ] diff -Nru u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch --- u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch 1969-12-31 16:00:00.0 -0800 +++ u-boot-2021.01+dfsg/debian/patches/pinetab/0001-configs-add-PineTab-defconfig.patch 2021-03-12 11:15:15.0 -0800 @@ -0,0 +1,45 @@ +From 2c346cacb4b0841051bceb27a57058020860ab8b Mon Sep 17 00:00:00 2001 +From: Arnaud Ferraris +Date: Wed, 2 Sep 2020 09:53:50 +0200 +Subject: [PATCH] configs: add PineTab defconfig +Forwarded: https://patchwork.ozlabs.org/project/uboot/list/?series=232582 + +The PineTab device-tree is already in u-boot, this commit adds the corresponding +defconfig, based on pinephone_defconfig. + +Signed-off-by: Arnaud Ferraris + +--- + configs/pinetab_defconfig | 22 ++ + 1 file changed, 22 insertions(+) + create mode 100644 configs/pinetab_defconfig + +diff --git a/configs/pinetab_defconfig b/configs/pinetab_defconfig +new file mode 100644 +index 00..71dda9f5d9 +--- /dev/null b/configs/pinetab_defconfig +@@ -0,0 +1,20 @@ ++CONFIG_ARM=y ++CONFIG_ARCH_SUNXI=y ++CONFIG_SPL=y ++CONFIG_IDENT_STRING="" ++CONFIG_MACH_SUN50I=y ++CONFIG_SUNXI_DRAM_LPDDR3_STOCK=y ++CONFIG_DRAM_CLK=552 ++CONFIG_DRAM_ZQ=3881949 ++CONFIG_MMC_SUNXI_SLOT_EXTRA=2 ++# CONFIG_VIDEO_DE2 is not set ++CONFIG_DEFAULT_DEVICE_TREE="sun50i-a64-pinetab" ++# CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set ++CONFIG_SYS_CONSOLE_INFO_QUIET=y ++# CONFIG_DISPLAY_CPUINFO is not set ++# CONFIG_DISPLAY_BOARDINFO is not set ++# CONFIG_SPL_RAW_IMAGE_SUPPORT is not set ++# CONFIG_SP
