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
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
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
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
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
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
** 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]
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
*
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"
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": [
** 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
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
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
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-
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.
ed 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 subscrib
** 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
** 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.
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
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,
** 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
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"
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
** 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
** 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:
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
** 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
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
@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-
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
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
ed 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 drive
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
** 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
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:
** 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
** 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
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
** 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)
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
--
** 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
**
** 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
** 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
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
er (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 Ne
nee: 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.launchp
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.
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.
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.
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:
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
** 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
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
** 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
** 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
** 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
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
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
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
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
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 |
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 |
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 |
** 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.
```
** 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
** 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.
** 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]
** 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.
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
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
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
** 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]
** 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]
** 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]
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.
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
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
** 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
** 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
** 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
** 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
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:
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
@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:
@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:
@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:
** 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]
** 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
** 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
** 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]
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
** 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
** 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
** 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,
ther 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
** 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
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.
**
** 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
tion 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:
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
1 - 100 of 130 matches
Mail list logo
