-
Notifications
You must be signed in to change notification settings - Fork 165
-
Notifications
You must be signed in to change notification settings - Fork 165
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't switch to nvidia card #39
Comments
Try latest version on AUR |
Yes please, latest version should be 0.6. (If the problem persists, please also post the log from the GDM service) |
Can't do much with that limited log, use the command |
I removed the nvidia drivers and I could login, then I installed again the latest version with its dependencies. Here are the logs now..
|
Sounds like your Nvidia driver isn't installed properly. If you completely remove optimus-manager and install the latest nvidia driver like you did before, are you able to execute the following commands without errors ?
|
With this installed:
This is the error:
|
Remove optimus-manager, and remove linux316-nvidia, mhwd-nvidia-340xx, mhwd-nvidia-390xx as well (those are outdated). Then try those commands again. |
I don't close this issue because I want to test it again.. It worked for me, but when I removed all and reinstall the drivers, it stop working.
|
I have the same issue. If I remove optimus-manger, uninstall then reinstall drivers I'm able to switch to Nvidia. However, upon reboot I'm unable to switch back to Nvidia. I was able to solve any issues with a black screen upon boot by adding |
Still having the same issue so will add to this thread instead of creating a new ticket because I think I'm experiencing the same problem as @Martin317 OS: Manjaro 18.0.2 Illyria
Would having a mhwd-gpu.conf file interfere with GPU switching?
|
Could you describe the issue more accurately ? Are you having an issue with starting in Nvidia mode, or starting in Intel and then switching to Nvidia ? In any case, how does it fail ? (like, is there a black screen, are you back to the login screen, are you able to switch to a TTY, etc) |
The issue is starting in Intel and then switching to Nvidia.
Afterward the screen goes black for 2 seconds before displaying the login screen.
|
Can you post the log of SDDM after trying to switch to Nvidia ? (use |
Issue here: |
This error means that the |
After reinstalling 'linux420-nvidia' and rebooting, there is still an issue. |
That could be a hardware incompatibility with your laptop model. What happens if you set the (note : please use pastebins to post logs instead of copypasting them directly in your posts) |
Never considered that. |
Hmmm 🤔 Then restart your computer and try again. |
This seems to work! |
Alright, so it's a bbswitch conflict. Someone else has asked for the bbswitch package to be removed from the dependencies because of another issue, so from the next release on I'll just mark it as optional and have a runtime check to see if it is available. That should solve both issues. Thanks for your input ! |
Optimus-manager works for me, but I have a friend I tried to guide to set it up but he has the same issue, or at least the outcome is the same: system boots in intel mode and when trying to switch to nvidia, session restarts and he is still in intel mode. We couldn't see any errors in any journals so far. I we wanted to try blacklisting bbswitch, one needs to have nouveau installed first? Right? But by default, it isn't so which package needs to be added to install nouveau? So am I right to say that first we need to install:
then blacklist bbswitch, reboot and test if it works? |
Hello, I will try it!! Thanks to all. |
@michaldybczak , the nouveau driver is already built into the kernel so you don't have to install anything else. Not sure what this package does. Also, even though the symptoms of your problem are similar to Martin's, there can be a whole range of reasons why optimus-manager refuses to do the switch. It may not necessary be a problem with bbswitch. But to troubleshoot further I would need some logs (at least the one from the display manager). |
It works for me too! Should I close this issue? My final packages:
And blacklist conf file like @Askannz said: |
He tried blacklisting bbswitch but it didn't help. Here are outputs I got from him. There are couple of differences in files here and there but I thought that you may notice something alarming or suspicious. Can you look? Most look OK but some things make me wonder... For example, I have optimus-manager.conf with intel in intel mode. He doesn't have it. He has /etc/mhwd-x86_64.conf I don't (optimus-manager works for me). At this point I'm not sure where to look or what looks OK or not. He has some amd confs, which is confusing for me. How? I asked him and I'm waiting for replay. Any of these may or may not interfere with optimus-manager but I can only guess. Here is the output:
/etc/mhwd-x86_64.conf (cat: MHWD64_IS_LIB32=“true”)
|
thank you @michaldybczak for helping me.
we using |
Reporting back again. Updated to the latest stable release of Manjaro which updated the kernel and Nvidia drivers. The update seems to have prevented switching from Intel to Nvidia again. To confirm, when on intel and trying to switch, the system simply goes back to the login screen after a few seconds. After logging in and checking the mode, Intel is shown. See the log of SDDM when trying to switch to Nvidia: |
There was update a few days ago in Manjaro testing that complained about not being able to write into nvidia-xorg.conf and that surprised me, so I looked up and it RESTORED this conf so I had to disable it again. I rebooted and optimus-manager worked as always for me, so aside of that, I didn't notice any problems. |
Sorry for the loooong delay, I was on leave. I think the root cause to all of those problems is MHWD (the hardware detection/driver installation tool of Manjaro). MHWD should NOT be used with optimus-manager (I should have made that more clear in the README). It's going to autogenerate files in If you have used it already, try wiping everything in |
MHWD confs are disabled but MHWD itself is still on the system so I guess, updates may trigger refreshing of confs. I don't think that uninstalling MHWD is wise thou. |
I have never seen mhwd regenerate files in |
I didn't touch mhwd and the info was definitely during the update, so something else must have triggered it. At this moment it's pointless to discuss it since I don't have the update output anymore. |
This issue occurs on ArchLinux too if you have the |
Further investigation leads to this:
|
Further findings lead me to this: No matter if you use nouveau or bbswitch the PCI device (the GPU) will disappear after suspending. And is present until you completely shut off the machine (POWEROFF, reboot won't work) |
So it's an ACPI thing? |
Is there any issue remaining with the current Git version of optimus-manager ? It should have a better compatibility with Manjaro and MHWD. |
Finally I installed primus. I could never make optimus-manager work. I'll try it another time. |
I'm closing this issue since the original problem should be long gone by now. Feel free to open a new one if you are still having problems. |
Hello, I'm new and I trying to setup optimus-manager. I don't know if I need to install a nvidia driver too.
What can I do?
I followed this repo's tutorial.
I'm using Manjaro Linux 18 with GNOME 3.30.2.
My notebook is HP OMEN 15-ax250wn.
My Graphic cards are Intel® HD Graphics 630 (Kaby Lake GT2) and GForce GTX 1050Ti.
The service is active.
What i did
After login:
The text was updated successfully, but these errors were encountered: