| 2022-09-21 04:07:35 |
jeremyszu |
bug |
|
|
added bug |
| 2022-09-21 04:08:48 |
jeremyszu |
bug task added |
|
oem-priority |
|
| 2022-09-21 04:08:57 |
jeremyszu |
tags |
|
oem-priority |
|
| 2022-09-21 04:09:01 |
jeremyszu |
oem-priority: assignee |
|
jeremyszu (os369510) |
|
| 2022-09-21 04:09:05 |
jeremyszu |
oem-priority: importance |
Undecided |
High |
|
| 2022-09-21 04:09:09 |
jeremyszu |
oem-priority: status |
New |
Confirmed |
|
| 2022-09-21 04:12:18 |
jeremyszu |
bug |
|
|
added subscriber OEM Solutions Group: Engineers |
| 2022-12-30 08:33:32 |
jeremyszu |
oem-priority: status |
Confirmed |
In Progress |
|
| 2023-01-03 05:15:14 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
TBC, I'll provide soon.
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials. |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
As the attachment "buildlog"
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials. |
|
| 2023-01-03 05:15:39 |
jeremyszu |
attachment added |
|
buildlog https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5638891/+files/buildlog_ubuntu-jammy-amd64.ubuntu-drivers-common_1%200.9.6.2~0.22.04.1+lp1990341_BUILDING.txt.gz |
|
| 2023-01-03 05:53:26 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
I will build a version soon. TBC
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
As the attachment "buildlog"
> install log
TBC, I'll provide soon.
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials. |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials. |
|
| 2023-01-03 05:53:37 |
jeremyszu |
attachment added |
|
installlog https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5638895/+files/installlog |
|
| 2023-01-03 06:10:44 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials. |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81 |
|
| 2023-01-03 06:11:07 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81 |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
|
| 2023-01-03 07:53:00 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
TBC, I'll provide soon.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
|
| 2023-01-03 07:54:23 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
7. sudo ubuntu-drivers install # it can install nv510 successfully.
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
|
| 2023-01-03 07:55:10 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
7. sudo ubuntu-drivers install # it can install nv510 successfully.
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
|
| 2023-01-03 07:57:09 |
jeremyszu |
bug |
|
|
added subscriber Ubuntu Release Team |
| 2023-01-03 07:57:18 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
TBC, will subscribe them after completing the materials.
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
Done
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
|
| 2023-01-03 07:57:23 |
jeremyszu |
oem-priority: status |
In Progress |
Incomplete |
|
| 2023-02-15 21:25:06 |
Brian Murray |
ubuntu-drivers-common (Ubuntu): status |
New |
Incomplete |
|
| 2023-02-16 14:28:52 |
Brian Murray |
removed subscriber Ubuntu Release Team |
|
|
|
| 2023-02-17 02:39:24 |
jeremyszu |
summary |
[FeatureFreeze Exceptions] Support to install nvidia driver by allowing list |
[Draft][SRU] Support to install nvidia driver by allowing list |
|
| 2023-02-17 02:39:34 |
jeremyszu |
oem-priority: status |
Incomplete |
Confirmed |
|
| 2023-02-17 17:18:10 |
Brian Murray |
removed subscriber Brian Murray |
|
|
|
| 2023-02-20 23:57:46 |
jeremyszu |
description |
> If the upload is a new upstream microrelease, the relevant part of the upstream changelog and/or release notes
Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
> An explanation of the testing which has been performed on the new version in Ubuntu, including verification that the new package:
For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/customized_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
> state the reason why you feel it is necessary (other bugs it fixes, etc.)
related bug: https://bugs.launchpad.net/ubuntu/+bug/1
In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
> attach (as files)
> diff of the Upstream ChangeLog (not debian/changelog)
> diff -u <package>-{old-version,new-version}/ChangeLog > changelog.diff
note that the ChangeLog sometimes is called CHANGES, is missing or the tarball merely has a NEWS file.
> the NEWS file, if you think that this information helps reviewing your request (true for most gnome packages)
N/A, FWIK, u-d-c hasn't an official release note something like "NEWS"
> build log (as file)
Please refer the attachment "buildlog"
> install log
Please refer the attachment "installlog"
> mention what testing you've done to see that it works
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
P.S. also tried:
1. wrong json format and it shows "DEBUG:root:package_get_nv_allowing_driver(): unexpected json detected." when enables the verbose.
2. try non exist nv driver (e.g. 525, has been remove from the pool) and it shows "DEBUG:root:nvidia-driver-525 is not in the package pool."
The instruction won't return failed but just do nothing from the hook.
> subscribe (do not assign to) the 'ubuntu-release' team.
Done
---
[Additional information]
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341 |
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510/520/525..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/custom_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341
* build log (as file)
Please refer the attachment "buildlog"
* install log
Please refer the attachment "installlog" |
|
| 2023-02-20 23:59:26 |
jeremyszu |
summary |
[Draft][SRU] Support to install nvidia driver by allowing list |
[SRU] Support to install nvidia driver by allowing list |
|
| 2023-05-31 05:40:19 |
Dirk Su |
attachment added |
|
force_install_NVIDIA_driver-jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5676866/+files/force_install_NVIDIA_driver-jammy.debdiff |
|
| 2023-05-31 05:40:32 |
Dirk Su |
oem-priority: assignee |
jeremyszu (os369510) |
Dirk Su (dirksu) |
|
| 2023-05-31 08:14:46 |
Ubuntu Foundations Team Bug Bot |
tags |
oem-priority |
oem-priority patch |
|
| 2023-05-31 08:14:50 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-06-07 11:59:01 |
Sebastien Bacher |
bug |
|
|
added subscriber Sebastien Bacher |
| 2023-06-08 08:28:35 |
Dirk Su |
attachment added |
|
force_install_NVIDIA_driver-jammy_2.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5678569/+files/force_install_NVIDIA_driver-jammy_2.debdiff |
|
| 2023-06-08 08:37:24 |
Dirk Su |
description |
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* For this feature which only impact if the target system has a custom file "/etc/custom_supported_gpus.json"
If the file presents, it will effect packages_for_modalias() and _is_runtimepm_supported(). Both functions are important when "ubuntu-driver install" a nvidia driver.
For installing nvidia driver, u-d-c has several test in autopkgtest which contains:
* different branch type: LTS/PB/NFB/Legacy..
* different version type: 390/470/495/510/520/525..
* For this particular feature, we created a new autopkgtest test_system_driver_packages_force_install_nvidia() which not only secure this FFE but each version bump.
which contains:
1. Normal case (Stock ubuntu), without /etc/custom_supported_gpus.json in the system.
2. If /etc/custom_supported_gpus.json contains incorrect json field / format.
3. /etc/custom_supported_gpus.json point to the older version than candidate.
4. /etc/custom_supported_gpus.json point to the same version than candidate.
5. /etc/custom_supported_gpus.json point to a non-exist version of ubuntu-archive (source list).
and you can see from "buildlog" attachment, all passed as well as "test_system_driver_packages_force_install_nvidia()"
Refer https://github.com/tseliot/ubuntu-drivers-common/pull/71 for more details.
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. add ppa, apt update and reboot.
4. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
5. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
6. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[ Other Info ]
* Upstream commit: https://github.com/tseliot/ubuntu-drivers-common/commit/a7d2d39805e995ed0e655de123b4bb6cff4e6434
* Jammy MP: https://github.com/tseliot/ubuntu-drivers-common/pull/81
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1990341
* build log (as file)
Please refer the attachment "buildlog"
* install log
Please refer the attachment "installlog" |
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users
[ Other Info ]
* the patches are picked from
- https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
- https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
- https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 |
|
| 2023-06-08 10:03:34 |
Sebastien Bacher |
ubuntu-drivers-common (Ubuntu): importance |
Undecided |
High |
|
| 2023-06-08 10:03:34 |
Sebastien Bacher |
ubuntu-drivers-common (Ubuntu): status |
Incomplete |
Fix Released |
|
| 2023-06-13 03:01:30 |
Andy Chi |
nominated for series |
|
Ubuntu Lunar |
|
| 2023-06-13 03:01:30 |
Andy Chi |
bug task added |
|
ubuntu-drivers-common (Ubuntu Lunar) |
|
| 2023-06-13 03:01:30 |
Andy Chi |
nominated for series |
|
Ubuntu Jammy |
|
| 2023-06-13 03:01:30 |
Andy Chi |
bug task added |
|
ubuntu-drivers-common (Ubuntu Jammy) |
|
| 2023-06-13 03:11:25 |
Andy Chi |
ubuntu-drivers-common (Ubuntu Lunar): status |
New |
Fix Released |
|
| 2023-06-13 03:16:00 |
Andy Chi |
ubuntu-drivers-common (Ubuntu Jammy): status |
New |
Fix Committed |
|
| 2023-06-14 12:32:50 |
Simon Chopin |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-06-15 03:15:14 |
Dirk Su |
description |
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool.
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users
[ Other Info ]
* the patches are picked from
- https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
- https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
- https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 |
[ Impact ]
* In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to OEM/ODM for production.
In the meantime, NVIDIA usually notify OEM/ODM/Canonical (under NDA) to use a specific nvidia version to development/production.
NVIDIA and OEN/ODM will announce the next generation combination at the same time usually when the factory ready to ship the product.
We made Ubuntu as a leading distribution supports many cutting edge devices, it's time to have an official way to make the nvidia installation consistent in unannounced (yet) nvidia devices to support OEM/ODM factory shipment for our growing counterparts.
[ Test Plan ]
* Steps to make sure it works:
1. pick a cutting edge nvidia graphic.
2. remove nv-525 from the pool by removing restricted in jammy-updates and jammy-security
3. check the nv support status:
```
$ ubuntu-drivers list
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
```
4. modify custom file
```
$ cat /etc/custom_supported_gpus.json
{
"chips": [
{
"devid": "0x24BA",
"name": "TEST 24BA",
"branch": "580.1234",
"features": [
"runtimepm"
]
},
{
"devid": "0x25BC",
"name": "TEST 25BC",
"branch": "510",
"features": [
"runtimepm"
]
}
]
}
```
5. make sure the hook works
```
$ ubuntu-drivers list
nvidia-driver-510, (kernel modules provided by nvidia-dkms-510)
oem-fix-gfx-nvidia-ondemandmode
libfprint-2-tod1-broadcom
oem-somerville-cinccino-meta
[ Where problems could occur ]
* This feature only impact target system has a custom file "/etc/custom_supported_gpus.json". And it won't generate automatically which should not impact normal users
[ Other Info ]
* the patches are picked from
- https://github.com/tseliot/ubuntu-drivers-common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3
- https://github.com/tseliot/ubuntu-drivers-common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115
- https://github.com/tseliot/ubuntu-drivers-common/commit/83528313da84b55c04daa62b5edcbf823e5c067b.
* Discussion is in https://github.com/tseliot/ubuntu-drivers-common/pull/71 |
|
| 2023-06-17 00:06:11 |
Steve Langasek |
ubuntu-drivers-common (Ubuntu Jammy): status |
Fix Committed |
Incomplete |
|
| 2023-06-19 01:57:56 |
Dirk Su |
attachment added |
|
force_install_NVIDIA_driver-jammy_3.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5680578/+files/force_install_NVIDIA_driver-jammy_3.debdiff |
|
| 2023-06-19 02:01:25 |
Dirk Su |
ubuntu-drivers-common (Ubuntu Jammy): status |
Incomplete |
In Progress |
|
| 2023-06-28 02:02:29 |
Dirk Su |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-06-28 02:12:33 |
Dirk Su |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-06-28 02:25:57 |
Dirk Su |
attachment added |
|
jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5682424/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5.debdiff |
|
| 2023-06-28 02:26:21 |
Dirk Su |
attachment removed |
force_install_NVIDIA_driver-jammy.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5676866/+files/force_install_NVIDIA_driver-jammy.debdiff |
|
|
| 2023-06-28 02:26:30 |
Dirk Su |
attachment removed |
force_install_NVIDIA_driver-jammy_2.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5678569/+files/force_install_NVIDIA_driver-jammy_2.debdiff |
|
|
| 2023-06-28 02:26:39 |
Dirk Su |
attachment removed |
force_install_NVIDIA_driver-jammy_3.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5680578/+files/force_install_NVIDIA_driver-jammy_3.debdiff |
|
|
| 2023-06-29 08:10:11 |
Dirk Su |
ubuntu-drivers-common (Ubuntu Jammy): status |
In Progress |
Confirmed |
|
| 2023-06-29 10:16:12 |
Julian Andres Klode |
ubuntu-drivers-common (Ubuntu Jammy): status |
Confirmed |
Invalid |
|
| 2023-06-29 10:16:15 |
Julian Andres Klode |
ubuntu-drivers-common (Ubuntu Jammy): status |
Invalid |
Incomplete |
|
| 2023-06-29 10:16:17 |
Julian Andres Klode |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-07-03 02:51:09 |
Dirk Su |
attachment added |
|
jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5_v2.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5683469/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5_v2.debdiff |
|
| 2023-07-03 02:54:41 |
Dirk Su |
ubuntu-drivers-common (Ubuntu Jammy): status |
Incomplete |
Confirmed |
|
| 2023-07-12 02:24:27 |
Dirk Su |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-07-13 00:29:43 |
Dirk Su |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2023-07-13 18:25:49 |
Sergio Durigan Junior |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-07-13 18:26:44 |
Sergio Durigan Junior |
ubuntu-drivers-common (Ubuntu Jammy): status |
Confirmed |
In Progress |
|
| 2023-07-14 03:44:49 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Sergio Durigan Junior |
| 2023-07-15 03:44:20 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Steve Langasek |
| 2023-07-21 05:55:05 |
Dirk Su |
oem-priority: status |
Confirmed |
Triaged |
|
| 2023-07-21 19:16:55 |
Steve Langasek |
ubuntu-drivers-common (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2023-07-21 19:16:57 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2023-07-21 19:17:00 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2023-07-21 19:17:06 |
Steve Langasek |
tags |
oem-priority patch |
oem-priority patch verification-needed verification-needed-jammy |
|
| 2023-07-25 03:39:55 |
Dirk Su |
tags |
oem-priority patch verification-needed verification-needed-jammy |
oem-priority patch verification-failed verification-failed-jammy |
|
| 2023-08-31 04:19:53 |
Dirk Su |
attachment added |
|
jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5_v3.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5696649/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.5_v3.debdiff |
|
| 2023-09-02 23:39:56 |
Mantas Kriaučiūnas |
bug |
|
|
added subscriber Mantas Kriaučiūnas |
| 2023-09-02 23:40:26 |
Mantas Kriaučiūnas |
bug |
|
|
added subscriber Baltix GNU/Linux system developers |
| 2023-09-12 02:01:22 |
Dirk Su |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-09-13 00:56:26 |
Dirk Su |
ubuntu-drivers-common (Ubuntu Jammy): status |
Fix Committed |
Confirmed |
|
| 2023-09-13 15:53:18 |
Jeremy Bícha |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-09-15 09:15:44 |
Dirk Su |
attachment added |
|
jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.6.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5701201/+files/jammy-0.9.6.2~22.04.4__0.9.6.2~22.04.6.debdiff |
|
| 2023-09-15 09:18:01 |
Dirk Su |
attachment added |
|
lunar-0.9.7.1.1__0.9.7.1.2.debdiff https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1990341/+attachment/5701202/+files/lunar-0.9.7.1.1__0.9.7.1.2.debdiff |
|
| 2023-09-15 09:19:09 |
Dirk Su |
bug |
|
|
added subscriber Ubuntu Sponsors |
| 2023-09-15 09:22:51 |
Andy Chi |
ubuntu-drivers-common (Ubuntu Lunar): status |
Fix Released |
Confirmed |
|
| 2023-09-22 16:59:55 |
Brian Murray |
removed subscriber Ubuntu Sponsors |
|
|
|
| 2023-09-22 21:43:15 |
Ubuntu Archive Robot |
bug |
|
|
added subscriber Brian Murray |
| 2023-09-29 19:53:10 |
Steve Langasek |
ubuntu-drivers-common (Ubuntu Lunar): status |
Confirmed |
Fix Committed |
|
| 2023-09-29 19:53:18 |
Steve Langasek |
tags |
oem-priority patch verification-failed verification-failed-jammy |
oem-priority patch verification-failed-jammy verification-needed verification-needed-lunar |
|
| 2023-10-05 02:31:34 |
Dirk Su |
tags |
oem-priority patch verification-failed-jammy verification-needed verification-needed-lunar |
oem-priority patch verification-done-lunar verification-failed-jammy verification-needed |
|
| 2023-10-05 03:35:49 |
Dirk Su |
tags |
oem-priority patch verification-done-lunar verification-failed-jammy verification-needed |
oem-priority patch verification-done verification-done-jammy verification-done-lunar |
|
| 2023-10-11 16:47:33 |
Launchpad Janitor |
ubuntu-drivers-common (Ubuntu Lunar): status |
Fix Committed |
Fix Released |
|
| 2023-10-11 16:47:39 |
Andreas Hasenack |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
