bumblebee team mailing list archive

[Marcos Alano <1758243@xxxxxxxxxxxxxxxxxx>]

Hi!

I thought NVIDIA On-demand would be enabled with the next version of
xserver. Wouldn't it?

Marcos Alano
Linux System Administrator
marcoshalano@xxxxxxxxx

On Thu, Oct 17, 2019, 06:41 Mathieu Reho <1758243@xxxxxxxxxxxxxxxxxx>
wrote:

> @Rocko
>
> Hello,
> Thank you for your help. Unfortunately your solution isn't working for me.
> I enabled the "NVIDIA On-Demand" parameter from nvidia-settings, then
> restarted my computer and exported all the env variables. I tried to launch
> a game, CS:GO for example, and when I type "mat_info" to see on which
> graphic chip it started, it tells me "Intel Graphics 630".
> It is starting on my Nvidia chip only if I force it in "PRIME Profiles"
> from nvidia-settings panel.
> Maybe if I make an "Application Profile" for all the programs that need
> graphic ressources I can get around the problem..
>
> I run on a Dell XPS 15 7590, with Ubuntu 19.10 installed and kernel
> 5.3.0-18-generic.
> The installed Nvidia driver is 435.21-0ubuntu2.
>
> If someone have a suggestion, please let me know :)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1758243
>
> Title:
>   bumblebee needs configuration changes to work with nvidia-driver-390
>   and libglvnd0
>
> Status in bumblebee package in Ubuntu:
>   Confirmed
>
> Bug description:
>   bumblebee fails to work in Ubuntu 18.04 with nvidia-driver-390 unless
>   these configuration changes are made:
>
>   1. For optirun to work, /etc/bumblebee/bumblebee.conf needs two
>   library paths changed (because of the changes for GLVND):
>
>   [driver-nvidia]
>   LibraryPath=/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu
>
> XorgModulePath=/usr/lib/x86_64-linux-gnu/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules/input
>
>   With these changes, optirun works correctly on my laptop (using the
>   primus bridge) but primusrun still fails.
>
>   2. For power management to work (ie turning the nvidia card off whilst
>   not in use), the nouveau and nvidia modules need blacklisting so they
>   don't load on boot, and nvidia_drm and nvidia_modeset need aliasing to
>   off so they never load. Otherwise, nvidia_drm attaches to
>   drm_kms_helper and then bumblebee can't unload the nvidia module and
>   turn off the card. This configuration file in /etc/modprobe.d/nvidia-
>   bl.conf works for me:
>
>   blacklist nouveau
>   blacklist nvidia
>   blacklist nvidia_drm
>   blacklist nvidia_modeset
>   alias nouveau off
>   alias nvidia_drm off
>   alias nvidia_modeset off
>
>   (The first two lines are already in bumblebee.conf. I found I also had
>   to alias nouveau to off because gdm?/mutter? so desperately wants to
>   load it.)
>
>   Update: aliasing nouveau to off doesn't stop the nvidia-fallback
>   service from loading the nouveau module, so if nouveau is still
>   loading, you could try running this command:
>
>   systemctl disable nvidia-fallback.service
>
>   You'll need to reboot because nouveau is already loaded, but the
>   change should be permanent unless something else re-enables the
>   nvidia-fallback service.
>
>   Finally, to run mesa applications, you need to set this variable:
>
>   export __GLVND_DISALLOW_PATCHING=1
>
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: bumblebee 3.2.1-17
>   Uname: Linux 4.16.0-041600rc6-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu10
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Fri Mar 23 12:18:02 2018
>   InstallationDate: Installed on 2017-08-16 (218 days ago)
>   InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
>   SourcePackage: bumblebee
>   UpgradeStatus: Upgraded to bionic on 2017-11-17 (125 days ago)
>   modified.conffile..etc.bumblebee.xorg.conf.nouveau: [modified]
>   modified.conffile..etc.bumblebee.xorg.conf.nvidia: [modified]
>   mtime.conffile..etc.bumblebee.bumblebee.conf: 2018-03-23T12:17:54.683287
>   mtime.conffile..etc.bumblebee.xorg.conf.nouveau:
> 2018-03-22T14:01:52.732698
>   mtime.conffile..etc.bumblebee.xorg.conf.nvidia:
> 2018-03-22T14:57:34.141995
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions
>

-- 
You received this bug notification because you are a member of Bumblebee
Project, which is subscribed to bumblebee in Ubuntu.
Matching subscriptions: Bumblebee Team
https://bugs.launchpad.net/bugs/1758243

Title:
  bumblebee needs configuration changes to work with nvidia-driver-390
  and libglvnd0

Status in bumblebee package in Ubuntu:
  Confirmed

Bug description:
  bumblebee fails to work in Ubuntu 18.04 with nvidia-driver-390 unless
  these configuration changes are made:

  1. For optirun to work, /etc/bumblebee/bumblebee.conf needs two
  library paths changed (because of the changes for GLVND):

  [driver-nvidia]
  LibraryPath=/usr/lib/x86_64-linux-gnu:/usr/lib/i386-linux-gnu
  XorgModulePath=/usr/lib/x86_64-linux-gnu/nvidia/xorg,/usr/lib/xorg/modules,/usr/lib/xorg/modules/input

  With these changes, optirun works correctly on my laptop (using the
  primus bridge) but primusrun still fails.

  2. For power management to work (ie turning the nvidia card off whilst
  not in use), the nouveau and nvidia modules need blacklisting so they
  don't load on boot, and nvidia_drm and nvidia_modeset need aliasing to
  off so they never load. Otherwise, nvidia_drm attaches to
  drm_kms_helper and then bumblebee can't unload the nvidia module and
  turn off the card. This configuration file in /etc/modprobe.d/nvidia-
  bl.conf works for me:

  blacklist nouveau
  blacklist nvidia
  blacklist nvidia_drm
  blacklist nvidia_modeset
  alias nouveau off
  alias nvidia_drm off
  alias nvidia_modeset off

  (The first two lines are already in bumblebee.conf. I found I also had
  to alias nouveau to off because gdm?/mutter? so desperately wants to
  load it.)

  Update: aliasing nouveau to off doesn't stop the nvidia-fallback
  service from loading the nouveau module, so if nouveau is still
  loading, you could try running this command:

  systemctl disable nvidia-fallback.service

  You'll need to reboot because nouveau is already loaded, but the
  change should be permanent unless something else re-enables the
  nvidia-fallback service.

  Finally, to run mesa applications, you need to set this variable:

  export __GLVND_DISALLOW_PATCHING=1


  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bumblebee 3.2.1-17
  Uname: Linux 4.16.0-041600rc6-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 12:18:02 2018
  InstallationDate: Installed on 2017-08-16 (218 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: bumblebee
  UpgradeStatus: Upgraded to bionic on 2017-11-17 (125 days ago)
  modified.conffile..etc.bumblebee.xorg.conf.nouveau: [modified]
  modified.conffile..etc.bumblebee.xorg.conf.nvidia: [modified]
  mtime.conffile..etc.bumblebee.bumblebee.conf: 2018-03-23T12:17:54.683287
  mtime.conffile..etc.bumblebee.xorg.conf.nouveau: 2018-03-22T14:01:52.732698
  mtime.conffile..etc.bumblebee.xorg.conf.nvidia: 2018-03-22T14:57:34.141995

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bumblebee/+bug/1758243/+subscriptions