-
Notifications
You must be signed in to change notification settings - Fork 12
reboot required to switch on Ubuntu 17.10 #34
Comments
As far as I can tell, that's a side effect of newer kernels alongside newer Nvidia drivers. Mint is the equivalent of goint back to Ubuntu 16.04 and using the default 4.4 kernel, so that might work for you. |
Oh, I have to use the 4.13 kernel... So I guess I'm doomed :( By the way, I read on nvidia dev talks that using systemctl restart display-manager after logout from the vterm resolves the restart issue.. Maybe you could add that to prime-indicator, if it detects the kernel\drivers are too new to just logout\login. Edit: Maybe a better way would be to ditch prime-select altogether and use nvidia-xrun instead. |
Wow, pretty cool. Thanks a lot. I haven't been having a lot of time to mess with this indicator. I'll see if I can pinpoint to yoh the location to insert the systemctl restart command in the scripts to see if it works for you. |
I've got an update - the restart of the display manager is only needed for GDM (maybe also Gnome) - moved to Cinnamon and LightDM, and now it works fine! |
I remember this whole scheme needed LightDM when I was researching how to
enable it for other distros.
…On Thu, May 17, 2018, 4:24 PM Guy Brand ***@***.***> wrote:
I've got an update - the restart of the display manager is only needed for
GDM (maybe also Gnome) - moved to Cinnamon and LightDM, and now it works
fine!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#34 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFd-utuP_xSCvivGrhvPzJL0_cJKw9NXks5tzc5pgaJpZM4T9lpC>
.
|
nvidia-xrun hasn't seen an update in awhile, and it seems to be the successor to bumblebee not nvidia-prime. I see a future for it where nvidia works like it does on windows with optimus. We could replace logout with sudo reboot or sudo systemctl restart display-manager |
ok so sudo systemctl restart display-manager is slower then a reboot and didn't switch the graphics. |
@aaahh restart display-manager was much faster than reboot on my machine, and it did switch the graphics.... And when I switched to lightDM, even this restart is not needed anymore. My nvidia-prime version is 0.8.5, perhaps 0.8.8 in bionic beaver is the problem? |
I have to take a proper look into this, but until September I can't promise anything... What I would do to try and pinpoint the problem is to switch graphics using the NVIDIA's control panel and seeing what it takes to do so properly. Is it a reboot? Log out and then in? Restarting the display-manager? A combination of some of these? My Indicator is basically a fancy icon in the tray + a script to run the switching without needing to sudo manually. |
I am on 0.8.8, also you were right on lighdm dependency, the power of Nvidia is found at everywhere I'm reading a reboot is required for 390. I remember reading somewhere that the alternative is basically to restart everything which is effectively a soft-reboot |
I get
I got nvidia 390.59-0ubuntu0~gpu17.10.1 with kernel 4.13.0-41-generic, and it work just fine with just login\logout with lightDM... Using the nvidia-settings control panel to switch, as @andrebrait suggested also works for me with a simple login/logout. |
Nvidia-settings tells me to "Please restart your computer to apply the changes" It's the kernel, 4.15.0-21-generic |
cat: /sys/kernel/debug/vgaswitcheroo/switch: No such file or directory |
Make sure you have intel switched on |
Yes, I'm on the iGPU right now. |
Well nvidia prime uses either vgaswicheroo or bbswitch, so I have no idea what is being used on your system, either way 0.8.8 and 4.15 brings switcheroo and requires reboot |
bbswitch has a problem loading on my system: dmesg | grep bbswitch
But I still switch with no problem... |
Can you tell if your nvidia is on? Like extra heat? I’m guessing your graphics card is never turned off |
sudo cat /etc/prime-discrete |
Using Ubuntu 17.10 with nvidia-390, Switching (either from intel to nvidia, or from nvidia to intel) no longer happens on logout, but requires fool restart.
The indicator asks to confirm logout, but does nothing. And manual logout results in a login loop.
After a restart the gpu is switched.. I wonder if that's an Ubuntu thing? Will switching to Mint 18.3 solve this problem?
The text was updated successfully, but these errors were encountered: