2015-12-09 11:16 GMT+01:00 Timo Diedering :

... I'm a bit afraid of installing the proprietary drivers, as Tumbleweed often provides kernels which are newer than those supported by the drivers. ...

The Bumblebee nvidia drivers for Tumbleweed (using DKMS) have been always up to date with the Tumbleweed kernel, don't be afraid. They just still don't support KMS, if the startup flickering doesn't matter. In most cases you must reinstall them in console mode to make them work after Tumbleweed kernel updates, that's a second disadvantage of the native drivers repo. There's no trigger for automatically reintegrate them in this case. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2015-12-09 13:25 GMT+01:00 Knurpht - Gertjan Lettink :

Bumblebee is no good here. The machine's intergrated card is switched off, so this should be treated as an NVIDIA-only situation.

If the reporter wrote "integrated graphics disabled", isn't this desired in this case? I use the Bumblebee nVidia drivers on ZBook 15 already a year, also with an integrated Intel graphics and nVidia card and I don't have general trouble provided the proper BIOS settings. Integrated: Intel HD Graphics (disabled) Discrete: nVidia GK208GLM [Quadro K610M]

DKMS is nice, but it doesn't patch the NVIDIA driver when it fails to compile against a new kernel in TW.

I'm using http://download.opensuse.org/repositories/home:/Bumblebee-Project:/nVidia:/l.... Isn't the Bumblebee nVidia repository already some kind of "guarantee" by the maintainer for compiling against the TW kernel not to fail? In worst case it fails to install, which I haven't noticed to this time. I guess the maintainers of this repository would not launch a new version if it won't be installable, or who checks whether there is a basic problem. They just can't guarantee there is no implementation problem with the driver in common. Of course, there should be taken care of X Server ABI versions, which use to be on the cutting edge between the Tumbleweed kernel and nVidia native drivers. You can also choose a fixed driver version, see http://download.opensuse.org/repositories/home:/Bumblebee-Project:/nVidia:/, but this is probably the worse choice due to the incrementing X Server ABIs in Tumbleweed. Maybe we should somehow take and show a video shot of the flickering and "stripes" initially mentioned. According to the initial description I saw this effect also for "radeon". There's a big question mark left whether this is a "nouveau" problem or whether to focus also to other layers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2015-12-09 14:19 GMT+01:00 Andrei Borzenkov :

On Wed, Dec 9, 2015 at 4:09 PM, René Krell wrote:

...

I'm using http://download.opensuse.org/repositories/home:/Bumblebee-Project:/nVidia:/l.... Isn't the Bumblebee nVidia repository already some kind of "guarantee" by the maintainer for compiling against the TW kernel not to fail?

Of course not.

In fact, you're right for the case of DKMS.

...

In worst case it fails to install, which I haven't noticed to this time. I guess the maintainers of this repository would not launch a new version if it won't be installable, or who checks whether there is a basic problem.

it is not a problem of new version, but the problem of old version no more building against new kernel.

From my experience the last year: I'm not happy not to use the nouveau driver, but they are definitely broken for my hardware beginning from kernel 3.19 and there is a open bug report on both sides, OpenSUSE and freedesktop.org. Bumblebee is just a faster and cleaner way to gain

But isn't this is a general risk if one uses drivers outside the kernel sources, not just from Bumblebee, but also when pulling them from the vendor? the goal regarding nVidia. BTW: Reinstalling them is necessary just due to the changing modules directories after kernel updates of versions within a.b.c-revision. There's probably no better choice if the "nouveau" driver or depending open source acceleration layers (GLX. OpenGL, EGL, Mesa, whatever the native driver doesn't link to) stopped working reliably. At least the initial reporter has the chance to check, whether this is rather a high-level problem in the graphics stack, like Plasma, right? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

2015-12-09 15:23 GMT+01:00 Timo Diedering :

I made a video of the problem, so you can check whether it's the same you are experiencing. You can find it at the following link: https://timod.stackstorage.com/index.php/s/MB1SFxRjLnOagmZ

This looks (unfortunately or not) totally different. For "radeon" I get thicker lines, black and white, more like thin rectangles, and the screen is heavily flickering with a lower frequency. I'll sent it later, as soon as I'll have access to that machine and the problem appears. It is also not easy to reproduce, mostly after a while of using (just running Firefox or Chromium at the Plasma desktop). Mostly when waking up from sleep mode, but sometimes also when scrolling in Firefox, for example. Maybe try to file a bug report at https://bugs.freedesktop.org/ directly for the nouveau driver. Otherwise you'll probably just get workarounds :-) If you intend to check the nvidia native drivers, version 352.63 compiles and works fine with kernel 4.3 and the current X server on TW for my hardware, however you'll install it (I used the repository mentioned before and it just works for me). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Op woensdag 9 december 2015 11:16:30 schreef Timo Diedering:

On Wednesday 09 December 2015 11:03:43 Knurpht - Gertjan Lettink wrote:

...

Op woensdag 9 december 2015 09:57:33 schreef Timo Diedering:

...

Hi all,

I recently switched to a different notebook, with an Intel Core i7 (integrated graphics disabled) and an Nvidia NVS 3100M. The backlight control with Nouveau works perfectly, the buttons to increase/decrease brightness are recognised and even auto-brightness works flawlessly.

However, if my screen locks, it should turn off the screen (including the backlight) in like 5 minutes. What happens, though, is that the screen gets all kinds of stripes (horizontal and vertical) and sometimes even starts flickering. When I move my mouse, everything turns to normal again (apart from some flickering which disappears after some time).

The strange thing is that when I turn off the screen in KDE display settings (to work for example on an external display) the backlight does turn off, however the stripes/flickering continues. It seems to be an error in Nouveau or something, but I haven't found any info on the Internet yet and I don't have any clue how to debug this problem.

Does anyone have an idea where the root of this problem is located and (more important) how to fix it?

Not realy a fix, but I've seen reports in the forums that using the proprietary NVIDIA driver fixes this. You might also have a look at the suse-prime package.

There's also Bumblebee, to deal with NVIDIA Optimus configurations.

Hi,

As I said, it isn't an Nvidia Optimus configuration (the Intel graphics are disabled, by hardware). I'm a bit afraid of installing the proprietary drivers, as Tumbleweed often provides kernels which are newer than those supported by the drivers.

You could lock the kernel to a version that the NVIDIA driver does work on. AFAIK there currently are no issues with the 4.x kernels. Driver is reported to work properly on Leap, which has 4.1, not much older than TW.

Because of the single graphics configuration, I don't think opensuse-prime will help much. No, it won't.

-- Gertjan Lettink, a.k.a. Knurpht Official openSUSE Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org