** Description changed:
This requires more input and is still awaiting the final MPs relevant
and discussed here. Therefor it is incomplete for the time being until
the information required is available.
## FFE ##
[Rationale]
* Extend the ubuntu-drivers capabilities to install packages in the
archive based on hardware information. This update allows ubuntu-drivers
to install packages based on dmidecode data (Nvidia RTX Spark machines)
and MIDR information (Vera Rubin), which do not posses other uniquely
identifiable attributes
* Having this in the ubuntu-drivers that is part of the ISO improves the
UX for people benefiting of these optimized packages.
[ Scope ]
* Adding two new matching mechanisms within ubuntu-drivers. Checking for
matches via dmidecode and checking the CPU MIDR values
* Dmidecode checking delivers a new binary package `dh-dmidecode`, which
can be used to substitute `XB-Dmidecode: ${dmialiases}` fields with
values from `debian/<packagename>.dmialiases.
- * [TODO] MIDR checking
+ * MIDR detection enables packages to list `XB-Midr: ..` in the control
+ file. Ubuntu-drivers retrieves these values from the live system and
+ checks the apt cache for matching packages and makes matching packagse
+ available for driver discovery. Eligible packages usch as OEM/HWE
+ metapackages can be selected to allow automatic installation of these.
+
+ * MIDR detection adds no new dependencies. Dmidecode detection adds a
+ dependency on dmidecode.
* $ seeded-in-ubuntu ubuntu-drivers-common
ubuntu-drivers-common (from ubuntu-drivers-common) is seeded in:
ubuntu-core-installer: daily-live
[ Regression Potential ]
* ubuntu-drivers is executed as part of the installation, so it can
result in failed provisioning runs at worst, making people unable to
provision systems, if due to the changes ubuntu-drivers fails out.
* This also modifies the output used and parsed by subiquity and other
installer programs. Warnings are now printed on std-err if ubuntu-
drivers <list|list-oem> is executed as a non-root user.
+ * Too broadly matching constraints could result in non-optimised
+ packages being installed on systems.
+
[ Testing ]
+ * The two changes add unit tests on their own, mocking CPU sysfs data,
+ multiple CPU types, oem-metapackage detection and local apt archives.
+
* Execute ubuntu-drivers <list|list-oem> and check if the additional
- packages containing Xb-Dmidecode or [TODO: MIDR] are available for
+ packages containing XB-Dmidecode or XB-Midr are available for
installation.
* Execute ubuntu-drivers install and check if the recommended packages
are also including packages with the new matching mechanism
* Execute ubuntu-drivers <list|list-oem> as a non-root user and see if
the warning is printed
[ Other Info ]
* Landing this allows us to further automate and optimise package
selection and matching mechanisms to improve the overall Ubuntu
experience for users. Since one of the main goals is the ubuntu-drivers
execution during subiquity it delivers an optimised performance from the
very beginning.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2167853
Title:
[FFE] Update ubuntu-drivers-common to 1:0.10.12 for stonking
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/2167853/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
