In my last post I was supposed to use your-user-name intead of my actual user name, so I corrected that. The reason I don’t usezangetsu wrote: I'd like to suggest for the previous post to edit the command stringsudo sh /home/yourUsername/.nvidia-offand substitute it withsudo sh ~/.nvidia-offbecause some forum user in future could be do a simple cut and paste of that and surely they will have a different username
~/ instead of /home/your-user-name is because there are some situations where ~/ won’t work in commands. This is one of them. If you change the Command line in the NVIDIA OFF launcher to sudo sh ~/.nvidia-off, then it won’t work when it is clicked. Try doing that and then use this command to check if the Nvidia card is ON or OFF:cat /proc/acpi/bbswitchHowever, if I run the .nvidia-off script in the Terminal using this command, then it works:
sudo sh ~/.nvidia-offThe same situation applies if I add a custom command to Session and Startup.
The bbswitch module will still be running until you restart or reboot. This command used in the Terminal will power the Nvidia card back on:zangetsu wrote: Last thing, at least for a while
-After having disabled it, what if do I want to enable again nvidia card without a system reboot? Will something likemodprobe bbswitch && echo "ON" > /proc/acpi/bbswitchwork?
sudo tee /proc/acpi/bbswitch <<<ONOr this command used in a script:
echo "ON" > /proc/acpi/bbswitchHowever, the Nvidia chip (the Graphics Processing Unit) on the card can’t be used until the Nvidia GPU is enabled in the PRIME Profiles page of Nvidia Settings or by using the command
sudo prime-select nvidia. Then you will need to reboot.So there’s no need to manually power on the Nvidia card. When you switch to the Nvidia GPU and reboot, the card will be powered on.
@roblm, thank you very much for your time