On 2018-05-09 12:03, Andrei Borzenkov wrote:
07.05.2018 21:51, Daniel Bauer пишет:
Ok, my rant was hard, I know. But having my laptop with non-working nvidia is nonsense, too. Expensive nonsense. The change - what ever it was - that made switching from intel to nvidia impossible,
Well, as I recently tried the same on Ubuntu (with mixed success, nvidia-prime worked by vdpau did not, and that was the only reason I considered switch to nvidia) I tested it using Leap 15 live GNOME image (updated to current versions including kernel) and drivers from nVidia openSUSE repository. I have HD5500 and GF830M muxless notebook with all outputs connected to Intel.
Well, guess what - it works :) Attached are actual files I used (partially based on nvidia-prime Ubuntu package). Additionally you will definitely want to enable modesetting in nvidia_drm, otherwise tearing makes any work impossible.
Some comments
1. Intel driver did not work. Everything was started but no output ever appeared, I was left with empty screen with mouse cursor. modesetting (for iGPU) worked.
2. Leap 15 defaults to wayland (at least in GNOME version). As far as I can tell there is no way to use muxless Optimus with wayland - mechanism to pass images between two GPU is Xorg-specific, wayland would need something similar ... except wayland is protocol, so *every* implementation of wayland composer (GNOME, KDE, ...) must implement support separately. Which is certainly an improvement over Xorg case ...
So you will need to disable wayland (/etc/gdm/custom.conf in case of GDM).
3. nVidia kernel driver must be loaded before Xorg starts. Otherwise apparently user space components attempt to load it, but somehow it results in kernel oops.
4. I have no idea whether each individual parameter in xorg.conf snippet is required; this is what Ubuntu generates and it actually worked so I simply used it.
Bonus point is that VDPAU actually worked in Leap while it did not in Ubuntu.
So you end with a machine that can not switch intel-nvidia on the fly, the instant you remove the power plug and start running on battery or vice versa, which is the point of having dual hardware. Thus this is hardware to be avoided, IMO. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)