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

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#1029962: check-missing-firmware fails to find firmware file or package on partitioned removable media

761fea8aa1921098 Mon Sep 17 00:00:00 2001 From: Pascal Hambourg Date: Sat, 1 Apr 2023 00:07:47 +0200 Subject: [PATCH 1/2] check-missing-firmware: improve firmware file lookup The current algorithm mounts only one device or partition. If it mounts the wrong one, firmware files are not found.

Bug#1033678: installation-reports: Unbootable install: MBR partition unusable with UEFI

Hello, Le 01/04/2023 at 00:41, Dima Kogan wrote: I got it running by using a friend's usb installer. HIS usb disk was a valid UEFI boot disk, so I could boot in UEFI mode, and do the normal install, which completed successfully. How was this "usb installer" created ? cp

Bug#1033678: installation-reports: Unbootable install: MBR partition unusable with UEFI

Hello, On 30/03/2023 at 01:21, Dima Kogan wrote: I'm installing from a USB drive. To make this work, I had to turn off secure-boot and UEFI in the BIOS. Why ? What happens if UEFI boot is enabled ? How did you prepare the USB drive ? What installation image did you use (full file name and

Bug#1033679: hw-detect/check-missing-firmware: add fallback module lookup by modalias and firmware

From: Pascal Hambourg Date: Thu, 30 Mar 2023 00:19:42 +0200 Subject: [PATCH 1/3] check-missing-firmware: add function get_module_by_bus_address Call this function for bus types other than usb and mhi. It looks up: - /driver/module - /driver - /modalias - udevadm modalias in order, and returns

Bug#1032852: Error message clue:

Hello, On 29/03/2023 at 00:23, Charles Curley wrote: I tried installing with the most recent weekly build. I noticed the following line toward the end of syslog: Mar 28 21:35:59 main-menu[425]: (process:4506): cut: /var/lib/dpkg/info/firmware-ipw2x00.md5sum: No such file or directory This

Bug#1033498: installation-reports: Missing FW files not detected on USB stick

On 26/03/2023 at 20:44, Rainer Dorsch wrote: I have not yet tested if that resolves the FW not found issue though. It would have helped me, if the installed would be a little bit more verbose and reported something like No non-free FW files found in these directories: Then it would have

Bug#1032377: firmware loading tests with bookworm-DI-alpha2

Hello, On 05/03/2023 at 15:59, Cyril Brulebois wrote: Pascal Hambourg (2023-03-05): I am afraid that when the firmware is missing the driver is not attached to the device so there is no direct way to retrieve it through /sys. Alright, nice to know which part of the lookup was failing anyway

Bug#1033035: hw-detect: trivial patches

From: Pascal Hambourg Date: Mon, 13 Mar 2023 14:57:52 +0100 Subject: [PATCH 1/3] hw-detect.pre-pkgsel.d/50install-firmware: fix path of deleted file --- hw-detect.pre-pkgsel.d/50install-firmware | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/hw-detect.pre-pkgsel.d/50install

Bug#1033035: hw-detect: trivial patches

On 16/03/2023 at 12:05, Cyril Brulebois wrote: Pascal Hambourg (2023-03-16): - check-missing-firmware.sh: shift positional parameters after reading -n IIUC the script arguments are expected to be network interface names except the first one which may be "-n". In this case,

Bug#1033035: hw-detect: trivial patches

: define local variables in functions - check-missing-firmware.sh: get package name from control instead of file name - check-missing-firmware.sh: replace spaces with tabs in indentationFrom e9a8ceeaa83fbf43e33cdd3745bbbf5d64c3291c Mon Sep 17 00:00:00 2001 From: Pascal Hambourg Date: Mon, 13 Mar

Bug#1032852: debian-installer: Intel Corporation PRO/Wireless 2200BG doen't work for d-i, does work on installed Bookworm

On 13/03/2023 at 04:35, Charles Curley wrote: On Sun, 12 Mar 2023 23:23:56 +0100 Pascal Hambourg wrote: Warning: as described in bug #1032377, the firmware package firmware-ipw2x00 should be reject for requiring license approval. Kibi fixed the typo in commit

Bug#1032852: debian-installer: Intel Corporation PRO/Wireless 2200BG doen't work for d-i, does work on installed Bookworm

On 12/03/2023 at 22:39, Steve McIntyre wrote: On Sun, Mar 12, 2023 at 03:13:34PM -0600, Charles Curley wrote: The wifi works once bookworm is installed, but not under d-i. I can see that d-i's firmware detection stuff worked just fine for the ipw2200 hardware (yay!): Warning: as described

Bug#1032435: installation-reports: Fails to install GRUB bootloader

On 07/03/2023 at 09:01, John Talbut wrote: Install in /dev/sda was just an example, it is the one that the installer suggests. Ok. I have tried /dev/nvme1n1, /dev/nvme1n1p1 (the ESP partition) and /dev/nvme1n1p2 (the boot partition) all with the same result: The rescue operation

Bug#1032435: installation-reports: Fails to install GRUB bootloader

Hello John, On 06/03/2023 at 18:19, John Talbut wrote: It is not clear where to install it but wherever I try I come up with a message "Unable to install GRUB in /dev/sda" (or the equivalent in other partitions). /dev/sda is the USB stick which contains the installer. You cannot install

Bug#1032377: firmware loading tests with bookworm-DI-alpha2

On 05/03/2023 at 13:49, Cyril Brulebois wrote: Mar 5 08:55:33 kernel: [ 184.568261] usb 2-4: Loading firmware file isl3886usb Mar 5 08:55:33 kernel: [ 184.568284] usb 2-4: firmware: failed to load isl3886usb (-2) Mar 5 08:55:33 kernel: [ 184.568294] usb 2-4: firmware: failed to load

Bug#1032377: firmware loading tests with bookworm-DI-alpha2

Package: installation-reports Boot method: USB stick Image version: debian-bookworm-DI-alpha2-amd64-netinst.iso debian-bookworm-DI-alpha2-i386-netinst.iso Date: 2023-03-05 Machine: various PC Processor: various Intel from Pentium 4 to Core i7 Memory: 1.25 to 16 GiB Base System

Bug#1032277: installation-reports: Installer too strongly urges users to set root password

On 02/03/2023 at 19:21, Cyril Brulebois wrote: What happens if you don't set a root password and got dropped into maintenance mode at boot-time? Or if you cannot open a user session for whatever reason ? You're stuck. Default settings allow to launch an unauthenticated root shell at boot

Bug#1032271: Module advansys fails to load on amd64

Package: src:linux Version: 5.10.162-1 Severity: normal Dear maintainer, Loading the 'advansys' module fails with any -amd64 kernel: # modprobe advansys modprobe: ERROR: could not insert 'advansys': No such device The module loads successfully with any -686 or -686-pae kernel. I observed the

Bug#1032071: ARM firmware packages included in amd64 installation images

Package: debian-cd Version: 3.2.0 Severity: minor debian-bookworm-DI-alpha2-amd64-netinst.iso includes firmware packages for ARM platforms: firmware-qcom-soc firmware-samsung firmware-ti-connectivity raspi-firmware These packages add 34 MB to the ISO image, which is not negligible.

Bug#1024817: Bug #1024817: grub2-common: /etc/default/grub still refers to 'vbeinfo' in the comments, should be 'videoinfo' now

mation and is available with both BIOS and UEFI boot. Thanks.From 7153497baac87187d7eaf72809aceaa8537a2c9a Mon Sep 17 00:00:00 2001 From: Pascal Hambourg Date: Thu, 23 Feb 2023 13:47:28 +0100 Subject: [PATCH] Replace 'vbeinfo' with 'videoinfo' in debian/default/grub 'vbeinfo' is available only wit

Bug#990447: Similar problems

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#1029962: check-missing-firmware fails to find firmware file or package on partitioned removable media

Package: hw-detect Version: 1.147 Tags: d-i Dear maintainer, In some situations, check-missing-firmware fails to find loose firmware file or package file on partitioned removable media (as most USB drives are nowadays). Observed behaviour: - When looking for a loose firmware file,

Bug#1029788: connman breaks systemd/udev network interface name policy

Package: connman Version: 1.36-2.2+deb11u1 Dear maintainer, When connman is running, new interfaces using enabled technologies are not renamed by systemd/udev and keep the original names assigned by the kernel despite the systemd name policy (systemd.link). Network interfaces added at boot

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

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

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

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#1029131: Additional information; missing MT7921E firmware; work around.

On 19/01/2023 at 10:24, Jonathan Wilson wrote: The issue seems to be that the driver isn't loaded, and then is being removed which is causing the crash dump. Not exactly. The module is loaded but fails to unload gracefully when the firmware is missing. This is actually a bug in the Linux

Bug#1028547: Missing firmware of Mediatek Wifi cause crash in linux kernel

On 12/01/2023 at 16:25, Bernhard wrote: 05:00.0 Network controller [0280]: MEDIATEK Corp. MT7922 802.11ax PCI Express Wireless Network Adapter [14c3:0616] Subsystem: Foxconn International, Inc. MT7922 802.11ax PCI Express Wireless Network Adapter [105b:e0cd] Kernel driver in

Bug#1021918: #1021918: Kernel module blacklisting doesn't work

Hello, On 07/01/2023, Ian Jackson wrote : We edited the vmlinuz line in the installer image boot menu (we were using the non-graphical installer) to add modprobe.blacklist=rtw88_8723de (...) The installer had *not* included anything in GRUB_CMDLINE_LINUX. Did you add the parameter

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

On 30/12/2022 at 01:03, Joshua McNeil wrote: On Thu, 8 Dec 2022 13:05:48 +0100 Bastian Blank wrote: Hibernation does not work on any modern x86 machine and you don't want to have huge swap on desktop machines as it only adds latency. (...) Hibernation works just fine on all of my modern

Bug#1016737: Loop in POST when using --removable option in grub-install

I wrote: I observe the same behaviour on my laptop. And on another x86 desktop PC too. When loaded from the removable media path (/EFI/BOOT/BOOTX64.EFI), shim loads fbx64.efi which reboots the system if it did not find any BOOTX64.CSV file in /EFI/BOOT, as expected on removable media.

Bug#1016737: Loop in POST when using --removable option in grub-install

Hello, I observe the same behaviour on my laptop. My workaround is to remove EFI/BOOT/fbx64.efi from the EFI partition. IMO --removable should not install this file.

Bug#1026915: grub-install --removable uses CD boot image instead of normal disk boot image

sions. IMO it would be better to reverse the order, cf. patch attached to bug #925309.From 304e813b0c1ff030c4d4dd896aeb46be88478763 Mon Sep 17 00:00:00 2001 From: Pascal Hambourg Date: Fri, 23 Dec 2022 12:13:20 +0100 Subject: [PATCH] Use normal signed EFI disk boot image with --removable gr

Bug#925309: Wrong prefix directory hardcoded in signed GRUB image

Control: reassign -1 grub-efi-amd64-bin Control: tags -1 patch On 13/12/2022 at 16:00, Pascal Hambourg wrote: On 24/03/2019 at 01:10, Colin Watson wrote: Possibly.  The prefix parameter given to grub-mkimage's -p option has to be an actual path, not a variable reference.  In order to make

Bug#925309: Wrong prefix directory hardcoded in signed GRUB image

(CC'in Steve McIntyre and debian-efi) On 24/03/2019 at 01:10, Colin Watson wrote: On Fri, Mar 22, 2019 at 08:47:37PM +0100, Pascal Hambourg wrote: grub-install installs this initial grub.cfg in the same location as the signed image, i.e. - /EFI/BOOT if the option --removable is present

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

On 08/12/2022 at 13:05, Bastian Blank wrote: Hibernation does not work on any modern x86 machine Why ?

Bug#1024524: Thunderbird: mail.compose.other.header side effects

Hello Carsten, On 21/11/2022 at 08:53, Carsten Schoenert wrote: Could you please report your problem to the Bugzilla bugtracker and give us a linking to the bug report afterwards? Thank you for the quick reply. Bugzilla found an existing bug report which seems to be related:

Bug#1024524: Thunderbird: mail.compose.other.header side effects

Package: thunderbird Version: 1:102.5.0-1~deb11u1 Hello, A long time ago, I set mail.compose.other.header=References,In-Reply-To,Message-ID,Sender in order to be able to set or override some header values when composing a mail or newsgroup post. It has worked as expected so far. This

Bug#1021918: debian-installer: Kernel module blacklisting inconsistent

On 08/11/2022 at 12:35, Olaf Meeuwissen wrote: Pascal Hambourg writes: I could not reproduce this after tricking the installer into unloading and reloading the mt7921e module. The module unloads and reloads cleanly. But I do not have any hardware matching this module. The freeze probably

Bug#1021918: debian-installer: Kernel module blacklisting inconsistent

ler does not seem to use the framebuffer and does not offer languages other than English.From 51ab95b8e612772b38f48a791aa2227717b4969c Mon Sep 17 00:00:00 2001 From: Pascal Hambourg Date: Fri, 21 Oct 2022 14:29:25 +0200 Subject: [PATCH 1/3] S02module-params: add "modprobe" to ignore list

Bug#1021918: debian-installer: Kernel module blacklisting inconsistent

On 22/10/2022 at 03:39, Olaf Meeuwissen wrote: Pascal Hambourg writes: On 17/10/2022 at 13:13, Olaf Meeuwissen wrote: I recently tried this version with hardware that triggers loading of the mt7921e kernel module. Loading the module fails due to a firmware file load error but the installer

Bug#1021918: debian-installer: Kernel module blacklisting inconsistent

On 17/10/2022 at 13:13, Olaf Meeuwissen wrote: I recently tried this version with hardware that triggers loading of the mt7921e kernel module. Loading the module fails due to a firmware file load error but the installer starts okay. However, the installer later crashes when probing for

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

Hello, On 09/09/2022 at 16:54, Johannes Schauer Marin Rodrigues wrote: > partman-auto/cap-ram=1024 (...) Description: for internal use; can be preseeded Cap RAM size to specified size in MB, when calculating the swap partition size. Defaults to 1024, meaning 1GB, and since swap is

Bug#1019569: Installing with USB, don't use USB3 port.

Hello, On 12/09/2022 at 10:47, KNE wrote: Boot method: USB stick to Network Image version: debian-11.5.0-amd64-netinst.iso (...) Comments/Problems: don’t know if this has been mentioned or not, but

Bug#1018894: rescue-mode: mounts wrong btrfs subvolume

On 05/09/2022 at 10:46, Ansgar wrote: On Sat, 2022-09-03 at 21:06 -0400, Nicholas D Steeves wrote:   grep 'ID\=debian' < /etc/os-release It should also test for `/usr/lib/os-release` in case the symlink in `/etc/` is not present. Neither will work with separate /usr.

Bug#1018894: rescue-mode: mounts wrong btrfs subvolume

On 04/09/2022 at 03:06, Nicholas D Steeves wrote: Pascal Hambourg writes: I guess that handling btrfs subvolumes or other root filesystem mount options would require changes in the root file system selection step. I do not see how it could be automated (rootflags are defined in the boot

Bug#1018894: rescue-mode: mounts wrong btrfs subvolume

On 03/09/2022 at 06:32, Philip Hands wrote: Ansgar writes: Source: rescue Version: 1.85 Severity: important I've installed a system using btrfs for the root filesystem with d-i (with disk encryption as well). As grub wasn't properly installed (not registered with EFI), I tried to use the

Bug#1010393: installation-reports: No swap partition which disables hibernate

Le 19/05/2022 à 14:48, Andreas Tille a écrit : OK, I tried again. I confirm the automatic installer now created a swap partition inside encrypted LVM (no idea whether I simply looked at the wrong place this morning.) However, that swap partition is only 1GB thus way to small to enable

Bug#1010393: installation-reports: No swap partition which disables hibernate

Le 19/05/2022 à 09:36, Andreas Tille wrote : I retried now with https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/11.3.0+nonfree/amd64/iso-dvd/firmware-11.3.0-amd64-DVD-1.iso to reinstall that laptop again. When choosing "encrypted LVM option" -> "using single

Bug#1010951: Support for dm-verity causes initramfs build failure on non-merged-/usr systems

Package: live-boot-initramfs-tools Version: 1:20220505 Hello, Support for dm-verity adds the following code in initramfs-tools hook script /usr/share/initramfs-tools/hooks/live : # dm-verity support if [ "${DISABLE_DM_VERITY:-}" != "true" ] && [ "${DISABLE_DM_VERITY:-}" != "yes" ] then

Bug#954816: mdadm: Debian stable system does not boot after kernel upgrade, RAID0 not activated

On Tue, 24 Mar 2020 00:19:10 +0200 Răzvan Sandu wrote: Package: mdadm Version: 4.1-1 Severity: normal Dear Maintainer, My Debian stable system, running on old i386 hardware, suddenly became unbootable after doing full upgrades via apt. Via upgrades, the system passed from kernel

Bug#1004274: debian-installer: graphical installer breaks debconf in rescue shell

Package: debian-installer Version: 20210731+deb11u2 Tags: d-i Hello, Steps to reproduce: - Boot the Debian installer - At the boot menu, select "Graphical rescue mode" - follow steps until "Enter rescue mode" - Select a Debian root device - Select "Execute a shell in " - in the shell, execute

Bug#1000239: Rescue system won't find root partition, but insists on /usr

essage ---- From: Pascal Hambourg Le 08/12/2021 à 10:49, Philip Hands a écrit : Is it a problem if /home or /usr/share are left unmounted during rescue? /usr/share contains architecture-independent files for many programs such as bash, grub, os-prober, debconf, dpkg, initramfs-tools... How

Bug#1000239: Rescue system won't find root partition, but insists on /usr

Le 09/12/2021 à 00:25, Steve McIntyre a écrit : Nod. A separate /usr filesystem is a configuration that was supported well by d-i and Debian for a number of years, hence I agreed that it was worth improving rescue-mode to explicitly support it. I *could* also be convinced that we should do

Bug#1000239: Rescue system won't find root partition, but insists on /usr

Le 08/12/2021 à 10:49, Philip Hands a écrit : Is it a problem if /home or /usr/share are left unmounted during rescue? /usr/share contains architecture-independent files for many programs such as bash, grub, os-prober, debconf, dpkg, initramfs-tools... How common is it to have a separate

Bug#1000239: Rescue system won't find root partition, but insists on /usr

Le 03/12/2021 à 22:08, Nicholas D Steeves a écrit : c) parse /target/etc/fstab, and attempt to mount other partitions The rescue system already offers to do it for separate /boot and /boot/efi, so why couldn't it do for separate /usr too ?

Bug#1000743: installation-reports: bootx64.efi didn't seem to get installed and no UEFI boot entry was created for Debian

Le 28/11/2021 à 23:07, Adam Baxter a écrit : Maybe it'd be worth having an option to allow a user to tether a mobile phone via USB to grab the firmware online. This is automatic if the phone emulates a USB-ethernet adapter. Perhaps the prompt should say "We can download the firmware

Bug#1000743: installation-reports: bootx64.efi didn't seem to get installed and no UEFI boot entry was created for Debian

Le 28/11/2021 à 15:06, Steve McIntyre a écrit : On Sun, Nov 28, 2021 at 02:24:06PM +0100, Pascal Hambourg wrote: Shouldn't there normally be EFI/boot/bootx64.efi? Not by default. It happens only if you choose to install a copy of the boot loader in the removable device path. The option

Bug#1000743: installation-reports: bootx64.efi didn't seem to get installed and no UEFI boot entry was created for Debian

Hello, Le 28/11/2021 à 12:28, Adam Baxter a écrit : Comments/Problems: Once the installer had finished and prompted me to reboot, the system came back up in Dell's hardware check mode and some investigation revealed there was no UEFI boot entry for Debian. Some UEFI firmwares are broken and

Bug#995209: d-i: partman-basicfilesystems: missing btrfs mount option descriptions

Package: partman-basicfilesystems Version: 156 Tags: patch Hello d-i team, The following mount options are advertised in mountoptions/btrfs from package partman-btrfs but lack descriptions in debian/partman-basicfilesystems.templates : nodatasum nodatacow nobarrier compress ssd noacl

Bug#995108: d-i: partman-crypto: plain dm-crypt device management issues

Package: partman-crypto Version: 114 Tags: patch Hello d-i team, I found several issues related to plain dm-crypt (i.e. non LUKS) encrypted devices in partman. 1) Partman does not add option "plain" for non LUKS devices in crypttab. This causes warnings at startup and when running

Bug#995104: d-i: partman-basicfilesystems; swap

Package: partman-basicfilesystems Version: 156 Tags: patch Hello d-i team, I am not happy with current swap management in manual partitioning. 1) All existing swaps are automatically marked as used and formatted. Formatting an existing swap changes its UUID. On multiboot setups this breaks

Bug#995091: d-i: partman-efi allows method "efi" on wrong device types

Package: partman-efi Version: 94 Tags: patch Hello d-i team, Partman allows to use any type of device as "EFI System Partition": not only regular partition but also LVM logical volume, encrypted device, RAID array... It should be allowed only on partitions which actually support an "EFI

Bug#741889: os-prober: The 90fallback script lists the least recent kernels first

Hello, On Mon, 17 Mar 2014 21:17:17 +0100 Wojciech Górski wrote: 2014-03-17 2:14 GMT+01:00 Cyril Brulebois : > Wojciech Górski (2014-03-17): >> I have no experience with other distros, but the debian based ones >> have a numbering schema allowing alphabetical ordering, not >> accidentally I

Bug#987503: swap partition only 1 GB instead of at least 1 x RAM size

Hello all, On Sun, 25 Apr 2021 17:33:28 + Martin wrote: On 2021-04-24 21:40, Steve McIntyre wrote: There is no such thing as a "correct" formula, though. The old formula was similarly causing lots of hassle for people installing on servers who didn't want to waste hundreds of gigabytes

