Backport amdgpu-pro support

Bug #1731873 reported by Alberto Milone on 2017-11-13
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-drivers-common (Ubuntu)
High
Alberto Milone
Xenial
High
Alberto Milone
Zesty
High
Alberto Milone

Bug Description

SRU Request:

[Impact]
Support for the amdgpu-pro driver has been available in Artful since May 2017. We need to backport the code to the other stable releases.

[Test Case]
1) Enable the -proposed repository, and install the new "ubuntu-drivers-common"

2) Make sure the amdgpu-pro packages are installed (if not, install them, and restart your system).

3) Check that power saving mode is supported:

amdgpu-pro-px --ispx

If it returns true, then it is supported by the hardware.

4) Set power saving mode:

sudo amdgpu-pro-px --mode powersaving

5) Restart your computer and check that the "Enabling power saving mode for amdgpu-pro" line is in your /var/log/gpu-manager.log.

6) Install the mesa-utils package:
sudo apt install mesa-utils

7) Check the output of the following command (which should mention Intel):
glxinfo | grep OpenGL

[Regression Potential]
Low, as the feature is disabled by default, unless users set power saving manually.

Changed in ubuntu-drivers-common (Ubuntu):
status: In Progress → Fix Released
Changed in ubuntu-drivers-common (Ubuntu Xenial):
importance: Undecided → High
Changed in ubuntu-drivers-common (Ubuntu Zesty):
importance: Undecided → High
Changed in ubuntu-drivers-common (Ubuntu Xenial):
status: New → In Progress
Changed in ubuntu-drivers-common (Ubuntu Zesty):
status: New → In Progress
Changed in ubuntu-drivers-common (Ubuntu Xenial):
assignee: nobody → Alberto Milone (albertomilone)
Changed in ubuntu-drivers-common (Ubuntu Zesty):
assignee: nobody → Alberto Milone (albertomilone)
Alex Tu (alextu) wrote :

@Alberto
what exactly version of the one proposed ?

I can not find related change log on current proposed : http://paste.ubuntu.com/25959552/

tags: added: from-1728547

Hello Alberto, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-zesty to verification-done-zesty. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-zesty. In either case, details of your testing will help us make a better decision.

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

Changed in ubuntu-drivers-common (Ubuntu Zesty):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-zesty
Changed in ubuntu-drivers-common (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed-xenial
Brian Murray (brian-murray) wrote :

Hello Alberto, or anyone else affected,

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

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

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision.

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

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers