#1005886 cdimage.debian.org: bookworm net-install CD hangs on "Detecting Network Hardware"

#1005886#5
Date:
2022-02-16 17:32:40 UTC
From:
To:
Dear Maintainer,

For a few days I've been trying to install Debian bookworm using the net-install ISO (e.g., all of today's). All of them hang when it reaches the "Detecting Network Hardware". I'm able to switch to the log console, and everything seems to be fine, however, that step doesn't work. If I go to the disk partitioning step, I have the same problem.

It feels that the options are not displayed.

Cheers,
Tony

#1005886#10
Date:
2022-02-16 17:54:21 UTC
From:
To:
I've tried all amd64 ISO-CD installers available here:
https://cdimage.debian.org/cdimage/daily-builds/daily/

The computer is:
Lenovo X1 Carbon Gen 6
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz
Intel Dual Band Wireless-AC 8265 (iwlwifi loads fine, during installation)
Intel Ethernet Connection (4) I219-LM
Samsung Electronics NVMe SSD Controller SM981/PM981/PM983

Everything is currently working fine with Debian bullseye, therefore,
it shouldn't be an hardware problem.

#1005886#15
Date:
2023-03-11 10:03:20 UTC
From:
To:

#1005886#26
Date:
2023-03-22 11:54:29 UTC
From:
To:
Sorry (both to you Tony, and also the Debian CD team) for confusion and wasting
time - I mistakenly reassigned this previously.  I've checked the list of
bug-tracking pseudo-packages[1] and I do think that cdimage.debian.org is the
correct package for this bug to be assigned to.

[1] - https://www.debian.org/Bugs/pseudo-packages

#1005886#35
Date:
2023-03-22 12:28:22 UTC
From:
To:
James Addison <jay@jp-hosting.net> (2023-03-22):

Hi Tony,

Please attach /var/log/syslog (compressed).


Cheers,

#1005886#44
Date:
2024-08-25 12:27:21 UTC
From:
To:
Hi Tony,
to attempt to replicate this bug using the bookworm 12.6.0 netinst ISO, and
similarly a recent daily trixie netinst ISO (from 2024-08-24).

I haven't been able to replicate the problem using either of those images;
however, if you still encounter it then please do attach the relevant syslog,
as Cyril mentioned, so that we can find and fix the problem.

I'll note that I know from experience with the Intel 826x chipset that there
have been fixes/improvements in the Linux kernel for it recently; it's possible
that those may have resolved the problem.  It would be nice to confirm exactly
what the cause of the bug was, but even if we cannot achieve that, then there
there is also value in confirming whether this bug still occurs at all.

Note: if you have Secure Boot enabled, and re-test using non-recent ISO images,
then you may encounter boot-time errors related to SBAT since the grub
version(s) in use in those images are no longer considered trusted.

Thanks,
James

[1] - https://lwn.net/Articles/986844/