Bug#1143094: hw-detect: Fails to detect network card under BIOS boot in qemu
Roland Clobus <[email protected]>
| Newsgroups | gmane.linux.debian.devel.bugs.rc |
|---|---|
| Message-ID | <[email protected]> |
Source: hw-detect User: [email protected] Usertags: amd64 X-Debbugs-Cc: [email protected] User: [email protected] Usertags: amd64 X-Debbugs-Cc: [email protected] Version: 1.176 Severity: grave Justification: renders package unusable Tags: d-i Hello maintainers of hw-detect, The new version of ethdetect.sh does not detect the network interfaces when booting from BIOS. This can be seen on openQA [1] where the installer fails to find the network interfaces for the BIOS scenarios. The UEFI scenarios still work. From the d-i syslog (broken, BIOS) [2]: Jul 29 21:33:12 main-menu[430]: INFO: Menu item 'ethdetect' selected Jul 29 21:33:17 net/hw-detect.hotplug: Detected hotpluggable network interface lo Jul 29 21:33:18 net/hw-detect.hotplug: Detected hotpluggable network interface ens4 Jul 29 21:33:18 kernel: [ 30.969705] virtio_net virtio0 ens4: renamed from eth0 Jul 29 21:33:19 check-missing-firmware: looking at dmesg for the first time Jul 29 21:33:19 check-missing-firmware: saving timestamp for a later use: [ 30.969705] Jul 29 21:33:19 check-missing-firmware: no missing firmware in loaded kernel modules From the d-i syslog (last working, BIOS) [3]: Jul 29 16:03:07 main-menu[430]: INFO: Menu item 'ethdetect' selected Jul 29 16:03:13 net/hw-detect.hotplug: Detected hotpluggable network interface lo Jul 29 16:03:13 kernel: [ 31.465192] virtio_net virtio0 ens4: renamed from eth0 Jul 29 16:03:13 net/hw-detect.hotplug: Detected hotpluggable network interface ens4 Jul 29 16:03:14 check-missing-firmware: looking at dmesg for the first time Jul 29 16:03:14 check-missing-firmware: saving timestamp for a later use: [ 31.465192] Jul 29 16:03:14 check-missing-firmware: no missing firmware in loaded kernel modules Jul 29 16:03:14 check-missing-firmware: taking network interface ens4 up/down Jul 29 16:03:15 check-missing-firmware: looking at dmesg again, restarting from timestamp: [ 31.465192] Jul 29 16:03:15 check-missing-firmware: timestamp found, truncating dmesg accordingly Jul 29 16:03:15 check-missing-firmware: keeping timestamp (no new lines): [ 31.465192] Jul 29 16:03:15 check-missing-firmware: no missing firmware in loaded kernel modules After 1.176 entered unstable, all BIOS installer tests started to fail. There are no version differences in the other udebs, so that's why I report against hw-detect. I think it might be caused by the 'Change hw-detect/firmware-lookup type to string' change, since that influences whether the network interface is taken down and up again. With kind regards, Roland Clobus [1] https://openqa.debian.net/tests/overview?build=20260729-7&distri=debian&version=testing [2] https://openqa.debian.net/tests/554214/logfile?filename=syslog.txt [3] https://openqa.debian.net/tests/554110/logfile?filename=complete_install-DI_syslog.txt
OpenPGP_signature.asc
(application/pgp-signature, 833 B)
-----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEUFVLM5Bdj7GSJEb+YsV8aqYUlb0FAmprLdAACgkQYsV8aqYU lb2rlg/9GNX4mTB+Ljd1o2Bw3yYAS/YbAm5XhOShfCmUtWyHqXoFci37FUMkjo4a dpJGzhnWmA8t1q21S1CgHrDAwjIgARCEVL42kFg7AQT9Uu6iKDMDEG1Umz1aEVne hIwuBamQMCNAX5X6aIT/tUf+zrdNCu0MpUwiiuhLDm/vTcF6XNPsOC+RbkvR/vmn a5iDU7hiy6c77dXg+Oj9Tw1+7Pds3yFNeqR9QJ21CHYsT0xjfe3B35fMcq0FwUC5 ljLAYOau1Nmlrvsu93lYHE68/Y9SEqclTlULJyK6LzQv8YTDUYgGRcmO+r9jKRU2 Mj/TXUreIRk1h4ZWX17Y3JWptzP+MoR6apczVqHdIG+xMaH7akcohyv4dup8fMHt nacMo76cr1d0wPY2zSyQk5Xixu1OtpYC+5DJG8F/Eml3jg4TJ0Isl2mCg1XoaRQ5 3SMdReQW9LbXnMik7RvgifY2DuL17A0kuNaR69HCEDRCLoDQkF23nkCf9mhLRtJy dLdpaVWWBbo9vHFYRt2aslUACCQZ/GzloX4kbq1V+oBMrzR9AaHTkxfFoMT2Z8B0 eauGeDAsNSwX1EMK/hEw1hJl7beRR8GoH7KjZ+3aOBp+CJ3VSZ6ZBg59myQefM6T 9EFuKGatjH4nNn9gFTd/yH8Gsv4mrIc1sxpJYNXFnqCFfSwbOrg= =6OYM -----END PGP SIGNATURE-----