After spending some more time with this, I can confirm that this is
definitely a regression. Both nouveau and the old bbswitch based method
in 16.04 were able to power off the nvidia card successfully when not in
use. The current implementation of prime-select in 18.04 doesn't do
that. It may be th
@Alberto, with prime-select intel as well as with bbswitch off, powertop
shows the nvidia tunable as "good". Still, the battery's discharge rate
on idle remains pretty high (around 20W) on prime-select intel. With
bbswitch off, it drops to 13W or thereabouts. Do you need any more
information ?
--
Attached powertop images. I'm not sure how accurate powertop's values
and distributions are. With prime-select intel, the total estimated
power remains high although it doesn't attribute it to nvidia. bbswitch
also stays on. I've also attached a bbswitch off capture after prime-
select intel. That
Thinkpad w530. Still looks like the nvidia gpu isn't turning off.
bionic+lightdm+unity7. Log attached.
prime-select query
intel
cat /proc/acpi/bbswitch
:01:00.0 ON
** Attachment added: "gpu-manager.log"
https://bugs.launchpad.net/ubuntu/+source/nvidia-prime/+bug/1778011/+attachment/5226
The official version of nvidia-settings-304 in the precise-updates
repository points to version 331. So if you have precise-updates
enabled, even if you try to install the 304 version, it will install 331
by default. One needs to manually select an older version to get around
this bug.
--
You rec
5 matches
Mail list logo