Bug#969516: F2FS support in Debian installer

On 11/01/2025 at 19:37, Lennart Sorensen wrote: On Thu, Jan 09, 2025 at 09:21:25PM +0100, Matej Marko wrote: I read, that F2FS works on HDD the same reliably as on SSD. F2FS was not designed for HDD nor SSD with sophisticated flash controllers. F2FS was designed for raw nand flash drives

Bug#1092977: debian-installer: systemd-cryptsetup package not installed on encrypted system

On 14/01/2025 at 02:51, Dave wrote: (Possible dupe of 1092968) Possible. I installed Debian testing from a live CD. During the installation process, I set up 2 encrypted partitions: - btrfs on LVM on LUKS for the root file system - swap on an encrypted partition with a random key (...) The

Bug#1092978: debian-installer: netinst installer uses efi partition from another disk

On 14/01/2025 at 04:04, Ted wrote: I installed Debian with "GNU/Linux trixie-DI-alpha1 _Trixie_ - Official Alpha amd64 NETINST with firmware 20241230-11:26" using the luks encrypted full disk partition scheme. It installed but the installer used an efi partition from another disk where there was

Re: ppc64el Trixie Alpha 1 /boot may be ext2 not ext4

On 13/01/2025 at 14:28, Diederik de Haas wrote: On Mon Jan 13, 2025 at 9:36 AM CET, Pascal Hambourg wrote: AFAIK the only implementation of Petitboot on arm64 (Odroid) supports ext4 so there is no need to rollback to ext2. I did not mean to roll back to ext2 but to create a separate /boot

Bug#1092892: partman-efi: Rework EFI partition management

On 13/01/2025 at 14:39, Holger Wansing wrote: Am 13. Januar 2025 10:06:55 MEZ schrieb Pascal Hambourg : On 13/01/2025 at 08:18, Holger Wansing wrote: Am 13. Januar 2025 00:38:50 MEZ schrieb Pascal Hambourg : In order to preserve unused existing EFI partitions (which may be used by other OS

Bug#1092892: partman-efi: Rework EFI partition management

On 13/01/2025 at 08:18, Holger Wansing wrote: Am 13. Januar 2025 00:38:50 MEZ schrieb Pascal Hambourg : In order to preserve unused existing EFI partitions (which may be used by other OS): - Keep the 'esp' flag on existing EFI partitions when the method is set to "do not use&

Re: ppc64el Trixie Alpha 1 /boot may be ext2 not ext4

On 13/01/2025 at 07:48, Holger Wansing wrote: Am 12. Januar 2025 23:44:27 MEZ schrieb Pascal Hambourg : Indeed we must make a trade-off between robustness (ext4 vs ext2), convenience (/boot in root filesystem vs small separate /boot) and compatibility with boot loaders. And I believe we can

Bug#1092892: partman-efi: Rework EFI partition management

Package: partman-efi Version: 101 Tags: patch Dear maintainers, EFI partition management by partman-efi has some issues. 1) update.d/efi_sync_flag interferes with the "boot" flag management done by partman-base and partman-partitioning. But on GPT disk label parted_server makes the "boot" fla

Re: ppc64el Trixie Alpha 1 /boot may be ext2 not ext4

On 12/01/2025 at 19:43, Holger Wansing wrote: Am 12. Januar 2025 19:17:19 MEZ schrieb Pascal Hambourg : On 12/01/2025 at 16:29, Holger Wansing wrote: Pascal Hambourg wrote (Sun, 12 Jan 2025 16:13:21 +0100): I just wanted to make sure everyone is aware that the revert fixes only this

Re: ppc64el Trixie Alpha 1 /boot may be ext2 not ext4

On 12/01/2025 at 16:29, Holger Wansing wrote: Pascal Hambourg wrote (Sun, 12 Jan 2025 16:13:21 +0100): I just wanted to make sure everyone is aware that the revert fixes only this specific use case (guided partitioning using LVM with or without encryption). The issue already existed and

Bug#1092809: USB hard drive not found on Banana Pi BPI-M1

On 11/01/2025 at 22:11, Andreas Barth wrote: If there is anything that would help finding out, please say so. I'm also happy to try different things if useful (and I'm also available on IRC). #debian-boot on OFTC is dedicated to the Debian installer. Disclaimer: my experience with ARM is very

Re: ppc64el Trixie Alpha 1 /boot may be ext2 not ext4

On 12/01/2025 at 14:51, Holger Wansing wrote: Pascal Hambourg wrote (Sun, 12 Jan 2025 14:13:40 +0100): On 12/01/2025 at 11:53, Holger Wansing wrote: Cyril Brulebois wrote (Sun, 12 Jan 2025 11:21:08 +0100): oliviosu_ppc6...@tutanota.com (2025-01-12): Hello, installing Trixie Alpha 1 on

Re: ppc64el Trixie Alpha 1 /boot may be ext2 not ext4

Hello, On 12/01/2025 at 11:53, Holger Wansing wrote: Cyril Brulebois wrote (Sun, 12 Jan 2025 11:21:08 +0100): oliviosu_ppc6...@tutanota.com (2025-01-12): Hello, installing Trixie Alpha 1 on Tyan TN71-BP012 (POWER8) (/images/trixie_di_alpha1/ppc64el 2024/12/31) Installation goes well but ins

Bug#1089010: debian-installer: arm64, armhf cdrom do not set the selected keyboard layout

Control: found -1 20230607+deb12u9 Bug #1089010 in debian-installer reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/installer-team/debian-installer/-/commit/f5

Bug#1023769: efi-reader: Please add support for "riscv64" arch

On Sat, 12 Nov 2022 23:00:17 + Steve McIntyre wrote: Are you sure you need to build efi-reader here? It's mostly a no-op package on the existing arches already, and I'd be surprised if there is any use for it on on riscv64. As far as I can see, - efi-reader just reads the Lang-* EFI variab

Re: Debian Installer Trixie Alpha 1 release

Hi Holger, On 31/12/2024 at 17:47, Holger Wansing wrote: I'd like to address special thanks to Holger Wansing who has done a tremendous job wading through many proposed changes in various installer components, in addition to coordinating translation efforts. Thanks for your warm words! I wou

Bug#931917: grub-installer: call efibootmgr (if available) to keep track of boot order/options

On 06/01/2025 at 08:16, Holger Wansing wrote: Am 5. Januar 2025 14:40:32 MEZ schrieb Pascal Hambourg : I found this bug report and thought it was a good idea so I rebased your commit on current master and tested it on amd64/efi with and without efivars and on amd64/generic -> ok. Could

Bug#1035356: hw-detect: rework looping over filenames

Hi, On 01/05/2023 at 20:21, Cyril Brulebois wrote: Control: retitle -1 hw-detect: firmware license cannot be accepted anymore Control: clone -1 -2 Control: retitle -2 hw-detect: rework looping over filenames Pascal Hambourg (2023-04-17): On 17/04/2023 at 17:52, Cyril Brulebois wrote: Pascal

Bug#928911: grub-efi-amd64: destroys EFI partition despite being told not to

On Sat, 25 May 2019 13:08:14 +0100 Colin Watson wrote: Control: reassign -1 grub-installer On Mon, May 13, 2019 at 12:10:07AM +0200, Adam Borowski wrote: > Just did a d-i bare-metal test run; installing to another disk, with the > obvious requirement of not damaging the primary system. Thus, I

Bug#931917: grub-installer: call efibootmgr (if available) to keep track of boot order/options

Hi, On Sat, 13 Jul 2019 09:24:06 +0200 Cyril Brulebois wrote: Control: tag -1 patch Cyril Brulebois (2019-07-12): > With stretch, we were getting efibootmgr's output in the installer's > syslog, which could help track down issues related to the boot sequence. > > With buster, due to grub2's

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

On 26/09/2021 at 12:48, Pascal Hambourg wrote: Package: partman-crypto Version: 114 Tags: patch <https://salsa.debian.org/installer-team/partman-crypto/-/merge_requests/4> Hello d-i team, I found several issues related to plain dm-crypt (i.e. non LUKS) encrypted devices in partma

Bug#1092142: partman-xfs: Add support for "discard" mount option

Package: partman-xfs Version: 68 Tags: patch XFS supports the "discard" mount option but partman-xfs does not offer it. Even though fstrim is the preferred discard method, partman offers the "discard" option for other filesystems which support it such as FAT, ext4 or Btrfs so it should also su

Bug#1092129: partman-auto-lvm may use the wrong partitions

Package: partman-auto-lvm Version: 91 Tags: patch The call to clean_method() was lost with commit cfc6797f (Factor out the creation of Physical Volume partitions). Without this call, partitions on other disks may be used in addition to the partitions created by the recipe. As a result, - such