Bug#980450: Bug 980450: Module ohci-hcd does not detect USB 1.1 devices

Control: found 980450 4.19.160-2 Hello folks, Having read the original thread in french and helped another user with the same issue, I would like to add some clarifications. The bug submitter has the following hardware : 00:03.0 USB controller [0c03]: Silicon Integrated Systems [SiS] USB

Bug#959799: /etc/network/interfaces: source-directory processing does not check filenames

Package: ifupdown Version: 0.8.35 Control: found -1 0.8.19 Hello, The interfaces(5) man page states : "Additionally, when "source-directory" is used, names of the files are checked to match the following regular expression: ^[a-zA-Z0-9_-]+$. In other words, the names must consist entirely of

Bug#852323: Problem: UUIDs not being used everywhere for disks in stretch

Hello all, On Fri, 19 Apr 2019 13:17:32 +0100 Steve McIntyre wrote: *In the installer*, we're not seeing *any* "change" events for the hard disk (vda in my case), in either stretch or buster. We just get the "add" and "remove" events. In the buster installer, my temporary hack of forcing the

Bug#958397: Missing 60-block.rules breaks grub-installer

Package: udev-udeb Version: 241-7~deb10u3 Control: found -1 232-25+deb9u12 Control: unarchive 852323 X-Debbugs-CC: st...@einval.com Hello, Udev has a rule with OPTIONS+="watch" to generate an event and update symlinks in /dev/disk/ when a block device is written to. In Jessie, the rule was in

Bug#925309: Wrong prefix directory hardcoded in signed GRUB image

Le 24/03/2019 à 01:10, Colin Watson a écrit : However when the signed image is installed in a different location, it still looks for grub.cfg in (EFI_PARTITION)/EFI/debian instead of $cmdpath and spawns the grub> shell unless grub.cfg is present in this location. In the shell, $prefix is set to

Bug#925309: Wrong prefix directory hardcoded in signed GRUB image

Package: grub-efi-amd64-signed Version: 1+2.02+dfsg1+13 From grub2 changelog : - Unconditionally create grub.cfg on our EFI boot partition in Secure Boot mode; GRUB always needs some configuration in this case to find /boot/grub, since we can't modify the signed image at install time

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Le 25/02/2018 à 23:59, Michael Biebl a écrit : Am 25.02.2018 um 23:22 schrieb Pascal Hambourg: This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should not be applied to udev plugins" which was closed because the affected program was not part of Debian. Now it seems

