Hello, I’m struggling with the same kinf od problem as onturenio. I’m not new to linux, but i’m new to Optimus (and the BTRFS/Snapper stuff in OpenSuse… this feature is awesome!).
In case anyone reads this thread and needs some help, I’ll summarize what I’ve done until now, because I needed a bit of time to get all this information together. I think that I’ve followed more or less the same steps and discovered the same things as onturenio.
[ul]
[li]First, let’s create a checkpoint if you’re using btrfs (everything here is to be done as root): snapper create -d “Checkpoint before messing with X” - this way you can always comme back to here if needed by running snapper list and then snapper rollback <number of checkpoint taken from the list> [/li][li]I have installed the nvidia drivers using the bumblebee repository (but not the bubmblebee program itself, only the drivers), as instructed here : https://lists.opensuse.org/opensuse-factory/2016-02/msg00482.html[/li][LIST]
[li]Something that is not well explained in the link is how to enable this repository. When you follow the link from the post above, you end up on a list of many repositories corresponding to various driver versions. The “latest” repository seems to expose dynamically the latest driver version so I took that one. When I click on the link, I get to a new page for the “latest” repository. On the top of this page are various tabs, including a “Repositories” tab. When I clicked that, I found a list of OpenSuseVersions, each of them with a “Go to download repository” link. This link is the repository URL you’re looking for. It can be fed to the YaST configuration utility to enable the repo. For me (OpenSuse Tumblewwed + latest drivers), it was : https://download.opensuse.org/repositories/home:/Bumblebee-Project:/nVidia:/latest/openSUSE_Tumbleweed/ [/li][li]Then run zypper install x11-video-nvidia to install the drivers [/li][/ul]
[li]Then I installed the suse-prime-alt repo for Tumbleweed into YaST with the URL linked on the author’s post I linked above: http://download.opensuse.org/repositories/home:/bosim:/suse-prime/openSUSE_Tumbleweed/ [/li][li]Then I ran zypper install suse-prime-alt [/li][li]At this point, it’s not yet possible to run prime-select nvidia, because the nouveau driver is currently loaded in the kernel and messes with nvidia. [/li][li]So let’s reboot the machine in command-line mode.[/li][ul]
[li]When grub is presented, select your OpenSuse entry and press e (the letter e, not the Enter key). This lets you edit the boot options (this is only temporary, the changes you make now will be discarded when you reboot). Look for the line which begins with “Linux” and add a stray 3 at the end. [/li][li]This one-time kernel option will start your system in runlevel 3 (command-line) instead of 5 (graphical user interface). [/li][li]Since you have a command line and your (possibly broken) graphical interface is not yet started, you can login (still as root) and run prime-select nvidia. the only line you should see is “running ldconfig” or so. This change is permanent, you can run prime-select intel later to get back to the intel chip. [/li][li]Then you can try to (re)start the graphical user interface by running service display-manager restart [/li][/ul]
[/LIST]
Now here’s my problem: obviously, this does not work (yet). I’ve solved a few problems already before coming up with the above steps, but something is still amiss. using the intel chip (prime-select intel) works apparently well (at least I get a fluid, working desktop), but nvidia does not. My screen does not display anything new when I try to start the display manager with it (it just shows the virtual console from runlevel 3 which i was previously using, but frozen). Interestingly, I can still go back to my console (Ctrl+Alt+F1) and restart it on intel (prime-select intel && service display-manager restart).
When I had a look at my systemd logs, it turned out that this failed attempt to start display-manager left no trace whatsoever there (no entry from the relevant date/time interval). Nothing either in dmesg. However, a file gets generated in /var/log/XOrg.log. The very weird thing is that there seems to be absolutely no problem according to this log: not even a warning! What do you think is going wrong then ? Here’s the xorg log in question:
[ 3541.062] (--) Log file renamed from "/var/log/Xorg.pid-8552.log" to "/var/log/Xorg.0.log"
[ 3541.062]
X.Org X Server 1.19.6
Release Date: 2017-12-20
[ 3541.062] X Protocol Version 11, Revision 0
(...)
[ 3541.062] (==) ServerLayout "layout"
[ 3541.062] (**) |-->Screen "nvidia" (0)
[ 3541.062] (**) | |-->Monitor "<default monitor>"
[ 3541.063] (**) | |-->Device "nvidia"
[ 3541.063] (==) No monitor specified for screen "nvidia".
Using a default monitor configuration.
[ 3541.063] (==) Automatically adding devices
[ 3541.063] (==) Automatically enabling devices
[ 3541.063] (==) Automatically adding GPU devices
[ 3541.063] (==) Max clients allowed: 256, resource mask: 0x1fffff
(...)
[ 3541.063] (II) systemd-logind: logind integration requires -keeptty and -keeptty was not provided, disabling logind integration
[ 3541.064] (II) xfree86: Adding drm device (/dev/dri/card1)
[ 3541.064] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 3541.065] (--) PCI:*(0:0:2:0) 8086:591b:1462:11d5 rev 4, Mem @ 0xdd000000/16777216, 0xb0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
[ 3541.065] (--) PCI: (0:1:0:0) 10de:1c20:1462:11d5 rev 161, Mem @ 0xde000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3541.065] (II) LoadModule: "glx"
[ 3541.066] (II) Loading /usr/lib64/nvidia/xorg/modules/updates/extensions/libglx.so
[ 3541.068] (II) Module glx: vendor="NVIDIA Corporation"
[ 3541.068] compiled for 4.0.2, module version = 1.0.0
[ 3541.068] Module class: X.Org Server Extension
[ 3541.068] (II) NVIDIA GLX Module 387.34 Tue Nov 21 02:04:31 PST 2017
[ 3541.069] (II) LoadModule: "nvidia"
[ 3541.069] (II) Loading /usr/lib64/nvidia/xorg/modules/updates/drivers/nvidia_drv.so
[ 3541.069] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 3541.069] compiled for 4.0.2, module version = 1.0.0
[ 3541.069] Module class: X.Org Video Driver
[ 3541.069] (II) NVIDIA dlloader X Driver 387.34 Tue Nov 21 01:38:22 PST 2017
[ 3541.069] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
(...)
[ 3541.084] (II) NVIDIA(0): Creating default Display subsection in Screen section
"nvidia" for depth/fbbpp 24/32
[ 3541.084] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
(...)
[ 3541.652] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 3541.652] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 3541.652] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 3541.652] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 3541.652] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 3541.652] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 3541.652] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 3541.652] (II) NVIDIA(0): Config Options in the README.
[ 3541.658] (II) NVIDIA(0): Setting mode "NULL"
(...)
[ 3541.712] (II) LoadModule: "libinput"
[ 3541.712] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so
(... lots of input-related stuff ...)
[ 3542.132] (II) config/udev: Adding input device (unnamed) (/dev/tty9)
[ 3542.132] (II) No input driver specified, ignoring this device.
[ 3542.132] (II) This device may have been added with another device file.
[ 3559.786] (II) event4 - (II) Power Button: (II) device removed
(...)
[ 3570.999] (II) UnloadModule: "libinput"
[ 3571.005] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 3571.007] (II) Server terminated successfully (0). Closing log file.
