5

I just tried to install the HWE stack using sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04, but it does not fully install. There is no boot image generated, nothing is loaded in /lib/modules for it, etc. What am I doing wrong?

Output of install command:

The following NEW packages will be installed:
  linux-generic-hwe-18.04 xserver-xorg-hwe-18.04
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/15.2 kB of archives.
After this operation, 248 kB of additional disk space will be used.
Selecting previously unselected package linux-generic-hwe-18.04.
(Reading database ... 407048 files and directories currently installed.)
Preparing to unpack .../linux-generic-hwe-18.04_4.18.0.15.65_amd64.deb ...
Unpacking linux-generic-hwe-18.04 (4.18.0.15.65) ...
Selecting previously unselected package xserver-xorg-hwe-18.04.
Preparing to unpack .../xserver-xorg-hwe-18.04_1%3a7.7+19ubuntu8~18.04.2_amd64.deb ...
Unpacking xserver-xorg-hwe-18.04 (1:7.7+19ubuntu8~18.04.2) ...
Setting up xserver-xorg-hwe-18.04 (1:7.7+19ubuntu8~18.04.2) ...
Setting up linux-generic-hwe-18.04 (4.18.0.15.65) ...

Output of uname -a

Linux my-computer-name 4.15.0-45-generic #48-Ubuntu SMP Tue Jan 29 16:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Output of attempting to manually install two apparently missing dependencies:

sudo apt install linux-image-generic-hwe-18.04 linux-headers-generic-hwe-18.04
[sudo] password for brandon: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
linux-headers-generic-hwe-18.04 is already the newest version (4.18.0.15.65).
linux-headers-generic-hwe-18.04 set to manually installed.
linux-image-generic-hwe-18.04 is already the newest version (4.18.0.15.65).
linux-image-generic-hwe-18.04 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Output of dpkg -l | grep linux-image

rc  linux-image-4.15.0-20-generic                   4.15.0-20.21                                 amd64        Signed kernel image generic
ii  linux-image-4.15.0-45-generic                   4.15.0-45.48                                 amd64        Signed kernel image generic
ii  linux-image-4.18.0-15-generic                   4.18.0-15.16~18.04.1                         amd64        Signed kernel image generic
ii  linux-image-generic                             4.15.0.45.47                                 amd64        Generic Linux kernel image
ii  linux-image-generic-hwe-18.04                   4.18.0.15.65                                 amd64        Generic Linux kernel image

Output of sudo update-grub

Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-45-generic
Found initrd image: /boot/initrd.img-4.15.0-45-generic
Found Windows Boot Manager on /dev/sdb1@/efi/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for EFI firmware configuration
done

[This laptop came preinstalled with Windows and used to run it, hence the WBM entry.]

Error when trying to manually reinstall image:

depmod: ERROR: could not open directory /lib/modules/4.18.0-15-generic: No such file or directory
depmod: FATAL: could not search modules: No such file or directory
dpkg: error processing package linux-image-4.18.0-15-generic (--configure):
 installed linux-image-4.18.0-15-generic package post-installation script subprocess returned error exit status 1

15
  • Please run this command and add the result to your question. And also post output of uname -a.
    – Pilot6
    Feb 20, 2019 at 15:26
  • Added to question.
    – Brandon
    Feb 20, 2019 at 15:50
  • It is not the full output. But if there were no errors, reboot now, and you will be on the 4.18 kernel. But I don't see real kernel modules installed.
    – Pilot6
    Feb 20, 2019 at 15:54
  • ...except that is the full output. There were no messages about installing boot images like I expected. After rebooting I'm still on the 4.15 kernel, and the only "advanced" boot options are to boot into that 4.15 kernel or the accompanying recovery mode.
    – Brandon
    Feb 20, 2019 at 15:55
  • This is a mystery linux-generic-hwe-18.04 depends on linux-image-generic-hwe-18.04 and linux-headers-generic-hwe-18.04. But I don't see them installed. Something is broken in your system.
    – Pilot6
    Feb 20, 2019 at 15:59

2 Answers 2

3

You can reinstall this kernel and modules with low-level commands (download and direct extract to the file-system):

apt-get download linux-image-4.18.0-15-generic
apt-get download linux-modules-extra-4.18.0-15-generic
apt-get download linux-modules-4.18.0-15-generic
apt-get download linux-headers-4.18.0-15-generic

sudo dpkg -x linux-image-4.18.0-15-generic*.deb /
sudo dpkg -x linux-modules-extra-4.18.0-15-generic*.deb /
sudo dpkg -x linux-modules-4.18.0-15-generic*.deb /
sudo dpkg -x linux-headers-4.18.0-15-generic*.deb /

sudo update-grub

then reinstall them with regular way:

sudo apt-get install --reinstall linux-image-4.18.0-15-generic
sudo apt-get install --reinstall linux-modules-extra-4.18.0-15-generic
sudo apt-get install --reinstall linux-modules-4.18.0-15-generic
sudo apt-get install --reinstall linux-headers-4.18.0-15-generic

and finally install the HWE:

sudo apt-get install --install-recommends linux-generic-hwe-18.04 xserver-xorg-hwe-18.04
7
  • Why would I need to also install the 4.15.0-20 kernel when I'm currently running the 4.15.0-45 kernel?
    – Brandon
    Feb 21, 2019 at 21:26
  • @Brandon thanks, it was a typo. You need 4.18.0-15.
    – N0rbert
    Feb 22, 2019 at 9:21
  • Is it normal for "Processing triggers for linux-image-*" to take forever to complete? It's been quite a while, and looking at htop it seems like nothing's happening. EDIT: Also is reporting that these processes are sleeping, not running.
    – Brandon
    Feb 24, 2019 at 4:54
  • It is not normal. I have never seen such behavior. Are you sure that your filesystem is clean? Try to force fsck with sudo touch /forcefsck and reboot.
    – N0rbert
    Feb 24, 2019 at 7:45
  • fsck seems to have ran with no issue. Same behavior is being experienced the second time around. If it helps, the cursor in that terminal window changes from flashing to solid on occasion, and ps -a shows that there are dkms processes running.
    – Brandon
    Feb 24, 2019 at 16:24
0

See the same problem when deploying Bionics with FAI. The initrd is not generated when installing HWE kernels. As a workaround after installing the HWE packages I also manually create initrd with

update-initramfs -c -k `ls -1 /lib/modules/ | head -2 | tail -1`
update-grub

It suppose to take the latest kernel version from /lib/modules..

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .