[Kernel-packages] [Bug 1543919] Re: Remove EISA support from main kernel image and make it M (modular)
I've an emachines®/acer® EL1210-09 (Advance Micro Devices Inc. Athlon LE-1620 (P/N ADH1620IAA5DH); nVIDIA® nForce® 780a SLI with planar C77 a2 GPU; nVIDIA® GF119 a1 GPU on PCIe 2.0 x16 slot). The system DMesg predictably detects no EISA resources on probing platform eisa.0, so EISA.c and related headers can be compiled as a module with no effect on my system's kernel initialization. AFAIK, Intel PCI has replaced EISA on all x86 and x86_64 systems built after 2000. The following redact from /var/log/dmesg.0 on 17 July 2021 illustrates typical info: [0.00] kernel: Linux version 5.8.0-59-generic (buildd@lcy01-amd64-022) (gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0, GNU ld (GNU Binutils for Ubuntu) 2.34) #66~20.04.1-Ubuntu SMP Thu Jun 17 11:14:10 UTC 2021 (Ubuntu 5.8.0-59.66~20.04.1-generic 5.8.18) [0.00] kernel: Command line: BOOT_IMAGE=/vmlinuz-5.8.0-59-generic root=UUID=c4248af1-a4cf-49a2-ba18-4de2c65c815c ro acpi_force_32bit_fadt_addr acpi_rev_override check_enable_amd_mmconf pcie_bus_tune=off pcie_aspm=off pci_ports=native intremap=off agp=off nohugeiomap parport=0 hashdist=0 ... [0.212298] kernel: EISA bus registered ... [1.006643] kernel: platform eisa.0: Probing EISA bus 0 [1.006715] kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard [1.006779] kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 [1.006855] kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 [1.006917] kernel: platform eisa.0: EISA: Detected 0 cards I concur on the feasibility of offloading EISA from Kernel core and building a Module EISA.ko. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1543919 Title: Remove EISA support from main kernel image and make it M (modular) Status in linux package in Ubuntu: Triaged Bug description: (This is a sort of RfC. ) I have a PC that still has the good old PCI ports, but I am 100% sure that the active use of EISA dates back yet more 10 years. In other words, boards that _only_ support EISA date back 25 years now, while those that provide *one* EISA slot date back roughly 15 years (one of the Elitegroup K7 series comes to mind, from about 2001/02). So the EISA support *should* be provided, as we should even support ancient hardware (Linux principle :)) However, why the EISA support is *compiled in* is beyond me. For instance, it creates lots of totally unnecessary noise in dmesg: [0.08] EISA bus registered [1.598316] platform eisa.0: Probing EISA bus 0 [1.598345] platform eisa.0: Cannot allocate resource for EISA slot 1 (repeated 10 times, i=i+1) [1.598368] platform eisa.0: EISA: Detected 0 cards For a 1997 mainboard, this would make perfect sense. But it is very probable that said mainboard would require linux-image-extra nonetheless to support some days-of-yore chipset. So why not leave it as a *module*, while removing its support from main kernel image once and for all? Your turn. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1543919/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Update: Issue worked around with nVIDIA® geForce® driver 340.107 for C77 GPU in MCP78 northbridge (package:nvidia-340). Repeating report to Bug 1776616. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
Update: nVIDIA® geForce® driver 340.107 for the C77 GPU (package: nvidia-340) got to a successful power-down. Be advised that Packages nvidia-n are to be reserved for nVIDIA® nFORCE® MCP chipsets such as the MCP78 northbridge my EL1210-09; intel®, AMD®, and VIA® chipsets require different solutions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
Update: acpi=off only got me to a timestamped kernel message "reboot:System halted". acpi=force had no effect. Repeating report to Bug 1776616, which is specifically relevant to Kernel 4.15-n-generic on xubuntu™ 18.04-LTS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"
I encountered this issue installing xubuntu™ 18.04-LTS on an emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon® LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a Shuttle® PSU upgrade (PC631 in for stock 220W LITEON®) and the planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an msi® N610GT-MD1GD3/LP half-height video display adapter. I normally use: GRUB_CMDLINE_LINUX_DEFAULT="debug" in /etc/default/grub, which is how I confirmed the issue: Depending on shutdown or reboot option, the system halts at "Starting reboot..." or "Starting power-off...", forcing a manual power-down. Additionally: GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=force" had no effect, and: GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=off" only got me to a timestamped "reboot:System halted". Will report back after checking effect of nVIDIA® geForce® driver package for C77 GPU (part of nF720 chipset). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776616 Title: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power- Off" Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Hardware: HPE ProLiant DL360 gen9 Ubuntu Version: 18.04 Problem: When rebooting the server, everything goes well (shutting down services, unmounting etc) until the last step where it reads "Starting Reboot". At this point the system is getting stuck and nothing else can can be done than holding the power button in for a long enough time to turn it off. At the same time as the system get stuck, a red error light is lightening up on the server. This light is green until it reaches this "Starting Reboot" stage. The same happens if the server is shutdown, with the difference that the last message is "Starting Power-Off" instead of "Starting Reboot". The server is installed with a new clean 18.04 installation. This server was rebooting/shutting down without a problem with all releases between 16.04 and 17.10. This problem is serious as it prevents remote reboot. --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 13 11:16 seq crw-rw 1 root audio 116, 33 Jun 13 11:16 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=none MachineType: HP ProLiant DL360 Gen9 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic root=ZFS=rpool/ROOT/ubuntu ro ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-23-generic N/A linux-backports-modules-4.15.0-23-generic N/A linux-firmware 1.173.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: bionic Uname: Linux 4.15.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 05/21/2018 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1594023] Re: Poweroff or reboot hangs. Laptop won't shutdown. 16.04
This hang on shutdown and/or reboot is NOT confined to portables. I encountered the issue installing xubuntu™ 18.04-LTS on an emachines®/acer® EL1210-09 (2.3 GHz Advanced Micro Devices® Athlon® LE-1620; nVIDIA® nFORCE® 720 chipset; 2 x 2 GiB DDR2 main memory) with a Shuttle® PSU upgrade (PC631 in for stock 220W LITEON®) and the planar C77 geForce® 64-bit GPU by-passed for the nVIDIA® GF-109 on an msi® N610GT-MD1GD3/LP half-height video display adapter. I normally use: GRUB_CMDLINE_LINUX_DEFAULT="debug" in /etc/default/grub, which is how I confirmed the issue: Depending on shutdown or reboot option, the system halts at "Starting reboot..." or "Starting power-off...", forcing a manual power-down. Will report back after testing: GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=off" and: GRUB_CMDLINE_LINUX_DEFAULT="debug acpi=force" I'd rather save the C77 geForce® driver set (provided to Canonical Ltd. by nVidia Corporation) for the nFORCE® 720 as a last resort, as it affects Kernel behavior in both startup and shutdown. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1594023 Title: Poweroff or reboot hangs. Laptop won't shutdown. 16.04 Status in linux package in Ubuntu: Confirmed Bug description: This is about a fresh Ubuntu 16.04 install on a new laptop (asus x540sa). After pressing the shutdown button in the start menu; the shutdown procedure starts and in the final splash screen the system just hangs. Tried a second time by pressing Esc once the splash screen showed up and I saw that it reaches the line "Reached target shutdown" and just stops there, no matter how long I leave it there the machine won't turn off. I also tried a Kubuntu 16.04 fresh install on the same machine and it hanged too at the final splash screen where the pulsating logo stopped. Then I tried with Esc only to see the exact same line in the end. The issue seems to affect lately quite many users as shown by the google results of the past month / week or so. I have also tried shutting down from the console with shutdown -and all the parameters after that suggested online- and sudo poweroff but unfortunately they didn't do the trick. The exact same situation occurred. Unmounting the swap as suggested online doesn't work. Also rebooting the system is not working either due to the same issue. So right now the only way for me to poweroff the machine is to press the power button on the keyboard continuously. Reproducible: Always Steps to Reproduce: 1.Install OS 2.Do something, anything or nothing 3.Try to shutdown or reboot Actual Results: The computer is not shutting down: "Reached target shutdown" and hangs there. Expected Results: Powering off the machine. For what it's worth, closing the lid won't suspend the system, but using the menu buttons for suspension will do it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1594023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present
** Summary changed: - linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present + linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.img-4.8.0 when no corresponding vmlinuz present Status in linux-firmware package in Ubuntu: Confirmed Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade linux-firmware. Therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No attempt to generate /boot/initrd.img for missing kernels, thus no warnings, errors or fatals. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773476/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
Observed sequence of sbins when software-updater called apt-get upgrade linux-firmware: Cross-checking initramfs-tools and depmod for any misbehaviors that might exacerbate what I've observed. DIOSCOVERED POINT TO INVESTIGATE: Potential for Dependency this Bug on Bug #701578 "purging a kernel sometimes fails to remove kernel in armel" in initramfs-tools (ubuntu). ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic - Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. - --- + Same configuration report for "Setting up linux-firmware..." with sudo + apt(-get) install (--reinstall) linux-firmware and sudo apt-get upgrade + linux-firmware. Therefore: + + Reproducible: Always + Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. + Actual results, excepting actually installed Kernel Image packages: + + update-initramfs: Generating /boot/initrd.img-4.8.0-56 + WARNING: missing /lib/modules/4.8.0-56 + Ensure all necessary drivers are built into the linux image! + depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory + depmod: FATAL: could not search modules: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory + update-initramfs: Generating /boot/initrd.img-4.8.0 + WARNING: missing /lib/modules/4.8.0 + Ensure all necessary drivers are built into the linux image! + depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory + depmod: FATAL: could not search modules: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory + depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory + + Expected results, excepting actually installed Kernel Image packages: + + No attempt to generate /boot/initrd.img for missing kernels, thus no + warnings, errors or fatals. + + --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: - + DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz
[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
Update: A purge and reinstall of linux-firmware produces same results. Summary therefore: Reproducible: Always Steps to reproduce: sudo apt install (--reinstall) linux-firmware or sudo dpkg-reconfigure linux-firmware. Actual results, excepting actually installed Kernel Image packages: update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory Expected results, excepting actually installed Kernel Image packages: No warning, errors or fatals. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present Status in linux-firmware package in Ubuntu: Confirmed Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
** Changed in: linux-firmware (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present Status in linux-firmware package in Ubuntu: Confirmed Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773476] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1773476/+attachment/5144521/+files/ProcEnviron.txt ** Tags removed: apport-collected bionic third-party-packages -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present Status in linux-firmware package in Ubuntu: Incomplete Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. --- ApportVersion: 2.20.1-0ubuntu2.17 Architecture: amd64 CurrentDesktop: Unity Dependencies: DistroRelease: Ubuntu 16.04 InstallationDate: Installed on 2017-05-17 (373 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) Package: linux-firmware 1.157.19 [origin: unknown] PackageArchitecture: all ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 Tags: xenial third-party-packages Uname: Linux 4.15.0-22-generic x86_64 UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1773476] Re: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
apport information ** Package changed: linux (Ubuntu) => linux-firmware (Ubuntu) ** Tags added: apport-collected third-party-packages xenial ** Description changed: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic - Same configuration report for "Setting up linux-firmware..." with sudo - apt(-get) install (--reinstall) linux-firmware. + Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. + --- + ApportVersion: 2.20.1-0ubuntu2.17 + Architecture: amd64 + CurrentDesktop: Unity + Dependencies: + + DistroRelease: Ubuntu 16.04 + InstallationDate: Installed on 2017-05-17 (373 days ago) + InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) + Package: linux-firmware 1.157.19 [origin: unknown] + PackageArchitecture: all + ProcVersionSignature: Ubuntu 4.15.0-22.24~16.04.1-generic 4.15.17 + Tags: xenial third-party-packages + Uname: Linux 4.15.0-22-generic x86_64 + UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again. + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1773476/+attachment/5144520/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present Status in linux-firmware package in Ubuntu: Incomplete Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such
[Kernel-packages] [Bug 1773476] [NEW] linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present
Public bug reported: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1773476 Title: linux-firmware 1.157.19 attempts to generate /boot/initrd.img-4.8.0-56, /boot/initrd.ing-4.8.0 when no corresponding vmlinuz present Status in linux package in Ubuntu: Incomplete Bug description: With LinUX Images/-Extras 4.15.0-22-generic, 4.13.0-43-generic, 4.8.0-58-generic, 4.8.0-56-generic, and 4.4.0-127-generic installed, sudo dpkg-reconfigure linux-firmware returns the following to Console: update-initramfs: Generating /boot/initrd.img-4.15.0-22-generic update-initramfs: Generating /boot/initrd.img-4.13.0-43-generic update-initramfs: Generating /boot/initrd.img-4.8.0-58-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56-generic update-initramfs: Generating /boot/initrd.img-4.8.0-56 WARNING: missing /lib/modules/4.8.0-56 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0-56: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_AlVft4/lib/modules/4.8.0-56/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.8.0 WARNING: missing /lib/modules/4.8.0 Ensure all necessary drivers are built into the linux image! depmod: ERROR: could not open directory /lib/modules/4.8.0: No such file or directory depmod: FATAL: could not search modules: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.order: No such file or directory depmod: WARNING: could not open /var/tmp/mkinitramfs_OwnjIb/lib/modules/4.8.0/modules.builtin: No such file or directory update-initramfs: Generating /boot/initrd.img-4.4.0-127-generic Same configuration report for "Setting up linux-firmware..." with sudo apt(-get) install (--reinstall) linux-firmware. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1773476/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
