On Thu, 2014-11-13 at 22:25 +0100, Tobias Klausmann wrote:
On 13.11.2014 21:25, Roger Luedecke wrote:
On Thu, 2014-11-13 at 17:10 -0300, Cristian Rodríguez wrote:
El 13/11/14 a las 16:54, Roger Luedecke escribió:
I recently became aware of eudev while attempting to fix a botched Bumblebee install. Many users were advised to install eudev to resolve certain Bumblebee problems. It looks like the goal is to increase hardware compatibility for older hardware and alternate init systems. I'm wondering though based on the Bumblebee related anecdotes if it is something we should look into.
udev has nothing to do with this hack called bumblebee, the problem it attempts to address "nvidia optimus support" has to be fixed first in the kernel and then in the X stack, everything else is in the wrong layer and will cause endless pain.
I understand the mess with Bumblebee. In my case, after having installed it udev somehow was broken and would fail to load or initialize. In the course of researching "bumblebee udev" I stumbled across eudev. I though that in general (not specifically to Bumblebee) that it could bear a looking at.
if you are not using the proprietary driver(s), especially the NVIDIA one (not sure about the AMDs), you can use DRI_PRIME={0,1} to control offloading to the secondary card. It works just fine for me and with recent kernels which got render-nodes (3.17 +) we can use DRI3 which resolves some performance problems as well. So there is a infrastructure in the kernel and X. The Binary driver(s) just don't make use of it. Actually, from what I understand NVIDIA has an official solution using XrandR that Ubuntu is using.
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org