Multiple issues on HP ZBook 15 G7 after installing 20.04.2 image

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1914374

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

There is because the corresponding drivers is not be installed.

E.g. iwlwifi for AX201 wireless module.

In this case, the iwlwifi is in linux-modules-extra-5.8.0-41-generic.

So, the real issue is why the linux-modules-extra-5.8.0-41-generic is not be installed during the installation.

Could we get some more logs of such an installation? Would be nice to get the at least the ubiquity installer logs, maybe the list of packages on the system too.
Not sure what went wrong here - is this a device that should get the OEM stuff pulled in during installation? Since if that's the case, maybe something didn't quite work which would explain why so many drivers are missing.

Feb 3 06:56:32 ubuntu ubiquity: Removing linux-generic-hwe-20.04 (5.8.0.41.46~20.04.27) ...#015
Feb 3 06:56:32 ubuntu ubiquity: Removing linux-headers-generic-hwe-20.04 (5.8.0.41.46~20.04.27) ...#015
Feb 3 06:56:32 ubuntu ubiquity: Removing linux-headers-5.8.0-41-generic (5.8.0-41.46~20.04.1) ...#015
Feb 3 06:56:32 ubuntu ubiquity: Removing linux-hwe-5.8-headers-5.8.0-41 (5.8.0-41.46~20.04.1) ...#015
Feb 3 06:56:32 ubuntu ubiquity: Removing linux-image-generic-hwe-20.04 (5.8.0.41.46~20.04.27) ...#015
Feb 3 06:56:32 ubuntu ubiquity: Removing linux-modules-extra-5.8.0-41-generic (5.8.0-41.46~20.04.1) ...#015
Feb 3 06:56:33 ubuntu ubiquity: Removing linux-modules-nvidia-460-generic-hwe-20.04-edge (5.8.0-41.46~20.04.1) ...#015
Feb 3 06:56:33 ubuntu ubiquity: Removing linux-modules-nvidia-460-5.8.0-41-generic (5.8.0-41.46~20.04.1) ...#015

Those packages were removed by ubiquity

The attachment is from /var/log/installer

Feb 3 06:48:34 ubuntu ubiquity[1938]: ubuntu-drivers list-oem finished with: "oem-stella.cmit-meowth-meta"

$ pull-lp-debs oem-stella.cmit-meowth-meta focal

$ less oem-stella.cmit-meowth-meta_20.04~ubuntu1_all.deb | grep Kernel
 Ubuntu-Oem-Kernel-Flavour: oem

Feb 3 06:55:03 ubuntu ubiquity: Setting up linux-oem-20.04 (5.6.0.1042.38) ...#015

The machine in question is expected to install oem-stella.cmit-meowth-meta; remove the 5.8 hwe kernel; install linux-oem-20.04 v5.6 kernel.

The question is if this system working correctly with v5.6 oem kernel; or if it should be using the default v5.8 kernel.

If you wish to switch it to v5.8 kernel for the installed system, then we will need to upload new oem-meta and respin the iso asap.

Please note that v5.10 oem kernel is not available on the installation iso.

I saw oem-stella.cmit-meowth-meta 20.04ubuntu11 in http://hp.archive.canonical.com/dists/focal/stella.cmit/binary-amd64/Packages depends on oem-fix-gfx-nvidia-1868199, but I can not find oem-fix-gfx-nvidia-1868199 on http://hp.archive.canonical.com/pool/public/o/.
So the dependencies of oem-stella.cmit-meowth-meta in OEM archive is broken.

Have we checked the installation without Internet? Will it still fail?

We have found the issue and are working actively on a fix - we actually have one already but we're just want to confirm that it indeed works and, at least as much as we can, checking that it doesn't regress anything else.

Hello Lukas, or anyone else affected,

Accepted ubuntu-drivers-common into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.8.6.5~0.20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Lukas, or anyone else affected,

Accepted ubiquity into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/20.04.15.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Ok, just did a quick sanity test of the new ubiquity (20.04.15.7) and ubuntu-drivers-common (1:0.8.6.5~0.20.04.1). I have booted up the last .2 RC, downloaded xnox's ubuntu-drivers mock wrapper, installed its dependencies (via universe), upgraded ubiquity and ubuntu-drivers-common and then started the installation. The installation finished with success. I then checked the syslog to see if the right kernel and nvidia drivers combination has been used - all good: oem kernel, no hwe kernel installed, oem nvidia drivers. I also checked if any -edge kernel packages have been selected by mistake - there were none.

I think this is enough of a validation that the packages are sane at least. Let's get it migrated to -updates and then test some more on the RC images.

The verification of the Stable Release Update for ubiquity has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5~0.20.04.1

---------------
ubuntu-drivers-common (1:0.8.6.5~0.20.04.1) focal; urgency=medium

  * tests/test_ubuntu_drivers.py:
    - Add testcase for list-oem --package-list (LP: #1914051).
  * UbuntuDrivers/detect.py:
    - Fix the way we validate the nvidia modules metapackages
      (LP: #1914374).

 -- Alberto Milone <email address hidden> Wed, 03 Feb 2021 19:23:18 +0100

This bug was fixed in the package ubiquity - 20.04.15.7

---------------
ubiquity (20.04.15.7) focal; urgency=medium

  [ Dimitri John Ledkov ]
  * install_misc: refuse to install packages that have been marked for removal.
    This should generally fix issues we've been seeing with installations using
    the OEM metapackages. (LP: #1914374)

 -- Łukasz 'sil2100' Zemczak <email address hidden> Wed, 03 Feb 2021 21:29:05 +0100

Verified by using 'focal-desktop-amd64.iso' from http://cdimage.ubuntu.com/focal/daily-live/pending/

SHA256 e2ce1771e352b04cfdef5bf6583f6a7d62b1f2967903fae512506d18d251a434 *focal-desktop-amd64.iso

$ sha256sum focal-desktop-amd64.iso
e2ce1771e352b04cfdef5bf6583f6a7d62b1f2967903fae512506d18d251a434 focal-desktop-amd64.iso

I tested the machine with today's new image and everything looks good now.

This bug was fixed in the package ubuntu-drivers-common - 1:0.8.6.5

---------------
ubuntu-drivers-common (1:0.8.6.5) hirsute; urgency=medium

  * tests/test_ubuntu_drivers.py:
    - Add testcase for list-oem --package-list.
  * UbuntuDrivers/detect.py:
    - Fix the way we validate the nvidia modules metapackages
      (LP: #1914374).

 -- Alberto Milone <email address hidden> Wed, 03 Feb 2021 19:13:21 +0100

This bug was fixed in the package ubiquity - 21.04.11

---------------
ubiquity (21.04.11) hirsute; urgency=medium

  [ Didier Roche ]
  [ Jean-Baptiste Lallement ]
  * Configure krb5 client so access to AD with GPO enabled works out of the
    box after installation.
  * Keep packages required for AD installed. When AD installation is selected
    we want to keep all the packages used to make it work and remove them
    otherwise.

  [ Dimitri John Ledkov ]
  * install_misc: refuse to install packages that have been marked for removal.
    This should generally fix issues we've been seeing with installations using
    the OEM metapackages. (LP: #1914374)
  * Merge netcfg 171 from Debian into ~ubuntu-installer repo, and subtree
    pull it in.
  * Automatic update of included source packages: netcfg 171ubuntu1
  * Build udebs with !noudeb profile set, to actually build with udebs.
  * Delete KeyboardNames.pl becuase it is annoying.
  * Automatic update of included source packages.
  * Properly drop dh-systemd build-dep from the d-i/update-control script.
  * Add symlink in netcfg mock_paths with and without _fn suffix, cause
    check in hirsute-release & hirsute-proposed want one or the other.

 -- Dimitri John Ledkov <email address hidden> Wed, 17 Mar 2021 02:22:11 +0000

Hello Lukas, or anyone else affected,

Accepted ubuntu-drivers-common into groovy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.0~0.20.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-groovy to verification-done-groovy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-groovy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Lukas, or anyone else affected,

Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.0~0.18.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello Lukas, or anyone else affected,

Accepted ubuntu-drivers-common into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu-drivers-common/1:0.9.0~0.18.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

The version of ubuntu-drivers-common in the proposed pocket of Bionic that was purported to fix this bug report has been removed because the bugs that were to be fixed by the upload were not verified in a timely (105 days) fashion.

An upload of ubuntu-drivers-common to bionic-proposed has been rejected from the upload queue for the following reason: "It doesn't seem like there is any interested in testing or organizing testing of this update. If someone turns up we can always accept the package from the rejected queue.".