Bug#1059167: installation-reports: installer hangs while recognizing network hardware

2023-12-20 Thread Pascal Hambourg
Hello Janusz, On 20/12/2023 at 20:52, Janusz Bień wrote: I understand the installer now includes non-free drivers, No, only non-free firmware. but I suspect it missing one needed for my hardware, which is Intel Ethernet Connection (7) I219-V Intel Dual Band Wireless-AC 3168 (on the

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-10 Thread Pascal Hambourg
On 10/04/2023 at 15:13, Steve McIntyre wrote: Overall comment: I'm not trying to make the heuristics 100% reliable here, as I don't think that's actually possible. Instead, I'm trying to tread the fine line of: * minimising false negatives - let's try to pick up on the most common cases

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-10 Thread Pascal Hambourg
partman-efi "Fix detection of BIOS-bootable systems" provides a significant improvement over previous behaviour. However I have a few comments. 1a) The patch assumes that a GPT disk may be BIOS-bootable only if it has a BIOS boot partition. But a GPT disk can be BIOS-bootable even without a

Bug#1033913: partman-auto-lvm: Broken "Guided - use entire disk and set up LVM" in UEFI mode

2023-04-03 Thread Pascal Hambourg
Hello, On 03/04/2023 at 21:50, Cyril Brulebois wrote: - It very much looks like the intermediary states are slightly different when setting up LVM and when setting up encrypted LVM, and the LVM case case leads to some confusion in partman-efi's /lib/partman/init.d/50efi (which

Bug#990447: Similar problems

2023-02-01 Thread Pascal Hambourg
On 02/02/2023 at 00:33, Phil Dibowitz wrote: And I've run `grub-install` with my EFI dir mounted. What's interesting is the version in EFI is different than the version staged by the package: ``` # sum /usr/lib/shim/shimx64.efi /boot/EFI/EFI/debian/shimx64.efi 47979   918

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

2023-01-25 Thread Pascal Hambourg
Sorry for the late (and long) answer... On 23/01/2023 à 19:36, Oleg A. Arkhangelsky wrote: I tried this *.deb (Pascal approach). It doesn't change behaviour introduced after this patch [1]. Yes, restart for "allow-hotplug" interfaces work but I got the same system boot lag in Jeff

Bug#1022843: Bug#1029352: Bug#1022843: ifupdown: network down after systemctl restart

2023-01-22 Thread Pascal Hambourg
Oleg A. Arkhangelsky wrote: Note that we have to use '--ignore-errors'. Otherwise if we have real hotplug interface that is not present at the moment of restart, `ifup` returns non-zero and systemd unit fail. "--ignore-errors" marks missing interfaces as configured, so ifup will not configure

Bug#1029352: netcfg: broken ifupdown support for wireless interfaces

2023-01-22 Thread Pascal Hambourg
Hello, On 21/01/2023 at 17:14, Cyril Brulebois wrote: # Second issue Once that's fixed, if one gets both DHCP+SLAAC, the generated /e/n/i looks like this (± comments/newlines): allow-hotplug wlXXX iface wlXXX inet dhcp iface wlXXX inet6 auto wpa-ssid my-home-network

Bug#784070: mdadm Software RAID1 with GPT on Debian 8.0.0 amd64 - Does not mount/boot on disk removal

2015-05-09 Thread Pascal Hambourg
I can reproduce the problem, which did not happen with Wheezy. UEFI boot, fresh Debian 8 amd64, RAID 1 on two GPT disks. Another person experienced it too on disks with legacy MBR/MSDOS partition scheme, so I do not think it is related to GPT. Note that this does not happen when the missing