Bug#1089540: Discover wants to "upgrade" to Debian 9 from Debian 13

Control: reassign -1 plasma-discover Hi, This bug report is about the plasma-discover package, not discover. Originally attached screenshots can be downoladed from On Sun, 08 Dec 2024 16:51:06 +0100 kritomas wrote: Package: disco

Bug#1091651: Trixie d-i alpha1 installation report on armhf/efi

Package: installation-reports Installation date: 2024-12-28 Installation image: debian-trixie-DI-alpha1-armhf-netinst.iso Installation media: USB flash drive Boot mode: U-Boot EFI on micro-SD card (no EFI boot variables) Target: Olimex A20-OLinuXIno-LIME2 (Allwinner A20 ARMv7 SoC) Tasksel selecte

Re: Bug#1076723: grub-common: duplicate GNU/Linux in menuentry and submenu lines of /boot/grub/grub.cfg

Control: tags -1 patch On 26/12/2024 at 20:37, Cyril Brulebois wrote: Vincent Lefevre (2024-07-22): After a recent grub2 upgrade, there are now duplicate "GNU/Linux" in menuentry and submenu lines of /boot/grub/grub.cfg, e.g. menuentry 'Debian GNU/Linux GNU/Linux' --class debian --class gnu-

Re: systemd-boot-installer_0.7_source.changes ACCEPTED into unstable

On 26/12/2024 at 19:14, Holger Wansing wrote: However, sublevel4 is "specific to less-popular arches (such as powerpc, mips or sparc) or used in experimental features". That leads to the decision, which arch is popular and which is not. But since arm64 is somewhat new, we could count that to the

Bug#1091441: grub-installer should be disabled on non-EFI armhf

Package: grub-installer Version: 1.204 Severity: minor Tags: patch Commit 9e11cfba (Add support for armhf EFI machines) does not disable grub-installer on non-EFI armhf. The "Install the GRUB boot loader" menu item is available in expert install, and if selected, grub-installer will try and fa

Bug#1087489: [RFD] partman: Add support of the 'legacy_boot' flag to manual partitioning

On 21/11/2024 at 05:08, Holger Wansing wrote: Please go ahead. Now going into technical implementation details. Script partman-partitioning/active_partition/toggle_bootable/choices enables the "Bootable flag" toggle in partition settings. Script partman-partitioning/active_partition/toggle

Bug#1035085: Bookworm RC2 grub-installer/os-prober quirks

Please ignore the attached patches. I created a merge request on salsa: <https://salsa.debian.org/installer-team/grub-installer/-/merge_requests/16> On 08/05/2023 at 22:04, Pascal Hambourg wrote: 1) In expert install (or low priority), the new os-prober dialog displayed by grub-installer

Bug#1086840: remove grub-legacy support

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

Bug#1086840: remove grub-legacy support

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

Bug#1082741: Xorg fails loading in graphics mode on trixie installer (loop keeps failing), nvidia, amd radeon

Control: reassign -1 xserver-xorg-core-udeb 2:21.1.7-3 Control: tags -1 d-i It appears that this bug is a duplicate of bug#1075713 (maybe the two bug reports should be merged): (TL;DR: a change in Linux 6.9 triggered a bug in Xorg fb

Bug#1089036: Manual network configuration did not set up DNS

Control: tags -1 patch On 05/12/2024 at 21:33, Pascal Hambourg wrote: I am reassigning the bug to netcfg anyway because either you hit some edge case or used the wrong separator but netcfg did not display an error. I opened a merge request to address the latter case and other minor issues

Re: Uploading linux (6.12.3-1)

On 08/12/2024 at 03:55, Cyril Brulebois wrote: Cyril Brulebois (2024-12-08): FWIW the X server no longer starts when d-i is built against 6.12.3, it loops with “no screens found”. This is the gtk mini.iso, standard QEMU in stable, and 2G of RAM (i.e. `kvm -cdrom netboot/gtk/mini.iso -m 2G`).

Re: Processed: Re: Bug#1089010: debian-installer: armhf cdrom initrd.gz does not set the selected keyboard layout

On 06/12/2024 at 09:05, Franz Gratzer wrote: Sorry if I am wrong, but yesterday I installed Debian testing from the GNOME live image and couldn't decrypt via LUKS afterwards because the keymapping was probably in English despite me using the German keyboard layout when I installed it. There ar

Re: Debian testing netboot installer can't find any kernel

[Please do not reply to an existing thread when posting about unrelated topics, this one is about keyboard layout in armhf and arm64 cdrom installer] On 06/12/2024 at 09:45, Franz Gratzer wrote: A few days ago I tried installing Debian testing on my laptop using the then most recent official t

Bug#1089036: installation-guide-amd64: Installer using manual network configuration did not set up DNS

Control: reassign -1 netcfg 1.187+deb12u1 Control: retitle -1 Manual network configuration did not set up DNS On 05/12/2024 at 20:46, Michael P. Soulier wrote: I don't recall if the UI asked for a comma or a space between servers The UI asked "Please enter the IP addresses (not host names) of

Bug#1089036: installation-guide-amd64: Installer using manual network configuration did not set up DNS

On 05/12/2024 at 16:52, Michael P. Soulier wrote: On 2024-12-05 03:47, Pascal Hambourg wrote: Which hostname ? I cannot reproduce the issue on debian-12.8.0-amd64-netinst.iso with the above settings. /etc/resolv.conf is populated as expected with two "nameserver" lines. ho

Bug#1089010: debian-installer: armhf cdrom initrd.gz does not set the selected keyboard layout

Control: tags -1 patch

Bug#1089036: installation-guide-amd64: Installer using manual network configuration did not set up DNS

Le 05/12/2024 à 00:54, Michael P. Soulier a écrit : On 2024-12-04 14:34, Pascal Hambourg wrote: Which installation image did you use ? debian-12.8.0-amd64-netinst.iso ? Do you mean /etc/resolv.conf in the installer root or in /target ? Can you post the network parameters you set in the

Bug#1089036: installation-guide-amd64: Installer using manual network configuration did not set up DNS

On 04/12/2024 at 16:15, Michael P. Soulier wrote: Apologies as this must be the wrong package to report against. I was using the amd64 net installer, on a network without a DHCP server. So I set up the network manually, including DNS. Unfortunately the installer did not populate the /etc/resolv.

Bug#1089010: debian-installer: armhf cdrom initrd.gz does not set the selected keyboard layout

Package: debian-installer Version: 20240914 After booting debian-testing-armhf-netinst.iso, I select the French keyboard. Expected outcome: French keyboard layout is set. Observed outcome: default US keyboard layout remains. Error message in /var/log/syslog: ckbcomp-mini: /usr/share/console-

Bug#1029543: check-missing-firmware stops scanning (through mountmedia) as soon as it could mount one partition.

On 26/11/2024 at 22:10, Fab Stz wrote: I'm actually affected by the call to mountmedia in check-missing- firmware. Especially by: "  - Insufficient lookup (something about stopping at the first partition    that's found or something, but I don't know the specifics, and I'm    not diving in

Bug#1088225: debian-installer: automatic partitioning does not allow for hibernation

On 26/11/2024 at 20:25, allan wrote: https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-12.8.0-amd64-netinst.iso This is a stable image. Please download a recent daily or weekly build testing/sid image from My comment on some earlier posts:

Bug#969450: #969450 partman-auto: on a machine with 384 Gb Ram and 512 Gb SSD, creates 400 Gb swap partition

On 23/11/2024 at 15:33, Holger Wansing wrote: Ah, indeed I forgot that part. I should have known, that you understand that all better than I do ;-)) No worries, even I tend to forgot about my own work sometimes. But I would not fix a regression with another regression knowingly. By the way, y

Bug#969450: #969450 partman-auto: on a machine with 384 Gb Ram and 512 Gb SSD, creates 400 Gb swap partition

On 23/11/2024 at 15:05, Pascal Hambourg wrote: The new PRIORITY values defined in other recipes Correction: the new MINIMUM and PRIORITY values. (atomic, home, multi, small_disk) were designed to limit the swap size to approximately 5% of disk size. And the new MAXIMUM values limit the

Bug#969450: #969450 partman-auto: on a machine with 384 Gb Ram and 512 Gb SSD, creates 400 Gb swap partition

On 23/11/2024 at 14:32, Holger Wansing wrote: Pascal Hambourg wrote (Sat, 23 Nov 2024 14:17:31 +0100): On 23/11/2024 at 14:03, Holger Wansing wrote: but the main issue (a heavy swap partition eats up most disk space) is now solved with the server recipe, so I think it's ok to close

Bug#969450: #969450 partman-auto: on a machine with 384 Gb Ram and 512 Gb SSD, creates 400 Gb swap partition

On 23/11/2024 at 14:03, Holger Wansing wrote: but the main issue (a heavy swap partition eats up most disk space) is now solved with the server recipe, so I think it's ok to close this report. This bug report could even have been closed in 2020 after the introduction of partman-auto/cap-ram.

Bug#969450: #969450 partman-auto: on a machine with 384 Gb Ram and 512 Gb SSD, creates 400 Gb swap partition

On 23/11/2024 at 12:03, Holger Wansing wrote: I was a bit surprised when I did a quick Debian Stable install on my new workstation (384 Gb RAM, 512 Gb ssd) and ended up with just 80 Gb usable diskspace, thanks to a 400 Gb swap partition that the Debian installer created. I think a warning/quest

Bug#1087489: [RFD] partman: Add support of the 'legacy_boot' flag to manual partitioning

Hi Adrian, On 20/11/2024 at 14:02, John Paul Adrian Glaubitz wrote: Can you elaborate on this a little more to explain the background? I thought the initial bug submission provided enough background. Some arm64 platforms need the 'legacy_boot' flag to boot on GPT but support of this flag wa

Bug#1087489: [RFD] partman: Add support of the 'legacy_boot' flag to manual partitioning

On 14/11/2024 at 11:09, Pascal Hambourg wrote: As the 'legacy_boot' flag is available only on GPT and the 'boot' flag is irrelevant (=esp) on GPT and should be ignored, the same displays could be used for both flags: - GPT -> manage 'legacy_boot' flag, ignor

Bug#1087489: [RFD] partman: Add support of the 'legacy_boot' flag to manual partitioning

Package: partman-base Version: 229 Affects: partman-partitioning partman-efi It was reported that setting the 'legacy_boot' flag to the boot/root partition on GPT disk label was required in order to boot on some arm64 platforms [1]. Support of this flag was recently added to automatic partitio

Re: partman recipes and deprecation of ext2

On 10/11/2024 at 02:43, Felix Miata wrote: Last week I was under a misunderstanding that upgrading EXT2 filesystems to EXT4 would be a satisfactory solution to eventual 64 bit timestamp support necessity, Upgrade of existing filesystems is outside of partman scope. Simply switching to EXT4 f

Re: partman recipes and deprecation of ext2

Hi Ben, On 10/11/2024 at 01:50, Ben Hutchings wrote: The ext2 filesystem uses 32-bit timestamps and will be unable to represent timestamps beyond early 2038. It is now deprecated in Linux for this reason. What exactly is deprecated ? The ext2 standalone driver (which is disabled in Debian k

Re: Trixie: closing in

Hi, On 02/11/2024 at 21:25, Holger Wansing wrote: There are some things going on on the partman front, however discussion is already done, so it's just a matter of implementing it. FWIW I just opened two more MRs for partman-auto. Removal of grub-legacy support from grub-installer is still pe

Bug#1086530: installation-reports: memmap kernel option containing '$' makes installed system unbootable

On 01/11/2024 at 00:28, Alexander Andreyev wrote: Proposed solution: backslash ('\') and dollar sign ('$') should be properly escaped when copying kernel parameters from /proc/cmd to /etc/grub/defaults. For example, this parameter from /proc/cmd memmap=0x1000$0x2f1ac000,0x1000$0x6af5300

Bug#1086051: [arm64] partman recipes: add new identifier for legacy_boot flag on GPT table?

Control: tags -1 patch On 31/10/2024 at 21:26, Holger Wansing wrote: Am 29. Oktober 2024 21:27:24 MEZ schrieb Pascal Hambourg : On 29/10/2024 at 06:04, Holger Wansing wrote: For the recipe / guided partitioning part: To be backward-compatible for the already existing identifier,, and keep

Bug#1086051: [arm64] partman recipes: add new identifier for legacy_boot flag on GPT table?

On 29/10/2024 at 06:04, Holger Wansing wrote: For the recipe / guided partitioning part: To be backward-compatible for the already existing identifier,, and keep the format consistent, I would prefer using identifiers like $bootable{ } $legacy_boot{ } as proposed in

Bug#1086051: [arm64] partman recipes: add new identifier for legacy_boot flag on GPT table?

(Forwarding the relevant part of this reply from bug#1078871 to bug#1086051) On 26/10/2024 at 02:35, Vagrant Cascadian wrote: I think there are several things that u-boot treats as bootable ... https://source.denx.de/u-boot/u-boot/-/blob/3fbc657669591ca893613f14d42e07069b7d56cd/doc/develop/dis

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 26/10/2024 at 02:35, Vagrant Cascadian wrote: https://source.denx.de/u-boot/u-boot/-/blob/3fbc657669591ca893613f14d42e07069b7d56cd/doc/develop/distro.rst?plain=1#L38-62 Distros simply need to install the boot configuration files (see next section) in an ext2/3/4 or FAT partition, mark

Bug#1086058: installation-reports

On 25/10/2024 at 21:22, DLQ wrote: Image version: https://cdimage.debian.org/images/unofficial/non-free/cd-including-firmware/archive/11.11.0+nonfree/multi-arch/iso-cd/firmware-11.11.0-amd64-i386-netinst.iso (...) As most Cherry Trail devices it has 32bit EFI, so i used an old multi-arch inst

Bug#1086051: [arm64] partman recipes: add new identifier for legacy_boot flag on GPT table?

On 25/10/2024 à 17:55, Holger Wansing wrote: Shortly it has been mentioned, that there are arm64 systems out there (for example Rockchip), which require the 'legacy_boot' flag on the root partition (or on separate /boot partition if such exists) on GPT table, to be able to boot. To be able to

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 25/10/2024 at 17:32, Holger Wansing wrote: I there some change needed for the esp flag part on arm64? No, the 'efi' method already sets thz 'esp' flag in arm64-efi recipes.

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 24/10/2024 at 22:04, Diederik de Haas wrote: On Thu Oct 24, 2024 at 9:08 PM CEST, Holger Wansing wrote: here you have a device|installation, which has the legacy_boot flag installed, but it did not work|boot despite of this. And you changed that legacy_boot flag into a boot flag, and that ma

Bug#1078871: some more data for bug

On 24/10/2024 at 21:40, Holger Wansing wrote: Pascal Hambourg wrote (Wed, 23 Oct 2024 17:09:22 +0200): To be honest, I considered using the "BIOS boot" type when I added the 16MB reserved partition to arm64 recipes. It has the additional advantage of allowing automatic partitioni

Bug#1078871: some more data for bug

On 23/10/2024 at 15:18, Marcin Juszkiewicz wrote: W dniu 23.10.2024 o 14:38, Pascal Hambourg pisze: On 23/10/2024 at 11:46, Marcin Juszkiewicz wrote: For that first 16MB partition it would be nice to use GPT type EF02 (BIOS boot partition) so partitioning tools will see that it is partition

Bug#1078871: some more data for bug

Hi Marcin, On 23/10/2024 at 11:46, Marcin Juszkiewicz wrote: For that first 16MB partition it would be nice to use GPT type EF02 (BIOS boot partition) so partitioning tools will see that it is partition for bootloaders. Partitioning tools do not really care about what a partition is for. AFAIK

Bug#1085849: partman-efi hangs the installer (trivial bug/fix)

Control: tags -1 patch

Bug#1085849: partman-efi hangs the installer (trivial bug/fix)

Package: partman-efi Version: 104 Dear maintainer, In update.d/efi_sync_flag, a required parameter is missing in a parted_server command. open_dialog SET_NAME "" should be open_dialog SET_NAME $id "" This makes the installer user interface hang when the command is executed.

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 21/10/2024 at 10:26, Diederik de Haas wrote: On Sun Oct 20, 2024 at 8:49 PM CEST, Pascal Hambourg wrote: On 20/10/2024 at 16:28, Diederik de Haas wrote: ``` root@cs21:~# parted -s /dev/mmcblk1 print Model: MMC NCard (sd/mmc) Disk /dev/mmcblk1: 61.9GB Sector size (logical/physical): 512B

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 20/10/2024 at 16:28, Diederik de Haas wrote: AFAIUI, UEFI requires GPT, but GPT does not require UEFI. No, UEFI does not require GPT, at least not on my amd64 machines (including QEMU+OVMF). It also supports booting on MSDOS. And as it happens to be the case, I have one device which act

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 19/10/2024 at 20:37, Pascal Hambourg wrote : On 19/10/2024 at 16:54, Diederik de Haas wrote: I already had a hunch why that may be and that's when I examined the SDcard with `lsblk` and later with `fdisk`. Went into `fdisk`'s expert menu and enabled the boot flag on partition

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 19/10/2024 at 23:58, Holger Wansing wrote: This Rockchip system uses the legacy msdos partition table, right? (No UEFI, thus no GPT). With this partition table it should be possible and is confirmed to be working, to set the bootable flag for a partition AFAIK (like an ext2 /boot partition).

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

On 19/10/2024 at 21:08, Diederik de Haas wrote: On Sat Oct 19, 2024 at 8:37 PM CEST, Pascal Hambourg wrote: On 19/10/2024 at 16:54, Diederik de Haas wrote: DeviceStart End Sectors Size Type /dev/sdb1 20483481532768 16M Linux filesystem /dev/sdb2 34816

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

Hi Diederik, First, thank you for the detailed test report ! On 19/10/2024 at 16:54, Diederik de Haas wrote: On Sat Oct 19, 2024 at 1:40 PM CEST, Holger Wansing wrote: @Diederik: could you test, if it works for you now? Or anyone else, who has the possibility/the hardware for this? (...) I

Re: New partition sizes in default recipes for d-i

Hello, On 04/10/2024 at 19:38, Holger Wansing wrote: Also there is a test in tests/desktop, if enough RAM is installed, to make sense for a desktop environment to be installed. The actual value is 64MB, from the beginning of this logic, thus it's 19 years old. So, if less than 64MB of RAM is in

Re: New partition sizes in default recipes for d-i

On 03/10/2024 at 12:11, Holger Wansing wrote: Tests show, that raising the limit by 1G to 4G brings back the old behaviour (no desktop task pre-selected), but to be a bit prepared for future growth, I would propose to go to 5G here? FWIW, 5GB is fine with the "multi" recipe minimum root size (

Re: New partition sizes in default recipes for d-i

Hello, On 03/10/2024 at 03:03, Holger Wansing wrote: There is infact some sort of (incomplete) check for enough disk space in tasksel. In 2007 there was: * Increase the minimum free disk for automatic selection of the desktop task to 3 gb. And that logic in tests/desktop controls indeed,

Bug#1082741: Debian testing Trixie installer issue

On 25/09/2024 at 12:04, Bit Cubic wrote: Installing debian testing (Trixie) with the "graphical install" option is not possible, the process stops immediately after launch, with a black screen with various errors in the same screen(perhaps from the x.org server) including: "Fatal server error: n

Re: New partition sizes in default recipes for d-i

Hi, On 16/09/2024 at 10:02, Diederik de Haas wrote: On Mon Sep 16, 2024 at 7:49 AM CEST, Holger Wansing wrote: I thought I go for some testing then, but sadly the mechanism to build mini.iso's from d-i commits seems broken for some time. Phil: are you aware of this? (...) That looks like the

Re: New partition sizes in default recipes for d-i

On 24/09/2024 at 17:16, Cyril Brulebois wrote: Pascal Hambourg (2024-09-24): Enable LVM with small_disk (again) ? Yes please. <https://salsa.debian.org/installer-team/partman-auto/-/merge_requests/19>

Re: New partition sizes in default recipes for d-i

On 24/09/2024 at 00:43, Cyril Brulebois wrote: Holger Wansing (2024-09-23): Pascal Hambourg (2024-09-23): Which method and recipe did you use ? Encrypted LVM. The default option works though. Ah, the small_disk recipe does not support LVM. It is intended, because I considered that

Re: New partition sizes in default recipes for d-i

Hi, On 23/09/2024 at 22:39, Holger Wansing wrote: Pascal Hambourg wrote (Mon, 23 Sep 2024 19:59:41 +0200): On 23/09/2024 àat 16:57, Cyril Brulebois wrote: Testing a local build against unstable, with a regular BIOS-based setup, I'm seeing a failure to automatically partition a 5G

Re: New partition sizes in default recipes for d-i

Hi, On 23/09/2024 àat 16:57, Cyril Brulebois wrote: Testing a local build against unstable, with a regular BIOS-based setup, I'm seeing a failure to automatically partition a 5G disk, which I'd call a major regression. Which method and recipe did you use ? With a 5GB disk, the only available

Bug#1078871: installer: reserve first 16 MiB space in default recipes for ARM devices?

Control: tags -1 patch On 17/08/2024 at 16:34, Holger Wansing wrote: Hi arm people, could you please comment on this bug, please? Is there a need for some change? I opened a merge request: >https://salsa.debian.org/installer-team/par

Bug#896826: #896826 partman-auto: Wrong minimal disk size calculation when using expert_recipe and lvm partitions

On 17/09/2024 at 22:28, Holger Wansing wrote: We have just overworked the partitioning recipes and some related things, so maybe your issue is also fixed now. Unfortunately I doubt the recent changes fix this issue. Most changes take place in built-in recipes so do not affect expert recipes.

Re: New partition sizes in default recipes for d-i

On 15/09/2024 at 20:43, Holger Wansing wrote: We cannot make it fool-proof for all and every situation. Maybe not, but identified bugs with available fixes should not be left unfixed.

Bug#1081888: [RFD] Update partman-auto/cap-ram default value to re-allow hibernation

Package: partman-auto Version: 167 Tags: d-i Dear maintainers, The debconf setting partman-auto/cap-ram was introduced to deal with the very special case of systems with more RAM than disk space with previous recipes setting the minimum (and maximum in most cases) swap size to 100% of RAM siz

Re: New partition sizes in default recipes for d-i

On 15/09/2024 at 14:39, Pascal Hambourg wrote: Summary: existing reusable partitions (efi and swap) minimum sizes may wrongly be ignored when calculating the required minimum disk size even when using an entire disk. (...) You may want to try the fix I prepared (...) <ht

Re: New partition sizes in default recipes for d-i

Hello Holger, On 15/09/2024 à 12:27, Holger Wansing wrote: Using the "separate home+var+tmp" recipe under UEFI variant on a 10G disk results in an error "Unable to satisfy all constraints on the partition" "Failed to partition the selected disk. This probably happened because there are too man

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 08/09/2024 at 18:34, Holger Wansing wrote: Am 8. September 2024 15:35:16 MESZ schrieb Pascal Hambourg : Another open point is the current partman-auto/cap-ram=1024 MB default value which limits swap size and may prevent hibernation. Yes, I am aware of this point. I didn't mentioned

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 08/09/2024 at 13:20, Holger Wansing wrote: Pascal Hambourg wrote (Sun, 8 Sep 2024 11:53:28 +0200): I also wrote a crude script which generates recipe files for the 5 architectures updated in this MR from a reduced set of parameters: (...) Cool! We should definetely include this into the

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 30/08/2024 at 13:32, Holger Wansing wrote: Am 27. August 2024 23:46:41 MESZ schrieb Pascal Hambourg : Looking at partman-auto-lvm code more closely, it seems that the lvmok flag check happens only after calling choose_recipe. So I guess the check should be moved into choose_recipe (in

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 29/08/2024 at 22:12, Holger Wansing wrote: Am 29. August 2024 20:25:05 MESZ schrieb Pascal Hambourg : On 28/08/2024 at 18:43, Holger Wansing wrote: Am 27. August 2024 23:46:41 MESZ schrieb Pascal Hambourg : Looking at partman-auto-lvm code more closely, it seems that the lvmok flag

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 28/08/2024 at 18:43, Holger Wansing wrote: Am 27. August 2024 23:46:41 MESZ schrieb Pascal Hambourg : Looking at partman-auto-lvm code more closely, it seems that the lvmok flag check happens only after calling choose_recipe. So I guess the check should be moved into choose_recipe (in

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 27/08/2024 at 22:54, Holger Wansing wrote: Am 27. August 2024 21:47:14 MESZ schrieb Pascal Hambourg : <https://people.debian.org/~holgerw/d-i__new-limits_and_fix-envelope-calculation/attempt_2/10G-disk__1G-RAM/use-entire-disk__separate-home-var-tmp.png> /home is smaller than the m

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 27/08/2024 at 12:42, Holger Wansing wrote: And I did some tests again; the results are at [2]. To give a short summary: the results are really really great !!! (I tested all default recipes). I wonder if / should not grow a bit faster (higher priority). Also, this caught my eye:

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 26/08/2024 at 08:34, Holger Wansing wrote: Am 26. August 2024 00:33:48 MESZ schrieb Pascal Hambourg : Maybe the firmware packages in /firmware and /pool are not deduplicated in your image ? Need to check: I used an instruction for remastering of the image from https://wiki.debian.org

Bug#1076952: [RFD] partman-auto: Update guided partitioning size limits for current and future needs

On 25/08/2024 at 22:48, Holger Wansing wrote: Pascal Hambourg wrote (Sun, 25 Aug 2024 22:03:28 +0200): On 25/08/2024 at 19:03, Holger Wansing wrote: I have prepared a netinst image for testing now with both above mentioned MRs: https://people.debian.org/~holgerw/d-i__new-limits_and_fix

  1   2   3   4   >