-
Notifications
You must be signed in to change notification settings - Fork 69
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
Unable to run gnome-session #118
Comments
Try replacing |
Unfortunately didn't work, results in the same issue. |
@PhibreOptix it could also be that if you're running GNOME in both cards together they might have some dbus session conflict. I had a similar problem when trying to run MATE in the Nvidia while GNOME was running in the Intel card. |
I can second this issue... |
It's good practice to blacklist the nvidia module so it doesn't get loaded at boot: if you do so, the kernel command line parameter becomes useless I think.
…On 5 August 2019 03:40:54 BST, Pranav Sharma ***@***.***> wrote:
I am able to run gnome-session without issue on Fedora 30, but I make
sure to logout of the intel gnome session before running nvidia-xrun
--
You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#118 (comment)
|
Using this on my rebaged clevo laptop at the moment with the PM systemd service, as if using bbswitch the laptop freezes upon Xorg starting when the card is powered down (and the acpi_osi workarounds don't fix the issue).
Works fine if using openbox on the other tty, if I try to nvidia-xrun gnome-session however it doesn't work.
Xorg starts, the screen flashes to a a slightly less dark black, then after awhile I am dropped back to the prompt with messages stating that Xorg server exited successfully.
If I logout of the existing (intel) session first and then switch to another tty and nvidia-xrun gnome-session, it works correctly.
No error messages that I can identify for gnome-session (I'm not well experienced in this area though).
The text was updated successfully, but these errors were encountered: