[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#943685: installation-reports: Missing modules for all ethernet NICs



Package: installation-reports
Severity: important

I have never seen this problem before with debian testing installer, but here it is


3d1f1fbae2fa937f6af9a71e96dbad10f9ce8ce1f0210deb1ac069b57f074948  debian-testing-amd64-netinst.iso

https://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd/debian-testing-amd64-netinst.iso

2019-10-27 22:45 	338M


I tried Expert install in virt-manager with qemu, both with rtl8139
emulated device, and with e1000e to no success. lspci does show them.

/lib/modules/5.2.0-3-amd64/kernel/drivers/net/ethernet/ has only one file: broadcom/cnci.ko

The debian installer says:


"No kernel modules were found. This is probably due to a missmatch
between kernel used by this version of the installer and the kernel
version available in the archive."


Ugh? I don't have access to any network yet, so I am not sure what
archive debian installer is talking about.


If it included different kernel to boot and different modules on the
medium that is definitively a bug in the debian installer build process
or in live wrapper or something.

In debug console it shows:

cdrom-retriever: warning: File /cdrom/dists/bullseye/main/debian-installer/binary-amd64/Packages does not exist.
(PS. Packages.gz does exists there tho).
cdrom-retriever: warning: Unable to find contrib/debian-installer/binary-amd64/Packages in /cdrom/dists/bullseye/Release.
cdrom-retriever: warning: Unable to find contrib/debian-installer/binary-amd64/Package.gz in /cdrom/dists/bullseye/Release.
anna[2050]: WARNING **: no packages matching running kernel 5.2.0-3-amd64 in archive




I did check manually zcat
/cdrom/dists/bullseye/main/debian-installer/binary-amd64/Packages.gz and
it does list multiple udeb packages for kernel 5.3.0-1-amd64-di. For
example nic-modules-5.3.0-1-amd64-di_5.3.7-1_amd64.udeb

The file does exist on the medium, and is 4.0MB.

The running kernel is 5.2.0-3-amd64

So maybe the issue is with the "-di" suffix?


Regards,
Witold



-- System Information:
Debian Release: bullseye/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'testing-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/32 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled


Reply to: