GithubHelp home page GithubHelp logo

system76-power's Introduction

System76 Power Management

system76-power is a utility for managing graphics and power profiles.

Switchable Graphics

Switchable graphics is a feature for laptops and all-in-one PCs. It is not supported on desktops.

A reboot is required for changes to take effect after switching modes.

Integrated

The integrated graphics controller on the Intel or AMD CPU is used exclusively.

Lower graphical performance with a longer battery life.

External displays connected to the dGPU ports cannot be used.

NVIDIA

The dGPU (NVIDIA) is used exclusively.

Higher graphical performance at the expense of a shorter battery life.

Allows using external displays.

Hybrid

Enables PRIME render offloading. The iGPU is used as the primary renderer, with the ability to have specific applications render using the dGPU.

PRIME render offloading requires the 435.17 NVIDIA drivers or later.

Applications must use GLVND to take advantage of this feature, so may not render on the dGPU even when requested. Vulkan applications must be launched with __NV_PRIME_RENDER_OFFLOAD=1 to render on the dGPU. GLX applications must be launched with __NV_PRIME_RENDER_OFFLOAD=1 __GLX_VENDOR_LIBRARY_NAME=nvidia to render on the dGPU.

Display offload sinks ("reverse PRIME") require 450.57 NVIDIA drivers or later. This feature allows using external displays while in this mode.

GPU support for run-time power management is required for the device to enter a low power state when not used. Only Turing cards and newer fully implement this functionality. Support for run-time power manage can be checked in the supported-gpus.json file provided by the driver. e.g.:

$ cat /sys/bus/pci/devices/0000:01:00.0/device
0x1f15
$ jq '.chips[] | select(.devid=="0x1F15")' < /usr/share/doc/nvidia-driver-460/supported-gpus.json
{
  "devid": "0x1F15",
  "name": "GeForce RTX 2060",
  "features": [
    "dpycbcr420",
    "dpgsynccompatible",
    "hdmi4k60rgb444",
    "hdmigsynccompatible",
    "geforce",
    "runtimepm",
    "vdpaufeaturesetJ"
  ]
}

Compute

The integrated graphics controller is used exclusively for rendering. The dGPU is made available as a compute node.

Power Profiles

Balanced

  • Set the sync data to disk to 15s
  • Enables laptop mode feature in kernel
  • Enables SCSI/SATA link time power management
  • Controls the Intel PState values if they exist

Performance

  • Uses settings from Balanced
  • Uses ACPI Platform profile if the hardware is supported by the kernel

Battery

  • Uses settings from Performance
  • Sets Screen brightness to a lower value
  • Turns keyboard backlight off

Hotplug detection

The dbus signal HotPlugDetect is sent when a display is plugged into a port connected to the dGPU. If in integrated or compute mode, the GNOME extension will prompt to switch to hybrid mode so the display can be used.

Adding hotplug detection

Intel-based systems

The GPIO (sideband) port and pins for the display ports can be determined with the schematics and output of coreboot-collector. The schematics will indicate which GPIOs are display ports (*_HPD). The corresponding GPP_* entry in coreboot-collector.txt will have the port/pin tuple.

Muxed DisplayPort

Some models have muxed DisplayPort ouput from mDP and USB-C. These units have a separate data switch pin that is used to determine which output is used.

AMD-based systems

A MMIO region for FCH GPIO controls is used to detect external display plug events. Display ports use *_HPD as Intel systems, but may not map to a literal GPIO (e.g., HDMI_HPD maps to DP3_HPD on kudu6). Generating a diff from coreboot-collector in NVIDIA mode before and after plugging in a display should provide the GPIO number.

system76-power's People

Contributors

13r0ck avatar ahoneybun avatar aidanharris avatar aklsh avatar bennetyee avatar brs17 avatar crawfxrd avatar curiousercreative avatar danieleades avatar ebobby avatar ids1024 avatar jackpot51 avatar jacobgkau avatar jsj1027 avatar krutkay avatar kylebakerio avatar laniakea64 avatar leviport avatar mmstick avatar rengare avatar scrufulufugus avatar tzigamm avatar watchmkr avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

system76-power's Issues

Authentication error!

Distribution (run cat /etc/os-release):
Now i'm in void-linux.

Issue/Bug Description:
I tried to remove some applications(Because i don't need some of them at all and i wanted to replace some others with better ones in IMHO). For example evince, gnome-user-doc, seahorse, nautilus.
When i removed nautilus for example, the font of terminal/system messed up. After reboot, i can't see the normal login screen of popos. it replaced by default gnome login screen and when i want to write my password, a hint appear in the below of inputbox says: "Authentication error". and after 2 second, the screen become black and i had to restart it. Again and again i see this issue, until i go back to void-linux.
Guys, why we can't delete default apps?

Steps to reproduce (if you know):
Start to delete those apps that i mentioned earlier.

Expected behavior:
Users should easily delete default apps and if they want, replace them with what they want.

Set APM for HDDs

NAME="Pop!_OS"
VERSION="19.04"
**Distribution:**
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco 

Related Application and/or Package Version:

hdparm:

  Installed: 9.58+ds-1
  Candidate:   9.58+ds-1
  Version table:
 *** 9.58+ds-1 500
        500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status

system76-power:

  Installed: 1.0.0~1555432002~19.04~1c347b8
  Candidate:   1.0.0~1555432002~19.04~1c347b8
  Version table:
 *** 1.0.0~1555432002~19.04~1c347b8 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

System76-power does not set a sane APM for HDDs. The usual APM level is 254, which resets after reboot. On an unrelated note: for some reason setting the apm value in /etc/hdparm.conf does nothing. Upon reboot it resets the value to 254. The problem with using any value above 127 is that the disk will not spin down and be idle. My HDD has been active all the time and generates a heckin amount of heat (I've seen something close to 50 degrees celsius, even when it's not in use... which is insane). Setting it on boot is ideal and I've made a udev rule to that effect (see screenshot). But this might also be a feature that the System76-power daemon might want to deal with. I'm not sure...

Steps to reproduce (if you know):

  1. Boot the system
  2. Run sudo hddparm -B /dev/sdX
  3. Be sad that you're abusing your HDD

Expected behavior:

That the HDD(s) have an APM level of 127 or less, so that the disk can spin down and be idle.

Other Notes:
If you're running a workstation and it needs to read from HDD all the time a level above 127 might be preferable. Having the full 254 levels of APM might be suitable for a server, but not a desktop. Power needs to be conserved and the lifespan of an HDD should be as long as possible.

Files:
popos_system76-power_hdparm

Switch between nvidia/intel shows an error, but actually works

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco
LOGO=distributor-logo-pop-os

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

N/A

Issue/Bug Description:

Switching nvidia -> intel or intel -> nvidia with the UI shows the below error message, however when restarting the laptop it does switch and works just fine.

image

Logs:

$ journalctl /usr/bin/system76-power -f
Oct 08 20:48:02 x1-extreme system76-power[1336]: [INFO] DBUS Received SetGraphics(intel) method
Oct 08 20:48:02 x1-extreme system76-power[1336]: [INFO] Creating /etc/modprobe.d/system76-power.conf
Oct 08 20:48:02 x1-extreme system76-power[1336]: [INFO] Disabling nvidia-fallback.service
Oct 08 20:48:02 x1-extreme system76-power[1336]: Removed /etc/systemd/system/graphical.target.wants/nvidia-fallback.service.
Oct 08 20:48:03 x1-extreme system76-power[1336]: [INFO] Updating initramfs
Oct 08 20:48:03 x1-extreme system76-power[1336]: update-initramfs: Generating /boot/initrd.img-5.0.0-31-generic
Oct 08 20:48:12 x1-extreme system76-power[1336]: cryptsetup: WARNING: The initramfs image may not contain cryptsetup binaries
Oct 08 20:48:12 x1-extreme system76-power[1336]:     nor crypto modules. If that's on purpose, you may want to uninstall the
Oct 08 20:48:12 x1-extreme system76-power[1336]:     'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
Oct 08 20:48:12 x1-extreme system76-power[1336]:     integration and avoid this warning.
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Config    : INFO     Looking for configuration...
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub           : INFO     System information:
Oct 08 20:48:31 x1-extreme system76-power[1336]:     OS:..................Pop!_OS 19.04
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Root partition:....../dev/nvme0n1p5
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Root FS UUID:........3c5a4310-5f0f-4c18-a33b-3c78ca0ca5cc
Oct 08 20:48:31 x1-extreme system76-power[1336]:     ESP Path:............/boot/efi
Oct 08 20:48:31 x1-extreme system76-power[1336]:     ESP Partition:......./dev/nvme0n1p1
Oct 08 20:48:31 x1-extreme system76-power[1336]:     ESP Partition #:.....1
Oct 08 20:48:31 x1-extreme system76-power[1336]:     NVRAM entry #:.......-1
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Boot Variable #:.....0000
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Kernel Image Path:.../vmlinuz
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Initrd Image Path:.../initrd.img
Oct 08 20:48:31 x1-extreme system76-power[1336]:     Force-overwrite:.....False
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Installer : INFO     Copying Kernel into ESP
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Installer : INFO     Copying initrd.img into ESP
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Installer : INFO     Setting up loader.conf configuration
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Installer : INFO     Backing up old kernel
Oct 08 20:48:31 x1-extreme system76-power[1336]: kernelstub.Installer : INFO     Making entry file for Pop!_OS

switching using cli command (system76-power graphics nvidia|intel) also works fine.

Steps to reproduce (if you know):

described above

Expected behavior:

successful message displayed with an option to restart/restart later

Other Notes:

Runing on Lenovo X1 Extreme Gen1

Screen brightness changes but does not change back

When changing power profile to a less power consuming state, the screen dims in brightness. Going back to a higher performing state, the tool does not remember what was last set in that profile and keeps the screen brightness at the lower setting.

I would expect each profile to remember the last screen brightness setting the user set before the user moved to a different power profile. When returning to the profile, the previous setting would be restored.

Brightness updates not reflected in slider

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 0.0.1152600575718.041222310
Candidate: 0.0.1
152600575718.041222310
Version table:
*** 0.0.1152600575718.04~1222310 776
776 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:
When switching power states and the brightness changes, the slider in the menu does not change.

Steps to reproduce (if you know):
Start in high power mode. Turn brightness to 100%, toggle to another power mode. The brightness will change but the slider will not change in the user menu.

Expected behavior:
The slider should reflect the current brightness level.

Other Notes:
gdbus call --session --dest org.gnome.SettingsDaemon.Power --object-path /org/gnome/SettingsDaemon/Power --method org.freedesktop.DBus.Properties.Set org.gnome.SettingsDaemon.Power.Screen Brightness ""

Sets the brightness, where XX is the percent from 0 to 100.

Add profile to turn off Turbo, allowing for cooler computer

This is a feature request. I request to add a profile, say Cool, which turns off Turbo while not limiting frequency.

I know that Battery Life profile already turns off Turbo, but in my case of a Serval WS 11, it also limits frequency to 2.5GHz. I request this profile because once air temperature rises above ~25 degrees Celcius, the Serval 11 cannot run full power without overheating. The automatic throttling does not kick in fast enough to prevent hardware error, and it has crashed my computer many times. In addition, having the computer run this hot makes the keyboard too hot to use comfortably.

I have tested quite a few power settings with the intel_pstate controls under /sys, and notice that just by turning off Turbo, the CPU temperature may drop from a critical 99 C down to a much more manageable 75 C. The CPU is still allowed to run up to 3.6GHz, instead of the 2.5GHz as limited by Battery Life profile.

My current workaround is to use a SystemD service to disable turbo, but system76-power apparently overrides the service at random times. Thus the feature request to incorporate this new profile.

Thelio Major Fan is Loud at Idle

Distribution

david@system76-pc:~$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version

david@system76-pc:~$ apt policy system76-power
system76-power:
  Installed: 1.0.0~1553639437~18.04~ce5c6e4~dev
  Candidate: 1.0.0~1553639437~18.04~ce5c6e4~dev
  Version table:
 *** 1.0.0~1553639437~18.04~ce5c6e4~dev 500
        500 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

At idle, the fan on my new thelio major is loud. It looks like(?) the system reports to the fan that the cpu is running much hotter than it actually is (tctl v. tdie), so the fan is spinning at full tilt:

david@system76-pc:~$ sensors
iwlwifi-virtual-0
Adapter: Virtual device
temp1:        +37.0°C  

k10temp-pci-00d3
Adapter: PCI adapter
Tdie:         +43.8°C  (high = +70.0°C)
Tctl:         +70.8°C  

k10temp-pci-00c3
Adapter: PCI adapter
Tdie:         +43.8°C  (high = +70.0°C)
Tctl:         +70.8°C  

amdgpu-pci-4100
Adapter: PCI adapter
vddgfx:       +0.77 V  
fan1:        1482 RPM
temp1:        +28.0°C  (crit = +94.0°C, hyst = -273.1°C)
power1:        5.19 W  (cap =  35.00 W)

k10temp-pci-00db
Adapter: PCI adapter
Tdie:         +32.5°C  (high = +70.0°C)
Tctl:         +59.5°C  

k10temp-pci-00cb
Adapter: PCI adapter
Tdie:         +34.1°C  (high = +70.0°C)
Tctl:         +61.1°C  

Expected behavior

The fan should run slower when the cpu is not that hot.

Power settings lack performance option

**NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
**

Issue/Bug Description:
There is no way to set a performance mode. The only way to set is through the current System76 Power extension between:

  • High Performance
  • Balanced
  • Battery Life

Nevertheless, it is currently impossible to change this extension's default to high performance when connected to electricity.

Steps to reproduce (if you know):
A. Settings

  • Access Settings > Power
  • Fail to change efficiency mode

B. System76 Power extension

  • Access extension's drop-down menu
  • Change to a different value. E.G.: High performance
  • Restart computer
  • default goes back to Balanced

Expected behavior:
A. Be able to set an efficiency mode
B. Be able to set a new default

Graphics Switching Option Does Not Appear In Pop 19.04 on Oryx 4

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="19.04"

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power 1.0.0~1551755982~19.04~f2d01db

Issue/Bug Description:

Graphics Switcher does not show up on Oryx 4 Laptop.

Steps to reproduce (if you know):
Install 19.04.
Reboot
Check power menu

Expected behavior:
Power Menu shows options to switch between Nvidia and Intel Graphics

Other Notes:
Switching manually using system76-power graphics works fine. Additionally, system76-power graphics switchable reports that the graphics are indeed switchable. Output of lspci | grep -i vga:

00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Mobile)
01:00.0 VGA compatible controller: NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] (rev a1)

GNOME Shell logs are attached.
gnome-shell_2018-03-18-17-23.log

[fan] account for GPU temperatures

In a test case on a 4 GPU Thelio Massive, GPU temps approached 90 C while the CPU temps stayed around 40 C using gpuburn.

With the current fan logic, that would result in intake fans that are off.

Cannot swithc to Nvidia Graphics

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 1.0.0153780841018.04821cc23
Candidate: 1.0.0
153780841018.04821cc23
Version table:
*** 1.0.0153780841018.04~821cc23 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:
Switching to nvidia card is not working.
I ran
system76-power graphics nvidia
and it seemed to work, but when I rebooted,
system76-power graphics
returned
intel

I checked journalctl /usr/bin/system76-power and got

Sep 29 23:11:40 pop-os system76-power[1129]: [INFO] Connecting to dbus system bus
Sep 29 23:11:40 pop-os system76-power[1129]: [INFO] Registering dbus name com.system76.PowerDaemon
Sep 29 23:11:40 pop-os system76-power[1129]: [INFO] Adding dbus path /com/system76/PowerDaemon with interface com.system76.PowerDaemon
Sep 29 23:11:40 pop-os system76-power[1129]: [INFO] Handling dbus requests
Sep 29 23:12:08 pop-os system76-power[1129]: [INFO] DBUS Received GetSwitchable method
Sep 29 23:12:08 pop-os system76-power[1129]: [INFO] DBUS Received GetGraphics method
Sep 29 23:15:20 pop-os system76-power[1129]: [INFO] DBUS Received GetGraphics method
Sep 29 23:17:58 pop-os system76-power[1129]: [INFO] DBUS Received SetGraphics(nvidia) method
Sep 29 23:17:58 pop-os system76-power[1129]: [INFO] Creating /etc/modprobe.d/system76-power.conf
Sep 29 23:17:58 pop-os system76-power[1129]: [INFO] Enabling nvidia-fallback.service
Sep 29 23:17:59 pop-os system76-power[1129]: [INFO] Updating initramfs
Sep 29 23:17:59 pop-os system76-power[1129]: update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Config    : INFO     Looking for configuration...
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub           : INFO     System information:
Sep 29 23:18:10 pop-os system76-power[1129]:     OS:..................Pop!_OS 18.04
Sep 29 23:18:10 pop-os system76-power[1129]:     Root partition:....../dev/nvme0n1p3
Sep 29 23:18:10 pop-os system76-power[1129]:     Root FS UUID:........cd799293-f112-462e-9300-4059073163b4
Sep 29 23:18:10 pop-os system76-power[1129]:     ESP Path:............/boot/efi
Sep 29 23:18:10 pop-os system76-power[1129]:     ESP Partition:......./dev/nvme0n1p1
Sep 29 23:18:10 pop-os system76-power[1129]:     ESP Partition #:.....1
Sep 29 23:18:10 pop-os system76-power[1129]:     NVRAM entry #:.......-1
Sep 29 23:18:10 pop-os system76-power[1129]:     Boot Variable #:.....0000
Sep 29 23:18:10 pop-os system76-power[1129]:     Kernel Boot Options:.quiet loglevel=0 splash
Sep 29 23:18:10 pop-os system76-power[1129]:     Kernel Image Path:.../vmlinuz
Sep 29 23:18:10 pop-os system76-power[1129]:     Initrd Image Path:.../initrd.img
Sep 29 23:18:10 pop-os system76-power[1129]:     Force-overwrite:.....False
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Installer : INFO     Copying Kernel into ESP
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Installer : INFO     Copying initrd.img into ESP
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Installer : INFO     Setting up loader.conf configuration
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Installer : INFO     Backing up old kernel
Sep 29 23:18:10 pop-os system76-power[1129]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
-- Reboot --
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Starting daemon
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Rescanning PCI bus
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] 0000:00:02.0: Intel graphics
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] 0000:01:00.0: NVIDIA graphics
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Disabling NMI Watchdog (for kernel debugging only)
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Setting automatic graphics power
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Enabling graphics power
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Initializing with the balanced profile
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Connecting to dbus system bus
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Registering dbus name com.system76.PowerDaemon
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Adding dbus path /com/system76/PowerDaemon with interface com.system76.PowerDaemon
Sep 29 23:18:47 pop-os system76-power[1099]: [INFO] Handling dbus requests
Sep 29 23:19:32 pop-os system76-power[1099]: [INFO] DBUS Received GetSwitchable method
Sep 29 23:19:32 pop-os system76-power[1099]: [INFO] DBUS Received GetGraphics method
Sep 29 23:20:26 pop-os system76-power[1099]: [INFO] DBUS Received GetGraphics method

Steps to reproduce (if you know):
The above. Not sure exactly why this is happening. Any help would be appreciated.

Expected behavior:
I expect it to switch to nvidia.

Other Notes:

The name com.system76.PowerDaemon was not provided by any .service files.

Distribution (run cat /etc/os-release):

keiron@ScuffBookPro:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

N/A

Issue/Bug Description:

Unable to run, due to a missing service file.

Steps to reproduce (if you know):

sudo apt install cargo libdbus-glib-1-dev tlp acpi-call
git clone https://github.com/pop-os/system76-power
make
sudo make install

Expected behavior:

For it to run.

Actual behavior:

keiron@ScuffBookPro:~$ system76-power profile battery
system76-power: "The name com.system76.PowerDaemon was not provided by any .service files

Other Notes:

Nvidia GPU not disabled when switching to Intel Graphics (MSI GE40 laptop)

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.10"
VERSION_ID="18.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 1.0.0153780841018.10821cc23
Candidate: 1.0.0
153780841018.10821cc23
Version table:
*** 1.0.0153780841018.10~821cc23 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:
NVIDIA GPU is not disabled when switching to Intel Graphics and restarting. Intel driver is being used but LED indicator shows the Nvidia GPU is still enabled and power draw remains high (verified in powertop)

Laptop: MSI GE40
CPU: Intel(R) Core(TM) i7-4702MQ
GPU: Nvidia GTX 760M

Steps to reproduce (if you know):
Install nvidia 410 drivers via popshop.
Switch to intel graphics mode via gnome power settings drop down and restart.

Expected behavior:
Nvidia GPU should be disabled. The laptop LED indicator should be blue and power draw lower.

Other Notes:
GPU appears to be correctly disabled when the default nouveau drivers are used as the LED indicator goes blue and power draw/heat generation is as expected.

Journalctl /usr/bin/system76-power

-- Reboot --
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Starting daemon
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Rescanning PCI bus
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] 0000:01:00.0: NVIDIA graphics
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] 0000:00:02.0: Intel graphics
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Disabling NMI Watchdog (for kernel debugging only)
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Setting automatic graphics power
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Disabling graphics power
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] 0000:01:00.0: Removing
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Initializing with the balanced profile
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Connecting to dbus system bus
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Registering dbus name com.system76.PowerDaemon
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Adding dbus path /com/system76/PowerDaemon with interface com.system76.PowerDaemon
Oct 31 14:53:04 pop-os system76-power[1146]: [INFO] Handling dbus requests
Oct 31 14:53:24 pop-os system76-power[1146]: [INFO] DBUS Received GetSwitchable method
Oct 31 14:53:24 pop-os system76-power[1146]: [INFO] DBUS Received GetGraphics method
Oct 31 14:56:52 pop-os system76-power[1146]: [INFO] DBUS Received SetGraphics(nvidia) method
Oct 31 14:56:52 pop-os system76-power[1146]: [INFO] Creating /etc/modprobe.d/system76-power.conf
Oct 31 14:56:52 pop-os system76-power[1146]: [INFO] Enabling nvidia-fallback.service
Oct 31 14:56:52 pop-os system76-power[1146]: Created symlink /etc/systemd/system/multi-user.target.wants/nvidia-fallback.service → /lib/systemd/system/nvidia-fallback.service.
Oct 31 14:56:52 pop-os system76-power[1146]: [INFO] Updating initramfs
Oct 31 14:56:52 pop-os system76-power[1146]: update-initramfs: Generating /boot/initrd.img-4.18.0-10-generic
Oct 31 14:56:57 pop-os system76-power[1146]: cryptsetup: WARNING: Resume target cryptswap uses a key file
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Config    : INFO     Looking for configuration...
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub           : INFO     System information:
Oct 31 14:57:13 pop-os system76-power[1146]:     OS:..................Pop!_OS 18.10
Oct 31 14:57:13 pop-os system76-power[1146]:     Root partition:....../dev/dm-1
Oct 31 14:57:13 pop-os system76-power[1146]:     Root FS UUID:........e86d005e-7d62-4a00-b374-5c83869d5ac8
Oct 31 14:57:13 pop-os system76-power[1146]:     ESP Path:............/boot/efi
Oct 31 14:57:13 pop-os system76-power[1146]:     ESP Partition:......./dev/sdc1
Oct 31 14:57:13 pop-os system76-power[1146]:     ESP Partition #:.....1
Oct 31 14:57:13 pop-os system76-power[1146]:     NVRAM entry #:.......-1
Oct 31 14:57:13 pop-os system76-power[1146]:     Boot Variable #:.....0000
Oct 31 14:57:13 pop-os system76-power[1146]:     Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash
Oct 31 14:57:13 pop-os system76-power[1146]:     Kernel Image Path:.../vmlinuz
Oct 31 14:57:13 pop-os system76-power[1146]:     Initrd Image Path:.../initrd.img
Oct 31 14:57:13 pop-os system76-power[1146]:     Force-overwrite:.....False
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Installer : INFO     Copying Kernel into ESP
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Installer : INFO     Copying initrd.img into ESP
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Installer : INFO     Setting up loader.conf configuration
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Installer : INFO     Backing up old kernel
Oct 31 14:57:13 pop-os system76-power[1146]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
-- Reboot --
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Starting daemon
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Rescanning PCI bus
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] 0000:01:00.0: NVIDIA graphics
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] 0000:00:02.0: Intel graphics
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Disabling NMI Watchdog (for kernel debugging only)
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Setting automatic graphics power
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Enabling graphics power
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Initializing with the balanced profile
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Connecting to dbus system bus
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Registering dbus name com.system76.PowerDaemon
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Adding dbus path /com/system76/PowerDaemon with interface com.system76.PowerDaemon
Oct 31 14:58:20 pop-os system76-power[1161]: [INFO] Handling dbus requests
Oct 31 14:58:33 pop-os system76-power[1161]: [INFO] DBUS Received GetSwitchable method
Oct 31 14:58:33 pop-os system76-power[1161]: [INFO] DBUS Received GetGraphics method

When Intel graphics are selected:

inxi -G
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           Display: x11 server: X.Org 1.20.1 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa tty: N/A 
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 18.2.2 

When Nvidia graphics are selected:

inxi -G
Graphics:  Device-1: Intel 4th Gen Core Processor Integrated Graphics driver: i915 v: kernel 
           Device-2: NVIDIA GK106M [GeForce GTX 760M] driver: nvidia v: 410.57 
           Display: x11 server: X.Org 1.20.1 driver: modesetting,nvidia unloaded: fbdev,nouveau,vesa 
           resolution: 1920x1080~60Hz 
           OpenGL: renderer: GeForce GTX 760M/PCIe/SSE2 v: 4.6.0 NVIDIA 410.57 

license?

is there going to be a license for this project?

Intel TurboBoost doesn't activate after Switching from "Battery Life" Profile

Hardware

Lenovo Ideapad 310-15IKB

  • Intel Core i5 7200U

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Issue/Bug Description:

When I turn on the laptop it starts with the Balanced Profile, using powertop I can measure the Max CPU Frequency at 3.1GHz (Official TurboBoost Frequency for this model). After switching to Battery Life profile, and then switching back to Balanced or Performance profile, the Max CPU Frequency is 2.5GHz (Official Basic Frequency for this model). This will stay like this until I reboot the Computer.

Steps to reproduce:

  • Turn on PC.
  • Change Profile to Battery Life.
  • Change Profile to Balanced or Performance.

Expected behavior:

After changing the Profile to Balanced or Performance from Battery Life, TruboBoost should return to the default status of that Profile.

Turn off animations on battery mode

The idea is to turn off gnome animations on battery mode as:

Battery Life --> animations OFF
Balanced --> animations ON
High Performance --> animations ON

Main reason is that animations on battery mode can be slow probably caused by the cpu clock reduction, resulting in a bad UX + I think it make sense to disable animations as it's gonna consumes less resources (more battery life).

PopOS ERROR: NVIDIA driver is not loaded

Distribution (run cat /etc/os-release):

 linarcx@pop-os:~$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

Issue/Bug Description:
Hello, I installed popos recently. And when I open nvidia settings, it shows me a blank screen. This is the log of it when i open it from terminal:

ERROR: NVIDIA driver is not loaded
ERROR: Unable to load info from any available system
(nvidia-settings:1801): GLib-GObject-CRITICAL **: 01:14:15.455: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
** (nvidia-settings:1801): WARNING **: 01:14:15.459: PRIME: Failed to execute child process “/usr/bin/prime-supported” (No such file or directory)
** Message: 01:14:15.459: PRIME: is it supported? no
**Steps to reproduce (if you know):**

dmesg | grep nouveau shows nothing me dmesg alone print out a lot of messages like this:

[ 3266.660270] NVRM: No NVIDIA graphics adapter found!
[ 3266.660506] nvidia-nvlink: Unregistered the Nvlink Core, major device number 236

And also this is the output of lspci:

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.5 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 6 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port Mobile SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
03:00.0 Network controller: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express) (rev 01)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

Also i try to switch between graphic cards. from start menu i choose nvidia Graphics and hit restart button. but after login i still have same issues, although dmesg shows one more line:

[ 1594.612389] NVRM: No NVIDIA graphics adapter found!
[ 1594.612779] nvidia-nvlink: Unregistered the Nvlink Core, major device number 236
[ 1594.810600] nvidia-nvlink: Nvlink Core is being initialized, major device number 236

My nvidia driver :
GeForce GT 540M.

My laptop specifications:
https://www.asus.com/Laptops/K53SV/specifications/

Expected behavior:
Just nvidia driver works!

system76-power daemon unable to start if laptop is on battery mode from start

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 1.0.0153780841018.04821cc23
Candidate: 1.0.0
153780841018.04821cc23
Version table:
*** 1.0.0153780841018.04821cc23 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
1.0.0
153780841018.04821cc23~dev 500
500 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 Packages

Issue/Bug Description:
system76-power daemon unable to start if laptop is on battery from start with the following message
[INFO] Starting daemon
[INFO] Rescanning PCI bus
[INFO] 0000:00:02.0: Intel graphics
[INFO] 0000:01:00.0: NVIDIA graphics
[INFO] Disabling NMI Watchdog (for kernel debugging only)
[INFO] Setting automatic graphics power
[INFO] Enabling graphics power
[INFO] Initializing with the balanced profile
[ERROR] failed to set initial profile: Operation not permitted (os error 1)

This is cause the ability to switch from intel to nvidia or vice versa unable to function as the daemon could not be started.

sudo systemctl status system76-power.service
● system76-power.service - System76 Power Daemon
Loaded: loaded (/lib/systemd/system/system76-power.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sat 2018-10-06 00:06:55 +08; 806ms ago
Process: 7821 ExecStart=/usr/bin/system76-power daemon (code=exited, status=1/FAILURE)
Main PID: 7821 (code=exited, status=1/FAILURE)

Oct 06 00:06:55 chc-predator systemd[1]: system76-power.service: Service hold-off time over, scheduling restart.
Oct 06 00:06:55 chc-predator systemd[1]: system76-power.service: Scheduled restart job, restart counter is at 5.
Oct 06 00:06:55 chc-predator systemd[1]: Stopped System76 Power Daemon.
Oct 06 00:06:55 chc-predator systemd[1]: system76-power.service: Start request repeated too quickly.
Oct 06 00:06:55 chc-predator systemd[1]: system76-power.service: Failed with result 'exit-code'.
Oct 06 00:06:55 chc-predator systemd[1]: Failed to start System76 Power Daemon.

Steps to reproduce (if you know):
Start the laptop on battery

Expected behavior:
system76-power daemon should be able to start like previous version and ability to switch intel to nvidia or nvidia to intel fully function

Other Notes:

Documentation request

**Hardware: **
Few System76 Oryx pro 4 laptops with GTX 1070 Max-Q that run on Ubuntu 16.04 LTS.

Distribution (run cat /etc/os-release):

$ cat /etc/os-release
NAME="Ubuntu"
VERSION="16.04.6 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.6 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
Not compatible on Ubuntu 16.04.

Issue/Bug Description:
There is no information for System76 laptop owners to build the drivers.

Steps to reproduce (if you know):
There is no documentation for System76 customers to build the driver packages for their System76 laptops. System76 doesn't provide ppa for driver installation in Ubuntu 16.04.

Expected behavior:
Could you provide build instruction/documentation so that System76 laptop owner can build the driver by themselves? Thank you.

Other Notes:

Brightness at startup is fixed and has to be changed manually

Hardware:

Lenovo Thinkpad T430

Distribution (run cat /etc/os-release):

Pop!_OS 18.10

Issue/Bug Description:

Screen brightness after booting is fixed to a certain level (about 50%), no matter at what value it was set in the last session. You have to adjust the brightness manually everytime. Usually the last value should be set again.

Other Notes:

Others also have the problem, see: https://pop-planet.info/forums/threads/brightness-at-startup.80/

19.x release has long delay in unbinding the Nvidia GPU

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

system76-power:
  Installed: 1.0.0~1553639437~19.04~ce5c6e4
  Candidate: 1.0.0~1553639437~19.04~ce5c6e4
  Version table:
 *** 1.0.0~1553639437~19.04~ce5c6e4 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu disco/main amd64 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

Using Ubuntu base 19.04, unbinding the Nvidia GPU now takes approx 2-3 minutes vs 18.10 being nearly instant.

-- Reboot --
Apr 15 15:58:32 pop-os systemd[1]: Started System76 Power Daemon.
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] Starting daemon
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] Connecting to dbus system bus
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] Rescanning PCI bus
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:01:00.0: NVIDIA graphics
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:01:00.2: Function for 0000:01:00.0
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:01:00.0: Function for 0000:01:00.0
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:01:00.3: Function for 0000:01:00.0
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:01:00.1: Function for 0000:01:00.0
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:00:02.0: Intel graphics
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] 0000:00:02.0: Function for 0000:00:02.0
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] Disabling NMI Watchdog (for kernel debugging only)
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] Setting automatic graphics power
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] Disabling graphics power
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] xhci_hcd: Unbinding 0000:01:00.2
Apr 15 15:58:32 pop-os system76-power[945]: [INFO] nvidia-gpu: Unbinding 0000:01:00.3
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] snd_hda_intel: Unbinding 0000:01:00.1
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] 0000:01:00.2: Removing
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] 0000:01:00.0: Removing
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] 0000:01:00.3: Removing
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] 0000:01:00.1: Removing
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] Initializing with the balanced profile
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] Registering dbus name com.system76.PowerDaemon
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] Adding dbus path /com/system76/PowerDaemon with interface com.system76.PowerDaemon
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] hwmon: coretemp
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] hwmon: acpitz
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] hwmon: iwlwifi
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] hwmon: pch_cannonlake
Apr 15 16:02:07 pop-os system76-power[945]: [ERROR] fan daemon: platform hwmon not found
Apr 15 16:02:07 pop-os system76-power[945]: [INFO] Handling dbus requests

Expected behaviour:

This should be the same behaviour as 18.x distro release where the unbinding happens almost instantly.

Other Notes:

I will be trying builds from master, and perhaps insert some logging to see if I can identify where the delay is actually happening.

system76-power prevents leow9-w from shutting down when a u.2 drive is connected

Issue/Bug Description:
Having the system76-power package installed, prevents the leow9-w from properly shutting down when a u.2 drive is connected.

Steps I used to narrow down that system76-power is the package causing issues:

  1. Connect NVME drive as well as U.2 drive.
  2. Install Ubuntu 18.04 from the Ubuntu website to the NVME drive.
  3. Note that powering the machine off will work just fine.
  4. Installed NVIDIA drivers from system76 repo.
  5. Successfully power off the machine once again.
  6. Add system76-power.
  7. See that system does not successfully poweroff on it's own.

failed to set disk APM level on "/dev/md0" to X: No such file or directory (os error 2)

Distribution (run cat /etc/os-release):

Gentoo

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

7abac87

Issue/Bug Description:

See title

Steps to reproduce (if you know):

  • Have an md raid device node at /dev/md0
  • Run the daemon (you'll get a warning but it otherwise works fine):

[WARN] Failed to set initial profile: Errors found when setting profile:
- failed to set disk power profiles: failed to set disk APM level on "/dev/md0" to 127: No such file or directory (os error 2)

  • Change the profile from balanced to performance:
$ system76-power profile performance
setting power profile to performance
daemon returned an error message: "Errors found when setting profile:\n    - failed to set disk power profiles: failed to set disk APM level on \"/dev/md0\" to 254: No such file or directory (os error 2)"

Expected behavior:

I'm not sure what the expected behaviour should be (this could just be a misconfiguration on my part in which case feel free to close this issue) but since md is software raid I don't think it should be trying to change anything for this "disk" and should ignore it.

Other Notes:

Automatically enter High Performance when plugged in

When connected to power (and perhaps once the battery is charged to a certain percent), we should switch into High Performance mode. I don't see a strong argument for trying to save power when connected to an effectively unlimited source.

Of course we should switch back to whichever profile the user had set if they disconnect power.

Switch GPU without reboot

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="18.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.10"
VERSION_ID="18.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

system76-power:
Installed: 1.0.0154525425718.10d861dfd
Candidate: 1.0.0
154525425718.10d861dfd
Version table:
*** 1.0.0154525425718.10~d861dfd 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:

It would be great to be able to switch GPU without needing to reboot the PC.

There is an implementation that has been made by MathieuGras

Automatically enter Battery Life when battery is low

Inversely to #8, we should consider dropping into Battery Life mode when the battery is below a certain percentage and the device is running on battery power. Like the other modes, the user should be able to toggle it back to whichever profile they'd like.

nvidia 435, change the fan speed

Distribution (run cat /etc/os-release):
[szydell@laPtak ~]$ cat /etc/os-release
NAME=Fedora
VERSION="30 (Thirty)"
ID=fedora
VERSION_ID=30
VERSION_CODENAME=""
PLATFORM_ID="platform:f30"
PRETTY_NAME="Fedora 30 (Thirty)"
ANSI_COLOR="0;34"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:30"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f30/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=30
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=30
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
[root@laPtak ~]# dnf info nvidia-driver
Last metadata expiration check: 0:00:14 ago on pon, 23 wrz 2019, 15:31:59.
Installed Packages
Name : nvidia-driver
Epoch : 3
Version : 435.21
Release : 1.fc30
Architecture : x86_64
Size : 21 M
Source : nvidia-driver-435.21-1.fc30.src.rpm
Repository : @System
From repo : n17_nVidia
Summary : NVIDIA's proprietary display driver for NVIDIA graphic cards
URL : http://www.nvidia.com/object/unix.html
License : NVIDIA License
Description : This package provides the most recent NVIDIA display driver which allows for
: hardware accelerated rendering with recent NVIDIA chipsets.
:
: For the full product support list, please consult the release notes for driver
: version 435.21.

Issue/Bug Description:
From the 435 driver, Nvidia changed the way hybrid graphics works. By default, everything is rendered now on the Intel GPU. To use the Nvidia, the application must be started with a proper env variable (details here: http://download.nvidia.com/XFree86/Linux-x86_64/435.21/README/primerenderoffload.html).

A bug is a fan speed on oryp4. It is working and generating noise even when no application is rendering using Nvidia. Nvidia settings show that the temperature of the GPU is 41oC.

Steps to reproduce (if you know):
Install Nvidia 435 driver.

Expected behavior:
Please make my laptop quieter. I don't want to work on intel-only configuration whole time. :/

nvidia card not shutting down when booting with intel

  • currently on pop 18.04, nvidia 396
  • in intel mode, bbswitch reports that my gpu still on
  • I have nouveau blacklisted since it segfaults

is there any logs I can check to see why bbswitch is not turning off the nvidia card?

Possible system76-power Hard Drive power management problem

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

system76-power:
Installed: 1.0.0 1558479403 19.04 33fe432
Candidate: 1.0.0 1558479403 19.04 33fe432
Version table:
*** 1.0.0 1558479403 19.04 33fe432 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:

Non-OS Hard Drive keeps falling in sleep mode and waking up in intervals of a few seconds. After going into Gnome Disks application, then drive settings and changing APM to 128 disk behaves as before (goes to sleep after normal time of inactivity).

Steps to reproduce (if you know):

N/A

Expected behavior:

Hard Drive goes to sleep after a few minutes of inactivity.

Other Notes:

Hard Drive model name:
ST1000LM024 HN-M101MBB (2BA30002), 1.0TB

Failed to switch to Nvidia graphics

NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

I was playing on my Nvidia graphic, and suddenly everything became unresponsive, so I did a force-reboot. After the reboot, I am unable to switch to my Nvidia.

This is the recent reboot logs

-- Reboot --
Mar 29 23:59:56 pop-os system76-power[1074]: [INFO] Starting daemon
Mar 29 23:59:56 pop-os system76-power[1074]: [INFO] Connecting to dbus system bus
Mar 29 23:59:56 pop-os system76-power[1074]: [INFO] Rescanning PCI bus
Mar 29 23:59:56 pop-os system76-power[1074]: [INFO] 0000:01:00.0: NVIDIA graphics
...skipping...
Jul 19 19:52:55 saber-home system76-power[1189]:     nor crypto modules. If that's on purpose, you may want to uninstall the
Jul 19 19:52:55 saber-home system76-power[1189]:     'cryptsetup-initramfs' package in order to disable the cryptsetup initramfs
Jul 19 19:52:55 saber-home system76-power[1189]:     integration and avoid this warning.
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Config    : INFO     Looking for configuration...
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub           : INFO     System information:
Jul 19 19:53:04 saber-home system76-power[1189]:     OS:..................Pop!_OS 19.04
Jul 19 19:53:04 saber-home system76-power[1189]:     Root partition:....../dev/nvme0n1p4
Jul 19 19:53:04 saber-home system76-power[1189]:     Root FS UUID:........6867d90f-d33e-4e19-be8e-1c661ade81d9
Jul 19 19:53:04 saber-home system76-power[1189]:     ESP Path:............/boot/efi
Jul 19 19:53:04 saber-home system76-power[1189]:     ESP Partition:......./dev/nvme0n1p2
Jul 19 19:53:04 saber-home system76-power[1189]:     ESP Partition #:.....2
Jul 19 19:53:04 saber-home system76-power[1189]:     NVRAM entry #:.......-1
Jul 19 19:53:04 saber-home system76-power[1189]:     Boot Variable #:.....0000
Jul 19 19:53:04 saber-home system76-power[1189]:     Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash
Jul 19 19:53:04 saber-home system76-power[1189]:     Kernel Image Path:.../vmlinuz
Jul 19 19:53:04 saber-home system76-power[1189]:     Initrd Image Path:.../initrd.img
Jul 19 19:53:04 saber-home system76-power[1189]:     Force-overwrite:.....False
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Installer : INFO     Copying Kernel into ESP
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Installer : INFO     Copying initrd.img into ESP
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Installer : INFO     Setting up loader.conf configuration
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Installer : INFO     Backing up old kernel
Jul 19 19:53:04 saber-home system76-power[1189]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
Jul 19 19:53:08 saber-home system76-power[1189]: [INFO] caught signal: 15
Jul 19 19:53:09 saber-home system76-power[1189]: [INFO] daemon exited from loop
-- Reboot --
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] Starting daemon
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] Connecting to dbus system bus
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] Rescanning PCI bus
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] 0000:01:00.0: NVIDIA graphics
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] 0000:01:00.0: Function for 0000:01:00.0
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] 0000:01:00.1: Function for 0000:01:00.0
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] 0000:00:02.0: Intel graphics
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] 0000:00:02.0: Function for 0000:00:02.0
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] Disabling NMI Watchdog (for kernel debugging only)
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] Setting automatic graphics power
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] Disabling graphics power
Jul 19 19:53:34 saber-home system76-power[1154]: [INFO] snd_hda_intel: Unbinding 0000:01:00.1
Jul 19 19:53:35 saber-home system76-power[1154]: [INFO] 0000:01:00.0: Removing
Jul 19 19:53:35 saber-home system76-power[1154]: [INFO] 0000:01:00.1: Removing
Jul 19 19:53:35 saber-home system76-power[1154]: [INFO] Initializing with the balanced profile
Jul 19 19:53:35 saber-home system76-power[1154]: [WARN] Failed to set initial profile: Errors found when setting profile:
Jul 19 19:53:35 saber-home system76-power[1154]:     - failed to set scsi host profiles: failed to set link time power management policy med_power_with_dipm on host0: No such file or director
Jul 19 19:53:35 saber-home system76-power[1154]: [INFO] Registering dbus name com.system76.PowerDaemon
Jul 19 19:53:35 saber-home system76-power[1154]: [INFO] Adding dbus path /com/system76/PowerDaemon with interface com.system76.PowerDaemon
Jul 19 19:53:35 saber-home system76-power[1154]: [ERROR] fan daemon: platform hwmon not found
Jul 19 19:53:35 saber-home system76-power[1154]: [INFO] Handling dbus requests
Jul 19 19:54:03 saber-home system76-power[1154]: [INFO] DBUS Received GetSwitchable method
Jul 19 19:54:03 saber-home system76-power[1154]: [INFO] DBUS Received GetGraphics method
Jul 19 19:54:03 saber-home system76-power[1154]: [INFO] DBUS Received GetProfile method


[REQUEST] Add option for AMD - NVIDIA switching for AMD APUs (Ryzen)

I don't know why no one is talking about this. But, this is a problem I'm currently stuck at.
I have an laptop with AMD APU (Ryzen 5 - 2500U) & nvidia gtx 1050. This laptop is Muxless. This laptop's display is attached to the iGPU (Vega 8).

I want to use Vega for normal tasks. & Nvidia for process hungry tasks (mainly CUDA & ML training stuffs).

There are many (glitchy) options for switching graphics (e.g Prime, bumblebee) . But, everyone states about Intel-nvidia. If you search more, you can find some about intel-amd switching.

But, nothing for AMD-nvidia switching.

APUs are things. Can anyone tell me how I can do this?

Note : I can't disable any graphics on bios. My laptop doesn't allow it.

Laptop : Asus F570D

What I have tried : I tried installing ubuntu multiple times. It (almost) disappointed me everytime. The last time I did, it was ALMOST working correctly (by setting flags like - noveau.modeset=0 ). It just sometimes freeze during boot forever.

Power state returns to Balanced after locking or suspending

Distribution (run cat /etc/os-release):
Pop!_OS 18.04

Issue/Bug Description:
Switching the power state to High Performance or Battery life and then locking the machine, when unlocking the machine the power state is back to Balanced.

Steps to reproduce (if you know):

  1. Switch to different power state.
  2. Lock or suspend the machine.
  3. Resume the machine (unlock).
  4. Note that the power state has returned to Balanced.

Expected behavior:
Power state should remain in selected power state.

Daemon does not set fan to auto after termination.

There should be a catch of SIGTERM and other signals when the daemon is stopped for any reason, and make sure that the fan is set back to auto.

If the user runs "sudo systemctl stop system76-power" and then starts a game or whatever, it will fry the machine :)

Discrete graphics turn on after suspend

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="18.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.10"
VERSION_ID="18.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

system76-power:
  Installed: 1.0.0~1555432002~18.10~1c347b8
  Candidate: 1.0.0~1555432002~18.10~1c347b8
  Version table:
 *** 1.0.0~1555432002~18.10~1c347b8 1001
       1001 http://ppa.launchpad.net/system76/pop/ubuntu cosmic/main amd64 Packages
        100 /var/lib/dpkg/status

Issue/Bug Description:

I am on a Lenovo T480 with intel and nvidia (mx150), when running on intel, after returning from suspend, the nvidia card is silently powered on.

Steps to reproduce (if you know):

Boot the machine in intel mode, check the power with system76-power graphics power, suspend and then power on and check again.

Expected behavior:

If nvidia is powered off at any point in time, I would expect to be kept off even if I suspend the machine for a while.

I dropped the following script into /lib/systemd/system-sleep as a workaround:

#!/usr/bin/env bash
case $1 in
  post)
    if [ $(/usr/bin/system76-power graphics) == "intel" ]; then 
     /usr/bin/system76-power graphics power off;
    fi
    ;;
esac

Other Notes:

Also noticed while testing that issuing system76-power graphics power off while in nvidia mode leaves the system76-power command unresponsive and the machine hangs trying to suspend, that's why the script has an if, I would expect system76-power just to give an error saying it is not possible to power off the card being in use.

intel mode not switching to intel for Vulkan

Note, my laptop is an Oryx Pro.

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 0.1.2152789808918.04038f099
Candidate: 0.1.2
152789808918.04038f099
Version table:
*** 0.1.2152789808918.04038f099 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
0.1.2
152789808918.04038f099~dev 500
500 http://ppa.launchpad.net/system76-dev/stable/ubuntu bionic/main amd64 Packages

Issue/Bug Description:
when set to intel mode, opengl apps correctly run using the Intel graphics card, but Vulkan apps fail. the error message given indicates they're still trying to use the NVidia card, which is shut off:

tessa@viper:~$ system76-power graphics
intel
tessa@viper:~$ vulkaninfo 
===========
VULKAN INFO
===========

Vulkan Instance Version: 1.1.70

Xlib:  extension "NV-GLX" missing on display ":0".
/build/vulkan-Kbdbga/vulkan-1.1.70+dfsg1/demos/vulkaninfo.c:2700: failed with VK_ERROR_INITIALIZATION_FAILED

Steps to reproduce (if you know):
set laptop to intel graphics, try to run Vulkan applications.

Expected behavior:
Applications run at reduced performance.

Other Notes:
It's especially strange because Vulkan should be able to handle video cards from multiple vendors present, so I'm not sure what the graphics switch app is actually doing here to break this.

system76-power incompatible with nvidia-driver-418

Distribution (run cat /etc/os-release):

NAME="Pop!_OS"
VERSION="18.04 LTS"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

On an oryp4 laptop running nvidia-driver-418.

Issue/Bug Description:

I cannot switch to Intel graphics using system76-power graphics intel.

The command itself doesn't print out any errors, but here's what's in the logs:

Apr 29 16:01:18  system76-power[1423]: [INFO] DBUS Received SetGraphics(intel) method
Apr 29 16:01:18  system76-power[1423]: [INFO] Creating /etc/modprobe.d/system76-power.conf
Apr 29 16:01:18  system76-power[1423]: [INFO] Disabling nvidia-fallback.service
Apr 29 16:01:18  system76-power[1423]: Failed to disable unit: Unit file nvidia-fallback.service does not exist.
Apr 29 16:01:18  system76-power[1423]: [ERROR] systemctl: failed with exit code: 1
Apr 29 16:01:18  system76-power[1423]: [INFO] Updating initramfs
Apr 29 16:01:18  system76-power[1423]: update-initramfs: Generating /boot/initrd.img-4.18.0-18-generic
Apr 29 16:01:34  system76-power[1423]: kernelstub.Config    : INFO     Looking for configuration...
Apr 29 16:01:34  system76-power[1423]: kernelstub           : INFO     System information:
Apr 29 16:01:34  system76-power[1423]:     OS:..................Pop!_OS 18.04
Apr 29 16:01:34  system76-power[1423]:     Root partition:....../dev/dm-1
Apr 29 16:01:34  system76-power[1423]:     Root FS UUID:........21898a4f-6af8-4792-86aa-e3ba4bdc6302
Apr 29 16:01:34  system76-power[1423]:     ESP Path:............/boot/efi
Apr 29 16:01:34  system76-power[1423]:     ESP Partition:......./dev/nvme0n1p1
Apr 29 16:01:34  system76-power[1423]:     ESP Partition #:.....1
Apr 29 16:01:34  system76-power[1423]:     NVRAM entry #:.......-1
Apr 29 16:01:34  system76-power[1423]:     Boot Variable #:.....0000
Apr 29 16:01:34  system76-power[1423]:     Kernel Boot Options:.quiet loglevel=0 systemd.show_status=false splash
Apr 29 16:01:34  system76-power[1423]:     Kernel Image Path:.../vmlinuz
Apr 29 16:01:34  system76-power[1423]:     Initrd Image Path:.../initrd.img
Apr 29 16:01:34  system76-power[1423]:     Force-overwrite:.....False
Apr 29 16:01:34  system76-power[1423]: kernelstub.Installer : INFO     Copying Kernel into ESP
Apr 29 16:01:34  system76-power[1423]: kernelstub.Installer : INFO     Copying initrd.img into ESP
Apr 29 16:01:34  system76-power[1423]: kernelstub.Installer : INFO     Setting up loader.conf configuration
Apr 29 16:01:34  system76-power[1423]: kernelstub.Installer : INFO     Making entry file for Pop!_OS
Apr 29 16:01:34  system76-power[1423]: kernelstub.Installer : INFO     Backing up old kernel
Apr 29 16:01:34  system76-power[1423]: kernelstub.Installer : INFO     Making entry file for Pop!_OS

Looking at this part:

Apr 29 16:01:18  system76-power[1423]: [INFO] Disabling nvidia-fallback.service
Apr 29 16:01:18  system76-power[1423]: Failed to disable unit: Unit file nvidia-fallback.service does not exist.
Apr 29 16:01:18  system76-power[1423]: [ERROR] systemctl: failed with exit code: 1

I found that the file existed in the nvidia-kernel-common-390 package:

$ apt-file search nvidia-fallback.service
nvidia-kernel-common-390: /lib/systemd/system/nvidia-fallback.service

but not nvidia-kernel-common-418:

$ dpkg -L nvidia-kernel-common-418
/.
/lib
/lib/modprobe.d
/lib/modprobe.d/nvidia-graphics-drivers.conf
/lib/udev
/lib/udev/rules.d
/lib/udev/rules.d/71-nvidia.rules
/sbin
/sbin/create-uvm-dev-node
/usr
/usr/share
/usr/share/doc
/usr/share/doc/nvidia-kernel-common-418
/usr/share/doc/nvidia-kernel-common-418/changelog.Debian.gz
/usr/share/doc/nvidia-kernel-common-418/copyright
/usr/share/initramfs-tools
/usr/share/initramfs-tools/hooks
/usr/share/initramfs-tools/hooks/framebuffer-nvidia

Switching power profiles will change display backlight

Distribution (run cat /etc/os-release):
NAME="Pop!_OS"
VERSION="18.10"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 18.10"
VERSION_ID="18.10"
HOME_URL="https://system76.com/pop"
SUPPORT_URL="http://support.system76.com"
BUG_REPORT_URL="https://github.com/pop-os/pop/issues"
PRIVACY_POLICY_URL="https://system76.com/privacy"
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 1.0.0154402773718.10413bafe
Candidate: 1.0.0
154402773718.10413bafe
Version table:
*** 1.0.0154402773718.10~413bafe 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:
According to Wiki, switching power profiles between balanced and performance should not change display backlight (The wiki even provides a section discussing why this should be the case). I totally agree with this setting.

However, on my laptop, system76-power doesn't behave as it is supposed to do.

  • When switch from performance to balanced, the display backlight is dimmed to a medium-low level from what ever I was using when I was in performance mode.
  • When switch from balanced up to performance, the display backlight is not changed. This case is working properly just like the wiki says.
  • When switch to battery life mode from either performance or balanced, the light is automatically dimmed to low level to save battery life. This case is also working properly.

Steps to reproduce (if you know):

Expected behavior:
Switch power profiles between performance and balanced should not modify screen backlight like what is suggested in the wiki.

Other Notes:

Unable to switch from Nvidia to Intel

Distribution (run cat /etc/os-release):
NAME="Ubuntu"
VERSION="18.04.1 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.1 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

Related Application and/or Package Version (run apt policy $PACKAGE NAME):
system76-power:
Installed: 0.1.2153670443918.04ad63c63
Candidate: 0.1.2
153670443918.04ad63c63
Version table:
*** 0.1.2153670443918.04~ad63c63 1001
1001 http://ppa.launchpad.net/system76/pop/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

Issue/Bug Description:
Using system76-power to switch from the (active) nvidia mode to intel mode results in nothing happening, and the computer continuing to run in nvidia mode. This causes my laptop to heat up faster, run louder, and use more battery.

Steps to reproduce (if you know):

  1. Activate "Nvidia Graphics" mode
  2. Select "Intel Graphics" from the system menu in Gnome, or run sudo system76-power graphics nvidia in a terminal
  3. Reboot

Expected behavior:
Computer reboots into Intel graphics mode

Other Notes:
Test machine: Sony SVF15N18PXB
GPU: NVIDIA GK208M [GeForce GT 735M] (rev a1)

I'm not sure when the original switch from intel to nvidia mode occurred, but it was likely several weeks ago when I was testing a Steam game.

Instructions for building a .deb would be nice

I am trying to use this code with a custom Debian install, I fetched and successfully built the code but there is no way to use it since it needs various service files and stuff set up due to dbus tomfoolery. Since it can't work without install scripts, anyone who wants to use it has to build a .deb. Could we add a make target for that or something?

A case for a latency-tuned performance profile

This is a follow up to my comment here: #2 (comment)

I came across some interesting performance discussions regarding Mac OS tuning (from the engineers) and RedHat tuning. Here are the two PDFs:

https://access.redhat.com/sites/default/files/attachments/201501-perf-brief-low-latency-tuning-rhel7-v1.1.pdf (see in particular p. 8 about performance profiles: "Because tuning for throughput often at odds with tuning for latency, profiles have been split along those boundaries as well providing a “balanced” profile").

Mac OS X it seems was tuned historically around audio performance and then battery life, because that is what revived the company and its core customer demographic. So OS X prioritizes audio latency above all other non-critical primary threads at all times, at the expense of throughput:
https://www.cse.unsw.edu.au/~cs9242/10/lectures/09-OSXAudio.pdf

Based on this, it seems to be somewhat of a case of "throughout, battery life, low latency: pick any two" and that philosophy could guide the shaping of performance profiles.

This means that anyone who needs a low latency system (such as for multimedia production) could benefit from a performance profile tuned to reduce both (average) latency and jitter (variation in latency).

In summary, I think it would be a mistake to conclude that a latency-tuned performance profile is only relevant and useful for certain server setups. It absolutely has a use in a desktop system with regards to multimedia work involving minute timing issues, as most audio and video does. In my research to configure my own system for audio production, I have also come across certain science and research applications also demand latency tuned systems.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.