[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Thanks for the reply. I create another PPA (https://launchpad.net/~dirksu/+archive/ubuntu/ubuntu-drivers-common- build-with-proposed-test) which build with -proposed enabled. And ubuntu-drivers-common built successful on arm64. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Reply to #34, I try to build 1:0.9.6.2~0.22.04.6 on my PPA (https://launchpad.net/~dirksu/+archive/ubuntu/ubuntu-drivers-common- build-test/+packages). And the package seems built successfully on arm64. Can you help to re-trigger the build for it? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Install jammy iso ubuntu-22.04.3-desktop-amd64.iso into Dell Precision 7680. Then install ubuntu-drivers-common 1:0.9.6.2~0.22.04.6 from proposed channel. ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list ubuntu@ubuntu-Precision-7680:~$ sudo cp /tmp/custom_supported_gpus.json /etc ubuntu@ubuntu-Precision-7680:~$ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x28B9", "name": "TEST 28B9", "branch": "535.113", "features": [ "runtimepm" ] } ] } ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic-hwe-22.04) System can use ubuntu-drivers to list package by adding customized JSON file. With command ubuntu-drivers install, Nvidia related packages can be added. After system reboot, Nvidia GPU work as expected. ** Tags removed: verification-failed-jammy verification-needed ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Install lunar iso into Dell Precision 7680. Then install ubuntu-drivers- common 1:0.9.7.1.2 from proposed channel. ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list ubuntu@ubuntu-Precision-7680:~$ sudo cp /tmp/custom_supported_gpus.json /etc ubuntu@ubuntu-Precision-7680:~$ cat /etc/custom_supported_gpus.json { "chips": [ { "devid": "0x28B9", "name": "TEST 28B9", "branch": "535.113", "features": [ "runtimepm" ] } ] } ubuntu@ubuntu-Precision-7680:~$ ubuntu-drivers list nvidia-driver-535, (kernel modules provided by linux-modules-nvidia-535-generic-hwe-22.04) System can use ubuntu-drivers to list package by adding customized JSON file. With command ubuntu-drivers install, Nvidia related driver can be added. And GPU works. ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Committed Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Thank for the advice. Revised patch to generate 0.9.6.2~0.22.04.6 ** Patch 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Confirmed Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Upload the patch for lunar ** Patch 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Confirmed Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2034121] [NEW] Support goodix fingerprint [27C6:6304] and [27c6:633C]
Public bug reported: This patch is include in https://salsa.debian.org/ubuntu-dev- team/libfprint/-/commit/96645eaa7ae99a12e08b65e24a8610a3c57a92b3 [Impact] * Support goodix [27C6:6304] and [27c6:633C] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034121 Title: Support goodix fingerprint [27C6:6304] and [27c6:633C] Status in libfprint package in Ubuntu: New Bug description: This patch is include in https://salsa.debian.org/ubuntu-dev- team/libfprint/-/commit/96645eaa7ae99a12e08b65e24a8610a3c57a92b3 [Impact] * Support goodix [27C6:6304] and [27c6:633C] fingerprint component. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The patch add new ids to id_table. Should not affect previous supported device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/2034121/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Upstream had fix the bug found in #22. Include the patch and generate debdiff again. ** Patch 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Tested with Nvidia GPU 10de:2717. Disable restricted in jammy-updates and jammy-security, which make Nvidia 525 unavailable. Add /etc/customer_supported_gpus.json { "chips": [ { "devid": "0x2717", "name": "TEST 2717", "branch": "510.60", "feature": [ "runtimepm" ] } ] } Type "ubuntu-driver list" in console did not show anything. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-failed verification-failed-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: oem-priority Status: Confirmed => Triaged -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Triaged Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Tested with laptop 202211-30793 which only has 1920x1200 for internal display. Install stock 22.04 iso image and update gnome-control-center 1:41.7-0ubuntu0.22.04.7 from jammy-proposed. Connected DUT with external monitor which had resolution 1920x1080. Open gnome-control-center, switch to Display panel and select mirror mode. And gnome-control-center won't crash. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Committed Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Tested with laptop 202211-30793 which only has 1920x1200 for internal display. Install stock 23.04 iso image and update gnome-control-center 1:44.0-1ubuntu6 from lunar-proposed. Connected DUT with external monitor which had resolution 1920x1080. Open gnome-control-center, switch to Display panel and select mirror mode. And gnome-control-center won't crash. ** Tags removed: verification-needed-lunar ** Tags added: verification-done-lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Fix Committed Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control- center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
I can reproduced the gnome-control-center crash on Lunar. The crash only happened when two monitor can't find match resolution. My laptop's internal display only has one resolution 1920x1200, external monitor's highest resolution is 1920x1080. When switching to mirror mode in gnome- control-center, it will crashed. ** Changed in: gnome-control-center (Ubuntu Lunar) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: New Status in gnome-control-center source package in Kinetic: Won't Fix Status in gnome-control-center source package in Lunar: Confirmed Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. 1. Connected monitors to system which don't have same resolution. 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] It only modified the code related to mirror mode in Displays panel. For KK and LL check variable (best_mode) before using it. For Jammy, modified the way to find cloning mode and check the variable (best_mode) . The second patch already included in gnome-42. The risk will be low. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
The second patch included in gnome-42. KK use gnome-43 and LL use gnome-44 as base, both of distribution had the second patch. ** Description changed: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] - It only modified the code related to mirror mode in Displays panel. And won't affect other part. The risk will be low. + It only modified the code related to mirror mode in Displays panel. For KK and LL check variable (best_mode) before using it. For Jammy, modified the way to find cloning mode and check the variable (best_mode) . The second patch already included in gnome-42. The risk will be low. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] It only modified the code related to mirror mode in Displays panel. For KK and LL check variable (best_mode) before using it. For Jammy, modified the way to find cloning mode and check the variable (best_mode) . The second patch already included in gnome-42. The risk will be low. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
** Patch added: "jammy_ubuntu0.22.04.6_ubuntu0.22.04.7.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2026228/+attachment/5684451/+files/jammy_ubuntu0.22.04.6_ubuntu0.22.04.7.debdiff ** Tags added: oem-priority originate-from-2023147 stella ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] It only modified the code related to mirror mode in Displays panel. And won't affect other part. The risk will be low. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
** Patch added: "kinetic_ubuntu2_ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2026228/+attachment/5684449/+files/kinetic_ubuntu2_ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] It only modified the code related to mirror mode in Displays panel. And won't affect other part. The risk will be low. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
** Description changed: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] + It only modified the code related to mirror mode in Displays panel. And won't affect other part. The risk will be low. + [Other info] + Two Merge Request are related + 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) + 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) ** Patch added: "lunar_ubuntu5_ubuntu6.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2026228/+attachment/5684448/+files/lunar_ubuntu5_ubuntu6.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: Incomplete Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] It only modified the code related to mirror mode in Displays panel. And won't affect other part. The risk will be low. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2026228] [NEW] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Public bug reported: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] [Other info] ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] 1. Connected monitors to system which don't have same resolution. 2. Switch to mirror mode through gnome-control-center 3. gnome-control-center won't crash [Where problems could occur] [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2026228/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Update changelog to document the apt_pkg.DepCache in _is_runtimepm_supported. Related discussion is at https://github.com/tseliot/ubuntu-drivers- common/pull/71/commits/025cce328b9909f3f421376be35cb34511b9ea2e#r884846872 [ Jeremy Szu ] * README, README.md, UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Let OEM image can locally extending the NVIDIA driver supported PCI IDs for cutting edge silicons by specifying related information in /etc/custom_supported_gpus.json file. (lp: #1990341) - Fix pkg.candidate.record retired from apt_pkg library - Support autopkgtest for force install Nvidia and update related section in README. ** Patch 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 ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Update debdiff based on the newly released ubuntu-drivers- common-0.9.6.2~0.22.04.4 ** Patch 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 ** Patch 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 ** Patch 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 ** Patch 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Based on the suggestion in #14, update the changelog to make the update more clearly for the use [ Jeremy Szu ] * README, README.md, UbuntuDrivers/detect.py, tests/test_ubuntu_drivers.py: - Let OEM image can locally extending the NVIDIA driver supported PCI IDs for cutting edge silicons by specifying related information in /etc/custom_supported_gpus.json file. (lp: #1990341) - Support autopkgtest for force install Nvidia and update related section in README. ** Patch 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 ** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: In Progress Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Description changed: [ 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. + 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 + * 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Lunar: Fix Released Bug 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 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
[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
** Changed in: ubuntu-drivers-common (Ubuntu Jammy) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1993019] Re: UnboundLocalError: local variable 'version' referenced before assignment
All related bugs https://bugs.launchpad.net/bugs/1988836 and https://bugs.launchpad.net/bugs/1935070 had been verified in Jammy. Can 0.9.6.2~0.22.04.3 be released to jammy-updates? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1993019 Title: UnboundLocalError: local variable 'version' referenced before assignment Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Bionic: Triaged Status in ubuntu-drivers-common source package in Focal: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Status in ubuntu-drivers-common source package in Kinetic: Fix Released Bug description: [ Impact ] * The introduction of the -open NVIDIA drivers requires a change in the way we detect driver series and flavours. Failing to do so, causes the ubuntu-drivers tool to crash (LP: #1993019), or to prefer the -open drivers over the non-open ones (LP: #1988836). * Furthermore, calling the ubuntu-drivers tool where the alsa-utils package is not installed (mainly on servers), ubuntu-drivers (through the sl-modem plugin) complains, unnecessarily about the missing aplay binary. [ Test Plan ] * Install the new ubuntu-drivers-common from -proposed on a system where the GPU is compatible with the 515 series (or higher). * Run the ubuntu-drivers list command, and make sure that the 515 driver series (or higher) is listed. * Try installing the driver using the following command: sudo ubuntu-drivers install * Check which driver series was installed (you can use the "sudo ubuntu-drivers debug" command), and make sure that the installation does not cause ubuntu-drivers to crash. [ Where problems could occur ] * A problem in the ubuntu-drivers tool can cause it to install a driver which is not recommended for the detected hardware, or even cause the package installation to fail, and prevent users from logging in through the graphics interface. [ Other Info ] * To prevent failures of the test-suite on architectures such as armhf (as seen in Lunar), we are skipping the tests for any architectures other than amd64 and arm64 (which are the only ones actually using ubuntu-drivers). This was already the case with riscv, and we now have an easier way to do so in the debian/rules file. == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * New upstream release: * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex in nvidia_desktop_pre_installation_hook. This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). === Jammy only (left over from 1:0.9.6.2~0.22.04.1) === * UbuntuDrivers/detect.py: - Make sure -open drivers have a lower priority (LP: #1988836). == Changelogs == === Kinetic and Jammy === [ Alberto Milone ] * debian/rules: - Limit the tests to the selected architectures (amd64, arm64). This prevents armhf builds from failing. * UbuntuDrivers/detect.py: - Make sure all -open drivers have a lower priority, regardless of whether the --server parameter is passed in or not. - Update regex and unify package name parsing in the following functions by using the new NvidiaPkgNameInfo class: nvidia_desktop_pre_installation_hook, _get_headless_no_dkms_metapackage, nvidia_desktop_pre_installation_hook, get_linux_modules_metapackage, This prevents ubuntu-drivers from crashing when dealing with the -open NVIDIA drivers (LP: #1993019). * tests/test_ubuntu_drivers.py: - Add tests so we make sure to keep preferring non-open NVIDIA modules over the -open ones, at least until the open modules catch up feature wise and performance wise. [ gongzhengyang ] * UbuntuDrivers/detect.py: - Fix local variable 'version' being referenced before assignment when catching ValueError (LP: #1993019). [ Jeff Lane ] * detect-plugins/sl-modem.py: - Add some error trapping when aplay is not installed (on servers). ===
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
** Description changed: [ Impact ] - * In NVIDIA new GPU release cycle, NVIDIA ships their new GPUs to + * 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: + * 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: + 3. 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 + 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" ] } ] } ``` - 6. make sure the hook works + 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 ] - * 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. + * 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 ] - - * 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" + * 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Found the debdiff in #6. Upload the modified debdiff ** Patch 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 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug 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" To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990341/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
@seb128 the patches in the debdiff file picked from https://github.com/tseliot/ubuntu-drivers- common/commit/ec675fba22c68932da9fae95e0f4f2fd10732bf3, https://github.com/tseliot/ubuntu-drivers- common/commit/4776c6b9f78411ef3b269a28e9546e4ffd2b7115 and https://github.com/tseliot/ubuntu-drivers- common/commit/83528313da84b55c04daa62b5edcbf823e5c067b. The patches were merged in the Pull Request https://github.com/tseliot/ubuntu-drivers- common/pull/76 and related discussion was in https://github.com/tseliot/ubuntu-drivers-common/pull/71 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug 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" To manage notifications about this bug go to:
[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
Tested with fresh installed focal on machine with Nvidia GPU. Enabled -proposed channel and install ubuntu-drivers-common 1:0.9.0~0.20.04.8. Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and related packages will be installed. Executed command "sudo ubuntu- drivers install nvidia:515-open" and Nvidia open driver 515 and related packages will be installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1988836] Re: LRMv7: Enable the open NVIDIA kernel modules
Tested with fresh installed jammy on machine with Nvidia GPU. Enabled -proposed channel and install ubuntu-drivers-common 0.9.6.2~0.22.04.3. Execute command "sudo ubuntu-drivers install" and Nvidia driver 530 and related packages will be installed. Executed command "sudo ubuntu- drivers install nvidia:515-open" and Nvidia open driver 515 and related packages will be installed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1988836 Title: LRMv7: Enable the open NVIDIA kernel modules Status in linux-restricted-modules package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-515 package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in linux-restricted-modules source package in Focal: Fix Released Status in nvidia-graphics-drivers-515 source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in linux-restricted-modules source package in Jammy: Fix Released Status in nvidia-graphics-drivers-515 source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [ Impact ] * The 515 series introduced open kernel modules for the NVIDIA driver. They come with an open source licence, and should be provided as an option for datacenter GPUs: https://developer.nvidia.com/blog/nvidia-releases-open-source-gpu-kernel-modules/ Currently, this is only production-ready (and enabled) on datacenter GPUs. * We should enable signed modules for the 515-open drivers, giving users the option to try the drivers. * The ubuntu-drivers tool should set a lower priority for the -open flavour, so that we do not end up recommending it over the plain 515 flavour. [ Test Plan ] * [ubuntu-drivers-common]: "sudo ubuntu-drivers install (to make sure the driver is not installed by default)" * [nvidia driver] "sudo ubuntu-drivers install nvidia:515-open" to make sure that the driver can be installed manually. Please make sure that this installs the correct linux-restricted- modules. Note: support for GeForce and Workstation GPUs is alpha-quality, and is disabled by default. This means that desktop testing is not needed at the moment. [ Where problems could occur ] * This adds a new driver combination, which is not meant to be default, and is only enabled for a limited amount of devices (datacenter GPUs). * We need to be sure that the driver is not recommended over the other drivers. [ Other Info ] - To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules/+bug/1988836/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990341] Re: [SRU] Support to install nvidia driver by allowing list
Add patch to support install nvidia driver by allowing list ** Patch 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 ** Changed in: oem-priority Assignee: jeremyszu (os369510) => Dirk Su (dirksu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1990341 Title: [SRU] Support to install nvidia driver by allowing list Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Incomplete Bug 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"
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
5G function enabled with ModemManager 1.20.0-1 ** Changed in: modemmanager (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libqmi (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libmbim (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in modemmanager package in Ubuntu: Fix Released Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 2009767] Re: external HDMI monitor is laggy on NV reverse PRIME system
** Tags added: originate-from-2008875 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/2009767 Title: external HDMI monitor is laggy on NV reverse PRIME system Status in OEM Priority Project: New Status in xorg-server package in Ubuntu: New Bug description: [Summary] When the graphic mode is on-demand mode and plug in the monitor to HDMI port, there are two issue occures: 1. External monitor's screen is very laggy in external monitor mode only. 2. External monitor's screen sometimes (~50%) will be blak in join display mode. [Steps to reproduce] 1. Boot in OS 2. Plug in the external monitor in HDMI port 3. Find the cursor moving in external monitor is laggy [Additional information] Feedback from NV: An NVIDIA driver built with the features needed to get rid of the laggy monitor problem causes Xorg 1.21.1.3 to crash. There's a patch for Xorg to fix the crash (https://gitlab.freedesktop.org/xorg/xserver/-/issues/1275) and it was first included in the 1.21.1.4 release. Since the older X servers crash, NVIDIA deliberately does a version check in the driver and enables these features for Xorg servers that are known to work, i.e. 1.21.1.4 or higher. This unfortunately prevents backporting the fix to 1.21.1.3. Engineering has chosen this approach since a crash is worse than the low FPS lag and the user might lose work merely by plugging/unplugging displays. If it was about a performance degradation, slight corruption, or something non-fatal, we wouldn't need to check Xorg version To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2009767/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1950282] Re: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support
Tested on machine with FM350 installed, with oem 6.0.0-1006 kernel, modem manager 1.20.0-1~ubuntu22.04.1, libmbim-glib4 1.28.0-1~ubuntu20.04 and libqmi-glib5 1.32.0-1~ubuntu0.22.04.1. System can connect to 5g network. --- General | path: /org/freedesktop/ModemManager1/Modem/0 | device id: b429ecd3cf5b14431f765b3a415cda29db1d504b --- Hardware | manufacturer: generic | model: MBIM [14C3:4D75] | firmware revision: 81600..00.29.21.24_GC | D47 | h/w revision: V1.0.6 | supported: gsm-umts, lte, 5gnr |current: gsm-umts, lte, 5gnr | equipment id: 358198520003138 --- System| device: /sys/devices/pci:00/:00:1c.0/:71:00.0 |drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) --- Status| lock: sim-pin2 | unlock retries: sim-pin2 (3) | state: connected |power state: on |access tech: lte, 5gnr | signal quality: 64% (cached) --- Modes | supported: allowed: 3g; preferred: none | allowed: 4g; preferred: none | allowed: 3g, 4g; preferred: none | allowed: 5g; preferred: none | allowed: 3g, 5g; preferred: none | allowed: 4g, 5g; preferred: none | allowed: 3g, 4g, 5g; preferred: none |current: allowed: 3g, 4g, 5g; preferred: none --- IP| supported: ipv4, ipv6, ipv4v6 --- 3GPP | imei: 358198520003138 | enabled locks: fixed-dialing |operator id: 46692 | operator name: Chunghwa Telecom | registration: home | packet service state: attached --- 3GPP EPS | ue mode of operation: csps-2 |initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 | initial bearer apn: internet | initial bearer ip type: ipv4v6 --- 3GPP 5GNR | mico mode: disabled --- SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active) | slot 2: /org/freedesktop/ModemManager1/SIM/1 --- Bearer| paths: /org/freedesktop/ModemManager1/Bearer/1 ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1950282 Title: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support Status in HWE Next: New Status in OEM Priority Project: New Status in libmbim package in Ubuntu: Fix Released Status in libqmi package in Ubuntu: Fix Released Status in linux package in Ubuntu: Incomplete Status in modemmanager package in Ubuntu: Fix Released Status in libmbim source package in Jammy: Fix Committed Status in libqmi source package in Jammy: Fix Committed Status in linux source package in Jammy: New Status in modemmanager source package in Jammy: Fix Committed Bug description: * Impact Fibocom FM350 modems aren't working with the current version of modemmanager in 22.04. * Test case - install modemmanager, libmbim, and libqmi from -proposed - reboot and try WWAN function to see if any regression there. - perform dogfooding of its reverse dependencies (network- manager, gnome-control-center etc.) The verification should be done on FM350 to ensure it's correctly handled but also on other hardware to verify that there are no regressions * Regression potential The SRU does an update to new modemmanager serie so we should do a complete round of testing on different hardware and confirm there are no regression. --- :55:00.0 Wireless controller [0d40]: MEDIATEK Corp. Device [14c3:4d75] (rev 01)
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-1996155 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
** Tags added: originate-from-1996495 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
Tested on OAS4-DVT1-C4 (202208-30540) which has Fibcom DW5931e installed. Install gnome-control-center 1:41.7-0ubuntu0.22.04.5 from jammy-proposed. And update modemmanager to 1.19.1-683270f4 from https://launchpad.net/~dirksu/+archive/ubuntu/wwan-test. Enabled mobile network through gnome-control-center, there is 5G option in 'Network Mode'. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy ** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Fix Committed Status in gnome-control-center package in Ubuntu: Fix Released Status in gnome-control-center source package in Jammy: Fix Committed Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. [Other info] This patch is from upstream gnome-control-center. For more information refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 The patch also adds some new user visible strings, those will be translatable on launchpad and initially displayed in english but we can get translations updated then as part of the next language packs refresh To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
** Description changed: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] - 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) + 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode - 4. There should be 5G related option + 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. + + [Other info] + This patch is from upstream gnome-control-center. For more information + refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. [Other info] This patch is from upstream gnome-control-center. For more information refer to https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1388 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
Tested with Upstream ModemManager, libmbim and libqmi. The WWAN function can be turned on through gnome-control-center, and 5G function works correctly. The upstream version get with "git rev-parse --short HEAD" listed as below: ModemManager: eebdbc45 libmbim: add668b libqmi: fa6c7a97 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libmbim in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
** Also affects: libmbim Importance: Undecided Status: New ** No longer affects: libmbim ** Also affects: libmbim Importance: Undecided Status: New ** Project changed: libmbim => libmbim (Ubuntu) ** Also affects: libqmi Importance: Undecided Status: New ** Project changed: libqmi => libqmi (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in libmbim package in Ubuntu: New Status in libqmi package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
** Tags added: oem-priority originate-from-1962525 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in OEM Priority Project: Confirmed Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
** Tags added: oem-priority originate-from-1962525 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in OEM Priority Project: Confirmed Status in gnome-control-center package in Ubuntu: New Status in gnome-control-center source package in Jammy: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
patch for kinetic ** Patch added: "gnome-control-center_42.2-1ubuntu3.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+attachment/5607123/+files/gnome-control-center_42.2-1ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] Re: Can't find 5G option in Network Mode under Mobile Network
patch for jammy ** Patch added: "gnome-control-center_41.7-0ubuntu0.22.04.4.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+attachment/5607124/+files/gnome-control-center_41.7-0ubuntu0.22.04.4.debdiff ** Changed in: gnome-control-center (Ubuntu) Assignee: Dirk Su (dirksu) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1983645] [NEW] Can't find 5G option in Network Mode under Mobile Network
Public bug reported: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Assignee: Dirk Su (dirksu) Status: New ** Changed in: gnome-control-center (Ubuntu) Assignee: (unassigned) => Dirk Su (dirksu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1983645 Title: Can't find 5G option in Network Mode under Mobile Network Status in gnome-control-center package in Ubuntu: New Bug description: [Impact] There is no 5G related option in Network Mode under Mobile Network [Test case] 1. System should have 5G capable hardware (SIM and WWAN module) and 5G enabled Modem Manager (>=1.19.1) 2. Enable mobile network 3. Check network mode 4. There should be 5G related option [Where problems could occur] gnome-control-center interact with Modem Manager to get current network mode and set preferred network mode. Modem Manager will filter the unsupported mode. The risk will be low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1983645/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1981190/+attachment/5602332/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] Re: Fibcom FM350-GL not able connect to network with 5G mode
apport information ** Tags added: apport-collected ** Description changed: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2022-06-15 (26 days ago) + InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) + NonfreeKernelModules: nvidia_modeset nvidia + Package: modemmanager 1.18.6-1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 + Tags: jammy + Uname: Linux 5.17.0-9012-oem x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1981190/+attachment/5602331/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent)
[Desktop-packages] [Bug 1981190] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1981190/+attachment/5602333/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1981190/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1981190] [NEW] Fibcom FM350-GL not able connect to network with 5G mode
Public bug reported: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred: none IP |supported: ipv4, ipv6, ipv4v6 3GPP | imei: 352750140002001 |enabled locks: sim, fixed-dialing | operator id: 46692 |operator name: Chunghwa Telecom | registration: home 3GPP EPS | ue mode of operation: csps-2 | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0 SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0 Bearer |paths: /org/freedesktop/ModemManager1/Bearer/1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-06-15 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) NonfreeKernelModules: nvidia_modeset nvidia Package: modemmanager 1.18.6-1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.17.0-9012.13+exp.27-oem 5.17.9 Tags: jammy Uname: Linux 5.17.0-9012-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True ** Affects: modemmanager (Ubuntu) Importance: Undecided Status: New ** Tags: apport-collected jammy wwan ** Tags added: jammy wwan -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1981190 Title: Fibcom FM350-GL not able connect to network with 5G mode Status in modemmanager package in Ubuntu: New Bug description: Fibcom FM350-GL can support 5G network (https://www.fibocom.com/en/products/5G-FM350-GL.html). But in Ubuntu 22.04, system can only connect to mobile network with 4G mode. General | path: /org/freedesktop/ModemManager1/Modem/0 |device id: e045a43cd7977e24e1a11af409a780c054e26b0e Hardware | manufacturer: generic |model: MBIM [14C3:4D75] |firmware revision: 81600..00.29.18.01_GC | C01 | h/w revision: V1.0.6 |supported: gsm-umts, lte | current: gsm-umts, lte | equipment id: 352750140002001 System | device: /sys/devices/pci:00/:00:1c.0/:73:00.0 | drivers: mtk_t7xx | plugin: generic | primary port: wwan0mbim0 |ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim) Status | unlock retries: sim-pin (3), sim-pin2 (3) |state: connected | power state: on | access tech: lte | signal quality: 74% (recent) Modes|supported: allowed: 3g, 4g; preferred: none | current: allowed: 3g, 4g; preferred:
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Tested with Dell machine (202203-30028) which has problem ambient light sensor. Import iio-sensor-proxy 2.8-1ubuntu2 from -proposed channel. With iio-sensor-proxy debug turned on, iio-sensor-proxy use buffer ALS to read light sensor value. Execute monitor-sensor can check ambient light sensor working properly ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to iio-sensor-proxy in Ubuntu. https://bugs.launchpad.net/bugs/1963628 Title: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models Status in OEM Priority Project: New Status in iio-sensor-proxy package in Ubuntu: Fix Released Status in iio-sensor-proxy source package in Focal: Fix Committed Bug description: We are encountering issues, that when enabling some Dell laptops, the readings from iio-poll-als are unstable, or could freeze on certain value. On these systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als", and removing iio-poll-als makes reading stable. This adds workaround to the affected Dell laptop models which may equip with ALS. [Impact] * Only models matching the same device BIOS IDs are affected. [Test Plan] * Pick devices which BIOS IDs are listed in the patch, and test whether it's ambient light sensors are working properly without unexpected brightness flickers. [Where problems could occur] * Machines matching the same BIOS ID, either having ALS built-in or not, but attached ambient light sensors externally (for example, ColorHug ALS) might experience failures. [Other Info] * Upstream merge request: https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Since this machine has all-in-one in chassis type, only enabled off-load mode and disabled RTD3. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-prime source package in Hirsute: New Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: RTD3 is a nvidia GPU feature to support runtime suspend. On-demand would be a X offloading feature. They are independent, according to discussion on https://github.com/tseliot/ubuntu-drivers-common/issues/55. Some parts need to be adjusted, e.g. ``` # If we are dealing with NVIDIA PRIME, and runtimepm # is supported, enable it if (os.path.isfile('/run/nvidia_runtimepm_supported') and os.path.isfile('/usr/bin/prime-select')): print('Trying to select the on-demand PRIME profile') try: subprocess.call(['prime-select', 'on-demand']) except: pass # Create the override file for gpu-manager with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: f.write('# File created by ubuntu-drivers\n') ``` --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965520] Re: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime-select@374:enable_profile:_disable_nvidia:_update_initramfs
Installed nvidia-prime 0.8.16~0.20.04.2 from proposed channel. Tested with command "prime-select on-demand | false" won't get error and traceback information. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1965520 Title: /usr/bin/prime-select:BrokenPipeError:/usr/bin/prime- select@374:enable_profile:_disable_nvidia:_update_initramfs Status in nvidia-prime package in Ubuntu: Triaged Status in nvidia-prime source package in Bionic: Triaged Status in nvidia-prime source package in Focal: Fix Committed Bug description: [Impact] * The progress bar that is drawn to keep track of the update- initramfs process can result, sometimes, in a BrokenPipe error. In no way does this affect the final result of the actual operation, yet it causes the progress bar to crash. [Test Plan] * Install the nvidia-prime package and , and then execute "sudo prime-select intel" so that NVIDIA can be disabled, and the update- initramfs command is called. This might need repeating (i.e. going back and forth from "sudo prime-select intel" to "sudo prime-select on-demand" until the BrokenPipe error shows up. [Where problems could occur] * This can cause no regression, since it does not alter the actual functioning on nvidia-prime, and the change has been in Impish since its release. [Other Info] __ The Ubuntu Error Tracker has been receiving reports about a problem regarding nvidia-prime. This problem was most recently seen with package version 0.8.16.1, the problem page at https://errors.ubuntu.com/problem/cd1fe5ff88b744e0d29132fef0be40627b6614e0 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1965520/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Since this machine has all-in-one in chassis type, only enabled off-load mode and disabled RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Since this machine has all-in-one in chassis type, only enabled off-load mode and disabled RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: RTD3 is a nvidia GPU feature to support runtime suspend. On-demand would be a X offloading feature. They are independent, according to discussion on https://github.com/tseliot/ubuntu-drivers-common/issues/55. Some parts need to be adjusted, e.g. ``` # If we are dealing with NVIDIA PRIME, and runtimepm # is supported, enable it if (os.path.isfile('/run/nvidia_runtimepm_supported') and os.path.isfile('/usr/bin/prime-select')): print('Trying to select the on-demand PRIME profile') try: subprocess.call(['prime-select', 'on-demand']) except: pass # Create the override file for gpu-manager with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: f.write('# File created by ubuntu-drivers\n') ``` --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
Install Focal on HP EliteOne 800 G6 All-in-One (202008-28167). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Since this machine has all-in-one in chassis type, only enabled off-load mode and disabled RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Check nvidia module parameter with "cat /proc/driver/nvidia/params | grep DynamicPowerManagement" and get result 2 which means GPU enabled with RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Check nvidia module parameter with "cat /proc/driver/nvidia/params | grep DynamicPowerManagement" and get result 2 which means GPU enabled with RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: RTD3 is a nvidia GPU feature to support runtime suspend. On-demand would be a X offloading feature. They are independent, according to discussion on https://github.com/tseliot/ubuntu-drivers-common/issues/55. Some parts need to be adjusted, e.g. ``` # If we are dealing with NVIDIA PRIME, and runtimepm # is supported, enable it if (os.path.isfile('/run/nvidia_runtimepm_supported') and os.path.isfile('/usr/bin/prime-select')): print('Trying to select the on-demand PRIME profile') try: subprocess.call(['prime-select', 'on-demand']) except: pass # Create the override file for gpu-manager with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: f.write('# File created by ubuntu-drivers\n') ``` --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
Install Focal on Dell notebook Precision 7750 (202004-27817). Enable focal-proposed channel, install nvidia with "sudo ubuntu-drivers install nvidia" then reboot system. Check system is in on-demand with "prime- select query". Check nvidia module parameter with "cat /proc/driver/nvidia/params | grep DynamicPowerManagement" and get result 2 which means GPU enabled with RTD3. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed: RTD3 is a nvidia GPU feature to support runtime suspend. On-demand would be a X offloading feature. They are independent, according to discussion on https://github.com/tseliot/ubuntu-drivers-common/issues/55. Some parts need to be adjusted, e.g. ``` - # If we are dealing with NVIDIA PRIME, and runtimepm - # is supported, enable it - if (os.path.isfile('/run/nvidia_runtimepm_supported') and - os.path.isfile('/usr/bin/prime-select')): - print('Trying to select the on-demand PRIME profile') - try: - subprocess.call(['prime-select', 'on-demand']) - except: - pass + # If we are dealing with NVIDIA PRIME, and runtimepm + # is supported, enable it + if (os.path.isfile('/run/nvidia_runtimepm_supported') and + os.path.isfile('/usr/bin/prime-select')): + print('Trying to select the on-demand PRIME profile') + try: + subprocess.call(['prime-select', 'on-demand']) + except: + pass - # Create the override file for gpu-manager - with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: - f.write('# File created by ubuntu-drivers\n') + # Create the override file for gpu-manager + with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: + f.write('# File created by ubuntu-drivers\n') ``` - --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + - Handle BrokenPipeError (LP: #1965520). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: RTD3 is a nvidia GPU feature to support runtime suspend. On-demand would be a X offloading feature. They are independent, according to discussion on https://github.com/tseliot/ubuntu-drivers-common/issues/55. Some parts need to be adjusted, e.g. ``` # If we are dealing with NVIDIA PRIME, and runtimepm # is supported, enable it if (os.path.isfile('/run/nvidia_runtimepm_supported') and os.path.isfile('/usr/bin/prime-select')): print('Trying to select the on-demand PRIME profile') try: subprocess.call(['prime-select', 'on-demand']) except: pass # Create the override file for gpu-manager with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: f.write('# File created by ubuntu-drivers\n') ``` --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. - --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + - Handle BrokenPipeError (LP: #1965520). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: As per LP: #1942307 we now set on-demand as the default. This however, causes "prime-select on-demand", called by ubuntu-drivers, not to even try to detect RTD3 and to enable it, since "on-demand" is already set. We cannot make informed choices about RTD3 in the postinstallation script of nvidia-prime, therefore we should simply drop the check that prime-select makes to abort if the new profile is determined to be the same as the current profile. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Handle BrokenPipeError (LP: #1965520). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to :
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed: - [Steps to reproduce] - 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. - 2. After the installation, press enter to reboot system - 3. prime-select query + RTD3 is a nvidia GPU feature to support runtime suspend. - [Expected result] - on-demand + On-demand would be a X offloading feature. - [Actual result] - performance + They are independent, according to discussion on + https://github.com/tseliot/ubuntu-drivers-common/issues/55. - --- + Some parts need to be adjusted, e.g. - It's because ubiquity launches `ubuntu-drivers install --packages-list - ...` in live system but install each package to target storage. + ``` + # If we are dealing with NVIDIA PRIME, and runtimepm + # is supported, enable it + if (os.path.isfile('/run/nvidia_runtimepm_supported') and + os.path.isfile('/usr/bin/prime-select')): + print('Trying to select the on-demand PRIME profile') + try: + subprocess.call(['prime-select', 'on-demand']) + except: + pass - When installing nvidia-prime, the preinst set "on" to "/etc/prime- - discrete" which will be referred by gpu-manager. The gpu-manager will - set to performance mode. + # Create the override file for gpu-manager + with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: + f.write('# File created by ubuntu-drivers\n') + ``` - After confirming with Alberto on Mattermost, since we don't have a - nvidia driver which lower than 450 version since focal. - - I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. - - nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) - - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Won't Fix Bug description: RTD3 is a nvidia GPU feature to support runtime suspend. On-demand would be a X offloading feature. They are independent, according to discussion on https://github.com/tseliot/ubuntu-drivers-common/issues/55. Some parts need to be adjusted, e.g. ``` # If we are dealing with NVIDIA PRIME, and runtimepm # is supported, enable it if (os.path.isfile('/run/nvidia_runtimepm_supported') and os.path.isfile('/usr/bin/prime-select')): print('Trying to select the on-demand PRIME profile') try:
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. + --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. - - nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) - - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: - [Steps to reproduce] - 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. - 2. After the installation, press enter to reboot system - 3. prime-select query + As per LP: #1942307 we now set on-demand as the default. This however, + causes "prime-select on-demand", called by ubuntu-drivers, not to even + try to detect RTD3 and to enable it, since "on-demand" is already set. - [Expected result] - on-demand + We cannot make informed choices about RTD3 in the postinstallation + script of nvidia-prime, therefore we should simply drop the check that + prime-select makes to abort if the new profile is determined to be the + same as the current profile. - [Actual result] - performance - - --- - - It's because ubiquity launches `ubuntu-drivers install --packages-list - ...` in live system but install each package to target storage. - - When installing nvidia-prime, the preinst set "on" to "/etc/prime- - discrete" which will be referred by gpu-manager. The gpu-manager will - set to performance mode. - - After confirming with Alberto on Mattermost, since we don't have a - nvidia driver which lower than 450 version since focal. - - I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. - - nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) - - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
Test plan had been updated to cover the nvidia-driver-390 case. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: New Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup impish on 201606-22344 in cert pool, this system's GPU can supported both with nvidia-driver-390 and nvidia-driver-470. Installed ubuntu-drivers-common, nvidia-settings from impish-proposed repository. With nvidia-driver-390, try to setup on-demand mode with "prime-select on-demand", system will fall back to nvidia mode after reboot. With nvidia-driver-470, setup on-demand mode with "prime-select on-demand", system will change to on-demand mode after system reboot. The behaviour of nvidia-drivers-common and nvidia-settings in impish-proposed is as expected. ** Tags removed: verification-needed verification-needed-impish ** Tags added: verification-done verification-done-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup focal on 201606-22344 in cert pool, this system's GPU can supported both with nvidia-driver-390 and nvidia-driver-470. Installed ubuntu-drivers-common, nvidia-settings from focal-proposed repository. With nvidia-driver-390, try to setup on-demand mode with "prime-select on-demand", system will fall back to nvidia mode after reboot. With nvidia-driver-470, setup on-demand mode with "prime-select on-demand", system will change to on-demand mode after system reboot. The behaviour of nvidia-drivers-common and nvidia-settings in focal-proposed is as expected. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in nvidia-settings source package in Focal: Fix Committed Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-settings source package in Impish: Fix Committed Status in ubuntu-drivers-common source package in Impish: Fix Committed Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). ** Changed
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * Old GPU (which supported by nvidia-390 only) will keep in performance mode, refer LP:1957094. Execute "prime-select query" should get "nvidia" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But + based on the Nvidia README, this case shall not happened. [Other Info] - - X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). -- You
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Setup impish on 201606-22459 in cert pool. Then doing same test as #3, test result is positive. GPU will keep in nvidia mode, and glxinfo works normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Impish: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
Installed nvidia-driver-390 on target system (201606-22459 in cert. poll). Then install nvidia-settings and ubuntu-drivers-common mentioned in #2. Try to switch on-demand mode with "prime-select on-demand" and nvidia-settings UI. After system reboot, GPU will keep in nvidia mode. And glxinfo works normally. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Fix Committed Status in ubuntu-drivers-common source package in Impish: Triaged Status in ubuntu-drivers-common source package in Jammy: Fix Committed Bug description: The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
With test on Dell Vostro 5568 witch got GPU can be supported by nvidia- driver-390 package. Install nvidia-driver-390 via ubuntu-drivers install nvidia:390. The default GPU mode will be nvidia. Manually switch GPU mode to on-demand, and running glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". It seems on-demand mode not work with nvidia-driver-390. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Focal: New Status in nvidia-prime source package in Hirsute: New Status in ubuntu-drivers-common source package in Hirsute: New Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955566] Re: iris driver doesn't load correctly on intel pci_id 0x4688
** Tags added: originate-from-1954392 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1955566 Title: iris driver doesn't load correctly on intel pci_id 0x4688 Status in OEM Priority Project: Triaged Status in mesa package in Ubuntu: New Bug description: [Impact] * iris driver doesn't load with pci_id 4688. Instead, it uses llvm. we expect the Intel GPU uses iris driver. [Test Plan] * $ DISPLAY=:0 glxinfo | grep -i opengl OpenGL vendor string: Mesa/X.org OpenGL renderer string: llvmpipe (LLVM 12.0.0, 256 bits) ... OpenGL version string: 3.1 Mesa 21.0.3 * After applying the fix, it shows: * $ DISPLAY=:0 glxinfo | grep -i opengl OpenGL vendor string: Intel OpenGL renderer string: Mesa Intel(R) Graphics (ADL-S GT1) ... OpenGL version string: 4.6 (Compatibility Profile) Mesa 21.0.3 (git-d4975a0dbc) [Where problems could occur] * This patch is backport the PCI ID mapping for enabling iris driver which is expected when users have a GPU. * If there is any issue occur then we need to fix it with iris driver. [Other Info] * It already in upstream and we have a platform which using ADL-HX in OEM project. Thus, we need to enable iris on it at least on focal. * The patch is simple as to add "CHIPSET(0x4688, adl_gt1, "ADL-S GT1", "Intel(R) Graphics")" in "include/pci_ids/iris_pci_ids.h". * Patch backported from df5b14969f9869f363bcc8b2a564c85aaa481597 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1955566/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946434] Re: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3
** Changed in: oem-priority Status: Confirmed => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946434 Title: SRU: Set on-demand as default, enable RTD3 only on laptops and decouple on-demand with RTD3 Status in OEM Priority Project: Invalid Status in nvidia-prime package in Ubuntu: Invalid Status in nvidia-prime source package in Focal: In Progress Status in nvidia-prime source package in Hirsute: In Progress Bug description: [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946434/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946440] Re: SRU: enable RTD3 only on laptops
** Changed in: oem-priority Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1946440 Title: SRU: enable RTD3 only on laptops Status in OEM Priority Project: Invalid Status in ubuntu-drivers-common package in Ubuntu: Invalid Status in ubuntu-drivers-common source package in Focal: In Progress Status in ubuntu-drivers-common source package in Hirsute: In Progress Bug description: [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power. [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946440/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Fix Committed Status in nvidia-prime source package in Hirsute: New Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
Create iso with live-build and import ubuntu-drivers-common 0.9.0~0.20.04.4 from focal-proposed. Install Ubuntu with "third-party packages" enabled. After installation finished, '/run/nvidia_runtimepm_supported' had been created and use 'prime-select query' get 'on-demand' ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed * Install Ubuntu on machine, in "Updates and other software" page select "Install third-party software for graphics and Wi-Fi hardware and additional media formats" * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Call "prime-select query" to make sure the default mode is "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to https://bugs.launchpad.net/oem-priority/+bug/1942788 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
Tested with iso built from live-build and import ubuntu-drivers-common from focal-proposed. After installation finished, check /var/log/installer/syslog can see error log as attachment. It says "ubiquity: chroot: failed to run command ‘prime-select’: No such file or directory", because 31ubuntu_driver_packages is called by target config hook which is run before target install stage. Also tested with 21.10 iso file and will got same error message in log. ** Attachment added: "syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816/+attachment/5546087/+files/syslog -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: Fix Committed Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed * Install Ubuntu on machine, in "Updates and other software" page select "Install third-party software for graphics and Wi-Fi hardware and additional media formats" * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Call "prime-select query" to make sure the default mode is "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to https://bugs.launchpad.net/oem-priority/+bug/1942788 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
@Brian I updated the description. Do you think the information in description is enough to continue the SRU process? And the packages is uploaded to queue. Focal: https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes Hirsute: https://launchpad.net/ubuntu/hirsute/+upload/27068995/+files/nvidia-prime_0.8.16.2~0.21.04.1_source.changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
@Brian I updated the description. Do you think the information in description is enough to continue the SRU process? And the packages is uploaded to queue. Focal: https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes Hirsute: https://launchpad.net/ubuntu/hirsute/+upload/27068995/+files/nvidia-prime_0.8.16.2~0.21.04.1_source.changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942789 Title: On-demand and RTD3 need to be separated Status in OEM Priority Project: Triaged Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: In Progress Status in nvidia-prime source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Focal: New Status in nvidia-prime source package in Hirsute: New Status in ubuntu-drivers-common source package in Hirsute: New Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942789/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
@Brian I updated the description. Do you think the information in description is enough to continue the SRU process? And the packages is uploaded to queue. Focal: https://launchpad.net/ubuntu/focal/+upload/27068997/+files/nvidia-prime_0.8.16~0.20.04.2_source.changes Hirsute: https://launchpad.net/ubuntu/hirsute/+upload/27068995/+files/nvidia-prime_0.8.16.2~0.21.04.1_source.changes -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1946476 Title: New on-demand default causes RTD3 never to be enabled Status in OEM Priority Project: New Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Status in nvidia-prime source package in Impish: Fix Released Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1946476/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. + * on-demand mode combined two features which are GPU offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have GPU offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand *
[Desktop-packages] [Bug 1942789] Re: On-demand and RTD3 need to be separated
** Description changed: - RTD3 is a nvidia GPU feature to support runtime suspend. + [Steps to reproduce] + 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. + 2. After the installation, press enter to reboot system + 3. prime-select query - On-demand would be a X offloading feature. + [Expected result] + on-demand - They are independent, according to discussion on - https://github.com/tseliot/ubuntu-drivers-common/issues/55. + [Actual result] + performance - Some parts need to be adjusted, e.g. + --- - ``` - # If we are dealing with NVIDIA PRIME, and runtimepm - # is supported, enable it - if (os.path.isfile('/run/nvidia_runtimepm_supported') and - os.path.isfile('/usr/bin/prime-select')): - print('Trying to select the on-demand PRIME profile') - try: - subprocess.call(['prime-select', 'on-demand']) - except: - pass + It's because ubiquity launches `ubuntu-drivers install --packages-list + ...` in live system but install each package to target storage. - # Create the override file for gpu-manager - with open('/etc/u-d-c-nvidia-runtimepm-override', 'w') as f: - f.write('# File created by ubuntu-drivers\n') - ``` + When installing nvidia-prime, the preinst set "on" to "/etc/prime- + discrete" which will be referred by gpu-manager. The gpu-manager will + set to performance mode. + + After confirming with Alberto on Mattermost, since we don't have a + nvidia driver which lower than 450 version since focal. + + I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode
[Desktop-packages] [Bug 1946476] Re: New on-demand default causes RTD3 never to be enabled
** Description changed: - As per LP: #1942307 we now set on-demand as the default. This however, - causes "prime-select on-demand", called by ubuntu-drivers, not to even - try to detect RTD3 and to enable it, since "on-demand" is already set. + [Steps to reproduce] + 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. + 2. After the installation, press enter to reboot system + 3. prime-select query - We cannot make informed choices about RTD3 in the postinstallation - script of nvidia-prime, therefore we should simply drop the check that - prime-select makes to abort if the new profile is determined to be the - same as the current profile. + [Expected result] + on-demand + + [Actual result] + performance + + --- + + It's because ubiquity launches `ubuntu-drivers install --packages-list + ...` in live system but install each package to target storage. + + When installing nvidia-prime, the preinst set "on" to "/etc/prime- + discrete" which will be referred by gpu-manager. The gpu-manager will + set to performance mode. + + After confirming with Alberto on Mattermost, since we don't have a + nvidia driver which lower than 450 version since focal. + + I think we are ok to switch to on-demand mode. --- [Impact] - * Ubuntu will set GPU mode to performance as default which may use more power - * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported - * According to Nvidia README, the RTD3 doesn't support on non-laptop machine + * Ubuntu will set GPU mode to performance as default which may use more power + * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported + * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] - * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" - * On non-laptop machine. Can set GPU mode to on-demand - * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" + * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" + * On non-laptop machine. Can set GPU mode to on-demand + * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. - * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. + * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. + * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile (LP: #1946476). - - Catch BrokenPipeError. - - Use bootvga detection when last_gfx_boot is - not available. + [ Alberto Milone ] + * prime-select: + - Detect chassis type and enable RTD3 only + on laptops (LP: #1942788). + - on-demand mode doesn't need to depend on + RTD3 (LP: #1942789). + - Use bootvga detection when last_gfx_boot + is not available. + - Don't check the current profile when setting + a profile (LP: #1946476). + - Catch BrokenPipeError. + - Use bootvga detection when last_gfx_boot is + not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium - [ Jeremy Szu ] - * Set on-demand mode as default nvidia mode (LP: #1942307) + [ Jeremy Szu ] + * Set on-demand mode as default nvidia mode (LP: #1942307) - [ Alberto Milone ] - * prime-select: - - Detect chassis type and enable RTD3 only - on laptops (LP: #1942788). - - on-demand mode doesn't need to depend on - RTD3 (LP: #1942789). - - Use bootvga detection when last_gfx_boot - is not available. - - Don't check the current profile when setting - a profile
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Description changed: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] - * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. + * on-demand mode combined offloading and RTD3. Nvidia driver lower then 450 (nvidia-driver-390) does not supported RTD3 and only have offloading feature. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
Previous discussion was at https://chat.canonical.com/canonical/pl/1mgrhibwpj8ojxk89tbpztjdar. Due to the design of ubiquity, it only use ubuntu-driver to get package list and install package in 31ubuntu_driver_packages. But ubuntu-driver not only install packages but also create configurations of Nvidia GPU. This patch will copy configurations and calling prime-select to make sure it get same result as calling "ubuntu-driver install" directly. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: New Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed * Install Ubuntu on machine, in "Updates and other software" page select "Install third-party software for graphics and Wi-Fi hardware and additional media formats" * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Call "prime-select query" to make sure the default mode is "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to https://bugs.launchpad.net/oem-priority/+bug/1942788 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942307] Re: ubiquity uses performance mode for nvidia driver
** Changed in: oem-priority Status: Triaged => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1942307 Title: ubiquity uses performance mode for nvidia driver Status in OEM Priority Project: Confirmed Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Incomplete Status in nvidia-prime source package in Hirsute: Incomplete Bug description: [Steps to reproduce] 1. Install 20.04.3 with "Third-party packages" on a system which containing a RTD3 supported nvidia card. 2. After the installation, press enter to reboot system 3. prime-select query [Expected result] on-demand [Actual result] performance --- It's because ubiquity launches `ubuntu-drivers install --packages-list ...` in live system but install each package to target storage. When installing nvidia-prime, the preinst set "on" to "/etc/prime- discrete" which will be referred by gpu-manager. The gpu-manager will set to performance mode. After confirming with Alberto on Mattermost, since we don't have a nvidia driver which lower than 450 version since focal. I think we are ok to switch to on-demand mode. --- [Impact] * Ubuntu will set GPU mode to performance as default which may use more power * User can't use GPU for other purpose (eg: deep-learning) if RTD3 is not supported * According to Nvidia README, the RTD3 doesn't support on non-laptop machine [Test Plan] * Install Ubuntu, and then execute 'ubuntu-drivers install' to install GPU driver. After the installation, reboot the system. Execute "prime-select query" should get "on-demand" * On non-laptop machine. Can set GPU mode to on-demand * On laptop with GPU in runtime PM support list. Set GPU mode to on-demand and Nvidia driver is loaded with "NVreg_DynamicPowerManagement=0x02" [Where problems could occur] * on-demand mode supported after nvidia driver 450. And focal does not have nvidia driver lower than 450. * With GPU supported RTD3 not able enable runtime PM on non-laptop. But based on the Nvidia README, this case shall not happened. [Other Info] X-HWE-Bug: Bug #1946434 Changelogs: nvidia-prime (0.8.16~0.20.04.2) focal; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). - Catch BrokenPipeError. - Use bootvga detection when last_gfx_boot is not available. nvidia-prime (0.8.16.2~0.21.04.1) hirsute; urgency=medium [ Jeremy Szu ] * Set on-demand mode as default nvidia mode (LP: #1942307) [ Alberto Milone ] * prime-select: - Detect chassis type and enable RTD3 only on laptops (LP: #1942788). - on-demand mode doesn't need to depend on RTD3 (LP: #1942789). - Use bootvga detection when last_gfx_boot is not available. - Don't check the current profile when setting a profile (LP: #1946476). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942307/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
** Description changed: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine - * Patch make system not enable RTD3 unless it's a laptop * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" + * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] - * Install Ubuntu on machine with "third-party packages" enabled + * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed + * Install Ubuntu on machine, in "Updates and other software" page select "Install third-party software for graphics and Wi-Fi hardware and additional media formats" * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. - * Execute "prime-select query" should get "on-demand" + * Call "prime-select query" to make sure the default mode is "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] - * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to + * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to https://bugs.launchpad.net/oem-priority/+bug/1942788 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: New Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" * Patch make system not enable RTD3 unless it's a laptop and set default GPU mode to "on-demand" [Test Plan] * Create Focal iso with live-build and import ubuntu-drivers-common from -proposed * Install Ubuntu on machine, in "Updates and other software" page select "Install
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
** Changed in: ubuntu-drivers-common (Ubuntu Hirsute) Assignee: (unassigned) => Dirk Su (dirksu) ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Dirk Su (dirksu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
** Description changed: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] - * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine - * Patch make system not enable RTD3 unless it's a laptop - * Install Ubuntu with "third-party packages" enabled, will not get same -GPU configuration by running "ubuntu-drivers install" + * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine + * Patch make system not enable RTD3 unless it's a laptop + * Install Ubuntu with "third-party packages" enabled, will not get same + GPU configuration by running "ubuntu-drivers install" [Test Plan] - * Install Ubuntu on machine with "third-party packages" enabled - * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. - * Execute "prime-select query" should get "on-demand" + * Install Ubuntu on machine with "third-party packages" enabled + * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. + * Execute "prime-select query" should get "on-demand" [Where problems could occur] - * With non-laptop machine use RTD3 supported GPU may use more power + * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] + + * For RTD3 (Runtime D3) doesn't support on non-laptop machine, refer to + https://bugs.launchpad.net/oem-priority/+bug/1942788 ** Changed in: ubuntu-drivers-common (Ubuntu Focal) Assignee: (unassigned) => Dirk Su (dirksu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubiquity source package in Focal: New Status in ubuntu-drivers-common source package in Focal: New Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
** Description changed: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] - X-HWE-Bug: Bug #1946440 + Information for Focal, refer to LP#1943816 ** Description changed: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] - Information for Focal, refer to LP#1943816 + Information for Focal, refer to + [LP#1943816](https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816) ** Description changed: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to - [LP#1943816](https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816) + https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Hirsute: Fix Released Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] Information for Focal, refer to https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
Tested on desktop and notebook machine with Nvidia graphic card. On notebook machine (chassis type 10), configuration file '/run/nvidia_runtimepm_supported' is created. On desktop (chassis type 3) machine did not generate the configuration file. Only notebook machine will enable runtime PM. ** Tags removed: verification-needed verification-needed-hirsute ** Tags added: verification-done verification-done-hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] X-HWE-Bug: Bug #1946440 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1942788] Re: Nvidia doesn't support RTD3 on non-laptops
** Changed in: oem-priority Status: Triaged => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1942788 Title: Nvidia doesn't support RTD3 on non-laptops Status in OEM Priority Project: Confirmed Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in ubuntu-drivers-common source package in Focal: Incomplete Status in ubuntu-drivers-common source package in Hirsute: Fix Committed Bug description: According to Nvidia README, the RTD3 doesn't support on non-laptop machine. https://github.com/tseliot/ubuntu-drivers-common/issues/55 We need to check chassis type before enabling RTD3. --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop [Test Plan] * Install Ubuntu on machine * Install GPU driver via 'ubuntu-drivers install' * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] X-HWE-Bug: Bug #1946440 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1942788/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
** Description changed: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). + + --- + + [Impact] + + * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine + * Patch make system not enable RTD3 unless it's a laptop + * Install Ubuntu with "third-party packages" enabled, will not get same +GPU configuration by running "ubuntu-drivers install" + + [Test Plan] + + * Install Ubuntu on machine with "third-party packages" enabled + * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. + * Execute "prime-select query" should get "on-demand" + + [Where problems could occur] + + * With non-laptop machine use RTD3 supported GPU may use more power + + [Other Info] ** Changed in: oem-priority Assignee: jeremyszu (os369510) => Dirk Su (dirksu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). --- [Impact] * According to Nvidia README, the RTD3 (Runtime D3) doesn't support on non-laptop machine * Patch make system not enable RTD3 unless it's a laptop * Install Ubuntu with "third-party packages" enabled, will not get same GPU configuration by running "ubuntu-drivers install" [Test Plan] * Install Ubuntu on machine with "third-party packages" enabled * On laptop with Nvidia RTD3 supported GPU. The configuration file '/run/nvidia_runtimepm_supported' will be created. * Execute "prime-select query" should get "on-demand" [Where problems could occur] * With non-laptop machine use RTD3 supported GPU may use more power [Other Info] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1943816] Re: "ubuntu-drivers install" needs to be used when installing nvidia-driver if enabling "third-party packages"
debdiff for focal ** Patch added: "ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1943816/+attachment/5537831/+files/ubuntu-drivers-common_0.9.0~0.20.04.3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1943816 Title: "ubuntu-drivers install" needs to be used when installing nvidia- driver if enabling "third-party packages" Status in OEM Priority Project: Confirmed Status in subiquity: New Status in ubiquity package in Ubuntu: New Status in ubuntu-drivers-common package in Ubuntu: Fix Released Bug description: ubiquity calls ``` ubuntu-drivers install $FREEONLY $NOOEM --package-list /run/ubuntu-drivers.autoinstall ``` to generate package list during live system but "ubuntu-drivers install" not only install packages but also create some config files for switching nvidia mode (e.g. on-demand) and change the runtime config as well (e.g. modify the iniramfs). Thus, not only package list needs to be referred but also the configuration. --- In ubuntu-drivers-common, which read the "/run/ubuntu-drivers.autoinstall" to install package. It also skipping the nvidia-mode changing (made by ubuntu-drivers install). ``` $ cat ubiquity/target-config/31ubuntu_driver_packages #!/bin/sh set -e # install all packages that "ubuntu-drivers autoinstall" installed into the # live system. Ubiquity calls this with --package-list /run/ubuntu-drivers.autoinstall PKGLIST=/run/ubuntu-drivers.autoinstall [ -e $PKGLIST ] || exit 0 for p in `cat $PKGLIST`; do apt-install $p done ``` --- We need to use a same approach to make sure the nvidia mode is same on a same system (either all handing by ubuntu-drivers install or change the logic to maintainer script in each package). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1943816/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp