On 19/04/2025 at 10:19, Martin-Éric Racine wrote:
Will the release team publish Trixie fully knowing that btrtfs hosts
will no longer be bootable via UEFI?
Not all btrfs hosts are affected. A fresh UEFI trixie btrfs virtual
machine boots fine on bookworm QEMU+OVMF. IIUC you wrote that trixie
On 19/04/2025 at 08:02, Martin-Éric Racine wrote:
la 19.4.2025 klo 8.43 Felix Zielcke (fziel...@z-51.de) kirjoitti:
Am Freitag, dem 18.04.2025 um 21:17 +0300 schrieb Martin-Éric Racine:
pe 18.4.2025 klo 19.39 Felix Zielcke (fziel...@z-51.de) kirjoitti:
You could though test the fs drivers of
On 17/04/2025 at 06:01, Martin-Éric Racine wrote:
ke 16.4.2025 klo 20.40 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti:
There may be some silent data corruption when grub reads the initramfs.
Can you test with the initramfs on another filesystem type (fat, ext4) ?
Can you test with grub
On 16/04/2025 at 15:51, Martin-Éric Racine wrote:
ke 16.4.2025 klo 15.41 Pascal Hambourg (pas...@plouf.fr.eu.org) kirjoitti:
On 16/04/2025 at 13:38, Martin-Éric Racine wrote:
As the attached screenshot shows, 'fuseblk' seemingly doesn't know
anything about the 'subvol'
On 16/04/2025 at 13:38, Martin-Éric Racine wrote:
As the attached screenshot shows, 'fuseblk' seemingly doesn't know
anything about the 'subvol' option for btrfs, which is what causes the
failure to mount root. As to whether this implies a GRUB or Linux
module, I wouldn't know.
The failure has
On 15/03/2025 at 13:54, Christian Lamparter wrote:
After some trouble getting it to load my compiled grub, because
grub-efi-amd64-signed was installed (I had to remove that package).
You could run "grub-install --no-uefi-secure-boot" instead.
On 14/12/2024 at 20:41, Holger Wansing wrote:
Tests with multi-OS installations (up to 3 installations of bookworm,
trixie and sid all mixed together) on multi-disk (2 disks) worked fine here.
Thank you for testing.
I have noticed, that the first (temporarily) os-prober run, which is execute
On 12/12/2024 at 22:00, Holger Wansing wrote:
Felix Zielcke wrote (Wed, 06 Nov 2024 15:07:15 +0100):
There's MR!20 [0] by Pascal Hamburg which completely removes the
grub-legacy parts of it.
[0] https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/20
Does anyone still wa
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 mainboa
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 w
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 B
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 log
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 /usr/lib/shim/shimx6
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 configuration
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
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
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 membe
17 matches
Mail list logo