Bug#891477: udev: MemoryDenyWriteExecute breaks gzip on i386

Package: udev Version: 232-25+deb9u1 This a follow-up to bug #855798 "udev: MemoryDenyWriteExecute=yes should not be applied to udev plugins" which was closed because the affected program was not part of Debian. Now it seems that gzip is also affected by MemoryDenyWriteExecute=yes when run by

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

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

Bug#638656: closed by Ben Hutchings b...@decadent.org.uk (Bug#638656: fixed in linux-2.6 2.6.32-36)

Hello, Debian Bug Tracking System a écrit : * Add longterm release 2.6.32.44, including: [...] - atm: [br2684] allow routed mode operation again Note that this also fixes bug #636781. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#636781: acknowledged by developer (closing 638656)

Why were bugs #636781 and #638656 merged ? They are completely different bugs. Bug #636781 affects only the version 2.6.32-35 of linux-2.6 while bug #638656 also affects several other versions. Shouldn't bug #636781 have been merged with bug #639425 (Changes from longterm 2.6.32.44) instead ?

Bug#638656: br2684: Sent packets truncated in VC routed mode

a08af810cdc29d2ca930e8a869d3d01744c392d8 upstream. Reported-by: Pascal Hambourg pas...@plouf.fr.eu.org Signed-off-by: Chas Williams c...@cmf.nrl.navy.mil Signed-off-by: David S. Miller da...@davemloft.net Signed-off-by: Greg Kroah-Hartman gre...@suse.de --- net/atm/br2684.c |2 -- 1 file changed, 2

Bug#636781: br2684: Routed mode interface cannot be activated

Pascal Hambourg wrote : The bug was fixed upstream in kernel 2.6.33 by the following patch, which has not been backported in upstream 2.6.32-stable yet (I have submitted a request to include it). The patch has been included in the new kernel 2.6.32.44 upstream. commit

Bug#636781: br2684: Routed mode interface cannot be activated

Package: linux-2.6 Version: 2.6.32-35 Tags: patch, fixed-upstream Hello, Due to a regression introduced in kernel 2.6.30, attempts to activate a nasX interface created by br2684ctl in routed mode may fail because of improper hardware address validation (a routed point-to-point interface

Bug#632885: xtables-addons-common: TEE support missing

Package: xtables-addons-common Version: 1.26-2 From the changelog : * Do not build the TEE target (Closes: #592237) In short, support for the TEE target (libxt_TEE.so) is disabled in xtables-addons-common 1.26-2 to avoid a conflict with iptables 1.4.9-1 which provides the same file. However

Bug#541169: linux-image-2.6.30-1-amd64 : sis190 driver doesn't work with Ethernet Adpator

Hello, Moritz Muehlenhoff a écrit : On Wed, Aug 12, 2009 at 06:27:19AM +0200, Pierre Meurisse wrote: My Ethernet device is unusable with amd64 kernels (2.6.26 ... 2.6.30). When connected to a dhcp server, the system gets a IP address, but no connection is possible You might have been

Bug#408096: whois won't try IPv4 address after IPv6 timeout

Package: whois Version: 4.7.5 Hello, My Debian Sarge system has global IPv6 connectivity, but currently the RIPE IPv6 prefix 2001:610:240::/48 is unreachable, I don't even receive ICMPv6 Destination Unreachable messages. As 'whois.ripe.net' resolves to both IPv4 and IPv6 addresses, whois uses

Bug#310772: bind9: unexpected error @ client.c:1325 stops IPv6 responses

Debian Release : 3.1 (sarge) Architecture: i386 Kernel : custom 2.4.33.3 Package: bind9 Version: 1:9.2.4-1 I just started to experienced the same problem after upgrading from woody (oldstable) to sarge (stable). After some testing, I believe I found out in which situation it happens, and a

Bug#351403: tftp uses wrong source port in last ack datagram on local connection

Package: tftp Version: 0.17-12 When tftp is used to retrieve a file from a TFTP server that is located on the same host, the last ACK datagram it sends in response to the last DATA datagram from the server has a wrong source port number, different from the one used in the request and in the

<    1   2