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

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

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-envelope-calculation/ Thank you. (960 MB, sorry) Wow, what makes it so much bigger than the 12.6 netinst

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

On 23/08/2024 at 17:52, Holger Wansing wrote: @Pascal: Would you be able to provide a merge request for this in partman-auto-lvm, please? After fixing a few typo's and minimal testing, I opened Note: partman-lvm-a

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

On 23/08/2024 at 17:52, Holger Wansing wrote: Am 23. August 2024 00:15:44 MESZ schrieb Pascal Hambourg : It is clearly a bug in partman-auto-lvm because the resulting sizes do not match the partman-auto-recipe specification. It remained unnoticed only because the EFI and /boot partitions

Re: XZ support in kmod.udeb

On 23/08/2024 at 08:46, Bastian Blank wrote: On Fri, Aug 23, 2024 at 12:39:14AM +0200, Pascal Hambourg wrote: On 22/08/2024 at 18:50, Bastian Blank wrote: | % grep ^depmod -B 3 -A 2 kernel-wedge-2.105/commands/copy-modules | if [ "$os" = lin

Re: XZ support in kmod.udeb

On 22/08/2024 at 18:50, Bastian Blank wrote: On Thu, Aug 22, 2024 at 04:38:30PM +0200, Marco d'Itri wrote: So, does d-i actually use depmod or modinfo? Yes, it does. I think we should get rid of it however. | % grep ^depmod -B 3 -A 2 kernel-wedge-2.105/commands/copy-modules |

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

On 22/08/2024 at 17:19, Holger Wansing wrote: Pascal Hambourg wrote (Thu, 22 Aug 2024 13:59:12 +0200): On 19/08/2024 à 07:50, Holger Wansing wrote: Am 18. August 2024 21:50:53 MESZ schrieb Pascal Hambourg : Should the "small_disk" recipes be resurrected ? I wasn't aware

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

Apologies for the late answer... On 19/08/2024 à 07:50, Holger Wansing wrote: Am 18. August 2024 21:50:53 MESZ schrieb Pascal Hambourg : I wonder, if we could grow up the root partition in "separate /home" and "separate /home, /var, /tmp" a bit (only relevant on small d

Bug#1079267: discover: turn into transitional empty packages?

On 22/08/2024 at 09:09, Petter Reinholdtsen wrote: [Chris Hofstaedtler] I don't know of any way of removing packages on upgrades from users systems, but at least the packages could become empty themselves. Perhaps we can turn them into empty packages, add a description specifying that they are

Bug#1079139: Failed boot after install

On 20/08/2024 tat 18:55, louigi 600 wrote: I dint think it even loads the grub efi file. System bios complains it can't boot from that device. Did you try an expert install with GRUB in the "removable media path" when prompted ? There is something Debian does not like about my Dell Optiple

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

On 18/08/2024 at 23:46, Pascal Hambourg wrote: The /boot partition size is bigger than I expected in all LVM cases, and I understand why. My previous calculations compensated the LVM PV priority used by partman-auto-lvm but not the minimum size (100MB) which is considerably smaller than the

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

On 18/08/2024 at 16:38, Holger Wansing wrote: I have uploaded some screenshots from tests with different disk sizes to https://people.debian.org/~holgerw/partman-auto___new-limits/ Thank you. The /boot partition size is bigger than I expected in all LVM cases, and I understand why. My previou

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

, the partition would reach 1.5GB in 80GB disk space (still not huge) but would now need 32GB disk space to reach 1GB instead of 12GB. On 18/08/2024 at 16:38, Holger Wansing wrote: Pascal Hambourg wrote (Sun, 18 Aug 2024 12:33:50 +0200): <https://salsa.debian.org/installer-team/part

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

On 17/08/2024 at 15:56, Pascal Hambourg wrote: On 17/08/2024 at 12:30, Holger Wansing wrote: Pascal, would you be able to form the proposed changes as they are currently into code for a patch or a merge request, maybe for amd64 only, for now? The details would be mostly as you stated in your

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

On 17/08/2024 at 12:30, Holger Wansing wrote: Pascal, would you be able to form the proposed changes as they are currently into code for a patch or a merge request, maybe for amd64 only, for now? The details would be mostly as you stated in your first proposal, AFAICS. Currently there are no s

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

Shouldn't this bug be advertised in debian-...@lists.debian.org so that people familiar with ARM platforms are aware of it ?

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

On 16/08/2024 at 00:27, Diederik de Haas wrote: On Thu Aug 15, 2024 at 10:24 PM CEST, Pascal Hambourg wrote: Then I guess a 16 MiB unused partition could be added to relevant recipes. Now, which are the relevant recipes ? In other words, which arch/subarch need it ? recipes-armhf-efi

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

On 15/08/2024 at 21:00, Diederik de Haas wrote: On Thu Aug 15, 2024 at 5:50 PM CEST, Pascal Hambourg wrote: On 15/08/2024 at 16:25, Diederik de Haas wrote: All that matter is that the first 16 MiB stay unused so that U-Boot can be put there. It is still unclear to me if it can be an unused

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

On 15/08/2024 at 16:25, Diederik de Haas wrote: On Thu Aug 15, 2024 at 3:46 PM CEST, Pascal Hambourg wrote: On 15/08/2024 at 08:26, Holger Wansing wrote: Am 15. August 2024 00:47:22 MESZ schrieb Diederik de Haas : So it would be very helpful if the recipe(s) for ARM devices would reserve

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

On 15/08/2024 at 08:26, Holger Wansing wrote: Am 15. August 2024 00:47:22 MESZ schrieb Diederik de Haas : I'm not 100% sure if this fits into this subject/discussion, but ... It is beyond the original scope (partition size limits) and I believe it would deserve its own discussion involving

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

On 09/08/2024 at 17:05, Philip Hands wrote: While we're changing things, could we distinguish between LVM recipes and non-LVM ones? What would be the differences between LVM and non-LVM recipes ? I do not see how to do this only in recipes, except by adding a dummy partition with $lvmignore{

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

On 07/08/2024 at 20:33, Holger Wansing wrote: A recipe specific for server installations, which limits the swap to let's say 1G or 2G, because the machine has enough RAM built-in. What would be the other partitions in this "server" recipe ? - /var/log as suggested by José Ángel Pastrana ? - /s

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

On 05/08/2024 at 17:47, Holger Wansing wrote: Is there an intended use case for built-in recipes ? Should there be different recipes for different uses cases ? E.g.: - minimal installation - workstation with graphic desktop environment - server Doesn't sound like a bad idea IMO. Could probably

Re: Bug#1070085: Enhancing default home folder permissions for improved privacy

On 05/08/2024 at 01:07, Chris Hofstaedtler wrote: On Tue, Apr 30, 2024 at 12:16:23AM +0200, Håvard F. Aasen wrote: Could default home folder permissions lean towards greater privacy, while administrators can adjust permissions to be less strict if necessary? What I would like is to have 'HOME

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

On 24/07/2024 at 17:16, Pascal Hambourg wrote: Poll: What should be the MIN, MAX and minimum disk size to reach MAX for Here is a first proposal to start the discussion. The raw priority value in recipes is quite obscure, and it turns out that expressing it with the minimum disk size to

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

On 31/07/2024 at 00:38, Thomas Hahn wrote: On Fri, 26 Jul 2024 14:00:51 +0200 Pascal Hambourg wrote: > > firmware-nvidia-graphics was installed on systems which already had > firmware-misc-nonfree because firmware-misc-nonfree recommends > firmware-misc-nonfree so that system

Bug#1077635: debian-installer: RFC: provide UEFI shell under Advanced/Export options

On 31/07/2024 at 03:04, Dmitry Baryshkov wrote: This is an RFC whether it would be possible to include UEFI shell into the debian installer media. I understand that it won't work with SecureBoot The menu entry can be hidden when secure boot is enabled. For example, on some of old Qualcomm-ba

Re: Testing CD preseed oops: regression

On 29/07/2024 at 20:28, Charles Curley wrote: Pascal Hambourg wrote: AFAICS if the file was not found, the message would say "the file could not be retrieved", not "the installer failed to process the file" which suggests the file may be corrupted. Did you check the insta

Re: Testing CD preseed oops: regression

On 28/07/2024 at 23:50, Charles Curley wrote: When I go to load the debconf file, the installer doesn't find it. I then go to a console and manually mount the USB stick on /media. I can then ls the stick, more the preseed file, etc. When I then go back to the installer, it still cannot find the

Bug#972396: Comment on «initramfs-tools: Installation fails (no space left on device)»

On 26/07/2024 at 13:27, Thomas Hahn wrote: There was some changes with the firmware packages. Yes, Nvidia firmware grew bigger (but not as much as the observed initramfs size increase) so they were moved from firmware-misc-nonfree to a new package firmware-nvidia-graphics, which is recommende

Re: Merge request for increasing ESP size

On 25/07/2024 at 21:59, Holger Wansing wrote: Pascal Hambourg wrote (Thu, 25 Jul 2024 21:47:19 +0200): On 25/07/2024 at 20:38, Holger Wansing wrote: Only on smaller disks it has ~512MB, so that could be changed to ~768MB to be consistent with /boot. OK. But with MIN=806 and PRIO=850 (how

Re: Merge request for increasing ESP size

On 25/07/2024 at 21:47, I wrote: Explanation: raw increment factors are normalized on a base 100 and rounded to integers. It means that it a raw increment factor is less ^^ if than 1% of the sum of all increment factors, then the normalized increment fac

Re: Merge request for increasing ESP size

Hello, On 25/07/2024 at 20:38, Holger Wansing wrote: on big disks (> 10G I guess) the ESP is already 1G Actually not. As mentioned in , the recipe had MIN=PRIORITY which resulted in the size being stuck to MIN (538 MB) regardless o

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

Package: partman-auto Version: 166 Tags: d-i Dear maintainers, Partition size limits in partman-auto recipes have issues: - some limits are too low for current needs and should be raised; - some limits are inconsistent across atomic, home and multi recipes; - some priorities prevent the size fro

Bug#1076753: partman-crypto: Default size for /boot partition too low

On 23/07/2024 at 01:49, Thomas Mayer wrote: when selecting "Guided - use entire disk and set up encrypted LVM" with a 256GiB disk, only 510MiB are used for the unecrypted /boot partition. Guided partition sizes are not defined in partman-crypto but partman-auto. With file sizes of 250MB for

Bug#1076695: debian-installer: /boot partition created by installer isn't big enough

On 22/07/2024 at 04:39, Cyril Brulebois wrote: Jonathan Kamens (2024-07-21): Something changed recently in testing which caused the size of my initrd to go up A Lot, e.g., on one computer from 70MB to 248MB. (...) Have you tried comparing before/after to see where this increase comes from? Ch

Bug#1076617: installation-guide: Severely outdated information wrt partitioning

(I replied to the list instead of the bug report, sorry for the duplicate) On 19/07/2024 at 20:54, Diederik de Haas wrote: There may be a bug here, in that the /boot partition was too small. That has been fixed in the installer, but unfortunately we don't have a general way to grow the partiti

Re: Bug#1076617: installation-guide: Severely outdated information wrt partitioning

On 19/07/2024 at 20:54, Diederik de Haas wrote: There may be a bug here, in that the /boot partition was too small. That has been fixed in the installer, but unfortunately we don't have a general way to grow the partition on installed systems. And there have been other reports that the kernel

Consequences of /tmp becoming a tmpfs by default on d-i guided partitioning

On 08/07/2024 at 11:23, Luca Boccassi wrote: On Mon, 8 Jul 2024 at 10:21, Pascal Hambourg wrote: Looking at systemd changelog: * Make /tmp/ a tmpfs by default. Restore the upstream default and make /tmp/ a tmpfs. Can be overridden with: touch /etc/systemd/system/tmp.mount or

Re: partman-basicfilesystems_166_source.changes ACCEPTED into unstable

On 07/07/2024 at 22:41, Debian FTP Masters wrote: [ Luca Boccassi ] * Note that /tmp is a tmpfs by default in partition choice. Looking a systemd changelog: * Make /tmp/ a tmpfs by default. Restore the upstream default and make /tmp/ a tmpfs. Can be overridden with: touch /e

Bug#875308: linklocal ipv6 addresses in debian-installer netcfg

On 06/07/2024 at 10:53, Marc Haber wrote: On Sat, Jul 06, 2024 at 12:09:09AM +0200, Pascal Hambourg wrote: When entering link local ipv6 addresses with interface suffixes as gateway during the network configuration in the debian installer, the installer detects the address to be malformed

Bug#875308: linklocal ipv6 addresses in debian-installer netcfg

When entering link local ipv6 addresses with interface suffixes as gateway during the network configuration in the debian installer, the installer detects the address to be malformed. Why would you need to do this ? AFAICS entering the plain link-local IPv6 address without the interface suffix

Re: Heads-up: Verifying shim SBAT data failed: Security Policy Violation

On 03/07/2024 at 08:13, Roland Clobus wrote: Who can find out which part in this file is causing the issue? Or which tools do I need to use to debug this? Maybe increase shim verbosity with # mokutil --set-verbosity true

Bug#1074036: systemd-boot-installer/skip true halts the installer

Control: tags -1 patch On 22/06/2024 at 08:04, ov2k.github wrote: Alternatively, move this code into an isinstallable script, where a return value of 1 is appropriate. This is what is proposed in

Re: Grub error on an installed system

On 06/06/2024 at 12:35, darkpenguin wrote: Harmless messages are fine, but what could be taking about 4 seconds of waiting at "Welcome to GRUB!" before the menu? Is there any way to find out? You can try adding 'set debug=all' and 'echo ' commands in /boot/efi/EFI/debian/grub.cfg and /boot/gr

Re: Grub error on an installed system

On 06/06/2024 at 11:51, darkpenguin wrote: On a new Bookworm installation I see a new issue: before grub-efi shows the menu, it pauses for a whole few seconds on "Welcome to GRUB!", and then flashes an error for a split second: error: no such device: /.disk/info error: no such device: /.disk/mi

Bug#1072215: USB wireless Netgear WNA1100 fails to load

On 01/06/2024 at 10:08, Tom Overlund wrote: Running the patched installer, the output was a bit different, and it DID unload the module ("ath9k_htc: Driver unloaded"), Thank you for testing. It is still not clear which method identified the actual module. I should make it more verbose. I susp

Bug#1072215: USB wireless Netgear WNA1100 fails to load

On 31/05/2024 at 14:59, Tom Overlund wrote: Can you tell me the best way to apply these patches? I tried: $ apt-get source hw-detect # apt-get build-dep hw-detect $ cd hw-detect-1.159/ $ mkdir debian/patches and copying the three .patch files there, followed by: $ debuild -b -uc -us I was ho

Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

On 31/05/2024 at 13:51, Pascal Hambourg wrote: Maybe running "udevadm trigger" during specific moments and recording its output may provide useful information: Sorry, I meant "udevadm monitor".

Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

On 31/05/2024 at 10:26, Roland Clobus wrote: * Moment 1: the first d-i screen is shown. The USB device is seen by the kernel, but the module is not yet loaded ls -d /sys/bus/usb/drivers/r8712u/1-3* No such file or directory As expected, the module is not loaded so /sys/bus/usb/drivers/r8712u

Bug#1072215: USB wireless Netgear WNA1100 fails to load

Hello Tom, On 30/05/2024 at 13:33, Tom Overlund wrote: /var/log/syslog indicates it tried to load firmware for the USB WiFi device, failed, but loaded the kernel module anyways. Then the installer detected this, installed the package with the firmware, and then got some errors about realoding U

Re: migrating grub from BIOS to UEFI loses /etc/default/grub

On 30/05/2024 at 12:07, Felix Zielcke wrote: d-boot is actually the wrong mailing list to discuss grub. Right, so I posted a digest of this thread to the GRUB maintainer list for further discussion.

Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

On 26/05/2024 at 22:29, Roland Clobus wrote: Your patch series works fine, the firmware is correctly identified and loaded. Unfortunately for me, it still needs a reconnect cycle. See the attached syslog for their effect. (I've used sid) Thank you for testing my patches but I did not expect

Re: migrating grub from BIOS to UEFI loses /etc/default/grub

On 26/05/2024 à 16:08, Harald Dunkel wrote: This is a highly destructive bug. You have UEFI boot finally working, you just do some cleanup, and on the next reboot of your server 8 weeks later it doesn't boot anymore. :-( On the other hand, I doubt many users care to purge the old grub package

Bug#1071927: discover: Discover displaying packages wrong.

On 26/05/2024 at 05:58, user wrote: Package: discover Version: 2.1.2-10 Severity: normal X-Debbugs-Cc: heterocycle_papill...@simplelogin.com Dear Maintainer, When I open Discover and type "antivirus" into the search bar, packages from the KDE Store appear, but when I click on settings and then

Bug#1071903: hw-detect: USB wireless adapter r8712u needs physical disconnect and reconnect for firmware to work

On 25/05/2024 at 22:10, Roland Clobus wrote: When I run the Debian installer, the missing firmware file is correctly identified and installed by 'check-missing-firmware.sh'. However, the kernel module is mis-identified as 'usb'. This is a more generic issue already reported in #1033679

Re: migrating grub from BIOS to UEFI loses /etc/default/grub

On 24/05/2024 at 11:08, Harald Dunkel wrote: if I migrate a bookworm installation from grub-pc to grub-uefi, then grub-pc.postrm removes /etc/default/grub on the final purge. AFAICT /etc/default/grub is still processed for UEFI, so why is it deleted? It is a known bug. At the very least, /etc

Bug#1034812: Unbootable after install: UEFI installed to wrong ESP

On 17/05/2024 at 13:22, Jmkr wrote: Pascal Hambourg wrote: You can set an alternative name and location by running grub-install with --bootloader-id= or with GRUB_DISTRIBUTOR= in /etc/default/grub. It also affects the directory name in the ESP. But depending on the grub package version

Bug#1034812: Unbootable after install: UEFI installed to wrong ESP

On 10/05/2024 at 00:52, Jmkr wrote: Pascal Hambourg wrote: You could just run grub-install to reinstall GRUB into the new ESP and register it in EFI boot variables. I wanted to try the manual way to learn + to create my EFI boot entry with a customized name. I think GRUB installation can

Bug#1034812: Unbootable after install: UEFI installed to wrong ESP

On 09/05/2024 at 12:42, Jmkr wrote: - I archived "/boot/efi/EFI/debian/grubx64.efi" from "/dev/sda1" to "/ Archive.tar". - Then, I unmounted "/dev/sda1" from "/boot/efi" and mounted "/dev/sdb1" to "/boot/efi" and extracted "/Archive.tar" in "/boot/efi" again. - Later I changed UUID of ESP in "

Bug#1055583: base-files: EFI System Partition should mount on /efi not /boot/efi

On 15/04/2024 at 13:51, Santiago Vila wrote: In this bug report, I'm asked to provide /efi as a mount point for the EFI partition. Given that base-files does not even contain /boot/efi (the supposedly "old" location), I believe this is a decision for you to make, hence the reassign. partm

Bug#1068833: discover: A game installed via Discover doesn't start

Control: reassign -1 plasma-discover 5.27.5-2 On Thu, 11 Apr 2024 21:49:48 + Ilkka Kallioniemi wrote: On Thu, 11 Apr 2024 21:45:53 +0200 Pascal Hambourg wrote: > Discover is a hardware identification system. Aren't your confusing with > plasma-discover ? Yes, I am. Sorry fo

Bug#1068833: discover: A game installed via Discover doesn't start

On 11/04/2024 at 20:22, Ilkka Kallioniemi wrote: Package: discover (...) When installing game MegaGlest using Discover, the installed game is not fully installed. Discover is a hardware identification system. Aren't your confusing with plasma-discover ?

Re: removing grub-legacy from Debian

Hi Felix, On 03/03/2024 at 14:28, Felix Zielcke wrote: we plan to totally remove GRUB Legacy from Debian. But grub-installer still has references to the old grub package. Especially if multipath is used. grub2 has long time ago gained support for the multipath devices. See #442382 [1] Anyone

Bug#769738: marked as done (debian-installer: Please automatically mount /usr in rescue mode)

On 02/03/2024 at 15:45, Debian Bug Tracking System wrote: Your message dated Sat, 2 Mar 2024 15:42:38 +0100 with message-id and subject line Re: #769738: split usr is unsupported Seriously ? has caused the Debian Bug report #769738, regarding debian-installer: Please automatically mount /usr

Bug#1065048: installation-reports: partition tool in d-i remembers choices; 'delete partition' (encrypted Part.) always stays 'yes'

On 29/02/2024 at 08:51, Frank Weißer wrote: Comments/Problems: 2nd NIC gets eth0 on reboot, 2nd NIC gets eth1 :-( eth* names are no persistent and may change at any boot. But ethernet interface should get predictable names like enpXsY or enoX. In /proc/interrupts we can see enp1s0. randomize

Bug#1064624: Hard to short-stroke an encrypted drive

On 27/02/2024 at 08:42, Philip Hands wrote: Matthew Wilcox writes: I want "use largest contiguous space and set up encrypted LVM". That would let me reserve 200GB of my SSD as unencrypted free space, which will improve the write endurance of my SSD. Can one achieve this by telling LVM to all

Bug#1064624: Hard to short-stroke an encrypted drive

On 26/02/2024 at 01:14, Matthew Wilcox wrote: - create a logical volume in the free VG space - blkdiscard the logical volume Last time I checked, dm-crypt did not pass DISCARD requests through to the underlying device because it's a security hazard. AFAICS dm-crypt and cryptsetup have suppo

Bug#1064624: Hard to short-stroke an encrypted drive

On 25/02/2024 at 23:55, Matthew Wilcox wrote: I want "use largest contiguous space and set up encrypted LVM". That would let me reserve 200GB of my SSD as unencrypted free space, which will improve the write endurance of my SSD. Alternatively, the installer allows to reserve free space in the

Bug#1064624: Hard to short-stroke an encrypted drive

On 25/02/2024 at 05:40, Matthew Wilcox wrote: The partitioner "guided partitioning" offers me: - use the largest continuous free space - use entire disk - use entire disk and set up LVM - use entire disk and set up encrypted LVM I want "use largest contiguous space and set up encrypted

Bug#1064617: Passwords should not be changed frequently

On 25/02/2024 at 01:17, Matthew Wilcox wrote: I just did an installation with the 2024-02-24 debian-testing-amd64-netinst.iso image. I forget the exact wording used, but when setting up a user, d-i printed advice that user passwords should be changed frequently. This is no longer current good

Bug#1064010: Kernel not compiling missing file drm_irq.h

On 15/02/2024 at 18:08, Joshua Brickel wrote: Whe running apt-get upgrade I get erors about the kernel installing/building and it tells me to look in the file /var/lib/dkms/evdi/1.7.0/build/make.log Are you doing an installation or an upgrade ? From/to which version(s) ? make[2]: *** [/usr/

Re: Debian installation wifi card not being detected

On 10/02/2024 at 20:06, Andrew M.A. Cater wrote: It may also be possible to tether via a cable to a mobile phone and do the netinst install that way. Right, sorry for not mentioning it in my previous reply. The OP mentioned in debian-user that they have an iOS (Apple) device. The package i

Re: Debian installation wifi card not being detected

On 10/02/2024 at 12:48, Exeonz wrote: I'm trying to install debian bookworm 12.4 on MacbookAir7,2 that doesn't have an ethernet port and the installer doesn't recognize it's wifi card and what drivers it needs for the card to work. From searching the web I found that it uses Broadcom BCM 4360 wir

Bug#1060422: partman-crypto: add support for new cryptsetup options for opal/sed

On 11/01/2024 at 12:56, Luca Boccassi wrote: Yes it is a firmware feature, so it depends on the hardware, and in all drives I know of that will be the case, yes. From that point of view, to me it doesn't seem that far away from dm-crypt using the CPU's AES- NI to actually encrypt/decrypt data, o

Bug#1060368: partman-auto: add basic support for loongarch64

Hello, On 10/01/2024 at 04:15, zhangdandan wrote: Support automatic partition adaptation partman-auto for debian-installer. Please consider the patch (my local patch) I have attached. I do not know anything about the loongarch64 architecture, but I can't help having questions about the propo

Bug#1059370: Installation did not work: Kernel panic, see below

nstallation log (/var/log/installer/syslog) please ? I also activated 'GRUB_DISABLE_OS_PROBER=false' so Ubuntu is also taken along, for all cases (so said in germany...). Then this process is finished for me and I thank you for your help, Christian Am Mittwoch, dem 27.12.2023 um

  1   2   3   >